I would suggest going with Flutter (at least for now) as when compared to Compose, it is more mature, has decent community support. Compose is inspired by flutter in my personal opinion but is still WIP. Not to mention the restriction of using Android Studio for that doesn't seem to be going away as per me, anytime soon.
The use of Android Studio Canary shouldn’t be a big deal. Thats only for a short term specially that Compose is going stable in july and so does AS as well.
There are also alot of things that werent considered here. For one, going Flutter pretty much ties you up with Dart and Flutter and the integration with the native platform would be a big deal depending on the type of application you are targeting.
PS
Coming from someone who code Compose and Flutter for work, IMO, Compose is much much more natural to use, easier to understand, less boilerplate and much more customizable compared to what Flutter provides.
Thanks for your perspective @qrezet
. I'm definitely keeping my eye on Compose, and as I mentioned in the original question, I really enjoy the syntax a lot more than Flutter.
For someone that has zero knowledge in Android development, and wants to use either of these technologies for desktop development of mostly simple apps, the barrier just feels a lot higher with Compose right now. There are less resources, and what seems like more hurdles as Compose for Desktop appears to have a slightly different API to Compose for Android.
If there was a beginner book for Compose for Desktop, I'd be all over that in a heartbeat!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would suggest going with Flutter (at least for now) as when compared to Compose, it is more mature, has decent community support. Compose is inspired by flutter in my personal opinion but is still WIP. Not to mention the restriction of using Android Studio for that doesn't seem to be going away as per me, anytime soon.
How the UI would look like in Flutter: medium.com/flutter/announcing-flut...
Thanks @theimpulson , I think I have slowly been coming to the same conclusion.
That article looks really useful, thanks for sharing it.
I'll be keeping my eye on Compose, but I think I will continue with Flutter for now.
The use of Android Studio Canary shouldn’t be a big deal. Thats only for a short term specially that Compose is going stable in july and so does AS as well.
There are also alot of things that werent considered here. For one, going Flutter pretty much ties you up with Dart and Flutter and the integration with the native platform would be a big deal depending on the type of application you are targeting.
PS
Coming from someone who code Compose and Flutter for work, IMO, Compose is much much more natural to use, easier to understand, less boilerplate and much more customizable compared to what Flutter provides.
Thanks for your perspective @qrezet . I'm definitely keeping my eye on Compose, and as I mentioned in the original question, I really enjoy the syntax a lot more than Flutter.
For someone that has zero knowledge in Android development, and wants to use either of these technologies for desktop development of mostly simple apps, the barrier just feels a lot higher with Compose right now. There are less resources, and what seems like more hurdles as Compose for Desktop appears to have a slightly different API to Compose for Android.
If there was a beginner book for Compose for Desktop, I'd be all over that in a heartbeat!