2026
Padel-IN Qatar - v.1
Designed, built, and deployed the first version solo: court discovery, booking, and the basics of organising a game. It is a proposal, taken to a live build rather than a mockup.
Sports
Conceptual
Proposal
Know More
Padel is booming in Qatar, and getting on a court is more work than it should be. You juggle venues, open times, and finding people to play with. v1 set out to solve the most basic version of that: book a court, fast.
Padel is one of the fastest-growing community sports in the region. v1 had one job, and everything bent toward it. Get someone from wanting to play to a booked court in about a minute. Speed was the whole proposition.
The Hard Part
Booking flows die in the joins. Search, compare, pick a time, confirm: each handoff is a place to lose someone. On a small screen, in a hurry, any extra step is felt immediately.
The challenge was to make those steps feel like one motion rather than four. The fewer decisions the app asked for, the more likely the booking actually happened.
What I Did
I shaped the app around three repeated actions: find, book, connect. Each was cut to the fewest decisions it could survive on. Then I built and deployed it rather than leaving it as a design.
Availability and price read at a glance, and the booking path stays short and predictable. The whole thing is tuned for one hand and a hurry, on mobile or web.
What Changed
It works as a fast, calm, repeatable booking proposal you can open and use today. Building it as a real product, not a static mockup, is what exposed its limit. Fast booking alone was never going to bring people back.
Living with a working version made that gap obvious in a way screens never would have. That realisation became the brief for v2.
The Call
I could have loaded v1 with features to look more complete. I deliberately kept it narrow, shipping the smallest thing that proved the core loop. A tight, real v1 told me more than a broad mockup ever would.
That restraint is what made the v1-to-v2 jump clear rather than guessed. Building it for real was the decision that paid off.
More Works
FAQ
01
Are you available?
02
Full-time, freelance, or both?
03
What kind of work do you take?
04
Remote, on-site, or both?
05
Bilingual?
06
What do I need to get started?
07
What about unpublished or NDA work?
08
How long does an engagement take?
2026
Padel-IN Qatar - v.1
Designed, built, and deployed the first version solo: court discovery, booking, and the basics of organising a game. It is a proposal, taken to a live build rather than a mockup.
Sports
Conceptual
Proposal
Know More
Padel is booming in Qatar, and getting on a court is more work than it should be. You juggle venues, open times, and finding people to play with. v1 set out to solve the most basic version of that: book a court, fast.
Padel is one of the fastest-growing community sports in the region. v1 had one job, and everything bent toward it. Get someone from wanting to play to a booked court in about a minute. Speed was the whole proposition.
The Hard Part
Booking flows die in the joins. Search, compare, pick a time, confirm: each handoff is a place to lose someone. On a small screen, in a hurry, any extra step is felt immediately.
The challenge was to make those steps feel like one motion rather than four. The fewer decisions the app asked for, the more likely the booking actually happened.
What I Did
I shaped the app around three repeated actions: find, book, connect. Each was cut to the fewest decisions it could survive on. Then I built and deployed it rather than leaving it as a design.
Availability and price read at a glance, and the booking path stays short and predictable. The whole thing is tuned for one hand and a hurry, on mobile or web.
What Changed
It works as a fast, calm, repeatable booking proposal you can open and use today. Building it as a real product, not a static mockup, is what exposed its limit. Fast booking alone was never going to bring people back.
Living with a working version made that gap obvious in a way screens never would have. That realisation became the brief for v2.
The Call
I could have loaded v1 with features to look more complete. I deliberately kept it narrow, shipping the smallest thing that proved the core loop. A tight, real v1 told me more than a broad mockup ever would.
That restraint is what made the v1-to-v2 jump clear rather than guessed. Building it for real was the decision that paid off.
More Works
FAQ
01
Are you available?
02
Full-time, freelance, or both?
03
What kind of work do you take?
04
Remote, on-site, or both?
05
Bilingual?
06
What do I need to get started?
07
What about unpublished or NDA work?
08
How long does an engagement take?
2026
Padel-IN Qatar - v.1
Designed, built, and deployed the first version solo: court discovery, booking, and the basics of organising a game. It is a proposal, taken to a live build rather than a mockup.
Sports
Conceptual
Proposal
Know More
Padel is booming in Qatar, and getting on a court is more work than it should be. You juggle venues, open times, and finding people to play with. v1 set out to solve the most basic version of that: book a court, fast.
Padel is one of the fastest-growing community sports in the region. v1 had one job, and everything bent toward it. Get someone from wanting to play to a booked court in about a minute. Speed was the whole proposition.
The Hard Part
Booking flows die in the joins. Search, compare, pick a time, confirm: each handoff is a place to lose someone. On a small screen, in a hurry, any extra step is felt immediately.
The challenge was to make those steps feel like one motion rather than four. The fewer decisions the app asked for, the more likely the booking actually happened.
What I Did
I shaped the app around three repeated actions: find, book, connect. Each was cut to the fewest decisions it could survive on. Then I built and deployed it rather than leaving it as a design.
Availability and price read at a glance, and the booking path stays short and predictable. The whole thing is tuned for one hand and a hurry, on mobile or web.
What Changed
It works as a fast, calm, repeatable booking proposal you can open and use today. Building it as a real product, not a static mockup, is what exposed its limit. Fast booking alone was never going to bring people back.
Living with a working version made that gap obvious in a way screens never would have. That realisation became the brief for v2.
The Call
I could have loaded v1 with features to look more complete. I deliberately kept it narrow, shipping the smallest thing that proved the core loop. A tight, real v1 told me more than a broad mockup ever would.
That restraint is what made the v1-to-v2 jump clear rather than guessed. Building it for real was the decision that paid off.
More Works
FAQ
Are you available?
Full-time, freelance, or both?
What kind of work do you take?
Remote, on-site, or both?
Bilingual?
What do I need to get started?
What about unpublished or NDA work?
How long does an engagement take?