Several details of App login page design

Landing

Registered

Checkout

Calculation

Search criteria

Multiple steps

Long Form

Today, with our siege lions, we discussed the idea of landing page, and summed it up:

1. Landing page is the most easily overlooked basis

The first time you do a login page prototype, we can easily have the following error:

Register in front of login, occupy a prominent position

Ignore the "Forget password"/"Retrieve password" details.

In fact, the more mature design will be the importance of this arrangement:

Login > Registration > Forgot password

So, a minimum landing page that can be used should grow like this: pattern gallery is a virtual name.

Registration-1

2. Social account login has gradually become mainstream, but to prevent 2 pits

By logging in as a social account, the user simply clicks on the corresponding social media icon and completes it instantly. And the traditional login, at least need to fill in account number + password two complex input steps.

So if possible, logging in through social accounts is an important way to increase the rate of opening.

In the course of the discussion with the engineers, however, we found the following 2 pits:

1 The back-end program The ape proposed that if the user does not bind a social account (such as Weibo, QQ) when creating a separate account, the system creates a new user when they first log on through a social account. To bind again, you must authenticate through the phone, which is a very complex process. Or, some apps don't give you the chance to bind again.

Well, if that's the case, then we're just going to provide a social account login and not create an account on our own. This does not appear to be through a separate account login, the easiest.

No way!

This is the second pit--our iOS siege lion puts it: The Apple Store audit is now getting tighter, and for apps that only have a social account to log on, it can't be audited! Because you need to take into account that if the user does not have these kinds of social apps on his phone, he can still log in normally. , otherwise it is in the induction download (Apple Store's thoughtful, indeed impressive).

At this time the Android project Lion is very indifferent, said there is no such distress.

So, in this case we should still keep the login prompt for the standalone ID, then the login prompt for the Third-party platform. However, do not open the stand-alone account registration function to avoid the occurrence of just saying the first pit.

If you do not open the registration function of the independent account, there will be users because there is no installation of our connected Third-party platform to give up registration? Theoretically possible, but actually, we think that our target users should have at least: micro-letter/Weibo account, if none, so even if not registered is not a loss.

So what seems to be a reasonable idea right now is the following (name and chart are all virtual):

Registration-2

From the @ Sunset Temple 65th of the supplementary reminders, feel very helpful experience, also included down:

Personally, even a social account login actually requires a process to create your own account. Only Jianshu registration For example, I registered when the Watercress account, now every time the Web login to enter a Third-party Web page, rather than directly enter the account password can be logged in. Sometimes the third party Web page can not be brushed out, I do not even account for the way to log in. The year can be seen, foreign products or know, although you log in is to take social accounts, but after the guidance you have a website independent account and binding social accounts. This step is also very simple, in the registration, the determination of personal information can be completed.