RSPCA FINAL PROTOTYPE & USER TESTING
This blog will be about how to make a prototype according a user scenario to fulfil user goals and make user testing session to get the feedbacks about the user experience and also how changes can be made to the prototype by taking into consideration the testers feedbacks.
The Brief:
RSPCA is an independent, community-based charity providing animal care and protection services across Australia. However, they found that 62% of Australians owns a pet and most them does not have knowledge about how to take good care of their pets which leads to the increasing number of pet overweight in Australia. In addition, many people struggle to find their pet the right veterinary care and other services (such as grooming, and dog walkers) within their areas.
The audience for this app is anyone who wishes to adopt a pet and the RSPCA has come up with an idea to create a mobile app which helps people to adopt pets and also find other pet services. Due to user group research and interviews, I have determined different user goals that will be helpful while making the prototype.
User Goals:
- Simplify the adoption process on the mobile application.
- Help people who wish to adopt a pet on the mobile application to easily find a pet according to their choice.
- Facilitate adopters and pet owners with other services within the RSPCA app.
To make sure that I fulfil these goals mentioned above, before even starting the make the prototype, I decided to make 2 scenarios where the users will actually use to mobile application to adopt a pet. This will help me to determine features that can be included in the app to increase user experience and also fulfils the user goals.
Scenarios:
To understand more the user scenarios, I have decided to make storyboards of each scenario, to get visuals and understand very well the user journey map and get to know frame by frame where certain can be implemented on the mobile application to facilitate the user to adopt a pet on the RSPCA mobile app.
Storyboard for Scenario 1:
Storyboard for Scenario 2:
Now that storyboard has been made for both scenarios, I can get understand and visualize what the target audience are actually looking for when using the app to adopt a pet on the application.
Before starting making the prototype on Figma, I decided to include the low fidelity wireframes that I have made in assessment 2 as it relates to the user goals.
Low Fidelity wireframes from Assessment 2:
Now that I have the low fidelity wireframes, I can make use of these wireframes as a guide to start making the prototype on Figma.
Now that I have finished the prototype on Figma comes the most important step which is the user testing. User testing will allow me to understand how real users actually find the app and also get feedback which features and components are working properly. This exercise will also help me to know features that are not working properly in the application. However, within the user testing exercise, I will do the A/B split test where it consists of including variations of certain screens to gauge the effectiveness and also get to know what the testers think about the variations.
AB SPLIT TEST
For the A/B split testing, I have decided to make Version A and Version B of the Following screens:
- Landing Screen
- Questionnaire Screen
- Adoption Application Screen
- Confirmation Screen
- Booking Screen
Now that I have all the materials, I have chosen 5 users to test my prototype and also do the A/B split test.
User Testing Video Links:
- User Testing 1: https://youtu.be/GbfPiXd5m_Q
- User Testing 2: https://youtu.be/1YxRhvZUIr0
- User Testing 3: https://youtu.be/oz2ZuvHr8cw
- User Testing 4: https://youtu.be/fcxSH3K-8xw
- User Testing 5: https://youtu.be/c4YKKwTU4CY
User Testing report:
Most of them was able to navigate easily throughout the app and also find that the user flow is very smooth from registration to pet adoption. As for the aesthetic part, most of them said that the prototype is very clean and neat where every component and elements in the application is very well aligned, there is visual hierarchy and spacing has been correctly used which make the prototype very professional and easy to navigate. In term of functionality, most of them found that every feature included was very simple and easy to understand. Reflecting back on their comments, I found that most of them really like the option of filter search as it enables user to find their pet of their choice which fulfils the second goals of the application. Another point that most of them said, is that on the adoption procedures screen, it was very helpful to know about the different steps to adopt a pet, and the way that adoption steps was broken was simple and effective.
Drawbacks & Improvements:
- At the beginning, the slide animation time-lapse must be extended to allow the user to read properly.
- On the Menu, some options are not working properly.
- To include video title on the pet fitness screens.
- To re check to prototype flow on the pet diet screen.
AB split test:
1. Landing screen: According to user responses on the landing screen, 60% of the users choose Version B for landing Screen as it more appealing and makes a first impression as entry point.
2. Questionnaire Screen: 60% of them choose Version A as it is much simpler for them to type their answers and they are not overcrowded with information unlike Version B.
3. Adoption Application Screen: 60% of the user chose Version B as they the validation option kind of give them a guide whether they are filling the right information before submitting the adoption application.
4. Confirmation Screen: All of them like Version B very much as it gives them a satisfaction in term of emotion and empathy that has been successfully submitted.
5. Booking Screen: 80% of them chose Version A as it much simpler to select date and time to make a booking.
Changes to be made of Prototype:
- Increase slideshow time-lapse.
- Recheck the option of Menu.
- Reflecting on the results for A/B split test, I will change the landing screen with Version B and include validation option on Version A and also change the Confirmation screen with Version B.
Final Prototype Link:
Conclusion:
To conclude, I have found that the user testing was very helpful for me as I have got to know the feedbacks of other user what features are working properly and what changes can be made in the mobile application to increase user experience. Overall, I was very satisfied with the prototype as I have followed correctly each step in the process from User Research to Prototype development.