Just built it from source while waiting for Google to approve the app, and it's great. I had to use Firefox for the PWA because I need links to open in firefox when I click on them, but Firefox doesn't handle PWAs vey well. The native app fixes all these problems. Excited for it to be on the Google Play Store!
Also aeharding@lemmy.world will you upload the android app to F-droid? It would be nice to have it there rather than having to install it from the play store.
Thanks for all the work that you do! Voyager is a fantastic app.
Another thought, if it's feasible, maybe also post the apk releases on GitHub? So people have the option to download from there directly or use an app like obtanium to grab it from GitHub.
Just FYI it is possible to open links in Firefox despite Voyager being installed as a Chrome PWA. Click the link to open it within the app, then hit the 3 dots and "Open in Firefox" should be an option.
Not sure if this is different depending on the backing browser, but my experience with this is that it works great to open the link, but when you hit the back button to go back to Voyager, you get kicked out to your home page instead of back to the thread you were in.
This might not be caused by opening a page in the same browser as the PWA (could be due to issues with the back button that I think we're fixed in the latest build? Or was that about the native apps? Can't remember) but I've been assuming that's part of the issue 🤷♂️
I don't think so. You need to run npm build or something, then install ionic and capacitor, then run npx cap init, then go into the android folder and run ./gradlew build
That'll build it, but it won't make a signed release build. That will substantially weaken the security of the android app and it's sandbox, and expose all the data folders.
You'll want to use ./gradlew assembleRelease with keys, or make a signed release build in Android studio
Firefox for mobile is so broken compared to Chrome it's frustrating... sometimes I find myself having to switch to Chrome from it for stupid reasons like a single date picker vital to a part of a site is broken or a site runs monumentally slow for no reason, but on the chrome mobile app it just works. feels dirty having to use chrome every now and then >_>
Really? I haven't used chrome on a phone in... I'm not sure how long. Since pre-pandemic, anyway.
That said, I spend a lot of time on a laptop, so maybe I just don't use as many sites through the mobile browser. I DO sometimes use Edge or Brave on my laptop because sites don't work. It isn't so much the browser is broken as the sites, though.
As a ex-web developer: it is not Firefox that is broken, but those sites. They optimize for Chome and don't check firefox. I don't blame them, considering percentage of users, but it is not FF fault.
Google's apps are especially slower than in chrome