Feature flags without the mess
Flags let you ship unfinished work safely. They also rot into permanent branching nobody dares delete. The rules we use to get one without the other.
Blog
Notes from the build.
What we learned shipping our own products and clients’ — engineering decisions, testing, and how we work. Plus the archive from our consumer apps.
Designing an API your mobile team will not curse in six months
The mobile client cannot ship a hotfix in ten minutes. That single constraint should shape almost every decision about the API behind it.
What a good project brief actually contains
You do not need a spec. You need five things - and the one most briefs leave out is the one that determines the estimate.
Eight apps, one backend: what shared infrastructure actually costs
Our products share accounts, wallet and payouts. That saved us a great deal of work and introduced problems nobody warns you about.
Native or cross-platform: an honest decision tree
Not a verdict - a set of questions. Which parts of your product actually care about the answer, and where the choice matters far less than people argue.
How we test a rewards app before a player ever sees it
Where the money moves, testing stops being a checklist. The layers we run before a build reaches the store, and the ones we deliberately do not automate.
Server-authoritative game logic: never let the client decide the prize
If the phone decides whether a player won, someone will eventually teach the phone to always win. How we structure reward logic so the client only renders the result.
Cutting a marketing site from 3.9 MB to 90 KB
We rebuilt our own site and deleted jQuery, Bootstrap, four carousel libraries and 3 MB of images. Here is what actually moved the number.
Cash Queen – The Best Scratch Card Game to Win Real Cash Instantly
How the scratch-card mechanic works, what a prize actually costs to run, and why every outcome is decided on the server rather than the phone.