Candidate assessment · UI conceptGamification / Onboarding / Interface design

PocketWise

A growing plant. A way to gamify saving.

Overview

I designed PocketWise as a finance-app concept combining savings progress with a growing plant and calendar-led spending preparation. My work covers the concept, onboarding and interface design.

My contribution
Concept, onboarding, interface design & visual identity
Context & output
Four-day design exercise · Static interface concept
PocketWise welcome, calendar connection and dashboard concept screens.
Inputs

What did the app review help me prioritise?

Trust and tone

I tried Cleo and Emma and read public reviews. Clear data explanations, onboarding progress and encouraging messages stood out as patterns I wanted to carry into PocketWise.

Planning around personal events

Calendar-led planning around personal events was missing from the apps I reviewed. I made pre-planning a priority alongside spending summaries and reminders.

Concept

Make growth the idea and identity.

Saving as growth

The brief focused on onboarding and proactive financial advice. I developed the plant mechanic to give saving progress a visible form: a seed, plant and longer-term tree or forest.

Handwritten PocketWise idea map connecting pre-planning, trust and engagement with a growing-plant metaphor.
Original ideation. The plant-growth mechanic emerged alongside ideas for transparency and pre-planning.

A plant-and-pocket identity

I designed the logo as a plant emerging from a pocket, with a pale teal palette and a lower-right forward action on the welcome screen.

PocketWise welcome concept with a plant-and-pocket motif on pale teal and a forward action at the lower right.
Welcome: the plant-and-pocket identity and lower-right action.
Onboarding

Explain the value before asking for data.

Connection requests ask for trust, so I planned the explanation first. The flow introduces what PocketWise does and why data is needed, then asks about personal context and notification preferences before the proposed bank and calendar connections.

PocketWise onboarding flow from product explanation and data transparency through context, notification preferences, bank and calendar connections and the growth dashboard.
Early flow: product and data explanations come before connection requests.

Paper wireframes gave the sequence a layout, with space for progress, context questions and skip options. This kept the ordering decision visible as the screens took shape.

Six early paper wireframes showing welcome, explanation, data transparency and personal context, with progress and skip controls.
Paper onboarding: product explanation and data transparency precede the personal questions.
User control

Keep choices visible and the tone supportive.

Context questions

I kept Skip visible alongside the context questions. Labelled choices and radio-button shapes add cues beyond colour, reflecting the accessibility priorities I explored during ideation.

PocketWise context questions with labelled radio choices, a progress bar and a skip option.
Later context screen: Skip remains visible above the labelled choices.

A manual calendar alternative

I explained why calendar data would help before offering Apple, Google or manual entry. Help stays available so someone can decide what to share and how.

Calendar connection concept with service options, help and a manual alternative.
Later calendar step: manual entry offers an alternative to a service connection.

Advice with a response

I used a conversational tone for accepting, adjusting or dismissing advice, showing “Adjust Goal” and “Sounds good”. Contrast, plain language and a supportive tone remain accessibility priorities to evaluate.

PocketWise notification explanation describing accept, adjust and dismiss choices, with a two-button sample.
Later notification explanation, with an example event-related suggestion.
Pre-planning

Connect upcoming plans with spending choices.

I sketched the growth hub and planning views together, linking progress with upcoming expenses. These layouts gave the plant mechanic a place beyond onboarding.

Three paper sketches connecting a growth hub, upcoming-expense plan and calendar view.
Early planning layouts connect growth, upcoming expenses and a monthly view.

The dashboard brings plant progress, a weekly report and upcoming events into one view. The calendar links example savings suggestions to upcoming events, so the concept supports planning ahead as well as reviewing past spending.

PocketWise dashboard concept showing plant progress, an example weekly report and upcoming events.
Dashboard: progress and upcoming plans share one view. Figures are illustrative.
Calendar concept showing upcoming events and example saving suggestions.
Calendar: the gym, night out and team lunch each have an illustrative suggestion.
Conclusion

Bring motivation and planning into one concept.

PocketWise brings motivation, event-led planning and visible choices into one interface concept, with a growing plant making saving tangible and calendar-led pre-planning helping people prepare for spending before it happens. The main design thread is explaining a request before asking people to act on it.

The next step is to evaluate whether people understand the suggestions and can continue without connecting a calendar.

From there, the app could develop through a tiered subscription that rewards good financial habits with a reduced fee, deeper AI pre-planning through email and Apple Wallet integration, and a built-in calendar that turns screenshots of bookings and tickets into planned spending automatically.

Keep exploring

Next / UX/UIMountain WarehouseAll UX/UI work →

Image detail

View original ↗