First-time user has multiple sign-up options ( e . g . username / password and social sign-up )
Users should be presented with multiple sign-up options , such as username / email and password , and social sign-up . Because , while some users may prefer the faster approach of social sign-up ( e . g . via G +, Facebook or Twitter ), others may prefer to keep their different social profiles separate , and others again may not even be consumers of social networks . ( See image 09 )
User can select to reveal or hide password as they type , during sign-up or sign-in ( e . g . by toggling a ‘ reveal ’ or ‘ hide ’ control )
Give users the option to quickly select a toggle control that reveals - or hides - their password as they type . This will reduce password input mistakes , during sign-up and sign-in . ( See image 09 )
When asked if they ’ d prefer to click through to an app or a mobile website from mobile search results , more people prefer the app . Here ’ s why : Apps I have installed will have my login details pre-entered and save me time ( 51 %).
App-Nesia in the UK : The Need for Re-Engagement Marketing , 2015
image 09
Return-user is persistently signed-in to their app
Users shouldn ’ t have to keep signing-in to their apps once they are created , because one of the main differences between a site and an app is an app provides a persistent experience , to provide ongoing convenience and personalisation . A persistently signed-in user base enables crossdevice conversion tracking . One caveat to persistent sign-in is apps in regulated verticals ( e . g . financial services ) or those that store highly sensitive data ( e . g . personal health records )
Touch ID is presented to iPhone ( 5S and up ) users as a convenient way to sign-in
Companies can employ Touch ID ( fingerprint recognition ) to enable iOS ( version 5S and up ) users to more conveniently log-in to apps , such as users of Evernote Premium who get access to a passcode lock with Touch ID compatibility . ( See image 10 )
User is asked to grant app permissions and is given reasons why ( and perceive the benefit )
Only ask for permissions that enable your app to provide the user with value , ask at the appropriate time ( in context to what user is doing ), and with a clear benefit statement . For example , request permission for a users current location when they initiate a search or service : “ ACME would like to use your current location so we can help you remember events ” ( See image 11 )
13