Experiential Design - Task 2 / Experience Design Project Proposal

23.9.2024 - 9.11.2023 (Week 1 - Week 7)

Chong Hui Yi / 0363195

Experiential Design / BDCM

Task 2 / Experience Design Project Proposal

TABLE OF CONTENT

1. Lectures
2. Instructions
3. Task 2
4. Feedback
5. Reflection

LECTURES

Click HERE to view the lectures & exercises

INSTRUCTIONS

Task 2: Experience Design Project Proposal

Requirement

"Based on initial idea discussions, students are required to come up with an experience design project from a subject/topic of their choice. This can be anything from screen experience to physical space experience. They are required to create a professional experience design proposal document that explains their project idea and how will the experience be for the user. The proposal should contain analysis of current experience, comparison with similar solutions and how it can be better, Sketches to visualize the experience, Mock design of how the final outcome should be from the user’s perspective."

Progression

In Task 1, I proposed three AR project ideas: Restaurant Menu, Chemical Elements Education, and Furniture Placement. After receiving feedback from Mr. Razif during Week 5, I began reassessing the feasibility of these ideas and decided to change direction.

My reasoning for changing ideas is as follows:

Restaurant Menu: This concept relies heavily on high-quality 3D models. Without realistic food models, the project would struggle to achieve its goal, and finding such models is particularly challenging.
Chemical Elements Education: While I initially aimed to make chemistry more engaging through the app, I found it difficult to develop interactive and educational elements beyond visualising molecular combinations. The potential for using AR seemed limited within my current capabilities.
Furniture Placement: This type of AR app faces strong competition from established players, such as IKEA. To stand out, the app would need a unique selling point that is difficult to achieve.

Due to these challenges, I drew inspiration from Idea 1, which also revolves around food, and came up with Idea 4: Food Inventory Management.

Fig. 1.0 4 Idea for AR project

Fig. 1.1 User Persona 1

Fig. 1.2 User Persona 2

Fig. 1.3 User Persona 3

User Experience Map:

This section outlines the typical steps people take in managing food, highlighting the challenges and pain points faced during the process.

Step	Pain Point
Buying ingredients and putting them in the fridge	- Not sure what the ingredients are. - Don't know how to store different ingredients. - Don't know the nutritional value of ingredients.
Check the fridge and pantry	- Items are messy and hard to find. - Forget what ingredients are available.
Look at food items to check expiry	- Don’t remember when food was bought. - Some food gets hidden and forgotten.
Decide what to cook	- Hard to decide what to cook with what’s available. - Limited ideas for meals, unsure how to use the food.
Cook the meal	- Waste time looking for recipes.

Pain Point	Solution
Not sure what the ingredients are. Don't know how to store different ingredients. Don't know the nutritional value of ingredients.	AR Food Scanning for Basic Info: The app lets users scan food to get information about its name, type, nutritional value, and storage instructions.
Items are messy and hard to find. Some food gets hidden and forgotten.	Custom Notes: Users can add notes for each food item, such as location, price, or where it was bought, for better tracking.
Forget what ingredients are available.	Quick Ingredient Overview: The app shows a clear list of available ingredients on the homepage, which can be filtered by type, purchase date, or expiry date. Ingredient List Sharing: Users can share their ingredient list with family or friends to avoid duplicate purchases.
Don’t remember when food was bought.	Record Purchase Date: Users can manually enter the purchase date or automatically when scanning food Purchase History & Expiry Tracking: Users can see past purchases and check the expected expiry dates of each item.
Hard to decide what to cook with what’s available. Limited ideas for meals, unsure how to use the food. Waste time looking for recipes.	Smart Recipe Matching: Based on the ingredients users have, the app suggests recipes that only need a few additional items, helping reduce waste and save shopping time. Personalised Recipe Suggestions: The app suggests recipes based on users' past choices and dietary preferences, like recommending low-calorie meals for health-conscious users.

Fig. 1.4 New User Journey Map (Miro Board Link: https://miro.com/app/board/uXjVLG1YTWQ=/?share_link_id=200751479763 )

Fig. 1.5 Moodboards

Fig. 1.5 Sketch

Fig. 1.6 Homepage & Inventory Page

When users open the app, they will see the homepage (Fig. 3.1 left image) with two choices: “Scan Ingredients” and “View Inventory.”

On the inventory page (Fig. 3.1 right image), ingredients are shown in different categories. Users can sort them by expiry date or A-Z. Each ingredient card has a label showing the type and whether it is expired, so users can see important details easily. Tapping the "+" box will take users to the AR scan page to add new ingredients.

Fig. 1.7 AR Scanning Guide

When entering the AR scan page, users will see a guide explaining how to use it. This page includes:

Back Arrow: Allows users to return to the previous page.
Info Button: Provides a way to review the guide again.
Plus (+) Button at the bottom: Adds the scanned ingredient to the inventory.
Checkmark Button in the center: Confirms that the ingredient is selected for the recipe.
Chef's Hat Button on the right: Generates recipes using the selected ingredients.

Fig. 1.8 View information & add ingredient to inventory

When the AR identifies an ingredient, an info dot will appear. Users can tap it to view nutrition info and storage info. The purchase date is editable but defaults to the current date, and the expiry date is automatically calculated. Additionally, when users tap the plus (+) button to add the ingredient to the inventory, they will receive feedback confirming it has been successfully added.

Fig. 1.9 Generate Recipe & Recipe Details Page

When the user taps the middle button to confirm the ingredient, it will turn into a thumbnail (e.g., bitter gourd and eggs). Then, by tapping the button on the right, recipe ideas will be generated with some options. When the user taps on a recipe, they will be taken to the recipe details page with detailed instructions. After cooking, the user can tap "Complete Cooking," and if the ingredient has been used up, it will be removed from the inventory.

Fig. 2.0 Figma Prototype (Click HERE to view in Figma)

Fig. 2.1 Figma Prototype - Mobile Version (Click HERE to view in Figma)

Final Outcome

Fig. 3.0 Final Experience Design Project Proposal

Canva Presentation Slide Link:

https://www.canva.com/design/DAGWZMCvhq4/k_ZPw6XdOf8Qj_f7o_NV7A/edit?utm_content=DAGWZMCvhq4&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton

Fig. 3.1 Presentation Slide

Presentation Video YouTube Link:

https://youtu.be/TJiPiGQVhUY

Fig. 3.2 Presentation Video

FEEDBACK

Week 5:

Restaurant Menu: This depends on your product. You can find 3D models online, but ensure they look appealing and are realistic. The food should match your theme.
Chemical Elements Education: There is potential, but further exploration is needed.
Furniture Placement: The competition is tough. Consider what could be better or more appealing than just the idea. Alternatively, create a journey map for the IKEA app to identify any issues.

Week 7:

Highlight actions (e.g., prompts to move the phone). You could darken the camera background, use semi-transparency, or apply a glass morphism effect.

REFLECTION

At the beginning of Task 2, I felt quite confused and uncertain about whether I could make my idea work. So, I decided to rethink my idea for Task 2, which made the time quite tight. I realised that the proposal would require a lot of work, such as creating user personas and user journey maps. However, through this process, I gained a better understanding of the gain points and pain points, which helped give me a clearer direction. Initially, I thought creating a mockup would be quick, but I later realised that it actually takes a lot of time. I also started worrying about whether I would be able to implement it in Unity. Through this experience, I’ve come to understand that "design is meant to solve problems." I think this is very important, and it shows why research at the beginning is necessary, rather than jumping straight into the design.

Search This Blog

Chong Hui Yi (0363195)