#metabrainz

/

      • vardhan joined the channel
      • vardhan has quit
      • Kladky has quit
      • Kladky joined the channel
      • jbrr joined the channel
      • davic has quit
      • ijc has quit
      • ijc joined the channel
      • q3lont joined the channel
      • Maxr1998_ joined the channel
      • Maxr1998 has quit
      • kepstin has quit
      • kepstin joined the channel
      • vardhan joined the channel
      • jbrr has quit
      • HemangMishra[m] has quit
      • jasje[m] has quit
      • q3lont has quit
      • q3lont joined the channel
      • q3lont has quit
      • monkey[m] has quit
      • q3lont joined the channel
      • yvanzo[m] has quit
      • HemangMishra[m] joined the channel
      • HemangMishra[m]
        jasje: Would you consider upgrading the navigation in our app to Type Safe navigation or maybe Navigation 3 released last week, which offers more flexibility and control by exposing the back stack as a list? I am already changing some routes to accommodate for the new onboarding graph, so I thought this upgradation might give us more flexibility in navigation once it gets more complex.
      • jasje[m] joined the channel
      • jasje[m]
        Hemang Mishra: i do like the new api
      • Give it a whirl
      • Don’t change the whole apps nav to nav3
      • Just use it for onboarding
      • HemangMishra[m]
        <jasje[m]> "Just use it for onboarding" <- Sure, I'll try the new API with existing navigation. I'll have to once see that there should be no issues while navigating from any existing screen to any if the new onboarding screen.
      • SothoTalKer_ joined the channel
      • SothoTalKer has quit