As part of Sprinthackular May 2026 several design explorations around the welcome survey have been made (as part of DE1.3 Progression system). This task captures the related UI prototypes that have been developed and collects the challenges, blocker and learnings around it.
Product questions
- Per designs the survey can be skipped at any step. Should we capture interim results as a regular submission?
- How often do we think the questions can change? Last time took some years.
Technical questions
- When should the WelcomeSurvey be presented? Same as current behavior?
- What should be the long-term storage solution? Currently it's a user option
- How should be the data-write request be performed, currently handled as a special page post action. May vary if partial results are allowed.
UI/Design challenges
- The multi-step pattern, be it on dialogs or not, is repeating itself across different extensions (GrowthExperiments onboardings, PersonalDashboard quiz exploration). What's the most appropriate mechanism to share components between two extensions?
- Codex icons are provided via a ResourceLoader callback hook for each module requiring some icon. How should a component that uses a codex icon be architected so it's reusable.
- The nature of designs (some views are in the MW content surface while others on top of a dialog) make the UX mobile experience challenging in terms of orchestration of view navigations. Using some conventional tool like vue-router could come very handy. Also to allow some sort of "state URL serialization" so the survey can be recovered on its last state.
- The current Codex dialog offers fixedHeight property to expand but does not take the full screen viewport. On narrow screens, the close button is always shown.
- If the survey is fully rendered on the client, what should show while it loads?