Experiential Design: Final Project/ Completed Experience

9/7/2024 - 1/8/2024 / Week 11 - Week 15
Janice Marie Eng Chia Hui  / 0361521
Experiential Design / Bachelor of Design in Creative Media / Taylor's University 
Final Project

Table of Contents:


Task

To-do list:
  • Continue developing your app.
I have mostly developed all the AR elements in Project 2: App Prototype, so I mainly focused on creating everything else for the final project. 

Landing Page

I initially wanted to make a splash screen, but I did not know a splash screen was called a splash screen then. So when I googled how to make a splash screen, I searched for how to make a loading screen instead. Which wasn't what I wanted. Initially, I had a landing page with the splash screen image and a button that said START at the bottom.

Additionally,  I had a logo on my 'landing page'. However, when I showed it to Sir he said it was hard to read. Which is true. SO I went back home and changed the font I used for the logo. Hopefully, it's more legible now.

Figure 1.1 Initial landing page (27/7/24)


Figure 1.2 Initial Logo (left) vs final logo (right) (27/7/24)

Splash Screen

I figured out the splash screen was called splash screen lol. I went back and re-edited the landing page to look more like a splash screen and inserted it as a background image. I had help from a video to guide me along. 

I did have a problem where when I exported the file to my phone the background image wasn't showing up. After fiddling with it a few more times, nothing seemed to work, and I was just going to leave it as a white background. But on the last export it worked?? But all the settings were the same???? So I'm not too sure what went right.

Figure 2.1 How to edit a Splash Screen

Figure 2.2 Splash Screen Edit in Figma (27/7/24)

Figure 2.3 Unity Settings for the splash screen (27/7/24)

Chose your Project

For this page, there were not many technical issues, I just decided to add a 'Hi, user name' on the top to personalise the experience more. 

Figure 3.1 Choose your project page in Figma (27/7/24) 

Onboarding page

I decided to add a short and simple onboarding page to the app to help people understand the functions of the app better. I got the illustrations from a Figma Plugin.

I then exported the screen from figma (without the buttons and text) and placed them into Unity. 

Figure 4.1 Plugin from figma (27/7/24)

Figure 4.2 Onboarding page flow from Figma (27/7/24)

Filter + Catalogue Page

Initially, I was thinking of coding the filter. But that was a lot of work. So I just made use of the 'Set Active' function and the buttons to hide and show certain elements. 

The thumbnails in the catalogue were taken from the page MoodFabrics. I then edited them in Figma to fit the theme of my app. 

Figure 5.1 Edited Thumbnails (27/7/24)

Additional Changes to the old prototype

  • I change the thumbnail in the detailed information page of the sewing pattern.
  • I also updated the image target. However, I had an error that popped up constantly that said WebServiceFailed. In the end, I just updated the old image target image. 
  • Added a short information page in the AR Sewing Pattern screen to help users identify the function of the buttons. 
  • Fixed the glitching issue with the AR tutorial animation (with the help of Sir) by rearranging their order. 
  • Added a logo for the app
  • Updated the UI to a higher-resolution image.
Figure 6.1 Old (left) vs New (right) thumbnail (27/7/24)

Figure 6.2 New image target (27/7/24)

Figure 6.3 Information Page (27/7/24)

Figure 6.4 Changing the order of the elements (27/7/24)

Figure 6.5 Logo (27/7/24)

Final Submission

Google Drive Link (Unity File ZIP, APK File, Proposal Doc & Slides) :

Figure 7.1 SewIt Walktru+Presentation (27/7/24)

Feedback

Week 14
Specific Feedback:
  • To fix your glitching animation you can try changing the order of the AR element to make it first.
  • Since you can make the outfit, don't have to worry about the sizing issue for now.
  • Your logo cannot be read T^T.

Reflection

This task was not as challenging as I thought it would be. Mainly because my AR features and functions are quite simple. I'm not sure if I should have added more, but on the other hand I don't know what else I can add. 

Learning how to use Unity is an experience. After 14 weeks of using it, it is not as daunting as it was the first time I opened Unity. I still think that learning how to use Unity is a good skill to have. As a design student, I struggled a lot with the coding aspects of Unity. However, with the help of my classmate and the lecturer (and AI cough), I was able to make things work. I am grateful for Sir's feedback, he really did try to give feedback to anyone who needs it so that's nice. I am also grateful that I took Exp Design this semester because I heard that we would be using Unity for Game Development next semester, so maybe I am a bit better equipped to handle it. 

Overall, my experience with the Final Project was okay. I got most of the AR features done in the prototype. Genuinely, I hope that my project is not too simple cause I really do think it is simple.

Comments