Is using Voyager giving Chrome an opportunity to harvest user data? I’ll take whatever you know about the Voyager dependence on chrome.
Voyager is built using capacitor and ionic framework, which is a web framework to build mobile apps, basically. It doesn’t “use elements from chrome”, it uses progressive web apps (PWAs), which you can set up with whatever browser you choose. They’re basically web apps that you install to your phone’s desktop.
Additionally, there’s currently an app in TestFlight to install it on iOS natively and will probably soon be a version for Android. It’s still a web app wrapped in a native wrapper, but it unlocks native functionality and feels much nicer.
Anyway, all of this to say, nothing about the way the app was built inherently includes anything from chrome. Only if you use chrome to make it a PWA.
I’m pretty happy with the PWA. What sort of specific improvements does “native functionality” bring?
Haptic feedback and the status bar being able to match color right now. Not sure if there’s anything else right now, but man the app feels so much nicer with haptic feedback.
The back swipe / scroll bug is also fixed.
For me it’s better, but not gone entirely
It’s a webapp so you run it in your browser - it only uses chrome if you choose to use chrome.
I’m using it in Firefox on Android, but you could also use it in Safari on iOS for example.
It’s a webapp. If you’re uncomfortable with Chrome, run it with Firefox.
Ok I think I understand. You just go to vger.app whenever you want to use Voyager then.
That’s right. Sorry, if I’d been thinking I would have included the URL.
I hope you enjoy the (web)app!
