Teardowns, not think-pieces
Real screens, real architecture, real trade-offs. Bring a screen or a schema and leave with specific feedback.
- Flutter and native architecture reviews
- Release and store-review war stories
- What actually broke in production
Community · Builders in Dubai and online
Flutter and native engineers, AI builders, designers and indie founders comparing notes on the parts nobody blogs about — architecture calls, release weeks, store reviews, and keeping an app alive long after launch.
The Discord invite is being set up. Join the list below and you will get it first.
Real screens, real architecture, real trade-offs. Bring a screen or a schema and leave with specific feedback.
Engineers from Dubai and beyond who have taken apps through launch, scale, and the quiet year after.
Contract work, senior roles, and projects that need a second pair of hands. Shared openly, no recruiter spam.
How it works
Building alone means relearning lessons someone else already paid for. This is the shortcut — not a course, not a newsletter, a room with people who answer.
It is not for selling services to each other. Members who only broadcast get nudged toward the door.
One link, no application form. Introduce yourself in #introductions with what you build and what you are stuck on.
A bug that will not reproduce, a release that slipped, a store rejection. That is the price of admission.
Answer someone else first. The room works when the people ahead of you are the ones replying.
Stay in the loop
One email when a teardown, an app or a community note ships. Your name and optional WhatsApp stay in my private database — used to reply, never sold, never spammed.
Unsubscribe anytime; the link in every email deletes your details for good.
Who it is for