Hooptap was a startup focused on providing solutions for engament. Based on game mechanics and other features, the goal was to increase engaging numbers, and the formula was...
At his early stages the startup was
But there was a
All the core features were broken into components, the content consumption into different repeatable layouts, and all the ui elements into atoms. I am talking about
The team worked hard to build a large number of features that included profile status, notification system, recent activity feed, friend network, ranking(s), news feed, reward system (points, badges and prizes), quests, marketplace, second screen experience, voice recognition.. and by the other side a dashboard for content management that we friendly referred as “Skynet” 🤖.
No matter how fast you release new features, you’ll never be able to meet the needs of every single customer. But having an API gives your customers (and their development partners) the freedom to customize your software and build the exact solution they need today, not when you release the next version of your software.
Internally, it can be hard to show progress.
This might not be an issue in all companies, but it was in our case. Executives love demos to see progress, and these demos are usually based around the product’s user interface. The challenge with APIs is that they don’t have a UI—it’s just code. And for most people, it’s hard to see progress just by looking at code.
We had all the features (almost) ready, and our user workflows were defined, so I started to design all the elements (atoms), components, templates and screens.
Then started prototyping to test meaningful interactions, behaviours, and for product testing pourposes. The idea was well received, and the marketing team was interested in exploring more the possibilities of this demo.
Then implemented more complex features, such login. This allowed the team to test and get feedback about implementation issues related to sdk complexity.
Finally we implemented the widget inside a website and demonstrated the capabilities of the SDK and the API. You can trigger any action, like click, visit a page, scroll, etc and call the API to send and return data.
We worked, just for testing and validation pourposes, on a ficticious client which has an ecommerce inside entertainment/music industry. Our client is interested in rewarding key actions to his visitors, so we defined a strategic plan to engage the user.
We defined user journeys and targeted key user actions related to content and others related to core features:
Startups are hard. We made a bunch of great apps, but the latest product here described never made it into the hands of our customers. I'm proud of the work the team did and grateful for the opportunity. I'd like to specially thank the dev team for all of their lessons, for sharing their knowledge and for helping me to shape as the designer I am today.