.png)
PlutoPay, The Only Finance App You Will Ever Need.
Welcome to the PlutopPay case study. Here I will walkthrough the process of how it was created. Plutopay was part of my UX Design course.
Plutopay is an all in one solution for combining many different pay accounts cards & currencies. It is designed to be an complete solution for all your finance needs wether that is just to make simple payments or even if you deal with various currencies on a daily basis. The app is aimed at anyone who wants to easily manage everything.
Stage 1 - The Problem & Potential Solution
With all the different payment options, account and currencies available nowadays I believe that there is a great need for an E wallet that could combine everything together. I defined my problem statement and then thought about potential solutions.
Problem Statement:
Shoppers need a way to combine different payment providers and currencies securely because it is hard to manage so many different accounts. We will know this is true when we see users managing and making payments through the portal.
Potential solutions:
An E-Wallet solution that allows multiple payment providers & multiple currencies (standard & digital) to be added in one easy to use wallet. It shows the currency or payment provider with the least fees or highest rewards for the transaction. The solution would be secured using 2 step authentication and also blockchain technology for encrypted, de-centralised user data storage.
I then did some user research, including surveys and interviews to confirm if my assumptions were correct. These were confirmed so I knew I had the start of a solution and could move forward. I also conducted competitor research to see what was already available and how they worked.
Stage 2 - User Personas, User Journeys & User Flows
Creating the personas made it easier for me to get inside the minds of different types of users. I could better understand how, why and what the specific goals would be for using the app, and this in turn allowed me to plan for a better solution. This also reconfirmed that there was a problem that needs solving. So the persona needed to get from their entry points to their goals with the least amount of friction.
.png)
Stage 3 - Sitemap, Wireframes and Prototypes
Now I could base the sitemap off the user flows and build on it, I ran a card sorting exercise to see how would be best to group the various sections and the results had been apparent that a tools section was needed. I was confident this was the right way, are many different things that people would want to do with their funds cards or accounts. The card sorting had also confirmed that my sitemap was logical. So I went ahead and created some wireframe sketches of the pages as the sitemap. Along the way I was always trying to think about the best and easiest way to make for the user. The low fidelity prototype was tested with users and the flows were working without a problem, this then showed me it was time to move to create the mid fidelity prototype. This was then the same moving from the mid to the high fidelity prototype.
It stayed nearly the same I just added a tools section as that is what the results of the card sorting showed.
The Wireframes were turned into a low fidelity prototype and tested for usability. As no issues were found I moved to the Mid fidelity prototype.
Again usability testing was done and no issues were found so I moved on to building the high fidelity prototype.
The prototype can be found Here
Stage 4
Now I had a high fidelity prototype built so needed to confirm that it was good, I ran user tests and found a few usability issues for one screen, so changed the design slightly and retested. Whenever there seemed to be a slight problem I would make changes and then retest. The testing had confirmed that the designs were heading in the right direction, getting more and more user friendly. Then I concentrated on polishing the design, ran a preference test to confirm which home screen would be better & took inspiration from Material Design.
Small changes made from the results of testing, I labeled the search box better.
Then I retested and found there still to be issues, so I changed the design again, this time in to a 2 page sequence to give more information about the process
.png)
Now it’s a case of refining and testing until the web app is complete.
