[openstreetmap/openstreetmap-website] Proposal: Seamless Sign-On for OpenStreetMap users from 3rd party apps (Issue #4128)

[Tobias]

> I suggest we use Figma, tool that we used to author the screenshots, since it offers easy zoom-in/out, and allows modifications of the design.

Thanks, I just tried it and it works great.

I updated my comment above.

---

Looking at the flow again @milan-cvetkovic I think there is an area that can be improved from a UX point of view if the right code path can be found: [Screen 201](https://www.figma.com/file/RqpiQmshkhjTew2Y1MvDn9/OSM-SSO?type=design&node-id=3-5876&mode=design&t=NodWVPMfzEMZfT9J-0) is the page after it was checked if the user is currently logged in or not. However, we don't know if the user has an account already. It looks like you assume that most users of your app will have an OSM account, because you link to the sign up page. Quite a few users will just add there data to this form, even if they are not signed up. The error case would be to show "unknown user/password".

I wonder how this error case can be improved. 
- Some apps say "there is no email address for this account, do you want to sign up". However that makes it easier to mass check email-addresses. We would have to check if we consider this an issue (or maybe its possible already via some flow).
- One could make the error message a bit more special like "Unkown user/password. Do you __want to sign up__" and create a link that will auto-fill the email+passwort on the signup page. This way the data given by the users will not be lost

Another thing could be to make the page 201 even more focussed on the OSM social login and make sure that the flow behind this handles both cases (sign up and sign in) the same way. For example to hide the input fields behind a "or use email+password instead" link.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/4128#issuecomment-1676219390
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/issues/4128/1676219390 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20230812/99516b42/attachment.htm>