Experiential Design · Task 3 · Project Prototype
| Instruction
| Visual Design Prototype
Concept and Theme |
Fig 1.1 Reference Moodboard
Design Guide |
- Primary Colors: Black, grey, white, light yellow-green (#DAFF8D)
- Accent Color: Light red (#ED484C)
- Font: Inter – chosen for its clarity and modern simplicity
|
| Fig 1.2 Design Guide |
Sketches |
|
| Fig 1.3 Sketches |
Visual Prototype |
Fig 1.5 Cover Background and Final Design
|
| Fig 1.8 Index Page Preview |
|
|
| Fig 1.9 User Flow |
To streamline integration with Unity, I organized all visual assets neatly in Figma.
|
| Fig 1.9 Assset Board |
| Progression in Unity
|
| Fig 2.1 Target Image |
|
|
| Fig 2.4 Target Image |
| Bugs & Incompleted Parts
Known Bugs |
|
|
| fig 3.1 Assets not appear |
Not Yet Finished |
| Presentation Video
| Reflection
Observation |
Throughout this project, I realized that I am good with the visual
design process. Creating the UI layout, choosing the color
palette, and building the overall look and feel of the app was
something I truly enjoyed. I didn’t face much difficulty during
the design phase—in fact, it was the most enjoyable part of the
project for me.
However, when transitioning to the technical side, especially
working with Unity and Vuforia, I encountered several challenges.
I often struggled with understanding how the system works behind
the scenes, especially with scripts, object hierarchies, and scene
management. Even small bugs sometimes took a long time to resolve
because I lacked the technical background.
Throughout this project, I realized that I am good with the visual design process. Creating the UI layout, choosing the color palette, and building the overall look and feel of the app was something I truly enjoyed. I didn’t face much difficulty during the design phase—in fact, it was the most enjoyable part of the project for me.
However, when transitioning to the technical side, especially working with Unity and Vuforia, I encountered several challenges. I often struggled with understanding how the system works behind the scenes, especially with scripts, object hierarchies, and scene management. Even small bugs sometimes took a long time to resolve because I lacked the technical background.
Findings |
I discovered that even though Unity offers a powerful platform for
interactive experiences, it has a steep learning curve for beginners.
Online tutorials were helpful, but not always directly applicable to
my exact situation. Many times, I had to experiment or find
workarounds through trial and error. This made me realize how
important it is to understand the logic and structure of Unity—not
just follow steps blindly.
I also found that proper organization of assets and keeping a clear
structure in the Unity hierarchy helped reduce confusion during
development.
What I Learned |
-
Technical Skills:
-
How to set up Vuforia in Unity for AR tracking
-
Importing and placing avatars using Ready Player Me
-
Creating animated UI elements that appear based on user
interaction
-
Writing basic scripts to connect buttons to external links
-
Soft Skills:
-
How to manage frustration and stay patient when solving bugs
-
How to search effectively for Unity-related solutions
-
The importance of testing features in small steps to prevent
bigger problems later
Overall, this project taught me that even though technical challenges
can be overwhelming, they can be overcome with persistence and
curiosity. I still have a lot to learn in Unity.
Technical Skills:
-
How to set up Vuforia in Unity for AR tracking
-
Importing and placing avatars using Ready Player Me
-
Creating animated UI elements that appear based on user interaction
-
Writing basic scripts to connect buttons to external links
Soft Skills:
-
How to manage frustration and stay patient when solving bugs
-
How to search effectively for Unity-related solutions
-
The importance of testing features in small steps to prevent bigger problems later



.png)




Comments
Post a Comment