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

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

  • May 10, 2018 at 6:59 pm
    Permalink

    Why do all these new things look like iOS?

    Reply
  • May 10, 2018 at 7:00 pm
    Permalink

    Does it working with custom controller instead of fragment (for example conductor controllers)?

    Reply
  • May 10, 2018 at 7:35 pm
    Permalink

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

    Reply
  • May 10, 2018 at 8:23 pm
    Permalink

    That really good improvement

    Reply
  • May 10, 2018 at 9:36 pm
    Permalink

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

    Reply
  • May 11, 2018 at 3:39 am
    Permalink

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

    Reply
  • May 11, 2018 at 5:13 am
    Permalink

    Big addition but very late…

    Reply
  • May 11, 2018 at 9:36 am
    Permalink

    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?

    Reply
  • May 11, 2018 at 11:35 am
    Permalink

    Guys re-invented Cicerone library from terrakok

    Reply
  • May 11, 2018 at 11:50 am
    Permalink

    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?

    Reply
  • May 11, 2018 at 1:54 pm
    Permalink

    Are they doing all navigation work in android studio? please reply me

    Reply
  • May 11, 2018 at 3:18 pm
    Permalink

    8:06 what is the role of the Activity? Yup, it is not just "a screen" 😀

    Reply
  • May 12, 2018 at 1:20 am
    Permalink

    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.

    Reply
  • May 12, 2018 at 10:14 am
    Permalink

    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?

    Reply
  • May 12, 2018 at 11:28 pm
    Permalink

    How I do handle shared elements on transitions from FragmentA to FragmentB? :O

    Reply
  • May 14, 2018 at 4:37 am
    Permalink

    Why are all the demo code in Kotlin and not Java ?

    Reply
  • May 15, 2018 at 3:42 pm
    Permalink

    4:13 Wohooooo!!!!!! Finally!

    Reply
  • May 16, 2018 at 8:16 am
    Permalink

    What is Steve Merchant is doing there?

    Reply
  • May 17, 2018 at 12:14 pm
    Permalink

    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?

    Reply
  • May 19, 2018 at 8:40 pm
    Permalink

    All the pain I had to suffer over the last years now seam so unnecessary

    Reply
  • May 20, 2018 at 4:26 am
    Permalink

    Why call it NavHost instead of NavigationHost? just introduces unnecessary inconsistency

    Reply
  • May 22, 2018 at 10:43 am
    Permalink

    Patching, Patching and Patching, what is the next? what is the end?

    Reply
  • May 22, 2018 at 6:47 pm
    Permalink

    Added depdencies, still unable find this "navigation editor". Anyone had any luck with this ?

    Reply
  • May 23, 2018 at 5:55 pm
    Permalink

    Nice idea but what should we do with tablet navigation?

    Reply
  • June 5, 2018 at 9:38 am
    Permalink

    You can download and see example app https://dotaslash.com we created!

    Reply
  • June 6, 2018 at 11:06 am
    Permalink

    What about startActivityForResult() ?

    Reply
  • June 25, 2018 at 3:08 pm
    Permalink

    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 ?

    Reply
  • July 3, 2018 at 8:46 am
    Permalink

    Can we use Android Jetpack on an Android 7 targeted devices?

    Reply
  • July 22, 2018 at 12:04 am
    Permalink

    You can't use findViewById in a fragment… getview()?.findViewById is correct ?

    Reply
  • July 26, 2018 at 1:12 pm
    Permalink

    put speed to at least 2x
    I need more than that via JS hack
    x)

    Reply
  • October 11, 2018 at 1:31 pm
    Permalink

    How do i get this presentation?

    Reply
  • October 20, 2018 at 8:53 am
    Permalink

    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

    Reply
  • November 28, 2018 at 1:47 pm
    Permalink

    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 ?

    Reply
  • November 28, 2018 at 6:34 pm
    Permalink

    Is there a sample of this code somewhere?

    Reply
  • December 24, 2018 at 12:32 pm
    Permalink

    are we be using navigation component and viewpager together

    Reply
  • January 3, 2019 at 12:03 am
    Permalink

    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.

    Reply
  • February 4, 2019 at 6:30 pm
    Permalink

    Why you guys did not give the answer to any of the comment?

    Reply
  • February 6, 2019 at 1:51 pm
    Permalink

    Navigation component crashes.
    java.lang.IllegalArgumentException: navigation destination 
    😫😫😫😫

    Reply
  • February 12, 2019 at 3:17 pm
    Permalink

    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 !!

    Reply
  • February 14, 2019 at 7:54 pm
    Permalink

    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 !!

    Reply
  • March 5, 2019 at 3:35 pm
    Permalink

    How to prevent fragment recreate during pop behavior ? Like Second fragment to first fragment .

    Reply
  • March 18, 2019 at 9:00 pm
    Permalink

    What about Instant Apps? How is it supposed to work with them?

    Reply
  • April 10, 2019 at 11:24 pm
    Permalink

    it's just like iOS. Thanks for doing this.

    Reply
  • May 11, 2019 at 2:15 am
    Permalink

    is it just for Fragments?

    Reply
  • June 14, 2019 at 3:25 pm
    Permalink

    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.

    Reply
  • October 5, 2019 at 6:28 pm
    Permalink

    Awesome

    Reply

Leave a Reply

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