The latest articles on DEV Community by shamir shakir (@shamir_shakir_e293eb37a32). https://dev.to/shamir_shakir_e293eb37a32 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%2F3995123%2F1bbd2677-801e-4743-a7f3-b7f274cde264.png https://dev.to/shamir_shakir_e293eb37a32 en shamir shakir Sun, 21 Jun 2026 09:36:01 +0000 https://dev.to/shamir_shakir_e293eb37a32/shipping-one-flutter-codebase-to-6-platforms-what-i-learned-building-tuneline-4jp8 https://dev.to/shamir_shakir_e293eb37a32/shipping-one-flutter-codebase-to-6-platforms-what-i-learned-building-tuneline-4jp8 <p>I spent the last several months solo-building <strong>Tuneline</strong>, a cross-platform media player, from a single Flutter codebase that ships native apps to <strong>macOS, Windows, Linux, Android, Google TV, and iOS</strong>. No Electron. Here is the stack and a few things that bit me.</p> <h2> The stack </h2> <ul> <li> <strong>Flutter 3.38 / Dart 3.10</strong> — one codebase, six targets.</li> <li> <strong>media_kit</strong> for playback — libmpv on desktop, ExoPlayer on Android. Avoiding per-platform video plugins was the single biggest sanity win.</li> <li> <strong>Riverpod</strong> for state, <strong>Hive</strong> for local storage, <strong>Dio</strong> for HTTP.</li> <li> <strong>Node.js + Prisma</strong> backend for the cloud-sync layer, so your library, favorites, and settings replicate across devices.</li> <li> <strong>GoRouter</strong> with a single-route, tab-driven shell so the same layout reflows from a phone to a 10-foot TV UI.</li> </ul> <h2> Things that bit me </h2> <p><strong>TV is its own design language.</strong> A 10-foot, focus-based UI is not a big phone. D-pad focus traversal, larger hit targets, and a separate Google TV store listing were all non-trivial.</p> <p><strong>Per-platform video quirks.</strong> Desktop (libmpv) and mobile (ExoPlayer) disagree on enough edge cases that a shared abstraction over media_kit earned its keep.</p> <p><strong>Sync is a distributed-systems problem in disguise.</strong> "Set up once, never rebuild it" sounds simple until two devices edit the same data offline. Keeping one canonical decoder for both the socket sync-down and the REST pull saved me from a whole class of drift bugs.</p> <p><strong>One codebase is not one design.</strong> Window management on desktop, picture-in-picture per platform, and safe-area handling on mobile each needed platform-specific care even with a shared core.</p> <h2> The product </h2> <p>Tuneline is a bring-your-own-content player, like VLC — you supply your own playlists and it does not host anything. Every viewing feature is free on one device, and the only paid tier is cloud sync plus multi-device. No subscriptions.</p> <p>Site: <a href="https://tuneline.app" rel="noopener noreferrer">https://tuneline.app</a> — happy to answer any Flutter or cross-platform questions in the comments.</p> flutter dart crossplatform mobile