18:04 separation of concerns, a really good explanation, I don't think I've seen this speaker before, but he REALLY does know his stuff, great video 100%
He'd better know his stuff, he is one of the architects of Compose. They should have done the same with the Data Binding library, then I wouldn't had to suffer from seeing people creating a mess when trying to use it
@@AndoNoSekai Agree, data binding was never documented very well back in the beginning, it's still pretty poor in terms of official guidelines and recommendations. I've seen some real hideous use of it in my time.
Shinigami Yagami just to drive the point home, this IS an answer to poor data binding documentation because it is an easier paradigm to understand that achieves the result with a lot less work and boilerplate
as someone who just started out with Kotlin and Android developement with jetpack Compose (coming from Java/Spring) I was really overhelmed by this approach very alien to me. After crwaling through many examples, I really liked this step back to look at the big picture. Great explaination here
We’re so happy to hear you enjoyed the video! If you’re interested in additional resources; check out the Jetpack Compose walkthrough and Intro to Kotlin here: developer.android.com/courses/android-basics-compose/course developer.android.com/courses/android-basics-kotlin/course
very interesting.. woaw... the cohesion coupling clarification was also interesting. the fact that the same language allow to remove the implicit coupling ( hard to debug .... problems down the line for the complex UI) was great. to make it short . Thank you.
I'm so greatful that I found out about the Compose. I come from React and I played a little bit with Flutter. Now I have to do Android Kotlin project for university course and this is heaven for me. All concepts are very familiar without even reading the docs. Classic Android UI with XML is way too heavy and unnecessarly complicated in my opinion. Building UI should be simple like Compose ;)
Is there a way to factorise the style of the « Composable » graphical elements out of the business logic (e.g. like CSS for HTML)? If not, one ends up with a mess like « Flutter » in which layout, style and business logic are all mixed together in a giant soup.
AliReza Beytari and SwiftUI and React Native. We’re seeing a consolidation around very reasonable to follow paradigma for asynchronous user interfaces that need to respond to many state changes. My bet is this paradigm would not have evolved natural in web land without mobile as quickly but I also expect to see this as the cross platform solution (not necessarily compose but why not) in a few years. React Native is already paving the way here
@@someonlinevideos Outside of XML based languages, similar syntax has been around on the desktop since 2009 with JavaFX Script and Qt QML. See en.wikipedia.org/wiki/JavaFX_Script and en.wikipedia.org/wiki/QML
@@daschewie Thanks for sharing. Will have a look. Why do you believe these technologies are both A) were forgone in favor of declarative UI styles for both main mobile platforms and B) seeing a resurgence in both as well as in the React paradigms as well?
@@daschewie I was working with JavaFX for a reasonable time and this is the first time I hear about JavaFX Script, it looked great! but I'm wondering what happened to that project and how JavaFX UIs becomes XML centric?
@@alifellahi oracle bought sun microsystems and acquired Java. They preferred switching to xml to sell tools. This is just one of the many bad decisions.
is there any bug in android studio canary 4.2? cause whenever i make changes in jetpack compose app i need to uninstall the app and then have to install it again in order to see changes. I'm not able to see changes after running app or instant run feature.
Thanks to this plus Kotlin I’m coming back to learn Android programming. I hate Java and your older methods of ui development. This finally looks to be worth my time. Thanks!
Feels a lot like React, the preview in AS is very slow still and there doesn't seem to be a live update like you have with React Native or Flutter but its early days I guess.
Thank you for that great video! I'm so excited for Jetpack Compose. However, I'm confused about the 22:45 example, fetching the ViewModel inside a compose function. How would that work with previews? I guess you could have a "base" compose a function that fetches ViewModel & state or observer/s. Then call the ChatScreen() with either state or flow/observable to have preview functionality with ChatScreen function. Or is there a way to overwrite/declare a mock ViewModel scope for previews?
can't we choose which composables are recomposed? why recompose the circle image anyway. no need to use remember there. There should be an annotation like @ComposeOnce
I see Jetpack Compose as the next frontier of UI design it really eliminates the concepts of frontend and backend for client applications as it blends all in a Great way and making design parterns like MVVM almost a natural thing
There's a mistake in the code shown at 3:26 by looking at the example shown to the right of the code, I believe the second column declaration must've been a row declaration instead.
Nice! No need for Fragments, Navigation Component, RecyclerView, ViewPager and all that other boilerplate! Finally I feel free to create engaging UIs! A few things are missing, but we are almost there
No need for Navigation component? Who's going to track the navigation state across process death? Of course, you can use my library too, but that's because they're on the same level of abstraction.
Android Development is like migrate your code in every 2 years to something different. Good side is you will never get bored they literally add new things too soon but down side it lot of work to do at same time to maintain code...
finally, I found the guy who explained exactly the purpose of remember(), thanks Leland
18:04 separation of concerns, a really good explanation, I don't think I've seen this speaker before, but he REALLY does know his stuff, great video 100%
He'd better know his stuff, he is one of the architects of Compose. They should have done the same with the Data Binding library, then I wouldn't had to suffer from seeing people creating a mess when trying to use it
@@AndoNoSekai Agree, data binding was never documented very well back in the beginning, it's still pretty poor in terms of official guidelines and recommendations. I've seen some real hideous use of it in my time.
Shinigami Yagami just to drive the point home, this IS an answer to poor data binding documentation because it is an easier paradigm to understand that achieves the result with a lot less work and boilerplate
Hey guys sorry 🙏
I didn't know Jake Gyllenhaal was an Android developer
First time I saw him I thought the same thing
I came to the comments to make sure someone mentioned it. 😂
lmao
😂😂
Lmao
This is hands down the best video I've seen so far on composable. Seriously, great work.
as someone who just started out with Kotlin and Android developement with jetpack Compose (coming from Java/Spring) I was really overhelmed by this approach very alien to me. After crwaling through many examples, I really liked this step back to look at the big picture.
Great explaination here
We’re so happy to hear you enjoyed the video! If you’re interested in additional resources; check out the Jetpack Compose walkthrough and Intro to Kotlin here:
developer.android.com/courses/android-basics-compose/course
developer.android.com/courses/android-basics-kotlin/course
5:30 Showing off that kotlin 1.4 supports commas at the end
just like dart, for formatting.
Damn, they are going to make us re-work everything and this just feels awesome to see the concepts getting buildup from the scratch.
One of the best Android video I have seen so far ....🎉
so detailed, simple and elegant. God bless you
very interesting.. woaw... the cohesion coupling clarification was also interesting. the fact that the same language allow to remove the implicit coupling ( hard to debug .... problems down the line for the complex UI) was great. to make it short . Thank you.
Holy cow this is so exciting can't wait to dig in. Awesome presentation. Loved the explanation of separation of concerns.
I'm so greatful that I found out about the Compose. I come from React and I played a little bit with Flutter. Now I have to do Android Kotlin project for university course and this is heaven for me. All concepts are very familiar without even reading the docs. Classic Android UI with XML is way too heavy and unnecessarly complicated in my opinion. Building UI should be simple like Compose ;)
actually you can use compose in xml by using , and use xml in Compose function by using AndroidView()
Oh my god .. Super presentation by Leland, Awesome man!
Well done. Video was super clear - excited for Compose :)
Is there a way to factorise the style of the « Composable » graphical elements out of the business logic (e.g. like CSS for HTML)?
If not, one ends up with a mess like « Flutter » in which layout, style and business logic are all mixed together in a giant soup.
The code suspiciously looks like Flutter. I love it! ❤
AliReza Beytari and SwiftUI and React Native. We’re seeing a consolidation around very reasonable to follow paradigma for asynchronous user interfaces that need to respond to many state changes. My bet is this paradigm would not have evolved natural in web land without mobile as quickly but I also expect to see this as the cross platform solution (not necessarily compose but why not) in a few years. React Native is already paving the way here
@@someonlinevideos Outside of XML based languages, similar syntax has been around on the desktop since 2009 with JavaFX Script and Qt QML. See en.wikipedia.org/wiki/JavaFX_Script and en.wikipedia.org/wiki/QML
@@daschewie Thanks for sharing. Will have a look. Why do you believe these technologies are both A) were forgone in favor of declarative UI styles for both main mobile platforms and B) seeing a resurgence in both as well as in the React paradigms as well?
@@daschewie I was working with JavaFX for a reasonable time and this is the first time I hear about JavaFX Script, it looked great! but I'm wondering what happened to that project and how JavaFX UIs becomes XML centric?
@@alifellahi oracle bought sun microsystems and acquired Java. They preferred switching to xml to sell tools. This is just one of the many bad decisions.
is there any bug in android studio canary 4.2? cause whenever i make changes in jetpack compose app i need to uninstall the app and then have to install it again in order to see changes. I'm not able to see changes after running app or instant run feature.
Yes!!!! Alpha is finally here 💥🎉
Hey there! How to become a gde? What skills do i need if i wanna be same in android?
@@stvayush descarta
@@rosenidiasivanaszko3315 what's descarta?
Thanks to this plus Kotlin I’m coming back to learn Android programming. I hate Java and your older methods of ui development. This finally looks to be worth my time. Thanks!
Finally!!!! I’m so excited! 🥳
So cool, very excited!
I see the potential of using Compose to develop UIs for other platforms that are supported by Kotlin.
what will be with animations: motion layout and transitions? will it support them?
8:30 why would ChatText be recomposed if text doesn't change? Doesn't Compose skip its recomposition whenever the input doesn't change?
Bloody marvellous, thanks.
Awesome feature, sooo excited
Please is there a web page to see all possible composables one can use?
This is just amazing!
I am so excited about Compose UI.🤩
Switching between Kotlin and Flutter just got easier.
This would require a shift in UI design thinking process for Android Developers.
If I didn't need the iOS version of my apps, I would probably switch completely from Flutter to Kotlin.
yay, learning React is really useful now :)
Feels a lot like React, the preview in AS is very slow still and there doesn't seem to be a live update like you have with React Native or Flutter but its early days I guess.
At this point of time I can not run any of example apps in android studio. Does anyone have similar issues?
Great Video and as always like your videos, very informative and gives a good understanding of solutioning real world problems.
We're glad you enjoyed the video, Praveen! Don't forget to check out our Jetpack Compose playlist for more videos like this 😊 → goo.gle/3DCKQeH
Great explaination !!👍
That is revolutionary
do we have pub.dev like component search for Jetpack Compose components?
Thank you for that great video! I'm so excited for Jetpack Compose.
However, I'm confused about the 22:45 example, fetching the ViewModel inside a compose function.
How would that work with previews? I guess you could have a "base" compose a function that fetches ViewModel & state or observer/s.
Then call the ChatScreen() with either state or flow/observable to have preview functionality with ChatScreen function.
Or is there a way to overwrite/declare a mock ViewModel scope for previews?
I'm highly interested in this too. Did you find an answer to your question already?
this helped me; thank you 😁
great video! thanks
The Compose slack link leads to kotlinlang group?
Exelente capacitacion gracias
what am i missing to use CoilImage?
So after all the effort to prevent multi level layout like linear layout.. we back using them?
I love this
I created a declarative framework for android back to 2014-01-23T05:42:00Z, but now you created it too.
Do you mean Anvil?
@@Vouskopes No, Pertusin. You can check it on GitHub.
Amazing explanation, very informative.
thanks!
Excited for the sample codes. :)
Was this video unlisted? How is your comment from 2 days ago 🤔
@@AndoNoSekai The video was released 2 years ago; in 2020.
Really great video
Here experience working with Fluter is really-really useful.
Exactly
First jetpack compose video from Googler where I am able to understand the English and didn't needed the subtitles.
can't we choose which composables are recomposed? why recompose the circle image anyway. no need to use remember there. There should be an annotation like @ComposeOnce
From what I understand if done properly a recomposition shouldn't be an expensive operation.
11:25 Shouldn't each "ChatMessage" include only one child? Why does it have 2 "ChatBubble"?
I see Jetpack Compose as the next frontier of UI design it really eliminates the concepts of frontend and backend for client applications as it blends all in a Great way and making design parterns like MVVM almost a natural thing
So we are slowly moving toward Flutter.
1 step closer to Flutter Native (Android) :P
Is it the same with Flutter UI?
Very similar yes, the flutter team helped to create compose as I heard. The speaker here comes I think originaly from the react world.
nice
do we still need fragment ? when i see this concept its not relevant to have fragment
Good question. I would also think no.
Great presentation! But boy I hate this idea of declarative UI paradigm thing. Yuuucck! But really great explanation from Leland.
There's a mistake in the code shown at 3:26
by looking at the example shown to the right of the code, I believe the second column declaration must've been a row declaration instead.
Congrats to Android world as we have Compose in alpha now...
Nice! No need for Fragments, Navigation Component, RecyclerView, ViewPager and all that other boilerplate! Finally I feel free to create engaging UIs! A few things are missing, but we are almost there
No need for Navigation component? Who's going to track the navigation state across process death? Of course, you can use my library too, but that's because they're on the same level of abstraction.
@@Zhuinden Navigation can be handle by Compose and single Activity apps are much more feasible
@@AndoNoSekai As long as you are acutely aware of still handling savedInstanceState and restoration of navigation state across process death, sure
@@Zhuinden Sure, that can be handled too. There are a few things missing to fully enable this nicely but it can be achieved
@@AndoNoSekai from what I understand that's not in the scope of compose.
Is That Good News For Android Users
Ugh I might need to learn Kotlin now
Would be a great choice! 👍
How can I like a video a few hundred times?
Finally in Alpha....
This is almost Flutter for Kotlin
Android Development is like migrate your code in every 2 years to something different.
Good side is you will never get bored they literally add new things too soon but down side it lot of work to do at same time to maintain code...
sounds like you are new to coding in general
3:20 the function name ‘JetChat’. Why the 'J' a capital letter
I think it's a convention meant to differentiate between composable functions which act more like components with memory, and normal Kotlin functions.
But it's like making android app in eclipse.
Wow wow wow. Alpha. Still showing dev 17
I don't know if i'm looking a flutter/dart code or kotlin code kkkkkkkkkkkk
This is so cool! But feels more like Flutter 😅
So?
it similar to flutter
okay after 2 years i am watching this video again
Notes for myself:
- States in compose: 11:40
- Architecture: 16:00
Hi all team
Please we need an application for videos like youtube rival and emulate youtube soon please
Correct me if i'm wrong. Kotlin is swift copycat, this one is SwiftUI copycat?
And SwiftUI is Flutter copycat? It's declarative UI pattern
Kotlin came out before Swift
Is swiftUi copycat of react then? All frameworks get inspired by the enviroment
And they are all just inspired by React and C#
@@AndoNoSekai and those are copying algol because they have for loops
Bro , you are moving too fast.. You should have spent some more time on basics first...
Slow slow slow slow slow compose is too slow
Stop introducing new. Fix existing.
They can't without introducing breaking changes which is why they decided to start over.