WEEK 16 TECHNICAL & CONTENT

 

Do Good Project WEEK 16

Demo day

I prepared the questionnaire based on these few criteria:

• To assess the navigation of the mobile webpage
• To assess the user tester’s understanding about the content (the budget habits and their traits)
• To assess the effectiveness of the interaction design in raising user awareness of their budgeting habits and the impact of these habits on their financial well-being. (the feedback mechanism in encourage positive financial behaviour.)

Number of user: 5

Questionnaire: https://docs.google.com/forms/d/e/1FAIpQLScpaBckHMYpbPftv2v0U3PUULbUGwm_41qFEfA6QAVi2zcz3A/viewform 

Key Takeaways:

• Overall, only 80% find it easy to navigate the mobile webpage whereas 20% find it hard
• 100% of the user find it easy to understand the content writing.
• 60% find the questionnaire page is confusing whereas 20% find join Space page is confusing.
• 80% thinks the button and icons are clear.
• 100% thinks the information is clear.

Addition Takeaways:

• Some users express it's hard to identify their characters on the screen.
• They think that ux writings are too long.
• The instructions of the Join Space are unclear.

Design development

Throughout the development, I've only been focusing on getting the technical aspect to function properly, such as the joystick and the object communication. With those key components somehow working, I began to shift some of my focus to the design aspect. Here, I just added some minor visuals and layout, which I plan to refine further in later.

To recap, the purpose of this project is to allow the educators and the workshops to collect data regarding their attendees' state of understanding regarding the financial literacy. So, there's a need for data visualizations to demonstrate the data collection.

Here are the initial sketches I worked on from previous few weeks:

Both of the sketches are really rough. While the data visuals are very clear, but they occupy too much space, and it might restrict the movement of the characters. So, I try to go for a more subtle visual.

I tried by placing the data visuals on the top/bottom and leaving more spaces for the characters to move around. Though I'm not satisfied with its layout, I find that it's challenging to incorporate the data visuals together with the interaction layout. Making it too big will restrict the character movement while making them small and simplified might diminish their purpose and confuse users.

I felt that I might need a separate screen for data collection. But I don't think I have enough time to execute this design plan. So, I intend to just focus on develop the design of the mobile webpage and the current screen I have.

Technical development

Vibration:

There's a part of the interaction emphasis on the need of the vibration to alert users about changes in the state of their characters.

I'm unable to get the vibration to work, and I can't seem to find any issues with the code. I assume that the problem lies with my phone and that it's not compatible with the vibration functionality. 

The trails:

Based on the beta tests, some of the users mention that it's hard to identify the position of their characters. Thus, I work on make the characters to leave behind some trails as they move. The trail method I use here is reference back to the first testing I did with the WebSocket, where user touch movement with leave behind strokes.

the outcome of the trail: