Apps introduce new technology, behaviour and interfaces to users. We discuss how onboarding patterns like tooltips, overlays, interactive setups and in-context & in-feed plugs can help ease users into apps on Android.
most engaged with your app during the ﬁrst few minutes of use • FIRST 7 DAYS For ‘decent’ apps, the majority of users retained for 7 days stick around much longer http://andrewchen.co/new-data-shows-why-losing-80-of-your-mobile-users-is-normal-and-that-the-best-apps-do-much-better/ 77% 23% Users Lost in First 3 days of Install
• They perform Key Actions • Blogging app = pick a theme, a name, write ﬁrst post • Social app = Import address book, Connect to a few friends, Opt into notiﬁcations • Enterprise Collaboration app: Start up a new project, add a couple coworkers http://appcues.com/academy/intro-to-user-onboarding/ http://andrewchen.co/new-data-shows-why-losing-80-of-your-mobile-users-is-normal-and-that-the-best-apps-do-much-better/
actions, quantify. • Talk to users for qualitative feedback. • Analyse cohorts: new users, dropped off users, activated users. • What features did they like? What features did they actually use? Did they share the app with others?
the better • Minimise the number of screens in an interactive setup/ tutorial • Use FAB, get focus on key actions. Users may not be interested in all your features • Features may be introduced lazily, over time
permissions at runtime • Individual permissions get greater visibility - win for users • Auto-update process is smoother - win for developers • checkSelfPermission() & requestPermissions() • Normal Permissions & Dangerous Permissions http://developer.android.com/training/permissions/index.html
• Prime the user - explain why you’d like the permission before asking for it • Alternatively, wait until users reject the permission till you tell them why you need it • Or a data-driven combination of these! • Do not imitate the native UI