Enable Toggle by default if user skips onboarding

[malmstein]

Task/Issue URL: https://app.asana.com/1/137249556945/project/1211654189969294/task/1213539375189609?focus=true

Description

Enables the toggle experience for users who skip onboarding

Steps to test this PR

Toggle enabled

• Fresh install
• Skip Onboarding -> I’ve been here before + Start Browsing
• Verify Toggle is enabled

Toggle disabled

• Fresh install
• Go through onboarding
• Don’t select the toggle
• Verify Toggle is disabled

---

Note

Low Risk
Low risk behavior change limited to the skip-onboarding path, setting a single DuckChat preference and adding a unit test to prevent regressions.

Overview
Users who choose Skip onboarding now have the DuckChat input screen explicitly enabled by default via duckChat.setInputScreenUserSetting(true) when confirming the skip.

Adds a focused unit test in WelcomePageViewModelTest to assert the preference is set when the skip flow primary CTA is clicked.

^{Written by Cursor Bugbot for commit add16ae. This will update automatically on new commits. Configure here.}

[malmstein]

• Enable Toggle by default if user skips onboarding #7863 👈 (View in Graphite)
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[joshliebe]

LGTM 🚀

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Setting persisted after navigation command risks cancellation
  • Moved duckChat.setInputScreenUserSetting(true) before _commands.send(OnboardingSkipped) so the setting is persisted before the navigation command can trigger ViewModel cancellation, matching the pattern used in the INPUT_SCREEN handler.

Or push these changes by commenting:

@cursor push c90b97ea55

Preview (c90b97ea55)

diff --git a/app/src/main/java/com/duckduckgo/app/onboarding/ui/page/WelcomePageViewModel.kt b/app/src/main/java/com/duckduckgo/app/onboarding/ui/page/WelcomePageViewModel.kt
--- a/app/src/main/java/com/duckduckgo/app/onboarding/ui/page/WelcomePageViewModel.kt
+++ b/app/src/main/java/com/duckduckgo/app/onboarding/ui/page/WelcomePageViewModel.kt
@@ -177,9 +177,9 @@
 
             SKIP_ONBOARDING_OPTION -> {
                 viewModelScope.launch {
+                    duckChat.setInputScreenUserSetting(true)
+                    pixel.fire(PREONBOARDING_CONFIRM_SKIP_ONBOARDING_PRESSED)
                     _commands.send(OnboardingSkipped)
-                    pixel.fire(PREONBOARDING_CONFIRM_SKIP_ONBOARDING_PRESSED)
-                    duckChat.setInputScreenUserSetting(true)
                 }
             }

[cursor]

Setting persisted after navigation command risks cancellation

Medium Severity

duckChat.setInputScreenUserSetting(true) is called after _commands.send(OnboardingSkipped). Since setInputScreenUserSetting is a suspend function, it yields the main thread when switching to IO, allowing the UI to process OnboardingSkipped and potentially cancel viewModelScope before the write completes. The INPUT_SCREEN handler correctly persists data before sending Finish. The same ordering pattern would be safer here — call setInputScreenUserSetting(true) before _commands.send(OnboardingSkipped).

---

_{Please tell me if this was useful or not with a 👍 or 👎.}

Additional Locations (1)

• app/src/main/java/com/duckduckgo/app/onboarding/ui/page/WelcomePageViewModel.kt#L214-L227