Duolingo asks 'Why are you learning a language?' and shows different content based on the answer. Headspace — 'What's bothering you?' and offers corresponding meditations. This isn't just a UX pattern — it's a mechanism that significantly increases the likelihood of user return: the app is relevant to them from the first seconds. Without personalization, users see the same interface, and content doesn't match their expectations. The questionnaire solves this: it collects key data and immediately configures the app. As a result, retention increases by 20–40%, and user acquisition cost is recouped faster. Our clients typically see a 35% increase in retention within the first month, translating to significant cost savings.
With us, you get 10+ years of mobile development experience and over 50 completed projects with personalized onboarding. We are a trusted partner, guaranteeing a measurable uplift in your app's engagement.
Why Personalized Onboarding Matters for Mobile Apps
According to Localytics, personalized onboarding increases retention by 25%. When users see relevant content from the first launch, the likelihood of repeat visits grows. The questionnaire is an effective data collection tool: it takes 30–60 seconds but gives a profile that determines the app's behavior for weeks ahead.
Questionnaire Architecture
The personalization questionnaire is not just a set of screens with 'Next' buttons. It's a flow with branching: an answer to question 2 may determine what the third question is. And the result is not just saved answers but a set of parameters that affect the app's initial state.
Data-driven configuration. Each question is an object with metadata:
struct OnboardingQuestion {
let id: String
let type: QuestionType // .singleChoice, .multiChoice, .slider, .text
let title: String
let subtitle: String?
let options: [QuestionOption]
let nextQuestionId: [String: String] // optionId -> nextQuestionId, or "default"
let analyticsKey: String
}
Branching logic via the nextQuestionId dictionary: if the user selects 'Stress reduction' — next question is q_stress_level; if 'Better sleep' — q_sleep_problems. 'default' is used for questions without branching. The configuration is loaded from the server or bundled in the app as a JSON file.
QuestionnaireCoordinator manages the question stack: history: [String] for the 'Back' button, currentQuestionId: String, answers: [String: Any] for accumulating answers. On pressing 'Back' — history.popLast() and transition to the previous question with the selected answer preserved.
How to Implement Question Branching in Swift?
At the center is QuestionnaireCoordinator. It receives the configuration, manages history, and determines the next question. Example:
class QuestionnaireCoordinator {
private var history: [String] = []
private var currentQuestionId: String = "q_goal"
private var answers: [String: Any] = [:]
private let configuration: [String: OnboardingQuestion]
func goToNext(selectedOptionId: String) {
guard let question = configuration[currentQuestionId],
let nextId = question.nextQuestionId[selectedOptionId] ?? question.nextQuestionId["default"]
else { return }
history.append(currentQuestionId)
currentQuestionId = nextId
}
func goBack() {
guard let previous = history.popLast() else { return }
currentQuestionId = previous
}
func currentQuestion() -> OnboardingQuestion? {
configuration[currentQuestionId]
}
}
Questionnaire UI
Navigation Between Questions
Transition between question screens — horizontal animation. On iOS: UIPageViewController in .scroll style or UIView.transition(with:duration:options:animations:) with .transitionCurlUp for a unique feel. In SwiftUI — TabView with tabViewStyle(.page) and fixed selection doesn't allow the user to swipe back — this needs to be controlled via interactiveDismissDisabled.
The best option is a custom animation using withAnimation(.spring(response: 0.4, dampingFraction: 0.8)) with offset and opacity. Gives full control: forward — slide left, backward — slide right.
Single Choice
Single choice — a list of cards or items, tap immediately transitions to the next question (no 'Next' button). Haptic .selection on selection. Selected card — animated background and border change.
Multi Choice
Multi choice — checkboxes or cards with multiple selection. A 'Next' button appears after at least one option is selected. LazyVGrid / FlowLayout for tag cards.
Slider
Slider — UISlider / Slider in SwiftUI for numeric values (age, frequency, level). Labels on edges for context. Haptic .selection at integer values.
Progress Indicator
Progress indicator — a progress bar at the top shows position in the questionnaire. Animated LinearProgressView / LinearProgressIndicator. Don't show exact step ('3 of 7') — users see the end and might drop off. Show only the bar without numeric labels.
Comparison of Linear vs Branching Questionnaire
| Parameter | Linear Questionnaire | Branching Questionnaire |
|---|---|---|
| Number of questions | Fixed (5-7) | Depends on answers (3-10) |
| Configuration | Hardcoded | Server-driven JSON |
| Analytics | Minimal | Detailed (Firebase Analytics) |
| Development time | 2 days (cost: $1,500) | 3 days (cost: $2,500) |
| Retention impact | Moderate | 2x better retention compared to linear — up to 40% increase |
UI Components by Platform
| Component | iOS | Android |
|---|---|---|
| Single choice | SwiftUI List + onTapGesture |
Jetpack Compose LazyColumn + clickable |
| Multi choice | SwiftUI LazyVGrid with checkboxes |
Compose LazyVerticalGrid with Checkbox |
| Slider | SwiftUI Slider |
Compose Slider |
| Progress bar | SwiftUI ProgressView |
Compose LinearProgressIndicator |
Example Configuration JSON
{
"questions": [
{
"id": "q_goal",
"type": "singleChoice",
"title": "Why are you using the app?",
"options": [
{ "id": "stress", "title": "Reduce stress" },
{ "id": "sleep", "title": "Better sleep" }
],
"nextQuestionId": {
"stress": "q_stress_level",
"sleep": "q_sleep_problems",
"default": "q_time"
},
"analyticsKey": "goal_selection"
}
]
}
Step-by-Step Implementation
- Define your target user segments and desired outcomes.
- Design 5-10 questions with branching logic.
- Implement the
QuestionnaireCoordinatorin Swift/Kotlin. - Build UI components for single choice, multi choice, and slider.
- Integrate Firebase Analytics and track key events (our SwiftUI onboarding components handle this seamlessly).
- Test the flow with A/B testing and iterate based on retention data. This entire UX onboarding flow is optimized for iOS personalization.
Result Personalization and Analytics
After completing the questionnaire, we collect a UserProfile from the answers:
struct UserProfile {
let primaryGoal: Goal // from question q_goal
let experienceLevel: Level // from question q_experience
let preferredTopics: [Topic] // from question q_topics (multi)
let availableTime: Int // minutes per day from question q_time
}
This profile determines: which content is shown on the main screen, which push notifications are sent, which sections are hidden/shown, and at what difficulty level the user starts. The profile is saved locally (UserDefaults / DataStore) and synced with the server — so that if the app is reinstalled or the device changes, the user doesn't have to go through the questionnaire again.
Analytics toolkit: Firebase Analytics — questionnaire_started, questionnaire_step_completed (with step_id and time_spent), questionnaire_skipped (with at_step), questionnaire_completed. This data reveals which questions users drop off at, which answers are most popular, and how the questionnaire affects retention. We integrate Firebase Analytics onboarding events out of the box. Firebase Analytics is the recommended tool for monitoring.
Skipping the Questionnaire and Editing
A 'Skip' button is always present. Not everyone wants to share information. Those who skip see default content, and periodically (after 3–7 days) we gently suggest filling it in 'for better recommendations.'
The ability to change answers later is available in the profile settings. Don't lock users into their initial choice. OnboardingQuestionnaireView is reused in settings with an edit mode — the same components but with pre-filled answers and a different completion action (profile update instead of transition to main screen). Profile editing is fully supported.
What's Included in the Work
- Configuration JSON file for the questionnaire with branching support
-
QuestionnaireCoordinatorin Swift or Kotlin - UI components (SingleChoice, MultiChoice, Slider, ProgressBar)
- Firebase Analytics integration
- Ability to edit the profile in settings
- Documentation on usage
Timeline: 2–3 days. A linear questionnaire of 5–7 questions with simple choice and applying the result to initial content — 2 days ($1,500). A branching questionnaire with server-driven configuration, multiple question types, analytics, and profile editing — 3 days ($2,500). Contact us to evaluate your project. Our company has 5+ years on the market, 50+ projects delivered, and 10+ years of mobile development experience. Get a free onboarding consultation.