PHP, Yii Framework, MySQL, Java
My Why is a mobile social platform that allows you to share your current feelings and support your close ones when you’re far away from each other. You share a story (photo or video) that describes your momentary emotions or explains why you’re experiencing them, and your friends react to your post by sending stickers.
The initial idea of the application was something else. It was supposed as This Is Why I Drink app which would allow users to share pictures, videos, GIFs or just simple text to let their friends know why they’re having a drink or two tonight. But the founders decided to change the idea because they wanted to broaden their audience with users under 21. As a result, My Why evolved as a gamified mobile platform for those who want to show sympathy and get support from their loved ones who aren’t there at the moment.
Once the client described what kind of app they wanted we dived into the first Agile sprint. First of all, we designed wireframes for multiple scenarios: updating your profile, sending emotion stickers, in-app purchases and creating user groups.
The client was demanding new features every sprint. We’ve designed ten prototypes before TIW became what it is today. It took 20 iterations to build the current version of the app.
There are 24 emotions to choose from. Basically, these are stickers that you can buy for virtual coins, or tokens.
When you publish a photo or video story you can specify visibility settings. The privacy settings for publications are highly customizable: for example, you can make an update available for a group of users and two-three users who don’t belong to the group. All others won’t be able to see what you’ve shared.
TIW is a gamified application. Users level up by collecting experience points for the activities with the platform. Tokens can not only be purchased for real money but also gained for completing simple quests.
The in-app currency, tokens are easily purchased.
We offered the client ten background videos. They narrowed the choice down to two videos and couldn’t decide which one would be better. We did some kind of an internal A/B test among Devvela team members who weren’t engaged in the project.