voyager
voyager copied to clipboard
iOS and MacOS Native support
Known issues with Compose
- ~~iOS Build fail when
androidMainwas resource files, apparently when building for iOS, the plugin is also using resources from other targets (in this case,androidMain).~~ (https://github.com/JetBrains/compose-jb/pull/1984) - BackHandler fail at build time when BackHandler was a default value.
- LazyColumn fails to start applications
TODO:
- [ ] Support iOS back handler (take a look at the Wear OS Swipe)
- [ ] Revisit AtomicInt32 or maybe replace with compose runtime AtomicInt.
- [ ] ThreadSafeMap
- [ ] Disable ios and mac on non darwin systems (Windows/Linux)
- [ ] Setup a CI for publishing to Maven Central on version release. Allowing setup 2 workflows, one special for macOS and iOS native publishing.
https://user-images.githubusercontent.com/29736164/160265768-16ecb936-d458-48ec-a828-de8f3369a424.mov
LazyColumn already works :)
I Will be working on the PR this weekend. Hopefully next week we can have a experimental artifact from Voyager running on Native / iOS
This looks very interesting, it would be really nice to test it in an alpha version. Voyager seems easier to get started compare to decompose.
I have this implemented in my fork of Voyager, I am planning to PR it when my other PRs are accepted https://github.com/Syer10/voyager
Closed in favor of: https://github.com/adrielcafe/voyager/pull/114