21–30 of 53 posts
If I'm to pick Flutter vs Jetbrains/Jetpack Compose - I'd pick Flutter because it supports desktop, mobile & web. And Flutter's philosophy of rendering directly using Skia on all platforms seems to be a sound strategy.
How is this better than Flutter? If the answer is Kotlin > Dart, then what if Google comes up with a Flutter version that supports multiple languages (Dark/Swift/Kotlin)? If I'm to pick Flutter vs Jetbrains/Jetpack Compose - I'd pick Flutter because it supports desktop, mobile & web. And Flutter's philosophy of rendering directly using Skia on all platforms seems to be a sound strategy.
I think flutter is more mature and has way better widgets.
However I like the general move towards "One UI Toolkit for all platforms" approach..
Off course we already have this but then never really worked on mobile: - QT - Java Swing - SWT - Flash
And I think, Web makes it easy to run a browser anywhere, but technically needing a whole browser engine to show a UI is just overcomplicated designs... I know web developers like it because they often dont know how UI toolkits are build outside of web... I think Flutter hits the nail on the head with the best of both worlds: Browser makers created flutter optimized for UI native applications, not for WEB in general.
How is this better than Flutter? If the answer is Kotlin > Dart, then what if Google comes up with a Flutter version that supports multiple languages (Dark/Swift/Kotlin)? If I'm to pick Flutter vs Jetbrains/Jetpack Compose - I'd pick Flutter because it supports desktop, mobile & web. And Flutter's philosophy of rendering directly using Skia on all platforms seems to be a sound strategy.
I wish there was a screenshot of a demo app. How do you market a UI toolkit without any screenshots of what I can do? I'm not going to build a demo project to see what the UI looks like.
There is if you scroll just a little bit down the page
I wish there was a screenshot of a demo app. How do you market a UI toolkit without any screenshots of what I can do? I'm not going to build a demo project to see what the UI looks like.
I guess, for Alpha stage they are not targeting wide audience but mostly people that are familiar with Compose (or wanted to try it).
In most cases you can just copy-paste your Android UI layer or make it cross-platform (like in this code-viewer example https://github.com/JetBrains/compose-jb/tree/master/examples...)
I wonder how easy/difficult would it be to use it from other JVM languages. If I can use it from Scala, it would be great.
How does this interact with the Accessibility settings on Mac OS?