MEASUREMENT
If app supports onboarding , it is used because it is essential for first use of the app
An onboarding sequence should only be employed if it is essential and contextual tips / help are insufficient . If used , it should only surface the highest priority learnings a user will need for first use . Try to engage users in the same way as ‘ tips and help ’, avoid using more than 3-or-4 screens and benefits , and minimise copy . Check analytics regularly , and if the flow isn ’ t working , kill it ! and consider another design approach . Rationale for using onboarding would be :
App is empty and requires user to input to populate it for first use App requires personal input or selections for first use App has complex functionality such as in a productivity-type app App relies on hidden or bespoke gestures unfamiliar to most users App has been updated with new features
If onboarding is used , the user can choose to skip it ( put the user in control )
Users should be able to skip the onboarding sequence if they wish not to be interrupted by it or do not perceive a benefit in swiping through it . Put the user in control of their time and initial experience of the app . Onboarding should only ever appear on first app use , or until user is signedin . ( See image 02 )
image 02
MEASUREMENT
Bounce Rate : you will want to reduce this ( e . g . firing events on loaded elements / packages to understand drop-off reasons ; track on-load type errors at a user level , which are key reasons for high app bounce rates )
User Timings : if you use Google Analytics , you can measure resource load times of a specific screen ( in Android and iOS apps )
If an onboarding sequence is used you could measure :
% users that complete onboarding screens and progress to home screen
% users that chose to skip onboarding
Time elapsed between onboarding screens
7