iOS and Android apps that start a round, a route, or a list in minutes.
For teams that want an app in the user's hand, on iPhone and Android. We often share a TypeScript codebase. We deliver store builds, privacy copy, and a path from TestFlight or internal testers to production.
Red Flags and Dirty Seconds are party apps. A group has to be in a round in minutes, often in a dim room, with large type. StepQuests runs in the street, with a map and live progress. Weekboodschappen takes the week menu into the shop. Offline is sacred where the round or the list must not wait on a network.
Which device your people hold, whether the app must work offline, and whether an Apple or Google account already exists.
Work that is live
Red Flags: the host opens a lobby, everyone else joins with a code or QR, product goal is an active round inside two minutes. Dirty Seconds: one phone in the middle, thirty seconds, offline once the round is going. StepQuests is the route on the street. Weekboodschappen is the Expo app for kitchen and shop. We do not publish download counts. This is the product.
Red Flags
Friends build ridiculous date profiles and vote on the loudest red flags. Product goal: an active round inside two minutes.
Screenshot of the live site, 25 August 2026.
Dirty Seconds
A 30 Seconds-style explain-and-guess game. Starting a round in under a minute is the success bar.
Screenshot of the live site, 25 August 2026.
StepQuests
Self-guided city walks with stories, quizzes and checkpoints. Web for discovery and booking. The app is the route on the street.
Screenshot of the live site, 25 August 2026.
Weekboodschappen
Weekly menus and shopping lists for busy households across the Netherlands. The product promise: a first plan in about 3 minutes.
Studio still, generated. This is not a screenshot of the live site.
What you get
A shared codebase where that fits (Expo / React Native), native store builds, privacy copy, and a path to TestFlight or internal testers and then production. Apple and Google accounts sit with you, or we say what must be ready before we submit.
How we start
Tell us which device people hold, whether the app must work offline, and whether an Apple or Google account already exists. First sprint: something on a phone, even while the rest is still rough. Store review sits in the plan. That wait belongs to Apple or Google, not to our compile.
When this fits
This fits when the job belongs on a phone: starting a round, walking a route, a list in a shop. A marketing site without a store build lives on the web page. The listing check is free if you are already in the store and want the copy scored.
Ready to tell us what you need?
Sketch the app. We come back with a price estimate and what must be ready for the store. If you already have a listing, get the score first.
Questions about this work
- Do you build native or with React Native?
- Often Expo and a shared TypeScript codebase, because Red Flags, Dirty Seconds, StepQuests and Weekboodschappen ship that way. If a piece has to be truly native, we say so in the price estimate.
- How long is the road to the store?
- Build work runs in two-week sprints. Then TestFlight or internal testers, and review at Apple or Google. We plan for review time. That calendar belongs to the store, not to our compile.
- Does the app have to work offline?
- Say so in the form. Dirty Seconds waits on no network once the round is going. StepQuests needs GPS in the street. That is a different architecture than wrapping a site.
- Do I need an Apple Developer account?
- For iOS in the App Store, yes, in your organisation's name. Google Play is the same for Android. We say what must be ready before we submit. Without an account we can test internally. We cannot publish.