AndroidX Navigation3 library is stable! And Compos...
# feed
k
AndroidX Navigation3 library is stable! And Compose Multiplatform version is on a way πŸ™‚ https://github.com/terrakok/nav3-recipes I prepared a migrated official Nav3-recipes demo to the multiplatform application with a Web Demo of course πŸ”₯ cmp https://terrakok.github.io/nav3-recipes/
πŸ”₯ 20
p
Hello, Konstantin! When click to one of menu items in demo and then click back, it leaves the site. It will be nice to go to main menu when back action occurs. It is on mobile browser. On desktop browser back button is not enabled. P.S. Refreshing the page reset the state to main screen. For demo it is ok. Thanks! 2 P.S. But may be for demonstrating back button it will be good to make it usable
k
yes. Nav3 is based on NavigationEvent library under the hood. And I wait when the library supports Browser History. Then I'll be able to integrate it with a browser history
βœ… 1
P.S.: Esc button calls a back event
OK. I added a back button πŸ™‚
πŸ”₯ 1
p
Is the web demo wasm or JS? - It is impressive how smooth it runs on Chrome Android. KMP web has improved tremendously.
and this CMP is 1.10-beta2 version with a lot of improvements
πŸ†— 1
p
Oh interesting, didn't know about this one.
k
thanks! is back navigation gesture supported on iOS?
k
have you seen the attached github link? πŸ€”
k
oh shoot, I swear it saw android in demo πŸ™ˆ
πŸ˜† 1
that's dope, I'm going to my project to it sometime soon
k
I published a small library to bind Navigation3 to Browser History! https://github.com/terrakok/navigation3-browser It supports two different modes: Chronological and Hierarchycal. Take a look at the demo app and feel free to use in your projects ❀️ An example how to use in a real project (not merged yet): https://github.com/JetBrains/kotlinconf-app/pull/569/commits/532ea255c1721674854ce663f47a7c4153b6430a
πŸ‘πŸ» 1
πŸ‘πŸΎ 2
K 2
K 2
kodee loving 2
πŸ‘ 17
d
A bit of a late reaction, but after having gone through a bunch of tutorials etc... I'm just wondering why there wouldn't be a few Accompanist (https://github.com/google/accompanist) libraries instead or along with the recipes for those that just want an opinionated way to accomplish basic nav2 things with nav3 (at least while migrating...)? Accompaniast libraries, I think, were just that, to be a temporary place to gather reactions about opinionated ways of doing things and either promoting them into the main libraries, or just deprecating them... @Konstantin Tskhovrebov.