Minor Project - Task 1 & Task 2


Week 01 - Week 14
Wong Khye Qing / 0361000
Minor Project/ Bachelor of Design (Hons) in Creative Media
Empathy Walk (Group 9)


 
Instructions
 



Week 1 - Week 4
Introduction to Minor Project and Group Formation, Client Meet

 

Fig 1.0  Project Briefs and Selections, Week 1




Fig 1.1  Empathy Walk Brief, Week 1

We were briefed on different projects that we can take on as well as forming a group with the selected projects, in a group that consists of students from different specializations. Then I have decided on choosing the Empathy Walk, which I went on finding my teammates for the project, I needed to find some of the course mates that were in different specializations. 

In no time, I was in the Group 9 that was one of the 3 groups for Empathy Walk and my group consisted of 7 members in total including myself. I have also been elected as the Group Leader and would need to oversee the whole progress of the team and distribute tasks. 

Fig 1.2  Ideation for the Topic, Week 2

We were required to find some ideas for the mobile app that we were going to do. A few references were pasted in the Miro board in order to simplify the brainstorming process. Other teammates were also required to do the same in order to gather each other's ideas and pick any similarities between them as the ideas to discuss.


Fig 1.3  Preparation of Hotspot Venue for Client Meet, Week 3

We have researched and have site visit to the venues in the campus in order to have a better grasp of the venue locations in the campus. Then we have compiled the potential campus hotspots that we will be presenting to the client. The red highlighted ones were the venues that the clients requested.


Fig 1.4  First Meeting with Client in Block A, Week 4

Met with the client for the first time physically in the campus. We have presented our ideas and the hotspot spreadsheet that we have prepared to the client. The client was quite satisfied with our preparation prior the meeting and also provided feedbacks towards our directions to make some clarifications. 



Week 5 - Week 10
Interview, Response Analysis & Presentation


Fig 2.0  Student Ambassador Interview Analysis, Week 5


Fig 2.1  Student Interview Analysis, Week 6

We went to interview a 3 students and 3 student ambassadors to gain more insights towards the pain points during the open days and campus tour. Their insights were then been analyzed in spreadsheet to have more clarity. This way we were able to spot the similarities between the points that were given by the interviewee. Any similarities were then highlighted out and made into an merge into our analysis of each questions. 


Fig 2.2  User Persona Formation, Week 7

With the insights from the analysis, we were able to create 3 personas for Student, Parents, Student Ambassador. Each of the persona has highlighted their goals. motivations, frustrations and so on. Their pain points will be important for the ideation of our app features on ways to solve their pain points. 


Fig 2.3  Insights, Problem Statement and How Might We, Week 9

Each of the teammate have selected the 5 important insights to select the top 5 themes that we have from the interviews. Then, they were categorized and simplified into Key Themes. With the Key themes, we were able to form the Insight statements and find out the structure of our Problem Statement. The structured problem statement were also derived into How Might We.


Fig 2.4  Current and New Campus Tour Path, Week 9

Through the interview we have gained insights towards the path that the student ambassadors take and understood the design student venues. Through the combination, we have created the Design Student Tour, a merge between the current tour route and a program specific route. 

The Red boxes are the client requested venues, while the Black ones were the program specific venues, in which were the design program's venues. 


Fig 2.5 Proposing AR Features, Week 9

We have decided and summarized the AR features that we were going with such as the integration of AR with 360 video, Volumetric Video, Geospatial Mascot and so on. We have lay out these features into our slides to brief our clients about the features that will be in the final prototype. With that in mind these proposed features are just prototypes but required TrueXR to gauges its doability. 



Fig 2.6 Small Meeting Held & The Lo-Fi Wireframe, Week 9,10

A small meeting was also held between Gim Khoon, Xin Yee, Rui Ying and me in order to make sure that we were on track for the UI/UX interface that we were doing. We have also confirm with each other on our progress to meet the deadlines for the presentation. 

We have also made a Lo-Fi wireframe that was our initial idea on how our mobile app will be like. Of course, the wireframe will be presented to the client in order for them to have an idea on the app interface layout and design system that we have selected. 



Proposal Presentation Deck 


Fig 3.1 Figma Lo-Fi Prototype



Week 11 - Week 14
TrueXR, Finalize Prototype Final Presentation


Fig 4.0  Figma Lo-Fi Prototype

We went to the TrueXR to learn more about experiential design, especially Volumetric Capture. The staff at TrueXR have also given us briefs about some experiential features that could be of help towards  our tasks. Then, we have also asked them questions about the feasibility for the AR features in our app. Apparently, every features for our prototype were doable and able to be realized in a real app with some tweaking and scripting.

Visual Positioning System + Offline Map
 

Fig 4.1  Visual Positioning System + Offline Map

Visual Positioning System is a system that is able to recognize any captured point cloud location. Meaning if you take your camera to detect the venue, the system will be able to detect that it is the venue and act as a trigger to display something. So this VPS will act as a trigger to show the Offline Map after calibration using the VPS. 

Visual Positioning System + 360 Video
 

Fig 4.2  Visual Positioning System + 360 Video

As mentioned, the Visual Positioning System will be able to detect the LT12 and able to trigger the playing of 360 video in another page. It is necessary as it will enable the users to go to the venue in order to experience the atmosphere of the venue with the 360 video to add immersion during open days.  

Image Target + Volumetric Capture


Fig 4.3  Image Target + Volumetric Capture

An Image Target will be used as the trigger to activate the Volumetric capture model of a real human being instead of a rendered 3d model. Once the camera is able to detect a specific image, it will trigger the footage of a real human that was converted into a 3d model in order to allow users to look around real life footages of students carrying out activities and not just rendered footages. 

Geospatial Video 


Fig 4.4  Geospatial Video 

The Geospatial will be integrated with the Google Maps in order to pin point on the set location for the 3d model of the Duckie on the lake. With this feature, any users are able to detect that lakeside and able to automatically spawn the duck at the same location no matter which angle that the users are standing. 

Taylor's Duckie Mascot


Fig 4.5  Taylor's Duckie Mascot

The animated 2d Duckie mascot is a good addition in order to provide accurate information and fun facts to the users while browsing through different venues. 


Fig 4.6  Final App User Flow Map, Miro


Fig 4.7  Final Prototype Interface, Figma



Final Submission
 
Miro Board


Fig 5.0  Miro Board

Final Prototype
 

Fig 5.1  Final Prototype

Final Presentation Deck
  

Fig 5.2  Final Presentation Deck
Final Prototype Walkthrough Video


Fig 5.3  Final Prototype Walkthrough Video


Reflection

Week 14

With the presentation coming near, we were trying to finalise the presentation and the prototype. A few new features such as the volumetric prototype has been created using Adobe Aero and captured in the campus area. This is to create a placeholder GIF that was able to simulate the usage of AR. Mr Mike has also suggested that we make the prototype more clear by displaying the steps more clearly in order to not be vague with our features. Such as integrating animation towards the user pin location in the map. After that we will be presenting for the client our final prototype. Good luck


Week 13

After the confirmation of features, we have further structured the Design system to suit the final prototype and adhere to the brand identity of the university. We have also created a few pages and integrated a few new GIFs as the placeholder for the 360 degrees video that will be in the Hi-Fi prototype.


Week 12

This week, we visited TrueXR, which enabled us to learn more towards the features that are available for AR technology, such as the Volumetric Capture that will be a step up towards normal usage of 3d models in AR experiential design. With the visit, we have the professionals from TrueXR to affirm towards the feasibility of our proposed AR features, which every feature is doable by them. They have also suggested some alternatives for us to be able to increase the efficiency for the integration of those features.


Week 11

This week, we have continued our work on the Hi-Fi prototype as we have distributed the parts for different teammates. With the exploration of different features available for us to use and modify, we have finally decided on the features and directions that we will be heading. Then, we would need to prepare for the next visit to TrueXR to confirm on the doable of the features that we are heading for. 


Week 10

This week, we have presented to the client on our ideation and the insights that we have found. The presentation was primarily to propose the features in our final prototype. Then, we have also gained some of the information about the clients satisfaction towards some parts of what we have presented. Which is why we will need to keep our trajectory towards the insights that we have found and solve the pain points using features in the app.


Week 09

This week, with most of our insights being gathered and analysed, we were able to craft our “How Might We” questions. Then, a final check was done by Mr Mike for our presentation in order to make some amendments towards the flow and contents in the slides. He has given some suggestions towards the arrangement or the slides and given feedback to amend some parts of the Lo-Fi prototype that we have made. 


Week 07

This week, the parts of the first task are starting to form, by having the completion of the customer journey map and the continuation of preparing for our presentation, in the coming weeks. We have started to discuss the Design system for the application to decide on the design direction of the app. Then there were also some sketches on how the initial visual of the interface, to act as a foundation of ideation. 


Week 06

This week, we have wrapped up our interview towards the student and student ambassadors, thus, we have proceeded in compiling all the interview responses. The responses were then analysed to find any similar pain points that they have mentioned in order to use it for later analysing of insights. With these insights we will be able to pinpoint their pain points and solve it with a solution. We have also made an attempt on the User persona, which is the summarised insights from the interview towards their needs and solve the pain points. 


Week 05

This week, we went to have some interview sessions with the students and student ambassadors to gain more insights for the app. We have tried the approach of interviewing the students from different programmes in order to gain insights of the student pain points and their perspective of open days to inquire about their programmes. Then we have also interviewed student ambassadors in order to understand more about how the open days went and what are the pain points that the parents and students have gone through. 


Week 04

This week, we had our first client meeting. I was quite nervous about meeting with the client physically. Prior to last week, our group had prepared a list of potential hot spots venues which aided our presentation to the client with things prepared. The client also has mentioned not to have too many venues so as to not be too overwhelming for us. We have also listed down the interview questions for Mr Mike to look through and give us feedback. 


Week 03

I have looked into the Adobe Aero, which I have discovered the AR features that are in this program and tested on its capabilities. Our group has also started preparing a list of possible hotspots venues for the campus tour in order to use it during the interview. Mr Mike has suggested us to make a list as to be prepared to face the client and prepare sufficiently in order to spike the interest of the client


Week 02

This week, Mr Mike has started to introduce to us about the Design thinking systems as well as the importance of walking in other’s shoes, which is to stand in the point of view of users. As for the group’s progress, our group has finally been formed with finalised group members. With our research from last week being pasted in the Miro board, Mr Mike has given us some feedback towards our ideas toward the project. We were also briefed further about Adobe Aero and some of its capabilities. With that in mind, it was quite useful for us to know where we should start our further research as well as creating our project prototype. Moving forward, we will be carrying out our research towards Adobe Aero and the preparation towards the client meeting.


Week 01

Our group has yet to form in the first week due to the lack of members, we have tried to find other classmates from the same class to join our group. I have understood the brief that was given by Mr Mike, he has provided us with a few options for the topics that we will be selecting. Honestly, I was a bit overwhelmed with the choices given and the decision to choose a topic. It was also nice that the lecturer has aided us in sorting out the groups and making sure that we are on the right track. Moving forward, it was about finding the remaining group members and also to distribute the task among ourselves for better workflow.