Stack Exchange Network
Stack Exchange network consists of 181 Q&A communities including
Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
The best answers are voted up and rise to the top
10 years, 11 months ago
I'm designing a mobile app that requires the user to log-in with their LinkedIn account.
I feel I might have cluttered too much info into it, but everything seems to be important.
I want the user to understand that:
This is NOT LinkedIn.
We cannot show her search results if she doesn't log-in.
We don't keep her username and password (she enters them on LinkedIn's permissions dialogue, much like when you connect with your Facebook account)
She will only have to do this once.
If she doesn't have a LinkedIn account, she could register.
If she doesn't want to give us permissions, she could go to LinkedIn directly, but she'll have to redo her search there.
I also can't change the button (it's mandatory according to LinkedIn's API rules).
Is this too cluttered? If you think it is, do you have any idea how to redesign this to be more usable and look better?
37.1k 24 24 gold badges 122 122 silver badges 156 156 bronze badges
Jun 6, 2012 at 8:38
Yosef Waysman Yosef Waysman
4,457 2 2 gold badges 23 23 silver badges 30 30 bronze badges
You are using way to much text. The great example Adriann gave explains a great deal just via the graphics. Don't feel you have to explain every little thing... users are much more sophisticated than we think sometimes. Clearly if this becomes an issue it will be obvious when you user test... but start with simple and then build in complexity as you need it.
Don't use words like "unofficial" makes you sound dodgy (:
If you have a good logo it will show that you are your own company. I love the "Powered by the Linked in API" shown in the example.
You are definitely providing too many options. Number 3 should go. Number 2 should just be presented subtly.
If you really can't change the button you can do something like this:
download bmml source – Wireframes created with Balsamiq Mockups
Jun 9, 2012 at 1:15
Lisa Tweedie Lisa Tweedie
2,406 1 1 gold badge 14 14 silver badges 36 36 bronze badges
You could remove the third step completely, unless you have some way that the user will be able to come back to your app once they've finished on LinkedIn.
Though I understand your app is not LinkedIn itself, you are still using the API from LinkedIn so you are still using their services.
Have a look at the example below:
Introduction gives context by using the word 'profile'
Powered by gives credibility and re-enforces that this app isn't LinkedIn, but rather using LinkedIn's engine.
The way LinkedIn is brought in near the bottom at the 'Forgot your password?' link is brilliant and again - reaffirms that this app is not LinkedIn.
Hope that gives you some input.
Jun 6, 2012 at 9:37
1,250 1 1 gold badge 8 8 silver badges 29 29 bronze badges
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our
Accept all cookies
Necessary cookies only