Tom MacWright (UX & engineering)
Saman Bemel-Benrud (UI & engineering)
David Clark (engineering)
In the early days, the on-boarding flow focused heavily on professional GIS users and cartographers, explaining how different pieces of Mapbox fit together. As the product focus shifts to be more developer-oriented, we needed a method to help users to start building and tinkering right away.
The first problem we are trying to solve is: how can we help developers to use our resources and succeed.
For the new on-boarding flow we focused on a very simple task: adding a basic map view. After the install flow, we guide users to more complicated examples. We've discovered through user interviews that examples (not documentations) are a primary source of how people learn our tools.
After the launch we've seen an increase in new account activations, mobile SDK adoptions, and other metrics. Platform separation also allows us to collect more accurate persona information for targeted marketing campaigns. The open/click-through rate of our on-boarding emails increased significanltly with an CTA of 30% for Android developers.
The signup page was the main entry point to the onboarding flow. The main goal is to provide users a better overview of all the features and sell the SDK.