So, my initial plan was to dive into the entire series yesterday. However, as it turned out, I managed to get through five of the videos (leaving two remaining). Unfortunately, time caught up with me, and I had to surrender to sleep. Thus, I made the decision to wrap up for the night and put off the next videos for tomorrow. Yet, I must admit, my resolve crumbled quite spectacularly. I found myself ensnared in the clutches of laziness, and the entirety of my day slipped away unproductively. Now, on a somewhat more positive note, I did manage to conquer the sixth video. However, I'm afraid the prospect of tackling the seventh video tonight is quite improbable, considering it's nearly a quarter to 1 am. With hope firmly in my corner, I aim to complete the series tomorrow-perhaps in the morning. I still can't help but express my sincere gratitude for these amazing videos. Your work is greatly appreciated, and please know that we hold you in high regard. Keep up the outstanding work, and until next time, take care!
It would be fantastic to see a NavigationDrawer implementation for M3. Your previous video on this topic is now outdated, as the M3 Scaffold no longer includes the 'drawerContent' parameter. Instead, we now have to use ModalNavigationDrawer. Amazing video as always Philipp, thanks! :)
Appreciate it big 🐕. Upgraded my older BottomNavBar with the material3 one. I totally hate how the bottom nav bar overlays your screen components. I guess the solution is to just give your bottom component on the screen a set Dp padding about equal to the height of your bottom nav bar? It's such a hacky inelegant solution but I don't know of a better one. Does the bottom nav bar change sizes (height) depending on screen size?
Hey Philipp, Thank you so much for all these content & that too very beautifully. I had one question, which I'm right now asking directly without looking it up elsewhere or even in any of your blogs so please don't mind the context. Here at 2:00 ; you mentioned that we should never use BottomAppBar & BottomNavBar together. Is that a hard & fast rule, just a general guideline or is there any particular reason of not using them together?
Funny how the recommendation is to only use this if you have 3-5 entries to navigate to (which I agree with), but Gmail has 2 entries in their navigation bar lol.
I would love ot see a follow up on this where you have different top bars items specific to the bottom bar item or hide the top bar for a certain bottom bar item. With
There isn't a whole lot to it. I have my NavigationBar in its own Composable (so basically what Philipp has, in a different Composable I call "BottomNavigationBar", because I send a few config options to it). One of the parameters in that Composable is an "onItemClick" function, which expects my BottomNavItem class and returns Unit. My "NavigationBarItem" onclick event does the following: set the selectedIndex, just like Philipp shows, and then calls the "onItemClick" I sent to my Composable. In the parent calling Composable that calls my "BottomNavigationBar" Composable, I have the following as the "onItemClick" I send: "navController.navigate(route = it.route)" (my BottomNavItem data class stores the "route" for each item, as Philipp does mention in the video but doesn't demo).
i come from flutter, i think that compose too many limitaion we can't see option to remote overlay color for indicator so we can remove ripple and more like in flutter, but i concerned about janky and laggy animation issue in flutter.. and i don't know that indicator has no animation like in material 3 specs
but this way of implementation doesn't work with navController as it refresh UI so the selectedItem is by default 0. It's just changing the index but doesn't work with navigation so what is the point put tutorial like that, Navigation actually without navigation
I watch every single video you upload. Thanks for such detailed content about Android. Keep uploading. Happy coding.
So, my initial plan was to dive into the entire series yesterday. However, as it turned out, I managed to get through five of the videos (leaving two remaining). Unfortunately, time caught up with me, and I had to surrender to sleep. Thus, I made the decision to wrap up for the night and put off the next videos for tomorrow.
Yet, I must admit, my resolve crumbled quite spectacularly. I found myself ensnared in the clutches of laziness, and the entirety of my day slipped away unproductively. Now, on a somewhat more positive note, I did manage to conquer the sixth video. However, I'm afraid the prospect of tackling the seventh video tonight is quite improbable, considering it's nearly a quarter to 1 am.
With hope firmly in my corner, I aim to complete the series tomorrow-perhaps in the morning. I still can't help but express my sincere gratitude for these amazing videos. Your work is greatly appreciated, and please know that we hold you in high regard. Keep up the outstanding work, and until next time, take care!
It would be fantastic to see a NavigationDrawer implementation for M3. Your previous video on this topic is now outdated, as the M3 Scaffold no longer includes the 'drawerContent' parameter. Instead, we now have to use ModalNavigationDrawer.
Amazing video as always Philipp, thanks! :)
Google is not following their own recommendations haha, Gmail app has only 2 actions in the bottom nav and also they don't show label at all 🤣
this happens all the time, even with Apple User Interface Guidelines
You are a great teacher
This video was awesome. Thanks a lot😊
Appreciate it big 🐕. Upgraded my older BottomNavBar with the material3 one.
I totally hate how the bottom nav bar overlays your screen components. I guess the solution is to just give your bottom component on the screen a set Dp padding about equal to the height of your bottom nav bar? It's such a hacky inelegant solution but I don't know of a better one. Does the bottom nav bar change sizes (height) depending on screen size?
Appreciate the valuable content 🙏🏼
Hey Philipp, Thank you so much for all these content & that too very beautifully.
I had one question, which I'm right now asking directly without looking it up elsewhere or even in any of your blogs so please don't mind the context.
Here at 2:00 ; you mentioned that we should never use BottomAppBar & BottomNavBar together.
Is that a hard & fast rule, just a general guideline or is there any particular reason of not using them together?
Do you have a video of how to use navcontroller with this?
This. This is exactly what we wanted
very very useful. Thanks🌱
nice videos...need a video of navigation drawer and bottom navigation bar combine with screen changes...plz...
Funny how the recommendation is to only use this if you have 3-5 entries to navigate to (which I agree with), but Gmail has 2 entries in their navigation bar lol.
I would love ot see a follow up on this where you have different top bars items specific to the bottom bar item or hide the top bar for a certain bottom bar item. With
Thanks mate, It is helpful.
Thank you bro
plz post a video on nav controller in bottom bar
Can you make a video about desktop navigation bar in compose desktop with material 3?
Informative video
Can you creat video talk about difference between flutter and kotlin and who the best ?
flutter to many issue the big issue is jank,laggy animation even jank issue come from 2015 till now
I am using this in my project this is SOOOOOO LAGGGYYY please tell me what to do? I tried it on different devices and in all of them were laggy...
Show us about playing hls video and v3.exo format plz
Can u make it to ModalBottomSheet asap.
As I'm unable to access it on m3 in Giraffe version
I hope to show us a practical example of how to implement a best practice navigation with bottom navigation bar
ua-cam.com/video/XyXPs6xOAfU/v-deo.html
There isn't a whole lot to it. I have my NavigationBar in its own Composable (so basically what Philipp has, in a different Composable I call "BottomNavigationBar", because I send a few config options to it). One of the parameters in that Composable is an "onItemClick" function, which expects my BottomNavItem class and returns Unit. My "NavigationBarItem" onclick event does the following: set the selectedIndex, just like Philipp shows, and then calls the "onItemClick" I sent to my Composable. In the parent calling Composable that calls my "BottomNavigationBar" Composable, I have the following as the "onItemClick" I send: "navController.navigate(route = it.route)" (my BottomNavItem data class stores the "route" for each item, as Philipp does mention in the video but doesn't demo).
@@clamum9648 did you share a gist or an example?
@@clamum9648 is the route stored in a format like "Screen.Home.route?"
hello sir, currently the controversy between KMM + compose Kmm vs flutter .Which is the best in the future?
i come from flutter, i think that compose too many limitaion we can't see option to remote overlay color for indicator so we can remove ripple and more like in flutter, but i concerned about janky and laggy animation issue in flutter.. and i don't know that indicator has no animation like in material 3 specs
TE AMO MALDITO YANKEE ,
but this way of implementation doesn't work with navController as it refresh UI so the selectedItem is by default 0. It's just changing the index but doesn't work with navigation so what is the point put tutorial like that, Navigation actually without navigation
Gandon
Why you don't use Kotlin ? I hear it it's better than java in android development
For sure he use kotlin
@@davidfeldman1746 But in most of his videos he uses Java
@@Mohsenjoke-x9hmost of his videos are in kotlin on this channel. This video was in kotlin.
OMG
Bruh