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
Yeah I still see brief locks, but they resolve much quicker
Right on, that does sound pretty cool. I may check it out.
I do have haptic feedback when using Voyager with Vanadium. I haven’t tested anything else but I don’t see how that isn’t possible.
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.
Yes but also your phone gives you the ability to “install” a web app as if it was a normal app. Go into the voyager settings and follow the instructions to do this. Basically what your phone is doing is saving a bookmark to the web app with an icon, but when it runs, it has the feel of an app instead of a website because it doesn’t open up the full browser with the url bar and all that other browsery stuff.
That’s right. Sorry, if I’d been thinking I would have included the URL.
I hope you enjoy the (web)app!
Where did you hear “built on elements from Chrome”?
Not sure it can be dependent on Chrome as it works on other browsers on multiple platforms.
I can’t search for the lemmy thread because I’m using jerboa, but it was on a thread about lemmy clients. Are you aware of this being a concern for other people maybe - lemmy.clients being dependant on chrome toolkits?
I’m sorry if I’m not being very clear, this entire thing about lemmy and different clients and defederation and chrome sucking for privacy and all is very new to me. I’ve checked the GitHub page for voyager, but it doesn’t really mention chrome anywhere so I don’t know what to make of the whole thing.
I’m not sure what you mean by chrome toolkits.
It sounds like you’ve confused several different things. Voyager is a progressive web app. You can think of it as a program that runs in your web browser. Whether that’s Chrome, Safari or whatever.
I understand it now, I think. Now I just need to figure out how to save it to my phone’s desktop.
Go to the voyager page, press the share button. Then select add to Home Screen, and it should look and be useable like your other apps
Thanks, this worked.
When I installed it it had to be safari. You save a bookmark of the web app on your iOS app home page so it appears like an app.
Try it out on safari and see what you think. The App Store version is imminent anyway if you wanted to wait.
There’s a testflight for the iOS app now, so you might be able to find a link to that. But they are coming out with a native ios app.
