Electric mobility platform · Mobile Engineering Lead · 07/2023 — 01/2026
EVLAB
An electric mobility platform for rentals, leasing, and marketplace — with mobile delivery owned end to end, from architecture to production support.

EVLAB
Chalhoub Group · Mobility
- Engagement
- Jul 2023 — Jan 2026
- Role
- Mobile Engineering Lead
- Platforms
- iOS · Android
- Based in
- Dubai, UAE
The brief
Challenge
EVLAB carries three business models at once — daily rentals, long-term leasing, and a marketplace — inside one product and one brand. The mobile apps had to serve all three without splitting into separate codebases, while meeting Chalhoub Group standards for security, release management, and production support.
Stack
What I did
- Led mobile engineering for the EVLAB platform across iOS and Android.
- Architected Flutter apps on Clean Architecture with Riverpod, SOLID boundaries, and reusable components.
- Integrated secure REST APIs, authentication, cloud services, analytics, and third-party SDKs.
- Coordinated Mobile, Backend, Product, UX/UI, QA, DevOps, and business teams through delivery.
- Implemented Codemagic CI/CD, reducing manual release effort, and owned release management and production support.
Engineering decisions
- 01
One Flutter codebase for rentals, leasing and marketplace
All three models share accounts, payments and authentication, so separate apps would have tripled release overhead and split the customer record. The product shipped as one app with modular boundaries instead.
Trade-off More feature-flag and navigation discipline up front, and a shared release train for every business unit.
- 02
Clean Architecture with Riverpod instead of a lighter state layer
Chalhoub Group standards and a multi-team delivery expected testable domain logic, clear dependency boundaries and components other engineers could reuse.
Trade-off More structure than a small app needs, and onboarding has to explain the boundaries, not just the screens.
- 03
Owned CI/CD and release management, not a handoff
Codemagic pipelines, store submission and production support stayed with mobile engineering, so release quality and incident response had one owner.
Trade-off Pipeline maintenance and on-call responsibility stayed on the mobile side as well.
Outcome
End-to-end mobile ownership
Mobile shipped as one platform instead of three parallel apps: shared architecture, shared components, and a release process the wider team could run. Ownership covered the full lifecycle — planning, development, testing, store releases, and production support — through the end of the engagement in January 2026.
Have a similar project?
I can own the build from architecture to production support.

