When someone opens a financial app, they are already in a high-trust moment. They are about to make a decision about their money. Every millisecond of loading, every confusing label, every unclear button costs trust — and trust is what fintech products run on.
SalaryNow helps employees access money they have already earned, without paperwork or high-interest loans. The Android app needed to make a novel financial concept feel immediately understandable — and safe.
My first priority was clarity. The earned-wage access model is unfamiliar to most users. The app had to explain what it does before it could ask for any commitment. I worked on the onboarding flow and dashboard to make the value proposition visible before the user takes any action.
In Kotlin, I built the screens that display a user's earned balance, their accessible amount, and the withdrawal flow. Every number needed to feel accurate and real — not estimated, not approximate. Users needed to see a figure they could trust.
The biggest mobile-specific lesson was about states. Empty states, loading states, error states, and success states all need as much design attention as the happy path. In financial apps, an ambiguous error state does real damage to user confidence.
Impact beyond the screen
- Contributed Android (Kotlin) development for the core SalaryNow mobile experience.
- Built earned-balance display and withdrawal flow screens.
- Improved onboarding clarity to explain a novel earned-wage model to first-time users.
- Designed robust state handling — loading, error, success — to maintain trust throughout the flow.
Lessons from the work
- Trust is the product in fintech — every design decision either builds it or erodes it.
- Empty and error states need as much care as the happy path.
- Explaining a new concept clearly is harder than building the technology behind it.
- Mobile-first financial design demands speed: every extra tap costs user confidence.
