Voyager

5607 readers

346 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Rules

Be nice.
lemmy.world instance policy

Sponsor development! 👇

💙

founded 1 year ago

MODERATORS

aeharding@lemmy.world

aeharding@midwest.social

aeharding@vger.social

534

Voyager released to Google Play! (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by aeharding@lemmy.world to c/voyagerapp@lemmy.world

119 comments fedilink hide all child comments

Hi there!

Voyager has been released to Google Play! You can check it out here:

https://play.google.com/store/apps/details?id=app.vger.voyager

Please try it out and let me know what you think below! Because it's brand new, let me know if you have any problems relative to the web app and I'll try to fix them ASAP. And if you have time, leave a review, that helps Voyager gain exposure.

Why use the native Android version? Well, there's a couple main benefits:

The back button works much better!
Your browser history shouldn't be inundated with Voyager entries.

Please note, it's currently a slightly outdated version of Voyager. Hopefully it should update soon!

As for Apple peeps, that's still in progress. If you're on TestFlight and have an Apple Watch, check out the brand new Apple Watch app (coming very shortly in an update). It's quite simple at the moment, but kind of neat and useful!

you are viewing a single comment's thread
view the rest of the comments

[–] boyi@lemmy.sdf.org 1 points 1 year ago (1 children)

Hi dev, got an update. As you said that's very strange as it is handled by browser, this make me think that it is a browser specific issue. I just found out that my default browser, Firefox, has a tendency to auto reload tab, - that explains it. I've installed addon to mitigate the issue - it seems to work.

As for implementing auto-cached as sync did, I can sense now that might be beyond your control as voyager relies on external browser to work.

[–] aeharding@lemmy.world 1 points 1 year ago

Oh, I'm glad you figured it out! I still think there may be a workaround for this, so keep an eye out for next release.