Based in Dubai, I work on mobile applications used across the UAE and GCC. At INAXUS, I lead the mobile platform from architecture and development through store publishing and post-launch support. This page connects the engineering problems I work on with examples you can explore.
When Flutter fits a mobile project
Flutter is useful when Android and iOS need a shared application experience. The choice still depends on the product: device integrations, existing native code, offline requirements and release processes all matter. My work combines Flutter and Dart with Android Kotlin and Java, plus iOS integration where needed.
Keeping field teams productive offline
Construction and inspection workflows need to work when connectivity is unreliable. At INAXUS, my work includes offline snag creation, background synchronization and document approval workflows. A useful discovery discussion starts with what users must do offline, how changes are reconciled, and what they should see when synchronization fails.
Explore the INAXUS mobile platform ↗UAE workforce applications
At Future Trend LLC in Dubai, I built Flutter and Android attendance and workforce monitoring functionality for the Federal Geographic Information Center. This work connected the mobile experience to backend systems for attendance tracking and reporting.
Explore FGIC Attendance ↗AI features with a clear purpose
My INAXUS work includes Gemini-powered document search and summaries. Separately, my personal Local AI Document Parser connects a Flutter client to a FastAPI backend using Ollama and Tesseract for local OCR and document processing. These are different approaches to explore when considering network availability and where document processing happens.
Explore the local AI document parser ↗From development to release
Mobile engineering includes more than screens: architecture, backend integration, testing, UAT with users, App Store and Google Play releases, crash monitoring and follow-up fixes. My experience includes working directly with product teams, engineers and client stakeholders on these stages.
Discuss your mobile engineering needs
Share who will use the app, the platforms you need, your existing backend and any offline or device requirements. If you already have an application, include the specific problems you want to solve. We can discuss the scope and whether my experience fits your project or team.