Walkadoo is an app that provides user with a new step goal every morning (calculated by our algorithm that references the amount of steps you took the last couple of days to calculate a realistic but challenging goal).
When I came aboard the Walkadoo team, there was an iOS app that had very basic functionality- see your step goal, see the feed, comment and smile on feed items. The app mirrored much of the predetermined web app branding. We began to plan for a relaunch, with which we would introduce new features monthly. We chose to focus on derbies, our competitive feature. We also wanted to add more social activity to the app, including the ability to search for friends, follow new people, and invite friends to join. Finally, we wanted to add the ability for users to select an avatar for the derby- users would receive new avatars as they level-up and complete tasks within the app.
We wanted to allow users to start using the product right away, without giving us any information. We wanted to lower the barrier of entry and get users engaged right from the start. So, we decided to allow the new user into the app and give them a practice step goal card so that they can start using Walkadoo right away. I knew that I didn't want to do a swipe-through tutorial; the app really doesn't take much explanation anyways! Instead, I opted to include a bunny character (WD has long used a bunny as our mascot) that would walk the user through the onboarding steps.
In order to start counting the user’s steps right away, we needed them to grant their permissions. Once permissions are granted, we encourage the user to start walking! I wanted to find a magic step number for the practice card. A number low enough that they could finish the card with their phone in their hand, but high enough that they wouldn’t count up to it in their head (just in case the phone mechanics are off!). I did a few tests walking around, and decided that 25 worked best.
I wanted to solve for the user who was not able to complete this flow in one feedback loop: the user on the bus, or in a car, or can’t immediately start the practice card for whatever reason. So, if a user is on their phone and grants permissions, but then doesn’t start walking after 10 seconds, we show a full screen message that entices the user to sign up. If they sign up, they will be all set up and ready to go for whenever they are ready to start taking those steps.
The user that does start taking the practice steps, however, will finish the card and receive a celebration moment, and a full-screen message inviting the user to sign up. If the user swipes the message away, we will continue to serve them daily cards, but won’t allow access to any other parts of the app.
"Derbies" are the social challenge feature in Walkadoo. Users can sign up with strangers or their friends, and we'll track their daily steps and move them forward on the race track as they move forward. At the end of the week, the person who has taken the most steps wins!
Bringing derbies to mobile would take a complete redesign. On web, they were laid out horizontally, and created with a lot of layered, skeuomorphic detail.
Now that we had the ability to view derbies on mobile, we wanted to build in functionality to create and invite people to join a derby from their phones.
I created a prototype of the micro-animations that would occur when the user invites others to join their derby.
Since we wanted to allow users to connect and socialize on the mobile app, we needed to start building a basic profile, starting simply with lists of followers and following, plus a link to settings. The next step was adding search.