ShefUp

Avatar customisation - 1
Completion of recipe
Avatar customisation - 2
Completed and favourited recipes
Filter list
Recipe list
Recipe Details
List of recipes available
Ingredients List
Camera access

What problem you are trying to solve?

Many people are unable to cook and do not enjoy cooking (which reinforces their inability to cook because they never practise). On the other hand many people have problems choosing what to cook because of too many choices being present.

Who would use it?

Beginner cooks who need incentive to cook for themselves. People who enjoy gamification and would like to try out new recipes.

What is your prototype?

An android application called ‘ShefUp’.

Project Features:

Filtering: Filter option to show completed/ new/ favourited recipes (not yet implemented)
Favourites: Mark a recipe as a favourite
Completion mark: Shows if a recipe has been successfully completed before
Ingredients and steps checklist: A checkbox list of ingredients that acts as a grocery shopping checklist and a preparation list. The steps are to easily keep track of the user’s progress through the recipe.
Visual preview of ingredients
Progress bar: Vision indication of how much XP has been earned and how far the user is to levelling up. XP is earned upon successful completion of a recipe.
Level up features: Visual animation of the progress bar changing when XP is gained.
Coin reward system: Upon completion of a recipe, a set number of coins will be rewarded to the user.
Option to take a photo of the dish to save it
Avatar customisation: choose from hair and background. Coins are used to purchase a new avatar custom feature and the user’s avatar gets updated.

How does your prototype work? How did you implement your prototype?

After determining that we wanted to develop an app for mobile we decided to work with the android platform due to the team having experience within it. Initially template screens were implemented straight from the wireframe to give everyone on the team a better grasp of the navigation of the app. This allowed for the backend to slow by implemented while the front end was being designed. Backend was placed with more importance in this application due to this being a hackathon where a minimum functional viable product was necessary. The backend was kept as simple as possible within the app with a repository pattern implemented that connected to the Room jetpack library (an implementation of SQLite). This allowed for persisting data on the local storage of the device with the app. There was no attempt at connecting up a remote database service due to lack of experience with the technology. The frontend was implemented by the rest of team in two parallel efforts. The designers iterate and create assets for the application including mockups of the screens from the templates and image icons for the interface. Our front-end developer would then take implement this changes as they came. This allowed separate parts of the codebase to be managed and updated as we planned and developed. This was in attempt to reduce the complexity of any code base merges but we still did experience merge issues.

Reference to any third party material used

No explicit third party material was used besides the adapting of the banana bread recipe found here: https://sallysbakingaddiction.com/best-banana-bread-recipe/?fbclid=IwAR3oRsp8_syYUmUzHgVNUm7FTykqMSb2TZj9sJ7Eu94sDHHS2XjlcFPLeF0 All image assets were made by the team ourselves. The code architecture was made referring to past projects. Background music - Invincible by DEAF KEV (NCS)

Link to your repository:

https://github.com/SorenAlex/CookingApp

Images/ screenshots of your project:

https://drive.google.com/drive/folders/1-XNX4JHZKj7QBsWdeZmNcWI3Zv4xwjEl?usp=sharing

The roles of each participant in the project team:

Emily Ha: Content and asset creator, Donna: Content and asset creator, Rebecca: Content creator, Video editor, Anh Tu: UX designer, Video editor, Alex: Backend developer, Vivian: Frontend developer.