Jetpack Compose is Android’s modern toolkit for building native UI. It simplifies and accelerates UI development on Android. We walk you through basic concepts of declarative programming, what is included in the toolkit, and some examples to help you get ready to adopt it in your apps.
Resources:
Get started with Jetpack Compose →
Jetpack Compose learning pathway →
Jetpack Compose sample apps →
Speakers: Clara Bayarri, Anna-Chiara Bellini
Watch more:
Android and Play at Google I/O 2021 Playlist →
All Google I/O 2021 Technical Sessions →
All Google I/O 2021 Sessions →
Subscribe to Android Developers →
#GoogleIO #Android #Featured #JetpackCompose
product: Android – Jetpack Compose; event: Google I/O 2021; fullname: Clara Bayarri, Anna-Chiara Bellini; re_ty: Premiere;
Watch more new videos about Android | Synthesized by Mindovermetal English
this is gorgeous!
nice, its much easier when you know flutter, I really prefer this approach than xml views
React Native or flutter developer will love this 🙌🏻
Inspired by flutter 😄
Thank you Google Team
Who's learning Compose right now? ✋
Was skeptical on Compose until I tried it, no Dev can resist compose.
finally! future is coming!) compose + kotlin multiplatform mobile = will be best multiplatform solution ever!
How is composable compared to flutter's widget?
Effortless waiting for a Menu with options "Migrate Xml to Compose".. Press and wala.. all converted!!😁😁😁😁… Deja-Vu… like migrate to AndroidX
I hope Jetpack Compose dev team will bring more amazing features in near future. Android dev love Declarative UI as iOS dev love SwiftUI. Hope they will make us surprise .
wait ?? , just LazyColumn , one line of code to replace recyclerView 😭
Finally!!! this is great step forward!
reminds me of react, worth a try a guess
Thanks for sharing
Can this support RXJava?
👍👍❤❇
LOL, we are back to the 80's where user interfaces were developed in code. Modern? There is a reason for having something like xml, json or html define a UI. The UI can be created on the fly which is useful. Creating code on the fly is possible but much more difficult if the code needs to be compiled. Imo a step backward.
How many of you love XML over Compose ?
So it's Flutter running on Kotlin.
Nice to have but Dart is still nicer.
it's basically flutter widgets on android…
How does it make the xml and drag and drop method in the layout editor less good?
Is an all brand new way to write UI, and we need "unlearn" the view way of thinking.
This isn't so straightforward as seems to be, guys! You can't just jump on to it like "just a new feature that I can grab on 15 minutes".
There is a learning curve. So let's do it.
So does Jetpack Compose make MVVM obsolete already? Or can we count on Compose to go the way of JavaFX, which is/was also 'declarative'?
I find compose intriguing – how does it handle different screen size buckets and configuration changes? The xml system had structured folder hierarchy system for choosing the right resources based on runtime layout/dimens/etc, I'm yet to see anything with compose that addresses this? Until I see how this is handled its just not viable for me .. plus copy/pasting entire chunks of code just to preview a view – you have keep copy/pasting code each time you make a change to the composable function? The IDE needs to be as rich design system as it does for xml layouts – if that happens I'm sold on compose, until then it seems a bit rough around the edges.
Good bye XML
Row, Column and … Box? Why not call it Stack/VStack?
Why you make too many frameworks instead of concentrating on one framework? We have old way to create apps, flutter and now this.
great feature, looking forward to dive
When will version 1 come to life?, and should I use Compose in a real production app now?
does jetpack compose works with android TV ?
…wait! Is it Flutter? I can see "Column", "Text" widgets… My mind is spinning …..
can I write a background @Composable, that does not produce a view, but just some value? Ideally, one that could be observed like LiveData or Flow.
– it could be used for control flow (better than xml Navigation) by treating the composition as a monad, effects would be wrapped to run the "first" time, one could easily revert to older state, have access to all variables, as they are just defined previously…
– it could handle the only issue I have with coroutines, that you cannot re-run back from a point in past, like a Gui monad.
– only limit is, that sometimes the @Compose function would have to get 'suspended' and stop running, until that part of 'decision tree' is reached…
this is so cool. being on react + ts this is something i would love to take up
Maintaining radio button/ checkbox state explicitly across menus and settings was always a pain..no more😭
You'll notice that they never use dependency injection in any of their Compose samples. In fact, DI is practically never used in any of the source code for Android. That should tell you how useless DI is.
kotlíìn
Please add LazyColumn cell change animation like we have with diffUtils now
XML never again.
Looking forward to it 🙂
Any fixes regarding multiple sheets within ModalBottomSheetLayout yet?
How can we watch all video at same time
2:45 with concentration ,
Do we look aliens 👽 or you think we are Elon Musk 💰🚀