The latest articles on DEV Community by Ahmed Mohamed (@ahmedinnov). https://dev.to/ahmedinnov https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4103544%2Fd7f02542-dfda-4f09-86f7-67795d0a6701.jpg https://dev.to/ahmedinnov en Ahmed Mohamed Tue, 01 Sep 2026 03:01:35 +0000 https://dev.to/ahmedinnov/how-i-ship-cross-platform-apps-with-flutter-laravel-firebase-45g8 https://dev.to/ahmedinnov/how-i-ship-cross-platform-apps-with-flutter-laravel-firebase-45g8 <p>I'm Ahmed Mohamed, Founder &amp; CTO of Ahmed Innovation. Over the past 6+ years I've built and shipped 47+ production apps for iOS, Android, and the Web — across e-commerce, gaming, fintech, and SaaS. Here's the stack and the approach I keep coming back to.</p> <h2> Why Flutter + Laravel + Firebase </h2> <p>Most of my projects need to launch fast on mobile and web, with a solid backend behind them. This trio covers all of it:</p> <p><strong>Flutter</strong> — one codebase for iOS, Android, and Web. Fast, expressive UI with near-native performance.</p> <p><strong>Laravel</strong> — a batteries-included PHP backend for auth, REST APIs, dashboards, payments, and business logic.</p> <p><strong>Firebase</strong> — real-time data, auth, push notifications, and cloud functions without standing up infrastructure.</p> <h2> The architecture I use </h2> <p>A Flutter app with a feature-first structure and a predictable state layer (BLoC or GetX). A Laravel API as the source of truth: versioned REST endpoints, policies for authorization, and queues for heavy work. Firebase for the real-time bits — chat, live order tracking, notifications — and Firestore where offline-first sync matters.</p> <h2> Lessons from shipping to the store </h2> <p><strong>Offline-first from day one.</strong> Cache aggressively and reconcile on reconnect. Users on flaky networks stay happy.</p> <p><strong>Watch cold-start time.</strong> Defer non-critical work, lazy-load, and keep the first frame cheap.</p> <p><strong>Instrument crashes early.</strong> I aim for 99.95%+ crash-free sessions — you can't hit that without visibility.</p> <p><strong>Automate the boring parts.</strong> CI/CD for builds and releases removes an entire class of human error.</p> <p><strong>Test the unhappy payment paths.</strong> Declines, timeouts, and refunds deserve as much attention as the happy path.</p> <h2> Closing </h2> <p>This stack lets me take a project from the first call to App Store approval — architecture, code, and delivery — all in one place. If you'd like to see some of what I've built, my portfolio is at <a href="https://ahmedinnov.com" rel="noopener noreferrer">https://ahmedinnov.com</a>.</p> <p>Happy to answer questions in the comments!</p> flutter laravel firebase webdev