SkillSwap

SkillSwap is a mobile concept for trading skills without money. You teach what you know, you learn what someone else knows. The interesting problem was never “build a learning app.” It was designing the conditions that make peer learning actually happen: clear discovery, enough trust to reach out, and scheduling that does not turn into ten messages of back and forth.

How might we help people find a relevant exchange partner, judge whether to trust them, and book a session, all without money changing hands?

I started by listening. A handful of short interviews with students and early-career learners surfaced the same story again and again: people want to swap skills, but the path from interest to a real session is full of friction.

Synthesizing those conversations, three insights shaped the whole product.

Two personas kept me honest about who I was designing for, and they pull in slightly different directions, which made the trade-offs sharper.

AKAishaLMLeon

Aisha

22

Student, new to the city

Aisha just moved to Göttingen for her master's. She wants to pick up practical skills like design and conversational German, but a student budget rules out paid courses. She is happy to teach what she already knows in return.

Goals

• Learn practical skills without paying for courses
• Find people nearby she can actually meet
• Offer a skill she is confident in as a fair trade

Frustrations

• Courses and tutors are too expensive
• She does not know who is credible enough to learn from
• Coordinating a time over chat never seems to work

Paid courses get expensive, content platforms feel passive, and communities are hard to navigate. Even when you find someone, the exchange falls apart without trust, structure, or a clear time to meet. So I framed a clear value proposition to design against.

• A fair trade

  No money, just a skill for a skill.

• Visible trust

  Credibility you can read before you commit.

• Availability up front

  When someone is free is part of the match.

• Local or online

  Both formats work, your choice.

• Reputation that grows

  Each completed swap builds standing.

• Just enough structure

  Guided exchange, not a paid marketplace.

I also audited how people currently learn skills. Each alternative solves part of the problem, but none covers fair two-way exchange, visible trust, and built-in scheduling together, which is exactly the gap SkillSwap targets.

Before designing a single screen, I mapped the full structure so every screen had a clear home: onboarding, a home dashboard, find-skill and post-skill flows, matches, profile, rate-user, and a settings menu. Getting this skeleton right kept the discovery and exchange flows simple later.

With the structure set, I sketched fast and broad in low fidelity, exploring how discovery, profiles, and posting a skill could feel before committing to any visual direction.

I mapped the primary task flow with explicit decision points, the two moments where people drop off: whether they trust the person enough to reach out, and whether both sides can lock a time. Designing those branches up front is what kept the happy path short.

The low-fidelity home was plain blocks: a “find a skill” search, a profile nearby, and quick actions to post a skill or check sessions. In high fidelity that same structure became a warm, scannable home, a personal greeting, a “Trending in Göttingen” feed, and a clear “Teach & Swap” split. Same skeleton, far more confidence. Drag the handle to compare.

Final

Wireframe

Drag to compare the wireframe and the final screen

Only once the flow held up did I move to visual design. A calm, trustworthy system: a confident blue primary, generous spacing, rounded cards, and clear hierarchy so the trust signals and the call to action always stand out.

The high-fidelity screens carry the exchange end to end, from discovery and search to a trust-rich profile, posting your own skills, and the request and scheduling flow.

View the interactive prototype in Figma

Back to the two people I started with.

This is a concept, so I frame the rest as what I would test next: less browsing effort because discovery filters around real exchange criteria, more confidence before connecting because trust shows up earlier, and less scheduling friction because availability lives in the request.

SkillSwap pushed me past screens and into behavior. It is not hard because of visual design. It is hard because peer learning runs on motivation, trust, fairness, and timing. If I took it further, I would validate the trust model first: a peer product can look polished and still fail if people do not feel safe enough to reach out.