-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Working Prototype (best viewed on mobile device or through Developer Tools in Chrome)
As stated in our proposal, our problem space is using technology to help with food planning and reducing food waste and thereby changing peoples behaviour to eat healthier and more environmentally sustainable.
For this project, we followed an HCI process that focuses on user-centred design using an iterative process. To create this project we have gone through several different stages before ending on a proof of concept high fidelity prototype. We started with identifying and analyzing previous work done within the field using that as a foundation for our own project. Thereafter, we conducted our own user research to find what users require in the application followed by an iterative prototyping process.
For the purposes of this project, there are two major limitations, Sustainability and Health data and Including a dynamic functional social element. In this project, we will not include accurate sustainability and health data as we do not have the knowledge required to include this properly. We will, however, include placeholder data with basic information on what elements can make a specific food healthy and sustainable. In addition to this, we will assign values to the different recipes in the application, but again this will not be accurate data but is there to simulate what the final product would look like and give an indication of the functionality. For the social element, we will include static elements that give perceived functionality but will not change much in term of content on in the application. This is done due to the time needed to implement it and because full functionality is not needed to give a good indication of how the final product would work, in other words, function as a proof of concept.
- Shopping cart
- Inventory
- Multi-User
- Eating out feature
- More social features
- Your impact based on friends and/or other users
During the initial stage of this project, the different group members read and compare the different proposals and together chose a problem space by combining certain elements from the two different problem spaces. Throughout the rest of the project, we adjusted our requirements and designs based on user testing and feedback. The overall project aims and goals have stayed the same throughout the project as no data has suggested the need for change. For more detail about the specific changes to the prototypes and their justifications see, Low-fidelity: Paper Prototype and High-fidelity: Code Prototype
Most of the theory used within the project has been derived from the different bibliographies made for this course. The different papers have given us different insights into how best to develop and design our application, as given in Relevant Theory
For the first part of this project all tasks were evenly divided among the members, all user research, designing of prototypes and evaluation was done in group meetings or split among group members during tim in-between meetings. After this initial stage, the tasks were divided differently although the different members were included in all work through giving feedback and advice.
Shaun and Jessica were responsible for the user testing, testing both the low and high fidelity prototypes. They were also responsible for the creation of the promotional material.
Sigurd and Thomas were responsible for the creation of both prototypes, make them ready for testing and writing the testing protocols. Due to technical difficulties with one of the computers most of the work on the application was done through a single Github account, however, the work done was evenly split among both members.
Every group member has been responsible to write up information on the Wiki, Shaun and Jessica did some initial work and writing while Sigurd and Thomas cleaned up large portions of the text and restructured content to fit the brief's requirements.