Collaborative app based on recipe version control. Imagine Git with food.
Fork is an idea of a collaborative recipe repository based on the "Git" version control system, giving users the opportunity to create personal recipes and leaving them freely available for others to make their own versions of those recipes, surpassing or changing them completely. Based on an extensive social system that aims to provide the user with a powerful repertoire of functionalities to be able to create teams, compete for scores or create competitions, starting from an original idea and converting the original recipe into something completely different, making the existing database of dishes to be prepared grow "automatically".
Don't play with the food was a phrase we were all told when we were little.
I propose to do the opposite > play with the food.
An initial problem of content and number of users arises that would be solved...
We are going to see some information about gamification.
It is a process that can have pedagogical and therapeutic characteristics.
It is capable of increasing different capacities > productivity and learning.
Now we will see which are the main competitors of our project.
Yummly asks questions to generate an accurate profile in terms of tastes or allergies.
...For a more efficient management.
Standardise the impossible
No cloning or competition like we do.
Goals to lose weight or save money.
Differentiation of ingredients according to recipe or according to supermarket section.
Both concepts are perfectly adapted to recipes.
Here is a brief summary of all of the previous thoughts.
Here is a summary of the most important points from the result of 237 answers of a questionnaire that I arrived at through the Lean Survey Canvas.
People who do not use recipes and make dishes from memory, and from memory with improvisation, add up to more than people who consult online.
Paper press comes very close.
We have to offer something fresh.
The idea of versioning dishes is accepted.
The theme of competition, not so much.
People seem to want to collaborate more than fight, which is a good sign. (For human kindness specially)
Gamification can get us involved and motivate us.
In terms of functionalities, having the construction of the recipe well detailed is the most valued thing.
I have interviewed 3 people, involved in gastronomy from more to less.
Sergio, a Chef, from whom I learnt that between professionals in the kitchen it is not accepted to correct each other, but as a fun game app type-of-thing it could be nice.
With this information obtained, in order to know the needs that the user has, I have done exercises mapping to know how users feel and what they need.
User Persona: a fictitious archetype, in this case, related to gastronomy.
Rita wants to apply Software version control to food.
Lucía wants to study new gastronomic ways. An app where to learn.
Javi wants to get publicity for his events in a parallel medium to his activities.
With the Empathy Maps we have gone inside the user personas' heads to see what influences them.
And everything that goes through their heads we have summarised in the user stories that I will show later.
I have empathised with the user personas to see how they feel in the interaction with the App in the Customer Journeys.
Rita gets to have fun cooking and create many of her own recipes with her desired version control.
Lucia expands her knowledge of cooking history and can now write a book.
Javi starts to stand out as an active user and gets much more audience for his events.
We have kept the most significant and important user stories.
Avant-garde gastronomic Fanatical.
Recipe cloning functionality.
See recipe evolution and have fun.
Cooking history scholar.
needs to use tags to create lists of recipes related to each other.
Write a book on the history of cooking.
As an organiser of gastronomic appointments.
an option that allows me to generate events.
to be able to invite users .
These are the conclusions in terms of functionalities that we reached with the empathy mappings.
We see them in the MOSCOW method already divided into priority areas.
The functionalities that will be included are:
This is the hierarchical structuring of our App.
In the user flows we have what would be the Happy Path of the user
I have made the crazy 8 system to get fast and without blockages to the wireframes.
Pen and paper main user flow
The Moodboard - This would be the soul in terms of style and concept of the App.
The App is called Fork.
Fork is what cloning and versioning is also called in software.
The logo is like a history of three versions of the same fork.
Dark and light modes
Home screen light version
Home screen dark version