in2Play
Pickleball ranking, matching & community
in2Play is a Flutter app for competitive pickleball: it ranks players, matches them against opponents at their level, and gives local communities the tooling to run organized play without a spreadsheet and a group chat. It is an in-house IN2Labs product — we researched it, built it, own it, and operate it.
At a glance
- Status
- Beta — open to new players by invitation
- Category
- Sports & community
- Platforms
- iOS, Android, and web from one Flutter codebase
- Built by
- IN2Labs — in-house product, not client work
- Core problem
- Skill-appropriate matching and trustworthy local rankings
The problem with recreational pickleball
Pickleball's growth has outrun its infrastructure. Local play is organized through group chats and paper sign-up sheets, skill levels are self-reported and wildly inconsistent, and the result is the single thing that drives players away fastest: lopsided matches. A 3.0 player against a 4.5 is not a game for either of them.
The ranking systems that do exist are built for tournament play. They ignore the vast majority of pickleball, which is recreational, local, and continuous — exactly the play that has the most data and the least structure.
Ranking that reflects how people actually play
in2Play derives a rating from match results rather than self-assessment, so a player's number reflects outcomes against real opponents instead of optimism. Ratings update continuously as matches are recorded, which means the system converges on an accurate picture of a player quickly and keeps up as they improve.
Matching then works off that rating: the app proposes opponents and doubles pairings likely to produce a close game. Competitive balance is the product — everything else exists to serve it.
Community as a first-class feature
Pickleball is intensely local. Play clusters around specific courts, specific times, and specific groups of people who show up regularly. in2Play is built around those groups rather than around a global leaderboard nobody in a given city cares about.
Communities get the scaffolding they were improvising: organized sessions, recorded results that feed the rankings, and a shared view of who plays where and at what level.
Why Flutter
Players are split across iOS and Android with no clear majority, and organizers want a web view for managing sessions on a laptop. Building three native clients for a product at this stage would have meant shipping a third as often.
One Flutter codebase covers all three surfaces, which is the same architectural argument we make to consulting clients — and a good reason to have proved it on our own product first.
Capabilities
What it does
- Match-result-derived player ratings, not self-reported skill levels
- Skill-based opponent and doubles-pairing suggestions
- Local community and session organization
- Continuous rating updates as results are recorded
- One Flutter codebase across iOS, Android, and web
Built with
FAQ
Questions about in2Play
Is in2Play available now? +
in2Play is in beta. It is open to new players and communities by invitation while we work with early groups — get in touch and we'll talk about getting your group on.
How is the rating calculated? +
From recorded match results against other rated players, updated continuously rather than in periodic batches. Self-reported skill levels are not used as an input, because they are the source of the mismatching problem in the first place.
Is in2Play a client project? +
No. It is an in-house IN2Labs product — researched, built, owned, and operated by us. Our client engineering work is a separate practice at in2labs.dev.
Other products
Need engineering help on your own product? That's our consulting practice at in2labs.dev.