Improve OSM account creation or submission #5740

New issue

Open

opened 2023-08-17 13:45:39 +00:00 by privatemaker · 0 comments

privatemaker commented

2023-08-17 13:45:39 +00:00

(Migrated from github.com)

Is your feature request related to a problem?

To serve the goal of making it easier to contribute OSM content as per #5686

The current user registration form of OSM has multiple UX issues. It breaks most UX principles for easy signup. There are some UX issues with OSMs Third Party Authentication

Select Third Party Authentication provider
Discover it still requires an email address, unique display name, and the only benefit is not requiring a manually entered password.
OSMs form validation when attempting Third Party Auth is very bad

This negates most of the benefits of third-party auth altogether. This is obviously not OMaps issue, but rather OSM side of things.

However, this impacts curious OMaps users who may want to try contributing data to OSM unless they complete the standard form, as cumbersome as it is

Describe the solution you would like

Some solutions to explore are:

Improve OSM signup flow and potentially make Third Party Authentication a user selectable option from directly within OMaps
Use OS level Single Sign-On to bootstrap a user into OSM account:

The technical feasibility with respect to infrastructure required by OMaps and OSM's API is beyond scope of this UX audit, but this feels worth exploring.

Describe alternatives you have considered

An alternate option to consider is to create multiple anonymous OSM user accounts that are hard coded into OMap builds. An example of this is the privacy protecting Google Play app store Aurora Store, see their account UI:

This would offer users ability to "submit data anonymously" to OSM and cut out the user-experience signup flow altogether.

Given the difference of this being POST style action compared to Aurora's GET requests, this does pose some ethical threat vectors to consider.

This relates to privacy concerns in #5727 and being able to toggle submission ability per Place.

SCORE: 4

**Is your feature request related to a problem?** To serve the goal of making it easier to contribute OSM content as per #5686 The current user registration form of OSM has multiple UX issues. It breaks most [UX principles for easy signup](https://www.learnui.design/blog/tips-signup-login-ux.html). There are some UX issues with OSMs `Third Party Authentication` 1. Select Third Party Authentication provider 2. Discover it still requires an email address, unique display name, and the only benefit is not requiring a manually entered password. 3. OSMs form validation when attempting Third Party Auth is very bad ![osm-onboarding-third-party-validation](https://github.com/organicmaps/organicmaps/assets/49612519/0ecf7314-bd80-4087-8d37-a6aec4332093) This negates most of the benefits of third-party auth altogether. This is obviously not OMaps issue, but rather OSM side of things. However, this impacts curious OMaps users who may want to try contributing data to OSM unless they complete the standard form, as cumbersome as it is **Describe the solution you would like** ![osm-onboarding-sso](https://github.com/organicmaps/organicmaps/assets/49612519/6b5b8051-8406-4e2a-b150-7babefca50aa) Some solutions to explore are: 1. Improve OSM signup flow and potentially make Third Party Authentication a user selectable option from directly within OMaps 4. Use OS level [Single Sign-On](https://en.wikipedia.org/wiki/Single_sign-on) to bootstrap a user into OSM account: - [Apple Documentation](https://developer.apple.com/documentation/authenticationservices) - [Android Documentation](https://developer.android.com/work/guide#sso) The technical feasibility with respect to infrastructure required by OMaps and OSM's API is beyond scope of this UX audit, but this feels worth exploring. **Describe alternatives you have considered** An alternate option to consider is to create multiple anonymous OSM user accounts that are hard coded into OMap builds. An example of this is the privacy protecting Google Play app store [Aurora Store](https://auroraoss.com), see their account UI: ![aurora-anon-signin](https://github.com/organicmaps/organicmaps/assets/49612519/a60e9de8-01bd-44a2-8277-c9289efa44de) This would offer users ability to "submit data anonymously" to OSM and cut out the user-experience signup flow altogether. Given the difference of this being `POST` style action compared to Aurora's `GET` requests, this does pose some ethical threat vectors to consider. This relates to privacy concerns in #5727 and being able to toggle submission ability per Place. SCORE: 4

👍 1

This repo is archived. You cannot comment on issues.