ok- so im in the final stage of migrating my app f...
# multiplatform
j
ok- so im in the final stage of migrating my app from Android standard to KMP. all my screens, viewmodels, etc are complete, but im still relying on my native compose navgraph implementation to navigate. Im reading about navigation3 and wondering if anyone has advice on path for migration, should I switch to navigation3 while im at it, or just use regular navigation? it seems nav3 is still in beta? im not really sure. my question is also from someone whos undereducated in nav3 so im thinking maybe i should stick to the old navigation patterns?
w
What platforms do you support? I publish on web and Nav3 has made it much easier to support forwards navigation in the browser. The Nav2 -> Nav3 migration is not particularly difficult. You're more limited by whether Nav3 has built in support for stuff that you're using, like deep links, which still are only a recipe.
z
You can migrate to KMP keeping your existing (as I understand, Nav2-based) setup. Those same APIs exist for multiplatform as well, and they're stable. You can also move to Nav3, either before or after that migration. Nav3 is stable on Android, alpha for multiplatform but we're working on stabilizing it in the CMP 1.11 timeframe.
j
interesting insights @Winson Chiu in my case its only for mobile apps, for now. I think sticking to nav2 should be ok for now. nav3 might be a better standalone work instead of trying to combine it in my migration. Thanks for the advice both of you 🙏
so, im having an awful time with my composable navstates having nullables within them, but only on ios. is this normal? im getting the runaround from the ai bots. it made me write mappers but its not working or going very well. im thinking maybe if i upgrade to nav3 those problems go away?
w
Unfortunately I don't have any iOS experience, but Nav3 does utilize KotlinX Serialization for its NavKeys, which might be easier? I remember the NavType stuff in Nav2 being a massive pain.
🤷 1