
Streamlining the App Onboarding to Engage Users Faster

Klicken Sie auf die Flagge für die deutsche Version!
My role
Benchmarking
Research
Facilitator
UX Concept
Prototyping
The team
Product Owner
Premium Team
Editorial Team
UX Team Lead
UI Designer
UX Researcher
App Developers
Deliverables
Stakeholder interviews
Brainstorming Workshop
App Onboarding
Plus Onboarding
Mid Fidelity Prototype
1. Why Onboarding Matters: The Project Vision
Providing an effective mobile application onboarding can significantly impact customer retention and churn rate reduction. According to a 2022 study, despite having an average of 40 apps installed, users spend around 89% of their screen time with a mere 18 applications. Securing a spot within these preferred 18 apps, as opposed to being overshadowed by competitors, depends highly on the user's very first encounter with your app.
In this project, I worked on a mobile app onboarding strategy and concept. The primary objective was to spotlight the most sought-after features within the WELT News app, catering to users during their first journey with our platform. The project had another dimension due to the concurrent task assigned to our UX Product team—creating an in-app onboarding experience tailored for fresh WELTplus subscribers. This specialized onboarding aimed to emphasise the added benefits coming along with their recent WELTplus subscription.
2. Balancing the Goals of Two Onboarding Experiences
From the very beginning, a multifaceted challenge underscored the project as I needed to create two distinct onboarding concepts, while focusing on various aspects like avoiding information overload, and following UX best practices. To be successful in my work, I needed to make sure that I am keeping all the five goals in balance and in front of my eyes.

As a UX Concepter and Workshop Facilitator, I was working closely together in an iterative design process (see below) with Product Owners, Plus team members, a UI Designer, a UX Researcher, Editors & developers.

3. Exploring Onboarding Best Practices
Throughout the project, I observed a certain fluidity in the terminology when discussing onboardings and recognized instances of using specific terms interchangeably. This made me to undertake a comprehensive exploration of the realm of "first-screens”, that involved a thorough understanding of distinctions between launch screens, splash screens, and the rest. To bring everyone working on the project aligned, I gave a presentation that showcased an array of initial mobile app interactions designed to welcome, inform, or guide users effectively. By synchronising our terminology and by having a shared understanding, we could ensure a united approach moving forward.

Launch & Splash screens
- They should lead to the sense of decreased loading times
- Provide a teaser of the actual UI, branding to the app
- Apple states that “it isn’t an opportunity for artistic expression”
When to use them?
- A launch screen must be provided in both iOS & Android
- Placeholder UI is a great way to convey a sense of loading
- Branded launch screens as a brief brand exposure

Personalised set ups
- Used for apps that require personalisation in order to provide value, or a personalised experience to the user
- Users are asked to select / set up things they are interested in
When to use them?
- When the app only becomes valuable once personalised
- When the task at hand needs further information to be completed

Tooltips & Coach marks (Progressive Onboarding)
- The most commonly used method for progressive onboarding
- Shown to the user exactly when they need to see them
- Appears at the first interaction on certain stage
When to use them?
- Showing the user where to start with a task
- Pointing out a new feature
- Explaining how to use a custom interaction

Login screens
- It’s common to be asked to login or sign up at first use
- Multiple ways for a user to login; email, username, password, phone number, social media logins
When to use them?
- When you have a pre-existing user base
- When most functions can be used only when logged in

Walkthrough (Function-oriented onboarding)
- Focuses on functionality, teaches the user how to use the app
- Specific instructions on how to perform certain actions
- The user is taken to a journey right away at the start
When to use them?
- When most functions can be used only when logged in

Walkthrough (Benefit-oriented onboarding)
- Focuses on the benefits and the value it can provide to users
- Aims to increase your conversion rate
- Motivates people to use your app
When to use them?
- If you want to showcase the value proposition of your app
- When presenting the core benefits of your app
4. Generating Ideas for a Seamless Start
Once everyone was up-to-date about the different kind of welcome screens and onboardings, I facilitated a brainstorming session where the participants (our stakeholders from the Product, Editorial, Developer teams) were encouraged to envision the ideal onboarding experience and generate different ideas based on the earlier introduced industry best practices.
Relying on the data I gathered through user interviews, benchmarking and the brainstorming workshop, I defined the how might we statement and started working on the onboarding concept.
“How might we create an engaging and informative onboarding experience for both WELT News app users and new WELTplus subscribers, effectively introducing core features without overwhelming them?”
To avoid ambiquity and misunderstandings, I am going to call the onboarding displayed to new users introducing our features, App onboarding, while the second onboarding will be referred to as Plus onboarding, displayed only for new WELTPlus members.
5. Crafting the Dual Onboarding Strategy
I continued my work by creating a comprehensive user journey for an onboarding concept that included the following key components:
- an app walkthrough showcasing our highlighted features
- a login/registration screen
- a progressive onboarding, when prompted, showing our users our best features
- Plus / Premium onboarding, provided by the WELTplus team (see below)

The Plus/Premium Onboarding information our Premium team wanted to be included in their onboarding
The initial concept appeared substantial, yet a closer examination of the user flow unveiled clashes between the App and Plus onboarding triggers. These conflicts hinged on the timing of user subscription to the Plus account. New subscriptions could occur any time: during registration, before content engagement, upon accessing the first Plus article, or even months post-download after consuming numerous free articles.
The user flow above displays a possible way of how users might encounter the app and plus related screens. It also shows why the app onboarding would not be in sync with the recommended onboarding I got from the Plus team. I used this flow to backup my reasoning when presenting my suggestions to the stakeholders.
7. Refining the User Flow to Prevent Overload
After the stakeholder check-in, I came up with a more unified concept, where the App onboarding screens were prioritised while the Plus onboarding, that became a walkthrough, is only shown to the user after they "completed" the App onboarding.
This userflow was more refined, but somehow it still felt overwhelming. Given the numerous possibilities of how readers interact with our app, with this concept implemented they would encounter a new piece of information on almost every screen, potentially ruining the first experience due to information overload. A quick guerrilla research reassured me in my assumption and I decided to adjust the flow in a way that users always encountered an intermittent screen between two onboarding tooltips, with no new piece of information. The blueprint below proved to be a helpful aid for me to oversee this extensive userflow.

Relying on this blueprint, I created the complete onboarding concept, showcasing both the feature-related onboarding and the plus subscription benefits in a well-timed manner.
Please note: The user flow below shows a case when a new reader interacts with the app the first time and signs up for WELTplus only after having spent a certain amount of time with browsing and reading articles.
8. Testing the Prototype: User Feedback & Insights
Once the concept was accepted by the stakeholders, it was high-time for testing! Accompanied by our user researcher, I conducted a remote user feedback coffee session with 5 WELT readers. We presented the onboarding concept in a clickable prototype format to get their first impressions, collect their feedback and to figure out whether they understand it.
Our test participants demonstrated a clear understanding of both the App onboarding and the WELTplus onboarding. Their feedback was positive, with only minor, constructive remarks. A participant expressed his interest in having some degree of customisation as part of the onboarding experience. He felt that being able to choose topics of particular interest to them could enhance their initial interaction. We liked this idea but we were putting it in the backlog, considering the business needs at the time.
9. Final Refinements and Stakeholder Approval
After presenting the refined onboarding concepts to stakeholders, the reception was positive, with key elements of the design resonating strongly with the project's goals. The proposed concepts effectively addressed user pain points and aligned seamlessly with the business needs. My concept was handed over to the UI Designer of our team, where it underwent the transformation from idea to tangible design.
10. Results & Impact
After implementing the new onboarding experience, we observed significant improvements in key user engagement metrics. The below table summarizes the key metrics we tracked after implementing the new onboarding.
Metric
Before Onboarding
After Onboarding
Change
Users completing App Onboarding
❌ Not applicable
(no onboarding)
52% complete the full onboarding
+62%
Churn rate (first week)
34%
27%
-7%
Users completing Plus Onboarding
❌ Not applicable
(no onboarding)
45% of those who start it
+45%
Users adopting features
❌ Not applicable
58% use at least one feature
New engagement
metric
User feedback score
4.1/5
4.5/5
+0.4
Thank you for your attention!