I am designing the onboarding flow for a mobile application.
The first image below shows a simplified version of the flow. The application consists of two parts; the onboarding for new users and the main application for returning users (after registration).
Users first register as an individual and later register the group (company, family or band for example) they want to use the application with.
The onboarding screens are as shown below:
One - An overview of application USPs.
Two - User registration.
Three - Group registration.
Currently I'm looking at the application entry points for when the user exits the onboarding process and returns later.
The simplified flow above is a 'happy flow'. The users do what we want them to. This is of course too good to be true. Users can exit the application whenever they like.
Should the user return to the exact position(/screen) in the onboarding process when he returns after closing the application?
The onboarding process is especially designed for the first run. In an ideal situation the user completes the onboarding in the first run and enters the application via the 'main' view every other time he uses the application.
In the example below the entry point for users who didn't complete the onboarding process is the 'group list' view. This is a view that's accessible from the main application (for registered users to add a second group, for example).
So if a user quits after registering as a user but before registering his group he 'skips' the onboarding upon his return.
I'm trying to figure out entry points for 'returning first time users' without confusing them about their position in the onboarding process.