I'm Kirollos — 11+ years building native iOS at scale. Now I'm building the infrastructure for an AI-first world, where agents act on our behalf and software renders itself, on-brand, for each person.
For over a decade I've shipped native iOS: a 1M+ user app at 99.99% crash-free, senior mobile work across e-commerce, and an internal AI platform I initiated and led — on-device and server LLMs with multi-agent orchestration, running in production.
Egyptian, based in Dubai, and happiest right at the edge of what's just become possible. I build in the open, and I move fast toward the future I believe in.
↓ View my résuméStatic screens give way to UI an agent composes at request time — grounded in real data and a real brand, so it's on-brand without being hand-built.
Every system exposes its data, its actions, and its design language as agent-friendly tools — not opaque dashboards or frozen templates.
Encode a brand as machine-readable tokens — color, type, spacing, voice — and an agent can render a thousand true variations instead of one static theme.
Requirement → user stories → UI → implementation → automated tests, in one continuous pass. My Create & Analyze plugins already do this.
The Vault: an index of a codebase, its components and APIs, so an agent knows exactly what it touches and what to reuse. Stories become executable plans.
An MCP that carries a brand's design language, so agents compose on-brand experiences per person — the storefront as something generated, not frozen.
MCP as the connective layer for AI-first products — starting with commerce and Shopify, then everywhere software meets an agent.
A user story on its own can't drive development — it doesn't know the codebase. So I built the Vault: an index of a codebase, its UI components, and its APIs. The Create User Story plugin writes against it, so every story already points to the exact modules it touches and the components to reuse — and generates UI from the product's real look and feel.
Stories are wishes — they don't map to real code, so they can't lead implementation.
Index the code into the Vault; write stories against it so they reference what actually exists.
Stories become executable plans — and new engineers ship in week one, not quarter one.
Plugins that carry a requirement all the way to implementation and automated tests — in one continuous loop.
Collapsing the delivery cycle so a refined requirement flows straight to UI, code, and tests — nothing lost in the handoffs.
An index of a codebase, its components and APIs, that grounds every generated story in real, reusable code.
The phone was built for taps. The next generation of devices will be built for agents — ambient, intent-driven, rendering experiences on demand. Software will be written for the agent as much as for the human. That's the shift I'm preparing for, and building toward — one layer at a time.