search

OpenArchive / Save-app-ios

Secure Mobile Media Preservation
https://open-archive.org/
GNU General Public License v3.0
10 stars 3 forks source link

IA Signup flow: Option to create a new API key should be presented first, not existing API key flow #206

Closed huertanix closed 10 months ago

huertanix commented 2 years ago

At the moment, the first thing a new user is presented with in the IA setup flow is something that looks like a login screen but asks for an Access Key and Secret Key, neither of which are familiar words for most people, since many have never used or have heard of an API before. See:

save_api_key_ia

It may be worth exploring changing this step in the flow so that the user is first presented with the option to generate a new API key first, with maybe some text explaining that this will be a one-time process.

Then maybe leave a small "Use an existing Internet Archive API Key" (or similar verbiage) link to this existing API keys screen somewhere at the bottom, for the presumably smaller contingent of users who already have an IA API keypair.

tladesignz commented 2 years ago

The original thinking behind this is, that the app doesn't want to get near the Internet Archive credentials, so the user doesn't need to trust the app with them.

huertanix commented 2 years ago

At present, the existing flow copies API keys from an in-app webview and puts them into these fields, so the app is already very near the API credentials. If you mean the IA username and password though, then yes, currently the app doesn't touch those, but has the technical capability to do that. I'm not partial to Save directly asking for IA credentials but this would be a discussion to have with IA on whether there would be a way AI could offer access to some of IA's features via third-party apps like Save.

tladesignz commented 2 years ago

At present, the existing flow copies API keys from an in-app webview and puts them into these fields, so the app is already very near the API credentials. If you mean the IA username and password though, then yes, currently the app doesn't touch those, but has the technical capability to do that. I'm not partial to Save directly asking for IA credentials but this would be a discussion to have with IA on whether there would be a way AI could offer access to some of IA's features via third-party apps like Save.

Hm. I guess, I forgot to write explicitly, what I implicitly meant:

"The app doesn't want to get near the credentials, except when the user expressly wants it to do so."

That's why all the explanation is there and an extra button press is necessary before the process begins.

johnhess commented 1 year ago

One potential improvement here is to have the CTA to "Acquire Keys" go away once they've been acquired. Then the "Connect" action is clearly the next thing you can do...

Let's leave this one on hold til we get a design person in (soon, if all goes to plan).

foundscapes commented 10 months ago

solved for in Save 2.0 ux updates