Happy v1!
Yes, there are still outstanding bugs. It’s not perfect, and we will continue to make things better! But Voyager has come a long way, and all of the core functionality is there to use and enjoy lemmy. 🙂
Happy version 1.0! 🎉
This release only has one major new feature: Unique time-based sort icons! You can now quickly glance to see what sort you’re currently on. Thanks @tilden!
Voyager is going to the App Store
I’m also excited to announce that the next major focus will be on releasing Voyager as an iOS app! This will fix various iOS bugs that we’ve encountered (white status bar, scroll “freezing” etc), and bring some nice functionality like haptics and tapping the status bar to scroll to top, and also improve onboarding for people that aren’t familiar with Progressive Webapps. It also opens the possibility for other neat features, like the option to open links in your browser instead of in-app. You can see most of the work done in #410, to be merged shortly!
If you’re curious how this is possible, check out Capacitor and AppFlow!
Note, an iOS app is subject to approval from Apple which may significantly delay its public release.
(Don’t worry! The PWA isn’t going anywhere! It has it’s own benefits like being self-hostable, quicker updates and being available on desktop computers.)
Once the iOS app is released, work will begin on releasing to the Play Store.
What’s Changed
- Add custom icons for time-based sorts by @tilden in https://github.com/aeharding/voyager/pull/524
- Forcing high resolution icon for iOS by @fer0n in https://github.com/aeharding/voyager/pull/526
- Fix block, message user not presenting login when logged out by @aeharding in https://github.com/aeharding/voyager/pull/528
New Contributors
- @tilden made their first contribution in https://github.com/aeharding/voyager/pull/524
Full Changelog: https://github.com/aeharding/voyager/compare/0.28.1...1.0.0
I just expected Voyager to go through the same process as Memmy did, beta-testing through TestFlight and then finally publishing to AppStore once it’s “ready”. Meanwhile, on Android you don’t even need to publish on Play Store. A lot of FOSS apps choose not to simply because it takes so much longer when an apk file would do just fine
Oh you meant side-loading, I see. They’ll probably use Appflow’s live updates, which makes it pretty easy to keep apps updated. If you wanted an APK enough you could pull down their code once they push their capacitor-supported version and build it as an APK yourself
They could also publish to F-Droid and other third party app stores. F-Droid is great for FOSS apps