Sapphic Savvy is a not-for-profit game where LGBTQ women guess and wager on the real experiences of their community, then see the truth. AppMakers USA designed and built it end to end, on iOS and Android. It looks like a simple quiz. Underneath, it is a serious data engine.
Sapphic Savvy came from a not-for-profit team, grant-funded and built with input from lesbian psychologists. The idea is deceptively simple. Each quarter, players guess how the wider community really answered a set of questions, wager points on their guesses, and report their own experiences. Then they see the truth, and the gap between the stereotype and the reality.
It is a game with a purpose: challenge negative stereotypes about lesbian, bisexual, and queer women, surface shared experience, and build community, with real cash prizes for the sharpest players. AppMakers USA designed and built the entire product, on iOS and Android, from sign-up to scoring to the well-being library.
Every account is tied to one verified phone number. When real cash is on the line and the whole point is trustworthy data, that anti-cheating rule is not a nice-to-have. It is the foundation.
The screens look like a quiz. The real product was the engine that decides what counts as right.
Every round mixes two kinds of questions. Sometimes you answer about yourself and see how the community split. Sometimes you guess a number and meet the truth. You wager points on how sure you are, and it all rolls up toward the cash prize.
Report your own answer, then see how the whole community actually split, with a fact behind it.
Guess the real stat for the community, then see your guess against the truth. Over, under, or spot on.
How sure are you? Bet extra points on it. The risk and reward math is real.
Win or lose the bet, then carry your score toward the quarter's cash prize.
Screens show the app with illustrative sample data.
The gap between what a player guesses and what is actually true is the whole game. Calculating that truth, fairly, across every combination of who is answering, is where the real engineering lived.
A clean, playful screen. Nothing about it hints at what it takes to produce that one honest number.
The visible app is straightforward: questions, dials, results. The complexity lived underneath, in the answer-evaluation and result-calculation flows. It only fully surfaced once we mapped real combinations of behavior, scoring paths, and conditional outcomes. Many edge cases were invisible in the wireframe and only appeared once the system behaved like a real product.
So the work changed shape. Requirement clarification became a technical activity, not a planning one. Our dev lead grew into a combined product and engineering lead, because the business rules had to be pinned down in the architecture before implementation could realistically move. The projects with the simplest-looking screens are often the ones that need technical product leadership the earliest.
It launched with three identity groups and five age groups on a fixed evaluation model. Once real players arrived, even in the first couple hundred, the team realized results needed to flex. We rebuilt evaluation so an admin can choose whether to score by age, by identity, or by both, on the fly. That became a funded V2 with real architecture changes.
You cannot manually QA a system whose behavior depends on accumulated, conditional data. So we built dedicated tooling to simulate realistic players and large combinations of states, and trained QA on the evaluation logic itself, not just the visible screens. Testing the aggregation became its own engineering track.
Built on React Native + Expo, Node/Express, and MongoDB. Late in Android prep, Google Play started enforcing 16 KB memory-page-size compatibility, which meant real migration work on native dependencies. On iOS, we chased TestFlight-only crashes that never reproduced in the simulator. The screens were the easy part.
Got an app whose real complexity is hiding under a simple screen?
Get a Free Project Estimate →The game is the hook. Around it we built the parts that make Sapphic Savvy a place to keep coming back to: a lie-spotting bonus round, a system where the community shapes future questions, and a well-being library with real support.
Spot the lie about featured players for bonus points. A social detective round.
Players vote on and submit questions, so the community decides what future quarters ask.
A well-being library: identity and stigma, mental and physical health, coping, and more.
Longer data commentary for players who want the story behind the numbers.
Play points and bonus points roll into one total as the quarter races toward the prize.
Points start at sign-up, so momentum builds before the first question even loads.
A build with this much hidden logic only works when engineering and product decisions happen in the same room. That is how we ran it, and it is why the client kept coming back.
We stopped splitting product and code into separate lanes. Once architecture limits and business rules were discussed as one conversation, communication with the client got dramatically better.
The team put in real effort outside normal hours to support releases and troubleshoot production issues fast. When a launch is on the line, that responsiveness is the whole difference.
Acting like a shared product team instead of a detached vendor is what turned a hard build into a positive relationship, and into follow-up work with the same client.
"The projects with the simplest-looking screens are the ones that need technical product leadership the earliest. On Sapphic Savvy, the combinational behavior underneath was the real project."
Sapphic Savvy shipped on the App Store and Google Play and has stayed in active development, with regular updates well over a year after launch.
App Store + Google Play, verified August 2026The scoring model flexed from fixed rules into admin-configurable evaluation, a real V2 the client funded once the product proved itself with real users.
From the project's PM and engineering recordA hard, hidden-logic build ended in a positive relationship and follow-up work, because we ran it like a shared product team.
From the project's PM recordThat is the work we do best: scoring engines, aggregations, conditional logic, the systems that are harder than they look. We build them right, ship them to both stores, and stay to keep building. The first project estimate is free.