← All work
2026In testing
Case study 02 · iPhone app · Built solo with AI

FairFive: pickup football, made fair.

Reserve a spot, balance the teams, pick a format that fits the pitch time, and run a clock nobody argues with. A complex system, kept simple for the person holding the phone at the pitch.

In testing with 30+ real players
FairFive onboarding: Step into the game
FairFive home: Play now, Plan a game, Have a code
FairFive: teams are made, Blaze and Volt
FairFive live match clock
FairFive session summary
My role
Solo, start to finish: research, UX and UI, flows and rules, brand and characters, and the build, with AI
When
31 Oct to 19 Nov 2026 · about 3 weeks to a tester-ready app
Team
Just me, with AI. No software engineers so far
Status
On TestFlight with 30+ testers · 6 builds
At a glance

At a glance

Problem

Pickup football runs on group chats and goodwill. Who's actually coming, who plays with whom, how long each match lasts, and who sits out are all argued on the spot.

What I made

  • 97 screens across 11 flows
  • Rules for four match formats
  • Logo, brand and an illustrated cast
  • The app itself, built solo with AI

The stance

  • One main action per screen
  • Skill tiers stay private to the host
  • Never leave a player out silently
3
weeks to a tester-ready app
30+
testers on TestFlight
1
person: design and build, with AI
230
unit tests on the rules
6
native builds
148
commits
01 · The problem

The game is simple. Organising it isn't.

Every weekly pickup game has the same problems. I play in one every Friday, so the first ideas came from my own games: "it's usually 10 minutes or 3 goals," and "a real keeper gives his team a big edge."

  1. Organising is messyThe organiser chases people on WhatsApp, and someone drops out an hour before.
  2. Teams cause argumentsCaptains pick friends, one team is stacked, and it's over in ten minutes.
  3. Formats are guessworkFour teams and a 2-hour booking: how long is a match, and who sits out?
  4. Time causes argumentsWhose phone is timing? How much time was lost when the ball went over the fence?
  5. Uneven numbers13 players for 5-a-side, one real keeper for two teams, and late arrivals.

FairFive isn't a league platform or a betting app. The motto that guided every screen: complex system, simple experience. One main action per screen.

02 · Who it's for

Built for the person who gets blamed.

Primary: the organiser of a weekly pickup game. They book the pitch, collect the names, and get blamed when the teams are unfair. Usually 10 to 25 players, 5 or 6-a-side with a keeper, and a 1 to 2 hour booking. Secondary: the regular player, who wants to know they're in, see the teams and trust the clock, without joining another social network.

The context: friends' groups of 20 to 40 people, a strong Egyptian and Arab community, first launched in New York City and built to work anywhere. The personas come from the real people and situations that shaped the features, not from a formal survey.

KarimThe weekly organiser · primary

30, runs a Friday 5-a-side for a crew of about 30 and books the pitch for 2 hours. Chases confirmations, loses players last minute, and gets accused of stacking teams.

Built for them: one link to share, a waitlist that fills itself, private tiers, fair teams in seconds, a plan that fits the booking, early teams.

OmarThe keeper who plays outfield too

Strong in goal, average outfield. Based on my own case: "I'm a flying keeper, but my hand hurts, so I play outfield now."

Built for them: separate in-goal and outfield levels, In goal or Outfield chosen each game, and No keeper, take turns.

JakeThe player who just shows up

Doesn't organise. Wants to tap a link, see You're in, know the kick-off and the place, and see his team.

Built for them: Have a code?, join and waitlist alerts, the teams and plan, the live table, Can't make it.

NourThe group admin

Helps run a 40-person group. Isn't always hosting, but helps when she plays.

Built for them: Groups, invites, admins who become co-hosts when they're in the game, Remove from game.

The walk-inNo account, no app

Turns up at the pitch on the night.

Built for them: added by name at check-in with a default tier, and kept as a guest on the teams.

03 · How it grew

Three weeks, one Friday at a time.

It started as Pitchside, a tournament organiser. Each step below came from a real game, a tester or a host.

  1. 31 OctBrief"Pitchside": plan a game, balance teams, choose a format, run a clock.
  2. 1–2 NovRules firstRound robin, mini tournament and winner stays on, and balance by skill tier. Then the screens.
  3. 2 NovReal-game detailsA goal limit, a confirm before the deciding goal, stoppage time and keeper tiers.
  4. 2–3 NovPlay nowStart at the pitch and add people by name. It became one of the three main buttons.
  5. 3–4 NovFairFiveRenamed for 5-a-side, the real target. A "Matchday" direction from my mood board.
  6. 4 NovOriginal charactersThe famous-player caricatures felt naive, so I dropped them.
  7. 5 NovArabic and LightEgyptian Arabic the way Egyptians talk about football, and a designed Light mode.
  8. 5–9 NovReal-world flowGame codes, late arrivals, the fullest teams play first, whole-pitch-time matches.
  9. 7–11 NovFriends, then GroupsGroups came from a tester: every crew has a group chat of about 40 people.
  10. 8–17 NovPlacesSearch like a maps app, a New York pitch list and map, and Book on the pitch's own site.
  11. 17–18 NovHosts' realityRemove a player, co-hosts, teams early, one editor at a time, add pitch time.
  12. 18 NovClean-upHelper text moved behind a small ⓘ. Each screen keeps only what you need now.

What never changed: fairness first, the organiser is whoever made the game, players never see their own tier, and there's no chat, feed, betting, penalties or bans.

04 · Research

How pickup football actually works.

Rules

Formats that never get stuck

Round-robin pairing, re-pairing semi-finals across tournaments, streak limits, extra time against penalties, stoppage time. It became a rules engine with 230 unit tests, run with 3, 4 and 5 teams, 15 to 25 players and 90 or 120 minute bookings.

Fairness

What "balanced" means

The sum of skill tiers per team, with subs counted at the squad average. "Good balance" means at most 0.4 tiers apart per place on the pitch. The app never shows a fake accuracy percentage.

Edge cases

About 20 real-world cases

No-shows, late arrivals, games never closed, too few players, overlapping games, people with the same name. All written down and decided on 9 Nov.

Language

Arabic as Egyptians say it

How people actually talk about a game and a tournament, so the Arabic reads naturally, not like a translation. Changa and IBM Plex Sans Arabic, with Barlow Condensed for timers.

Platform

App Store and iOS

Sign in with Apple, account deletion, Report and Block, Live Activities for the Lock Screen clock, and how TestFlight updates reach testers.

Places

Every field in New York

NYC Open Data for every park with an active soccer field, plus indoor centres checked by hand. FairFive points to the booking, it doesn't sell it.

05 · Every flow, every screen

97 screens, in the order you'd meet them.

Pick a flow, then scroll through it. Each flow runs from first tap to the end of that job, including the empty and edge-case screens.

Everyone is already at the pitch. From an empty account to match 1: set the time, add who’s here, make teams, pick a format, play.

  1. Play now: Home, tap Play now

    01Home, tap Play now

  2. Play now: Set the time

    02Set the time

  3. Play now: Just you so far

    03Just you so far

  4. Play now: Add each friend

    04Add each friend

  5. Play now: Add player · in goal or outfield

    05Add player · in goal or outfield

  6. Play now: Everyone’s in

    06Everyone’s in

  7. Play now: Pick the teams

    07Pick the teams

  8. Play now: Teams are made

    08Teams are made

  9. Play now: Choose how to play

    09Choose how to play

  10. Play now: The plan

    10The plan

  11. Play now: Match 1 is on

    11Match 1 is on

06 · Fair teams

Balanced from a level nobody else sees.

The host gives each player a private skill tier from 1 to 5. FairFive uses the tiers to balance the teams, and only the host ever sees them, enforced in the database. Players can state their own level as a hint, but it never counts. Try a simplified version below.

Example players and tiers
Set skill tier: a private sheet only the host sees
Uneven count: extras join as subs on the lowest teams
Adjust teams: skill total per team, with a lock on players who must stay
Set skill tier · Uneven count · Adjust teams. The host can still swap anyone; the app shows the skill total per team.
07 · Four formats

Every format knows who plays next.

I wrote the rules as tables for the build to follow, not just screens. Each format defines who plays whom, what happens on a draw, when the night ends and what happens when time runs short, so the app never gets stuck in a state nobody planned for.

08 · The clock

One clock everyone trusts.

Live match, host view 01 · Live

Kept on the server, not on one phone.

Everyone's phone shows the same time. The timer digits never animate, in any setting, so the number is always readable at a glance. One main button: pause.

Paused match 02 · Paused

Pause with a reason.

Injury, dispute, ball lost. The bar and glow turn orange instantly, so nobody wonders whether the clock is running.

Stoppage time in red 03 · Stoppage

Stoppage counts down in red.

Time lost to pauses is added back, played once at zero if it fits, and always taken from the session time. The summary reports any match that didn't fit.

Table during a match 04 · Table

The table, over the match.

It opens on top of the live screen while the clock keeps running. The running match counts once it's confirmed.

Hand over the clock 05 · Hand over

The host can hand over the clock.

Another player runs it on their own phone and account. One timekeeper at a time, and the host can take it back instantly.

Lock Screen live activity 06 · Lock Screen

The score without unlocking.

A Live Activity on the Lock Screen and the Dynamic Island shows the score and time. Red in stoppage, orange when paused.

09 · Decisions

Decided on paper, before a single pixel.

These are from the decisions log in my user-flows file. Each one closes a question that would otherwise turn into an argument at the pitch.

  1. Players never see their own tierIt avoids the "why am I Tier 2?" drama. Enforced in the database, not just hidden on screen.
  2. Balance beats preferencesA teammate request is honoured only if the result is exactly as balanced as the best line-up.
  3. Nobody is left out silentlyOne or two extras become subs on the lowest teams. Three or more form a short team with jokers.
  4. The fullest teams play match 1So anyone still on the way can make the next match. Late arrivals keep their place.
  5. No-shows are counted, never punishedOnly the organiser sees the count. No bans, no scores.
  6. Only honest labels"Good balance" or "Needs review", never a fake percentage. Winner stays on is called competitive, never equal.
  7. A server clockTime comes from server timestamps and pauses, so every phone shows the same time. One timekeeper at a time.
  8. Friends, no chatFriends and groups are the only social features. No chat and no feed.
FairFive user flows: the host from invite to session summary, the player from invite link to history, the running session menu, and the decisions made while designing.
The user flows board: host, player and the running session, with decision points in orange.
10 · How it changed

From a dashboard to a game.

The first high-fidelity screens worked, but they read like a dashboard: lime cards, small type, every option at the same volume. Over the following rounds the app got louder where it matters and quieter everywhere else. Drag to compare.

  • HomeI sketched on a screenshot that Home should show what the app does at a glance. It became three big ways in: Play now, Plan a game, Have a code?
  • Game pageOne headline, one main button that follows the game's state, and the code to share right under it.
  • New gameA loud header with a character, and the form grouped into When, Who and Where.

Finding the colour

My own note on 4 November: "80% black and lime, use the other accents." Early boards tested a lifted charcoal and colour-blocked cards, then the Play now screen went through rounds of its own: soft colour cards, outlined cards, a scoreboard layout and tiles, before settling on one rule: solid colours, no gradients, and only the main button is raised.

Colour directions: the current near-black and lime, A Floodlight with lifted charcoal, and B Matchday with colour-block cards.
Colour directions: current, A · Floodlight, B · Matchday.
  1. Play now v2 A

    v2 A

  2. Play now v2 B

    v2 B

  3. Play now v3 scoreboard

    v3 scoreboard

  4. Play now v3 result first

    v3 result first

  5. Play now v3 tiles

    v3 tiles

  6. Play now colour v3 lime accents

    colour v3 lime accents

  7. Play now colour v3 lime tone

    colour v3 lime tone

  8. Play now colour v3 one colour each

    colour v3 one colour each

  9. Play now, final

    Final

11 · Testing

Tested where it counts: at real games.

I used the app on my own iPhone every day, first in Expo Go, then development builds, then TestFlight, with changes going out in minutes. More than 30 testers, friends and regulars from my games, joined real planned games and sent screenshots and screen recordings of problems, often with the problem circled. I also ran usability tests, watching people try to join with a code, and hosts ran real games and told me what they needed.

A tester's screenshot of a real game page, with an arrow drawn to Open in Maps. The game code and host name are blurred.
Marked up on a real game page.
A screenshot of a group's games, with an arrow to the 6/20 player count in lime on white. The host name is blurred.
The 6/20 count, lime on white: too faint to read.
Play now in Egyptian Arabic and Light mode, on a real iPhone.
Egyptian Arabic, Light mode, on a real phone.

Screenshots from testing. Names and game codes are blurred.

What they said, and what changed

  1. 9 Nov · Tester

    A tester's iPhone 16 screenshot: the layout looked squeezed.

    Layouts scale with the screen width everywhere.

  2. 10 Nov · Tester

    A tester: every crew has a group chat of about 40 people.

    Groups, with codes, links, invites, admins and game alerts.

  3. 12 Nov · Tester

    Testers: most installs were 2 or 3 versions behind.

    The app checks for updates at launch and shows a New version notice.

  4. 12 Nov · Tester

    Usability test: people typed group codes into Join a game and thought it failed.

    One Have a code? box for every kind of code.

  5. 18 Nov · Host

    A host: "I can't remove anyone who joined."

    Remove from game, for the host and co-hosts.

  6. 18 Nov · Host

    A host: make teams as soon as the game is full, and send them out early.

    Teams early: Make teams now or Later, then Send to players.

  7. 2 Nov · My own test

    "A real keeper gives his team a big edge."

    In-goal tiers and a keeper bonus in the balance.

  8. 3 Nov · My own test

    Names too small, and "lots of people are called Mohamed".

    Bigger names, full names, and a way to tell the same names apart.

  9. 6 Nov · My own test

    Late arrivals changed the balance, but the teams didn't react.

    Arrived, Didn't come, subs move up, and the balance label updates.

  10. 7 Nov · My own test

    The keyboard covered the Location field.

    Keyboard-aware forms across the app.

  11. 18 Nov · My own test

    Lime text on white fails accessibility; buttons overflow at some sizes.

    Readable colour variants, and buttons checked at 320 pt, Larger Text and Arabic.

  12. 18 Nov · My own test

    Add pitch time only offered 15 or 30 minutes. "We usually add an hour."

    A stepper from 15 minutes to 3 hours, starting at an hour.

  13. 18 Nov · My own test

    Helper text under every option felt cluttered.

    Helper text moved behind a small ⓘ.

What kept coming up

Versions

Testers kept landing on old TestFlight builds. It was the most common issue, and led to the in-app update check.

Game-day mess

Late arrivals, removals, extra pitch time, early teams. Hosts kept finding situations the first design didn't cover.

Real devices

Screen sizes, Light mode contrast, Arabic type, a keyboard covering a field.

Codes and links

People don't know what kind of code they have, and they shouldn't have to.

Game full: make teams now or later
Teams earlyA host's idea: when a game fills, make teams now or wait for game day.
Someone is making teams
One at a timeTwo co-hosts could edit at once, so only one person edits; others wait or take over.
Add pitch time
Add pitch time"We usually add an hour", so one stepper starts at an hour.
Have a code?
One code boxPeople typed group codes into Join a game, so every code goes in one box.

The rules engine has 230 unit tests. A concurrency test has 20 people join at once, with the last spot claimed in one database transaction, and every screen is checked in Light, Dark, Arabic, 320 pt width and Larger Text before it ships.

12 · The brand

A pitch that reads as a five.

The working title was Pitchside. I renamed it FairFive because 5-a-side is the real target, and fairfive.app was available. The brand direction, "Matchday", came from my own mood board. Three ideas for the mark to start: a stopwatch ball for the fair clock, a number 5 shirt for five-a-side, and a pitch whose centre circle is an equals sign. The final mark combines the last two: the top touchline, the halfway line and half of the centre circle draw a 5, with the equals sign inside it.

Bold editorial sports, dark first.

NightThe pitch at night. Dark is native, not inverted.
LimeThe one main action per screen.
OrangeLive states, pause, a team colour.
PurpleFormats, fairness, a team colour.

07:42

Barlow Condensed · headlines, timer, scoresLoud, tall and condensed, so a timer reads from across the pitch.

Inter · body and labelsNeutral and legible at small sizes, for everything you read up close.

Motion rules: tap 150 to 250 ms, card 250 to 450 ms, reveal 500 to 800 ms with a spring, kick-off countdown, instant pause, and a 100 ms cross-fade with Reduce Motion.
Motion explains state changes, never delays an action, and never touches the timer digits.
13 · The characters

Original players, never real ones.

The app needed warmth for its big moments: welcome, you're in, teams ready, winners, loading. The style took four rounds to find.

  1. A football icon set with black outlines and flat lime, orange and purple fills.
    1 · IconsBlack outline, flat brand fills. Good for stickers, too small for a hero.
  2. Flat outlined players in brand colours: runner, striker, keeper, celebrating, referee and juggling.
    2 · Flat playersThe same style as the icons. Friendly, but it felt like clip art.
  3. Illustration tests made with Figma AI: a painted street scene, dry-brush on solid colour, and a streetwear cut-out.
    3 · Illustration testsPainted, dry-brush and cut-out styles, tested with Figma AI and Magnific.
  4. The final style on the four onboarding screens, with the art pieces: ball, cards, flag, goal, scale, stopwatch, ticket, whistle and players.
    4 · The final styleGrainy, painted cut-outs in team kits, with the props from the game.

An everyday cast

Early tests used caricatures of famous players. I dropped them: I didn't like the funny, naive feel, and real people raise rights questions. Pickup football isn't about stars anyway. The final cast is eleven invented, everyday players from the places pickup football is played, each with a job in the app.

The everyday cast: eleven invented players in football kits, Karim, Omar, Youssef, Amr, Nour, Saud, Yassine, Tunde, Rafa, Jake and Arjun, with where each one appears in the app.

Rules for the figures

  • One hero per screenA figure leads a moment and never competes with the main button.
  • Moments, not toolsWelcome, you're in, winners, loading. Never on the live clock or a form.
  • The kit must contrastShirts recolour per team, never the same colour as the block behind.
  • Winners wear their teamPodium figures use the winner's kit, so the picture carries meaning.
  • One ball, one directionNumbers are never mirrored, so figures are never flipped.
  • Motion is shortSlide in, settle, stop. Still with Reduce Motion on.
14 · Light mode and Egyptian Arabic

Light is designed, not inverted.

Light mode uses warm paper and deeper colour for thin text. Egyptian Arabic runs right to left, with timers and scores kept in English digits and the names people type left untranslated.

Home in Light mode
Game page in Light mode
Live match in Light mode
Friends in Light mode
Welcome in Egyptian Arabic
Home in Egyptian Arabic
Live match in Egyptian Arabic
15 · What I did

The whole product, start to finish.

I'm building FairFive on my own. No software engineers, no team: just me and AI. I make every product and design decision, direct the build, test it on my own phone every day, and ship the updates to testers.

Research

The problem, personas, rules and fairness research, and the testing with 30+ people.

UX and flows

Eleven flows, the edge cases and the decisions log.

Rules

Four formats, uneven counts, late arrivals and the clock.

UI

97 screens, components, Light mode and Arabic.

Brand

Logo, colour, type and motion.

Characters

The illustration style, the cast and the rules for using them.

The build

Built and shipped solo with AI: 148 commits, 6 builds and dozens of updates to testers.

FairFive is built with Expo, React Native, TypeScript and Supabase. I build it alone, with AI (Claude Code) writing the code under my direction. The research, UX, UI, flows, brand, characters and the reasoning behind each decision are mine. Names, teams, pitches and scores in the screens are example data. The characters are invented and don't depict real people.