Android Jetpack: manage UI navigation with Navigation Controller (Google I/O ’18)

Android Jetpack: manage UI navigation with Navigation Controller (Google I/O ’18)


    I waited so much time for something like this. It's a big improvement for the Android developers life! Thank you!

    How do I add business logic to the navigation? You showed static navigation, what about dynamic?

    Now the iOS developers that work near me can't mock me anymore for not having a storyboard 😀

    How do I handle CollapsingToolbarLayout for specific Fragment if I have Toolbar that is placed in the Activity?
    Do I hide the Activity's Toolbar and then handle Fragment's Toolbar separately? How will this affect the up navigation?

    Will there be a
    implementation 'android.arch.navigation:navigation-activity:1.0.0-alpha01'
    that fixes the up and back button handling for activities without the need to switch to this Fragment style?

    Okay so this explained some parts. But what about master-detail flows on tablets? How do I tell it whether I'm on a phone or tablet ui and where to load the fragment to? How would I modify the ActionBar Menu? What about Activities deeper in the hirarchy where I want an Up-arrow even on the topmost fragment to go up to another activity? So many things that are currently not explained anywhere, so we'll need to wait for blog posts and stackoverflow questions to pop up to fill all the blanks. Just like every io unfortunately. Things will be usable around the P release.

    Can a fragment in the navigation graph have multiple pop-to fragments? Can a navigation graph looks like a net?
    For example in the case of 06:17, what if an app has multiple entries to the user_profile? Or I'll need to create multiple separate paths?

    With larger applications with many fragments – can you have multiple .xml files for the navigation graph or can you only have one very large graph for the entire project?

    Finally after 10 years they are starting to understand that Android Fragments and UI design are completely shitty… And then they take inspiration from Apple ? Really ? What is going wrong with you Google ?

    why they copy ios i dont understand and even if they copy they cam make it better but these are only good for fragment transactions Not activity result

    How to manage fragment state duting backstack. Like first contains recyclerview and user scroll to end then onitemclick navigate to second screen. now if user back to previous fragment there is not state managed. it is possible or not.if possible how to manage ?

    Hello from 2019, navigation editor not working properly, as always all new features not production-ready – data binding, navigation… Looks like experiment, but not as usable feature.

    The details are so satisfying and awesome !! 🙂

    Oh by the way, is it ok if I can also seek your advice in this open source android app I have posted below? Just need some feedback about it…

    http ://bit. ly/2tldxaG

    thanks a-hundred-times !!

    Nice! I will be happy to follow and learn from you. 😛

    Oh by the way, is it ok if I can also seek your advice in this open source android app I have posted below? Just need some feedback about it…

    Just need to search ' pub:Path Ahead ' in Google Play (P & A are case sensitive).

    thanks a-hundred !!

    Every back button or navigation item selection recreates the whole fragment. So what is the use of this if I can't keep the last state of the fragment state.

    There is no proper way to update the toolbar based on the navigation destination… Currently It's basically impossible to implement a destination with a SearchView in the toolbar…

    Hello, I tried this but I have an issue accessing a nested graph fragment inside another nested graph from the root navhost. (Like from Home to contacts nested graph, contacts being inside the account nested graph). Global action does not work from root only from the account nested graph. And if I extract contacts from the account nested graph it works BUT the "selected" icon in my bottom navigation view will be "home" and not "account" :'(

Leave a Reply

Your email address will not be published. Required fields are marked *