I move from sketches into Figma, and everything feels sharper — but a new question opens up. The Dreambuilder is clearly mobile-first and inclusive. That part feels solid.

Now I wonder: is a configurator really just a product utility, or can it become Ferrari’s most engaging onboarding experience?

This question keeps pushing me: if users can dream, share, and play, then the Dreambuilder is no longer just a tool — it’s a real gateway into the real brand.

Iteration Steps

• I reframe the journey: onboarding first, configurator second.
• I test the placement of core actions (start, save/share, continue) so the primary hook is instantly visible and tap-friendly on mobile.
• I refine the layout with all the possible negative space and a consistent spacing system to keep hierarchy clear and the experience calm, not crowded.

Key Takeaways

The moment I lean into onboarding, the Dreambuilder changes category. It’s not about utility — it’s about conversion through play. Ferrari can use this as a killer entry point for fans, with viral potential far beyond standard configurators.

This log marks the shift: I start seeing Dreambuilder as the evolution of configurators into onboarding engines. That realization will guide everything I design from here.

<aside>

Clean Build

How these raw ideas evolve into final UX decisions? See the refined version → Digital wireframes (FD)

</aside>

<aside>

Roadmap & Progress Tracker

</aside>