GajiGesa App Revamp

ismarinii
Aug 28, 2022
2 min read

Updated: Mar 16

GajiGesa is a financial mobile application focused on services for Indonesian workers, where Earned Wage Access (EWA) is its flagship feature. In addition to salary withdrawal, this application has the secondary features where the users are allowed to do other transactions such as paying bills, doing top-up and investments.

Unfortunately, these secondary features were not discovered by the users despite their existing needs of the functionalities. This project of app re-design was done to improve the discoverability of these secondary features.

Who is this designed for?

This platform is designed for Indonesian blue collar workers who have no fair or formal sources for easy access to capital.

Why I did this project?

To improve the low numbers of active users, especially for the secondary features
More features on the app need to be added
To update the old design to become more aligned with current design trends

Old/Previous version of GajiGesa to revamp

Who did I work with?

Project Managers (PM), with whom I also did some user testings
Front-end developers
Back-end developers

What is my design process?

The process began with the project manager (PM) defining the requirements. These requirements included user persona, their needs, and the desired functionalities of the application.
After discussing the requirements with the PM, I did some design analysis from other existing apps (competitor apps or other platforms with similar cases) to observe the user experience and the interface design.
The low-fidelity design options were made after I combined the requirements and the design inspirations I observed from other apps.
Guerrilla testing was done using the low-fidelity designs to validate main functionalities.
After one of the low-fidelity design options were chosen and approved by the PM and the developers, I created the high-fidelity designs (where I used the components from our Design System library).
The last process was getting the feedback from our bigger team and stake holders, also from our users. The next iterations usually occured after collecting all the feedback.