1. The actual version of compose is just to have f...
# compose
c
1. The actual version of compose is just to have feedback from people playing with it, but it´s not expected to be enough to build a full app right? 2. Is someone trying to create a "real app" with compose and trying to have a polished view?. And in that case what are the thoughts about it?
t
I am currently working on an app which just uses compose for UI. Currently it is in closed alpha test. If you are interested i could add you to the testers.
My general thoughts are since dev09 compose feels much more polished. And it is also working stable for me. Just the AdapterList is not useable for a real app yet. So in my app currently i just use a VerticalScroller for now. (This limits the list size) Also the text input components don't really feel finished for now. But i did not looked into dev11 yet. So maybe some of this issues are fixed.
And maybe one more think. There are not many helper libs out for now. So you do have to develop your own e.g.: for image loading.
a
❤️ Apple BUT when SwiftUI/Combine Framework released it was crazy trying to get books, posts and Apps all published. With Compose the book and post are being written and Apps will be on the Store before Beta. We will be hitting the ground running when Alpha is released. We expect huge changes as we build and rely heavily on the community to help build @Vinay Gaba https://github.com/vinaygaba/Learn-Jetpack-Compose-By-Example is our goto documentation.
👍 2
🙏🏼 2
t
I will never use the legacy view system from android anymore (At least for new projects)
m
I am also creating an app currently in closed testing. Pretty much the same: text widgets and libraries.
Also I've been secretly hoping when my app is finished (or after a while), Compose will support iOS, and I can suddenly have an iOS version of my app. 🙂
a
@molikto Have you done SwiftUI /Combine Framework programming? It is very nice. I would be surprised if Compose can replicate what SwiftUI /Combine can do on native iOS ... it will be interesting to see what they come up with ???
m
I am under the impression Compose UI have very limited dependency on actual Android API, and also they are currently using Kotlin Multiplatform already, with some code for desktop. I haven't used SwiftUI, but tbh I like Compose more
a
All true but building the Apple UI Components is a huge undertaking ... I still have talks with the Flutter team about issues ... that is why we do SwiftUI/Combine ...
m
I think Compose has it's own widget? I'd rather have the UI look the same on two platform, all in material design
a
Yes, that is one way to do it. We like our iOS app to look like iOS (Apple HIG is impressive) and our Android Apps to be Material :-)