14 Updates Later…
Yeti is 18 weeks old and we just released version 2.2.0, our 14th update. After 2,000,000 swipes we’ve learned a few things. In this version we overhauled quite a bit of the app. Most interestingly, we added a lot of functionality by reducing the number of features.
For example, we simplified the navigation from 4 windows to 3 by combining the profile and bucket list:
The navigation is now a simple swipe to the left or right. That’s it. By reducing the complexity, we’ve clarified the architecture. More importantly, by combining the bucket list and profile, we’ve reinforced the idea that great places get stored in the same place, solidifying what the app is all about.
Pick One Thing
After millions of swipes in thousands of cities, we’ve learned a lot about optimizing a new user’s experience. When a user first installs your app, it’s important to focus on what one thing they should do. Should they create an account? Post content? Invite their friends? We’ve streamlined the process making it clear and easy for the user. You should too. Know your one focus for new user optimization.
Eliminate Typing
When we launched Yeti we were concerned with speed getting a new user in as efficiently as possible. We asked users to type their email and set a password, which seemed innocent enough. Problem is, people forget their passwords, it takes effort to type, and you aren’t getting their photo and name up front. With 2.2.0 we decided to introduce Facebook Connect, a quicker process for the user, eliminating the need for typing and automating the profile setup.
The second thing we did was to introduce a form of search. Only thing is, we don’t want to make users type. So we made it a tap-tap method. Super fast. Tapping the compass icon slides the cards down, revealing search options. Tapping an option brings the cards back, filtered for that category. Couldn’t be quicker, just tap-tap.
Less is More
Throughout the app we cleaned up unnecessary clutter, simplified, and tried to focus on one core action per view. In the screen below, a user has yet to decide if they want to save the item or pass on it. There’s also an ability to view it on a map, share it, leave a comment, etc. We decided to remove the option to “pass” as it’s a fairly low priority on this view, and we’re hiding the comment bar until a user has saved it. We then hid the lower level functions in the “…”, made the map easily accessible, and put the front and center. It’s pretty clear the main CTA is to save the item, with a big green button.
Give it a try
Try simplifying your app. Remember, less is more. Focus on one call to action per screen, and make things intuitive. We’ve spent a lot of time optimizing user experience, so feel free to email design@yeti.ai if you want some feedback. And likewise, check out Yeti at http://yeti.ai and send your thoughts. Thanks!
— Alex, CEO of Yeti
