What happen if the user click back key, would he return to parent destination defined in navigation graph or previous destination. What if the app is killed and user clicks on notification and then back key or up button in action bar? Will he exist the app or the custom navigation as we defined?
Does explicit deep links works only from a notification ? Can we create a url and share it over to the user as SMS. Will it work ? If yes, how to create external links ?
It's amazing the simplicity of this new component compared to what we had to do before. But it's really a shame that passing arguments to Fragment destinations doesn't take into account architectures with multiple Activities.
i will show you how to implement deep linking *goes ahead to create custom link behind the curtain how are beginners supposed to follow you? i cant find any shortcut metadata in my manifest as well. if your video cant help with steps that can be followed then it has failed in its purpose. you're just putting content out there.
@@AndroidDevelopers I'd assume that's you, hello sir. Hope to see you work on future APIs/frameworks, or on Compose itself. You give off pure developer vibes, it just completes the experience. Keep up the great work.
Developers to use implicit deep linking don't forget to add element that points to an existing navigation graph to an activity
Damned! I spent 1 hour to figure it out why I had "The app is not installed" error and then I see your comment. Thanks a lot!
With Android jetpack android development becomes a lot of faster and easier. Superb!
What happen if the user click back key, would he return to parent destination defined in navigation graph or previous destination. What if the app is killed and user clicks on notification and then back key or up button in action bar? Will he exist the app or the custom navigation as we defined?
Does explicit deep links works only from a notification ? Can we create a url and share it over to the user as SMS. Will it work ? If yes, how to create external links ?
look at that! what an earth google decided to teach us android development after 12 years! good video btw
And 0 words that deep link will create another instance of app
It's amazing the simplicity of this new component compared to what we had to do before. But it's really a shame that passing arguments to Fragment destinations doesn't take into account architectures with multiple Activities.
AFAIK, the Android team encourages using a single Activity in your app. I guess this is a way to nudge people :)
This is really amazing feature.
All along i thought that deep linking is for webiste. Until i watch and learn from this awesome tutorial. Thanks!
Thank you for this video
We also need these MAD Skills in Flutter Apps
Amazing sir
timestamps are wrong, there is a part about explicit deep links
HOW TO MAKE A DEEP_LINK OPEN A FRAGMENT WITHOUT BACKSTACK ?
i will show you how to implement deep linking
*goes ahead to create custom link behind the curtain
how are beginners supposed to follow you? i cant find any shortcut metadata in my manifest as well. if your video cant help with steps that can be followed then it has failed in its purpose. you're just putting content out there.
CHET! CHET! CHET! CHET! CHET!!!!
The enthusiasm is contagious! We love it 🎉
Chet is an amazing presenter, and he really can dive deep into a topic for you 😀
@@AndroidDevelopers I'd assume that's you, hello sir. Hope to see you work on future APIs/frameworks, or on Compose itself. You give off pure developer vibes, it just completes the experience. Keep up the great work.
Autograph please