Open 0xSwego opened 5 years ago
Should be a feature request for OSM.org first. But I doubt that it will go through 🤔
I was thinking on a possible approach, which could be pulling such info from some third party service. Googling for "public WiFi password database" lists wifimap.io, but I could not find any API or service for querying it. If anyone knows some free/open database, it might be useful for pulling data beforehand to have it available when offline. Just my 2c.
@pataquets I'd agree with pulling an offline database into the app, but I'd be against using a third-party API, because MAPS.ME has been becoming far too "online" in the past years already. I want it to be truly offline, so a downloadable database would be best.
However, since the team behind MAPS.ME has gone commercial (rather, even more so than it already had gone), I doubt they'll do anything without it being beneficial to their revenue model.
Yes, I fully agree. I meant to download it beforehand as you can do with maps, maybe selecting a region or box. Ideally, it would work both online and offline.
I started using Maps.me mainly because its offline features, which is a must for me.
The possibility to add WiFi credentials, rather than only signalling if a place has WiFi or not, would be extremely useful for the users and would definitely boost the app usage (while abroad, but also while in the home country).
From the UI point of view the changes would be in line with the current style and quickly assimilable by the users. It wouldn't weight too much on the DB (1 more table, with a couple of fields + the key).
When editing a place, under the WiFi toggle some inputbox would allow to insert WiFi name(s) and password(s).
The WiFi field would become clickable and show the place's passwords.
The community would keep passwords and names updated, like the rest of the info in the app.
EDIT: I understand that Maps.Me displays WLAN availability according to information from OSM.org and that OSM.org does not support the addition of fields relative to the WLAN. At this point I realize that the only workaround would be to have a small db for the additional information not supported by OSM.org and this might require a bit too much effort.
I'd still like to hear some opinions from the developers though.