-
Notifications
You must be signed in to change notification settings - Fork 936
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time to finally make an openstreetmap official app #2414
Comments
Sure, there's plenty of apps that use openstreetmap data. However there is still no official openstreetmap app. |
I'm not saying it it needs to compete with anybody. I'm just saying it should be an official reference version. |
What would be the benefit? |
The best way (less coding needed) would be an progressive web app #2361 but the benefits are not existing. |
This is the repository for the web site so is not the place to discuss a hypothetical mobile app. The team here develop the web site - if you want an official app then start a project to create one and persuade the OSMF to bless it as "official" presumably by allowing use of the trademark. |
Am Do., 24. Okt. 2019 um 06:10 Uhr schrieb 積丹尼 Dan Jacobson <
[email protected]>:
Well, what a great Improvement would that be? Well it might be a little
more efficient then going indirectly through a browser. And also it would
be an official implementation so people could be sure that there's no
browser bug causing something weird that they're seeing.
if there are bugs now on the website (and there are of course), they would
be similarly on the app. Either there are people caring for it, and will
fix them, or there aren't and then there won't be for the app (or even
"apps") either.
As a workaround, on iPhone you can open osm.org, go to "sharing" (from the
browser menu), tap on "Add to Home Screen", and you'll get an icon, offline
(distinct cache) and full screen experience, very similar to a native app.
Very likely there is a similar procedure on Android.
|
Hi, Obviously we can all agree that this doesn't really matter if you're already familiar with OpenStreetMap but it makes things more difficult to understand for the average person. I'm also not suggesting that the OpenStreetMap team work on an entirely new app, as there are already multiple good contenders for an official app. I'd also like to note that this decision would hinge on two parties, possibly even three: the OpenStreetMap Foundation, the developers of one of those apps, and possibly the users. As for what would need to be done: once the app to become official is chosen, it would just need it's name and icon changed in accordance with the OpenStreetMap trademark. The other solution is to simply add PWA support to the website as suggested in #2361 (although as mentioned, the benefits are not that obvious). The problem is that while the website does scale for mobile devices, it's clearly not made for them. So in my opinion, assuming an official app were to be made, it'd be better to just use an existing third-party app. As part of my quest, I not only wanted to find open-source apps, but also apps that were cross-platform. OpenStreetMap doesn't officially fulfil this criteria because there's no official app. (In practice however, through one of the multiple third-party mobile apps and the website, it is.) Thank you so much for making this wonderful service and I'll hope you'll consider this at some point! |
As @tomhughes already said - This is the repository for the web site so is not the place to discuss a hypothetical mobile app. |
I think openstreetmap needs an official app, iOS and Android. Wikipedia has a official app. Google maps has an official app. Yep, every website that is for real also has an official app.
Okay, so what should the openstreetmap official app look like? Well, it should look pretty much just like the website looks like.
Well, what great Improvement would that be? Well it might be a little more efficient then going indirectly through a browser. And also it would be an official implementation so people could be sure that there's no browser bug causing something weird that they're seeing.
The text was updated successfully, but these errors were encountered: