A UX audit and redesign of the withdrawal experience - from a 5-screen flow with a vague date range to a streamlined 3-screen flow that surfaces the right information before you commit.
Robinhood popularized commission-free trading and turned a generation of casual investors into active market participants. With over 23 million funded accounts and a median user age of 31, it sits squarely at the intersection of fintech and everyday spending. Many users treat it as a hybrid savings-and-investing account - they put money in during bull markets and pull it out when rent is due.
This makes the withdrawal experience unusually high-stakes. Unlike a brokerage used for set-and-forget investing, Robinhood users frequently move money in and out. Yet the cash-out flow feels like it was designed for a once-a-year occurrence. It's buried, confusing, and most critically, it withholds the one piece of information users care most about: when will my money actually land?
"I tried to withdraw my balance and got an error about 'buying power' vs 'available cash' - I had no idea what the difference was. Took me three tries to figure out the right number."
Robinhood user, Reddit r/RobinHood
This case study documents the full UX design process: from research and persona development through problem definition, wireframing, and a final high-fidelity interactive prototype.
Before redesigning, I studied how Robinhood's withdrawal experience compares to best-in-class alternatives. The benchmark apps I looked at were Cash App, Wise, and Venmo - all of which have set the standard for friction-free money movement.
| Feature | Robinhood | Cash App | Wise | Venmo |
|---|---|---|---|---|
| Screens to withdraw | 5 | 3 | 5 | 3 |
| ETA shown before confirm | ✕ Only on review | ✓ On amount screen | ✓ On amount screen | ~ On review |
| Exact arrival date given | ✕ Range only ("4–5 days") | ✓ Exact date | ✓ Exact date + time | ~ Range |
| Available balance clearly labeled | ~ Small grey text below button | ✓ Prominent | ✓ Prominent | ✓ Prominent |
| Quick-amount shortcuts | ✕ Manual keypad only | ✓ Yes | ✓ Yes | ✓ Yes |
| Bank shown on amount screen | ~ Source account only ("From Individual") | ✓ Full bank name + last 4 | ✓ Full bank name + last 4 | ✓ Yes |
| Rich success screen | ✕ Not observed in flow | ✓ Animated | ✓ Timeline | ~ Basic |
The pattern is clear: Robinhood is an outlier on almost every dimension. Every competitor has solved these problems. This isn't a technology limitation - it's a design prioritization gap.
of Robinhood users withdraw money at least once per quarter. For many, it's a monthly action tied to rent, bills, or emergency spending.
A common reported frustration is not knowing the exact withdrawable amount, and confusion around when transferred funds will actually be available in their bank account.
Redesign Robinhood's cash withdrawal flow so that a user can complete the task in under 30 seconds, with full visibility into their available balance and expected arrival time - without ever leaving the primary task flow?
From the home screen to a confirmed withdrawal, the current flow spans 5 screens and around 7 taps. The issue isn't the step count - it's the information that's missing or deferred at each step.
⚠️ = screen contains deferred or missing decision-relevant information
Walking through the current app flow reveals six distinct friction points, each of which either confuses users, forces them to backtrack, or withholds information they need to proceed confidently.
The redesign reduces the 5-screen flow to 3 by adding a direct Withdraw action on the home screen, then combining amount entry, bank, speed selection, ETA, and confirmation onto a single screen—so you commit only after seeing the full picture.
Use the buttons below each phone to step through both flows. Left = current UI; right = the redesign.
Every design decision targets a specific pain point observed in the actual app. The goal was to stay within Robinhood's existing visual language while reorganizing the information architecture.
The current flow requires navigating to Menu → Transfers to find the Withdraw option. The redesign adds a direct "Withdraw" entry point accessible from the home screen, the same pattern Cash App uses with its "Cash Out" button on the main balance view. Frequent actions should have short paths.
Currently "$421.80 available" appears as small grey text below the Continue button, after the keypad. The redesign promotes this to a green chip at the top of the screen, paired with a Max button that auto-fills the limit. Users who want everything out shouldn't need to read a number and retype it manually.
The current amount screen is a plain numeric keypad with no preset options. The redesign adds $200 / $500 / $1000 / Max chips, a standard pattern in Cash App, Venmo, and Wise that reduces input time and errors. The selected chip is highlighted using Robinhood's existing black-button style.
Standard vs Instant currently appears on the review screen, after the user has already tapped Continue on the amount screen. If someone needs Instant but sees this late, reversing requires going back and re-entering. Moving the speed cards to the amount screen means the choice is made with the amount, not after it.
The current review screen says "it may take up to 5 business days." The redesign shows a specific date - "by Thu March 25" for Standard, "today ~3:45 PM" for Instant. This matches what Wise and Cash App display. A specific date is actionable; a range is not. This is the same information, better presented.
The current flow shows bank context only on the review screen. Adding "To: Chase Checking ••1575" inline on the amount screen means users with multiple linked accounts can verify the destination without backing out. This removes a common reason for flow abandonment and re-entry.
The current confirmed state (not observed in this flow's screenshots, but typical) shows generic transfer text with no specific date. The redesign adds an exact arrival time and a two-step status indicator. This converts a dead end into a clear closure state that tells users exactly what to expect next.
The redesign uses white backgrounds, Robinhood's black pill buttons, the same "From Individual" account labeling, and the existing ⚡ Instant / Standard card pattern from the review screen. The goal is to feel like a natural evolution of the existing app, not a redesign that requires relearning.
Good UX design isn't finished at prototype - it needs to be tested against real behavior. Here's how I'd validate each major design decision.
| Hypothesis | Test Method | Success Metric |
|---|---|---|
| Home shortcut reduces time-to-withdraw | A/B test: current Menu → Transfers path vs direct home entry on 5% of users | >20% reduction in median time from app open to amount entry |
| Max button reduces manual entry errors | Track failed withdrawal attempts (insufficient funds errors) before and after | Measurable reduction in failed withdrawal submissions |
| Quick-amount chips reduce time-on-amount-screen | Session time measurement on the amount screen before and after | >25% reduction in time from landing on amount screen to tapping Continue |
| Upfront speed selection reduces back-navigation | Track how often users go back from review screen to change speed | Reduction in back-navigation from review screen; directional shift acceptable |
| Exact arrival date improves satisfaction | In-app survey (1 question) after withdrawal: "Did you know when your money would arrive?" | >80% yes in redesign vs baseline |
| Overall withdrawal completion rate improves | Funnel analysis: home → amount screen → review → confirmed | >10% improvement in end-to-end completion rate |
A few things worth investigating before shipping: Does showing the speed choice earlier (on the amount screen) increase or decrease Instant transfer adoption - and does that affect revenue? Does the home shortcut cause accidental withdrawals for users who were just checking their balance? And does the specific arrival date need a caveat for weekends and bank holidays?
The Robinhood withdrawal flow doesn't need to be rebuilt from scratch - it needs its information architecture reorganized. The app already shows users the right data: available balance, destination account, transfer speed, and cost. The problem is that this information arrives too late, in the wrong order, or at the wrong visual weight.
The redesign moves all decision-relevant context to the moment of decision, the amount screen, so that by the time a user taps "Review," they already know exactly where the money is going, how fast it will arrive, and what it costs. The review screen becomes a true confirmation, not a discovery screen.
The best financial UX doesn't make decisions for the user. It makes sure the user has what they need to decide for themselves before they commit.