Skip to content
Yusuf Mohammed-Ali
WorkAboutContact
Lagos --:--, GMT+1Résumé

© 2026 Yusuf Mohammed-Ali

  • LinkedIn
  • Contra
  • Behance
  • Dribbble
  • Résumé
All work

TimeSwapr

A time bank that lets neighbours trade an hour of help for an hour of help

Role
Solo Product Designer, with a UX writer
Timeline
3 months
Platform
iOS / Android app
Type
Self-initiated concept, usability-tested

Chapters

  1. 01Thinking
  2. 02The opportunity
  3. 03Defining success
  4. 04Constraints
  5. 05The job to be done
  6. 06What testing showed
  7. 07The decision
  8. 08The trade-off
  9. 09Priority
  10. 10Learnings

TimeSwapr is a time bank: an hour you give earns an hour you can receive. I designed it end to end, from a survey and competitive audit to a Maze usability test that reshaped the app's most important screen.

TimeSwapr home screen on a phone held by a window

01 / Thinking

Helping each other, without money changing hands.

People want to give back but lack the time, connections and resources, and many people with real needs can't pay for help. My survey backed this up: respondents listed what they could offer (tutoring, tech help, mentoring, childcare) and why they'd take part (personal growth, relationships, reciprocity).

The goal was a simple app where an hour you give earns an hour you can receive, usable by everyone from people in their early 20s to people in their 60s and beyond. Usability testing in Maze showed people couldn't tell an offer from a request, and restructuring that one screen became the key decision of the project.

02 / The opportunity

A time bank that feels like a modern marketplace app.

Time banking already exists, in Timebanking UK, Time Republik, Time Auction and Simbi. The opportunity was to make it feel like the apps people already use: browse, book, meet, rate.

03 / Defining success

Three things had to be true.

Easy first exchange

Sign up, pick skills and interests, and book or offer a service in a few steps.

Strangers feel safe

ID verification, a security code for in-person meetups, and mandatory mutual ratings.

People come back

A TimeCoin balance, leaderboards and badges, used sparingly.

04 / Constraints

  1. 01

    Trust without money.

    With no payment to dispute, trust had to come from identity, ratings and meetup security.

  2. 02

    A wide age range.

    From the 20s to 60s and beyond, so the interface had to stay plain and readable.

  3. 03

    A two-role model.

    The same person can be a Contributor, who offers, and a Requester, who requests, so labels and flows had to make the role obvious.

05 / The job to be done

Member

“When I need a hand with something I can't pay for, I want to find someone nearby who can help, and give my own time back later.”

The exchangeView offer or requestBook a timeAuthor acceptsChatMeet with a codeRate each other
Confirm booking: the TimeCoin cost shown before you commit
Confirm booking: the TimeCoin cost shown before you commit

06 / What testing showed

Offers and requests looked the same.

In the tested version, offers and requests were mixed on one page, alongside an All Services tab, and their cards looked alike. The Maze test showed two things: people couldn't tell which card was an offer and which was a request, and having both on the same page confused them.

07 / The decision

Split by intent, then by status.

I removed All Services and separated the tabs by what the person is doing, offering or requesting, then by where the exchange stands: going, pending, past. Category and mode badges (in person or virtual) were harmonised across cards.

  1. 01

    It fixes the exact confusion the test surfaced.

  2. 02

    Each tab answers one question, like “What can I get?” or “What's coming up?”

  3. 03

    It makes the Contributor and Requester roles visible without explaining them.

Tested: offers and requests mixed, with an All services tab
Tested: offers and requests mixed, with an All services tab
Shipped: Offers, Requests, Going and Pending, each its own tab
Shipped: Offers, Requests, Going and Pending, each its own tab

08 / The trade-off

People lose a single “see everything” view, but they always know what they're looking at.

09 / Priority

Core, designed and tested

  • Onboarding with skill and interest setup
  • Home: TimeCoin balance with request and offer actions
  • Services: offers, requests, booking and the exchange
  • Messaging
  • ID verification and the meetup security code

Supporting

  • Group sessions
  • Leaderboards and badges
  • Settings and profile
Leaderboard: top dealmakers
Leaderboard: top dealmakers
Badges, used sparingly
Badges, used sparingly

10 / Learnings

  1. 01

    Test the model, not just the screens.

    The confusion wasn't visual; it was two concepts on one page.

  2. 02

    Trust is a feature set, not a badge.

    Verification, meetup codes and ratings work together.

  3. 03

    Words are design.

    Working with a UX writer sharpened the labels, Contributor and Requester, and showed me how a writer works through a flow alongside the design.

Next case study

All work
Global Rights CSO DashboardTurning a static report on Nigeria's civic space into a live state ranking