Elkood

Elkood was my first full-time mobile development role: fifteen months, five production apps, and the place where I went from a competent Flutter developer into one who had seen the entire production lifecycle of half a dozen real apps.

What shipped

Across e-learning, marketplace, delivery, retail, and security verticals, I built and maintained apps that real users depend on every day — Be The Best (e-learning with real-time chat and subscriptions), Q2AUTO (a security-guard management system I built independently), Royal Button (a POS administration app with AI image search), G-Store Driver and G-Store Employee (a real-time delivery + warehouse pair), plus maintenance and enhancement work on existing apps.

How I worked

The pace was intense — two-week sprints in a cross-functional Agile team — and the volume of integrations was the highest of my career so far: SignalR real-time, Firebase, Google Maps with clustering and live tracking, in-app purchases, background services, push notifications, deep linking, and image-based search with Google ML Kit.

The architectural lessons mattered as much as the integrations. By the end of my time there, I was the developer most likely to be handed a legacy refactor, because the team had seen me improve maintainability on inherited projects. I introduced Clean Architecture into projects that hadn’t started with it, and stood up Codemagic CI/CD pipelines so releases stopped being a manual, anxious affair.

Why it matters

Elkood is the clearest proof in my portfolio of production-company work: not one polished demo, but a sustained record of shipping, maintaining, and hardening multiple apps in parallel — reducing crash rates by up to 30% while keeping the codebases healthy for the next developer.