Q: Has anybody on this Android ng tested the privacy-aware
FOSS Google Maps replacement, Vela Maps?
A: ???
The link which was provided to me is this, but it's for the F-Droid repo. <https://pimpinpumpkin.github.io/Vela/repo?fingerprint=F374920F2F5F38D7508D0B042125B8EAF23CF0F06FA7490280FB77115BB091DE>
I never use the F-Droid app since I download all my apps on the
desktop.
The Github link to the Vela repo appears to be[...]
<https://pimpinpumpkin.github.io/Vela/>
Turn-by-turn with lane guidance, route shields and the speedometer; the keyless OpenFreeMap basemap wearing Google's own sampled colors and Roboto labels, with rated POI icons and the tiered dots; live place data; the directions panel with alternates, traffic in plain words and the avoid toggles; live departure boards with a tap-through stop list for every
route; and the in-app light/dark themes (decoupled from the OS).
What you get
Why a degoogled app uses Google
A phone without Google Play Services cannot run Google Maps, and the open
map datasets fall well short on search, reviews, hours, and live traffic.
So Vela is a thin client over Google's public web endpoints. It asks them
the same way a logged-out browser does, once per user, with no account, no shared API key, and no server in the middle. NewPipe does the same for YouTube. There are no ads, and your searches, saved places, and history
stay on the phone. If you run GrapheneOS or another no-GMS ROM, this gets
you working maps back.
Q: Has anybody on this Android ng tested the privacy-aware
FOSS Google Maps replacement, Vela Maps?
A: ???
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 4 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 497102:19:33 |
| Calls: | 182 |
| Files: | 744 |
| D/L today: |
59 files (9,737K bytes) |
| Messages: | 73,647 |