Customer Experience in Android and Fire apps
In this section, you will learn about the login flow your customers will experience when they use Login with HAQM within your Android app. The Login with HAQM SDK for Android handles the entire login flow from signing in, to obtaining customer consent, to sharing profile information (if you requested it), to finally redirecting the customer back to your Android app.
- Step 1: The Login with HAQM Button
- Step 2: The Login Flow
- Step 3: The Login Screen
- Step 4: The Consent Screen
- Step 5: Success!
Step 1: The Login with HAQM Button
The login flow always begins when your customer clicks a "Login with HAQM" button in your Android app. We recommend placing these branded buttons on your app’s sign in and registration screens. You can also place Login with HAQM buttons in your app’s header or footer to enable a quick way for your customers to login to your app using their HAQM credentials.
For instructions on implementing Login with HAQM buttons, see our Getting Started Guide for Android.
Step 2: The Login Flow
The Login with HAQM SDK for Android will automatically provide each of your customers with one of the login flows below:
- Single Sign-On (SSO) flow: if the customer is signed into the HAQM Mobile Shopping app on their Android device, or they are using an HAQM-branded device running Fire OS.
- System browser flow: if the customer is not signed into the HAQM Mobile Shopping app on their Android device, and are not using an HAQM device running Fire OS.
Single Sign-on flow
If your customer is already signed into the HAQM Mobile Shopping app on their Android device when they click the "Login with HAQM" button, they will not be prompted to enter their HAQM account credentials. Instead, the Login with HAQM SDK for Android will recognize the customer’s authentication to the HAQM Mobile Shopping app or the HAQM device, and use that same account information to log them into your Android app. The customer will only need to provide one-time consent to share their profile information with your app (if your app is requesting it).
In SSO flow, a user visits your Android app (A). They click the Login with HAQM button (B) and get redirected to a secure, branded WebView within the HAQM Mobile Shopping app which requests their consent (C) to allow your app access to their profile data. If they have already consented, or if your app is not requesting a scope which requires consent, this step will be skipped. HAQM then redirects the user from the consent screen back to your app (D).
System browser flow
If your customer is not signed into the HAQM Mobile Shopping app on their Android device, Login with HAQM will redirect them to their system browser and provide them with a secure, branded screen where they can enter their HAQM account credentials to login to your app. After successfully signing in, the customer will need to provide one-time consent to share their profile information with your app (if your app is requesting it).
In system browser flow, a user visits your Android app (A). They click the Login with HAQM button (B) and get redirected out of the app and into a secure, HAQM-branded login screen in their system browser (C). After entering their HAQM account credentials, another secure, HAQM-branded page opens in their system browser and requests consent to allow your app access to their profile data (D). If they have already consented, or if your app is not requesting a scope which requires consent, this step will be skipped. HAQM then redirects the user from their browser window back to your app (E).
Step 3: The Login Screen
In system browser flow, the HAQM customer will see the login screen immediately after clicking a Login with HAQM button.
The HAQM-branded login screen consists of the following:
- The app name you select when you register with Login with HAQM.
- A Forgot your password? link the customer can click to reset their HAQM.com password.
- Fields for the customer to enter in their HAQM.com account credentials.
- A Show password checkbox the customer can select to display the password they're typing in. By default, the password will be shown.
- A Keep me signed in checkbox the customer can select to skip the login and consent screens the next time they visit your app and use Login with HAQM. Instead, the next time they log in to your app they will see an acknowledgement screen (shown above), where they can click Continue to login to your app with their HAQM account credentials.
- A secure Sign in button the customer can click when they’re ready to authenticate to HAQM using their account credentials. Clicking Sign in will redirect the customer to the consent screen, or to your app, as described in the Login Flows sections above.
- A Create a new HAQM account button the customer can click to create a new account, then sign into your app.
- A list of benefits for using Login with HAQM, and a Learn More link the customer can click for more details.
- Links to the Conditions of Use and Privacy Notice relevant to their usage of Login with HAQM.
Step 4: The Consent Screen
If your app requests access to a customer’s profile information (such as their name, email address, or postal code), the customer will be made aware of this via the consent screen.
The HAQM-branded consent screen consists of the following:
- A drop-down list showing the customer's name in the upper, right corner. Clicking the drop-down arrow will allow the customer to choose another HAQM account to authenticate with.
Note: This link is not shown in SSO flow. SSO flow will always automatically use the HAQM account already authenticated to the device or to the HAQM Mobile Shopping app.
- The app name and logo you provide when you register with Login with HAQM.
- A list of each permission requested by your app.
- An I agree button the customer can click if they agree to share their information. Clicking I agree will redirect the customer back to your app as described in the Login Flows sections above.
Note: A customer only needs to provide their consent once per app, per device. After they have consented to sharing their information with your Android app once, they will not be asked again, unless they intentionally remove their permissions from the Your Account link.
- A Cancel button the customer can click if they do not agree to share their information. Clicking Cancel will bring the customer back to your app unauthenticated.
- A Your Account link the customer can click to remove permissions they've granted to apps via Login with HAQM.
- A link to the privacy policy for your app that you provide when you register with Login with HAQM.
Step 5: Success!
After a customer has completed the login flow, they are automatically redirected back to your Android app.