Case Study
The Project
Tidewell is a self-initiated concept for a mobile banking app built around everyday money tasks. It is fictional: there is no client and no real bank. The project is a 13-state clickable prototype designed around one idea, that clarity builds trust.
The Problem
How might a mobile banking experience make everyday money tasks feel clear, trustworthy and easy to navigate without overwhelming the person using it?
A design question I framed for this exercise. It is not based on research.
The Goals
The Thinking
The Process
No user research, interviews or usability testing were done. The checks were functional, not research.
The Interface
Eight of the 13 states, shown as they appear in the prototype.
The Interaction
Primary flow:
Error and recovery:
Inside the screens: Activity has search, filters, a skeleton loading state and an empty state. Cards has a freeze control. Pay a Bill and Create Account validate their fields. In Send, enter ₱60,000 to see the error state.
Design Decisions
They say what happened and how to fix it, with an icon and text, never color alone.
Radio-style cards for two or three options: recipient, transfer speed and biller.
Shown only in account creation, the one genuinely multi-step flow. Welcome has a skip.
Skeleton loading and a clear empty state on Activity.
Tabular figures and consistent ₱ formatting keep amounts easy to compare.
44px touch targets, visible focus and On or Off text on switches.
Reflection
Tidewell shows how I approach hierarchy, forms, states and trust in a product where mistakes matter. Because it is a concept, it has not been tested with people. The next step would be usability testing of the Send flow.
Concept only. Tidewell is not a real bank, and no real data, users or results are shown.