My second published game. The starting question was not which game to build, but how much a second launch should cost once the first product already exists.
Place one queen in each row, each column and each coloured region, with no two queens touching. The rules are simple, but the puzzles become difficult quickly.
Binero was built from scratch. Queens Master was created to answer a different question: what can be reused from one app to the next?
The answer is everything that is not specific to the game itself: monetisation, subscriptions, analytics, consent, settings, themes, translations and store-release tooling. Each app can then focus on its own rules and content.
The benefit becomes visible quickly. A shared fix can be written once and applied across both products. When the common foundation already covers most of the underlying work, a new launch can take weeks rather than months.
One shared application foundation can support multiple product variants: one app per client, brand or market.
The hard part begins when those variants diverge. One client wants a feature the others do not need; another wants a similar feature implemented differently. The architectural challenge is deciding what remains shared, what becomes configurable and what genuinely deserves a separate implementation.
Queens Master gave me a production environment to test those trade-offs on my own products before applying the same thinking to client work.
Book a 30-minute call →