Can we have more of Jeremy in future videos? They're so natural in front of the camera, have top tier rizz, and speak very clearly by having an excellent cadence and rhythm. Also, it's so refreshing to see speaker diversity in the tech space!
The app I'm working on still uses Activities for each screen. I'm currently rewriting view by view in Compose to get it up to date and enabling main-detail screens and tablet layout on the way. Compose is awesome
that content {} is nice. Basically already built it out in an extension in our code base but nice. I feel fragments in a compose world are basically not needed but turning transition periods like right now for many, these help.
Android Honeycomb: here are fragments ❤ Every future Android version: here are fragments, which don't s*ck as much 😂 Keep up the good work, compose is awesome 😊
I tried the navigation-fragment-compose component without success. Since I am using the safeArgs plugin in my app, I am getting an error as soon as I add the Composable to my NavGraph, the plugin does not like the slash and the gradle task failes. Even though my Composable does not use any arguments.
When the official documentation on this will be released please? Composables in fragment navigation graphs don't work - specifically this "android:name="com.example.HomeScreenKt\$HomeScreen" I guess there must be a mistake somewhere in this guidance, it doesn't even compile
I think this fragment is redundand in Jetpack Compose we just can create separate components for every goal, we have Navigation Components, we can create on activity and app.kt and it's enough...
Is it possible to add an annotation for NagGraphBuilder that automatically adds the graph the the NavHost Composable. To remove the bolierplate of having to add all graph manually
Seems he explain everything excepted telling that we should add dependency: androidx.fragment:fragment-compose:1.8.3 else there is no way to find the content {} method :V
Android developers can't use simple development like in ios. Google as usual make a problem with backward compability. Complication ob the layer It's a main problem of android sdk
The backwards compatibility is a great tradeoff for complexity. On iOS you have a different problem when you use SwiftUI and want to support iOS15. Many features are only available in newer versions and you are constantly hacking and rebuilding existing stuff of newer iOS versions.
Subscribe for the latest updates → goo.gle/AndroidDevs
I hope Compose can also have a navigation graph preview
Can we have more of Jeremy in future videos?
They're so natural in front of the camera, have top tier rizz, and speak very clearly by having an excellent cadence and rhythm.
Also, it's so refreshing to see speaker diversity in the tech space!
Brilliant stuff, thanks for the video. Working with Fragments can be such a pain and this made them seem friendlier honestly
Jeremy Woods you are the best, the style and the clarity , love that
We can finally get rid of Fragments, nice presentation Jeremy
The app I'm working on still uses Activities for each screen.
I'm currently rewriting view by view in Compose to get it up to date and enabling main-detail screens and tablet layout on the way.
Compose is awesome
This guy is awesome. So clear and concise!
These new APIs are great. Kudos
I am currently migrating my companys app from old fragments and xml to compose. Thank you for the tips
that content {} is nice. Basically already built it out in an extension in our code base but nice. I feel fragments in a compose world are basically not needed but turning transition periods like right now for many, these help.
Waiting for Fragments in Navigation Compose! Currently using own custom implementation for old fragments with Compose navigation.
Clearly explained.
Thanks for sharing this article. Very useful :)
Android Honeycomb: here are fragments ❤
Every future Android version: here are fragments, which don't s*ck as much 😂
Keep up the good work, compose is awesome 😊
I tried the navigation-fragment-compose component without success. Since I am using the safeArgs plugin in my app, I am getting an error as soon as I add the Composable to my NavGraph, the plugin does not like the slash and the gradle task failes. Even though my Composable does not use any arguments.
When the official documentation on this will be released please?
Composables in fragment navigation graphs don't work - specifically this
"android:name="com.example.HomeScreenKt\$HomeScreen"
I guess there must be a mistake somewhere in this guidance, it doesn't even compile
@AndroidDevelopers any article about Composables in Navigation with fragments?? Also can you pass arguments to a composable destination??
Best Fragment API for composee
Thanks, from Vietnam😘
hi,In navigation to my composable. How do I pass arguments in the fragment -> Composable navigation?
best regar
let me sink that in, looks like the right approach to me. i was aware of the newer fragment APIs but not found much info so far.
Great success compost
Saved compose
What about the Bottom sheet screens, support for dialogs not just screens?
So, with fragments in compose, finally we can use dynamic feature modules using jetpackk compose?
I think this fragment is redundand in Jetpack Compose we just can create separate components for every goal, we have Navigation Components, we can create on activity and app.kt and it's enough...
Is it possible to add an annotation for NagGraphBuilder that automatically adds the graph the the NavHost Composable. To remove the bolierplate of having to add all graph manually
Does it really useful?
Don’t use flagment and single activity made me very happy
Nice
483rd...Thanks Jeremy
Seems he explain everything excepted telling that we should add dependency: androidx.fragment:fragment-compose:1.8.3 else there is no way to find the content {} method :V
good
does fragment transactions behave same in Compose
I want to know this too!
1:05
Android development is good but publishing app on playstore is very bad experience due to difficult or unexpected account issues.
right
Android development...ahh always complicating stuff. Ok quick how to turn my old android fragment based on views to a compose fragment.
Hello sir Good morning I'm from India
I want a full course app developer 😊
I hope you know that my fragments work perfect there is no need to redo them in Compose. Not a good investment of time. For new stuff yea Compose.
Bro I have a rap career too but somehow the bills have to be paid so I became a software developer as well
Android phone Android phone compose a
Android developers can't use simple development like in ios. Google as usual make a problem with backward compability. Complication ob the layer It's a main problem of android sdk
The backwards compatibility is a great tradeoff for complexity. On iOS you have a different problem when you use SwiftUI and want to support iOS15. Many features are only available in newer versions and you are constantly hacking and rebuilding existing stuff of newer iOS versions.
It's not as sweet as you think on iOS. Their way to navigate over the screens is sick! ;P
@@therebeliant3969 the way of navigate with compose much better? 😂
@@Ast991 Haven't said that! ;P