Fit Friends - A Mobile Application & Non GUI product
What is Fit Friends?
Fit Friends is a habit forming mobile application for people you want to develop a habit of exercising frequently.
Overview
From left : Rob, Kelly and Erin; Hook model synthesis
Objective: The purpose of was to produce a successful interactive experience for a habit forming product. The focus was to cheaply test the desirability, feasibility, and viability of those ideas. Also, learn about the fail fast attitude and how to pivot away from the bad idea. The habit forming application to exercise was given to me among class.
No research: The rules for designing were building a cup cake model, so the project did not involve prior research, instead the class worked on developing product validation techniques after the project was built. The project stated with the 2nd diamond from Double Diamond Theory.
Accelerators in Health Care: Played a game called ‘Accelerators in Health Care’ created by our professor Mike Begley. This game helped me build my idea on how can I structure my habit forming application
Details
Duration - 5 Months
Solo project
Research methods - Observation, User Interviews and Surveys, Affinity mapping, Personas, Journey mapping, MoSCow method, Kano model
Prototyping- Sketch App, Invision Studio, Photoshop, Pen and Paper
Developing the Idea : Storyboard, Wireframes, Specifying assumptions
Hook Model Strategy for Fit Friends
Hook Model By Nir Eyal: Reading and synthesizing the book and then applying the Hook model on my exercise application and brainstorming on different ideas on how to build the entire concept.
Strategy: So, I started with storyboarding, it was for getting clarity on how the product will interact with the user of the application. It also helped me to know how the product will fit into the ecosystem of user life or what will be the way the user will use the product.
Storyboard for Fit Friends
MoSCoW Method
Scope: While designing the scope and structure of the application. Few things were kept in mind like scope creep and feature creep. Scope creep is when there is unwanted growth in the project and project takes out more time to complete. Feature creep is when unwanted or extra features are added to the project to make the project look good. But instead the user will not be satisfied while using the product. So, I used my storyboard to approach this problem. Examining what important feature the user will need to complete the task through application. Then, talking about the feature selected for the application among my group mates. The discussion helps me to reason and gives me insights like what other possibilities can be there to explore.
Structure: Then the siteflow of the application was made. On the basis of selected features that I wanted to add to the application. Here I have chosen the tunnel structure, because Fit friends concept followed the process of first inputting the requirements, then selecting the friend then deciding on the place to meet. Therefore the pages were designed based on this structure and tunnel design suited it.
Skeleton: Designed the wireframes, as per the above findings in the scope and skeleton. I used iPhone template for designing the wireframe. The important aspects of developing the wireframes were properly annotating each element, clear spacing and element size.
Testing the Idea : Experiment and Measuring Result
Whats app messenger screenshot
Facebook post screenshot
Analysis & Results: The result was not as expected
Screenshot of analysis of results on Miro board
Risky Assumption Sheet: Writing down the top 3 risky assumptions that I want to test before I get to designing the application.
Postings: Posted on Facebook for interested users, which did not have impact. Then posted on other social media channel called What's app. And asked if they were interested in getting motivated personalized msg for workout. Also attached the video which I posted on Whats app
The result
Mobile application for Fit Friends (click on the photo to access the prototype )