Nav3 stable :kotlin_emoji: Any ideas for destinati...

# compose-destinations

[Suhaib Kazi]

Nav3 stable K
Any ideas for destinations 3.0? with Nav3

[Mini]

https://kotlinlang.slack.com/archives/C06CS4UCQ10/p1749567273849859?thread_ts=1749228530.073939&cid=C06CS4UCQ10

[David]

I've been so pleased with compose destinations, Rafael has done an amazing job. 🙏🦸 We use it for our app, reaching 500k+ installs and no issues caused by compose destinations, only the underlying nav library has given us some crashes every now and then.

We plan on migrating to Nav3 in the not too far distant future, the biggest benefit we see is the handling of scenes which will create a better experience for tablets & TV, but also the handling of the backstack making splashscreen/login flows easier.

I think there are quite some opportunities for the destinations way of annotating screens in Nav3 as well. I love the simplicity of destinations and it just being a lightweight shim that makes it easier to hook up everything. Not taking overly much responsibility or creating completely new concepts like some other libraries tries to do.

[Rafael Costa]

Thank you @David 🙂
Really appreciate the love.

[Rafael Costa]

I would like to explore nav3 compose destinations but no promises.

[Rafael Costa]

Hey if someone wants to take the opportunity and has the time, I assure them it will be worth it and they can count on me for ideas, feedback and who knows contributions 💡😜

[Mini]

Tbh I would be so happy if I could just inject navigators and resultlisteners into my viewmodels and otherwise keep using the library just as is 😅