<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Hammad Ali Shah on Medium]]></title>
        <description><![CDATA[Stories by Hammad Ali Shah on Medium]]></description>
        <link>https://medium.com/@hammadx02?source=rss-b3a2b9c3e21e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*g9nmVtVHImSn9Ntr6BIgvw.png</url>
            <title>Stories by Hammad Ali Shah on Medium</title>
            <link>https://medium.com/@hammadx02?source=rss-b3a2b9c3e21e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:58:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hammadx02/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I Reduced Our Flutter App Size From 55 MB to 11 MB With One Small Configuration Change]]></title>
            <link>https://medium.com/@hammadx02/i-reduced-our-flutter-app-size-from-55-mb-to-11-mb-with-one-small-configuration-change-f6e9601f248f?source=rss-b3a2b9c3e21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6e9601f248f</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[flutter-flavor]]></category>
            <dc:creator><![CDATA[Hammad Ali Shah]]></dc:creator>
            <pubDate>Sat, 17 Oct 2026 16:25:50 GMT</pubDate>
            <atom:updated>2026-10-17T16:25:50.555Z</atom:updated>
            <content:encoded><![CDATA[<p>When you’re building apps for multiple clients, the first solution isn’t always the one that scales.</p><p>In my previous role, we were managing a <strong>POS (Point of Sale)</strong> application built with Flutter.</p><p>Each restaurant needed its own app, with its own branding and a few client-specific configurations.</p><p>Initially, our approach was simple: copy the existing codebase, create another app, make the required changes, and deliver it to the client.</p><p>It worked when we had two or three clients.</p><p>But imagine doing the same thing for <strong>150+ clients.</strong></p><p>That approach quickly became difficult to maintain. We needed something more scalable.</p><h3>From Separate Codebases to Flutter Flavors</h3><p>We moved to Flutter flavors.</p><p>Instead of maintaining a separate codebase for every restaurant, we could manage different app variants within the same project.</p><p>Most client-specific changes were relatively small:</p><ul><li>App assets and branding</li><li>Application IDs</li><li>Theme and colors</li><li>Other client-specific configurations</li></ul><p>This made a huge difference in our workflow.</p><p>What previously took <strong>almost a day</strong> could now be done in around <strong>10 minutes</strong> for a typical client setup.</p><p>But as the number of flavors grew, I noticed another problem.</p><p><strong>Our app size was growing, too.</strong></p><h3>The Hidden Problem: Every Flavor Was Bundling Every Asset</h3><p>We had different assets for different restaurant brands, but the assets were organized in a way that allowed them to be included in every app bundle.</p><p><em>Think about it: why should Restaurant A’s app carry Restaurant B’s images if it never uses them?</em></p><p>With more clients, this meant we were potentially shipping a lot of unnecessary assets.</p><p>I started looking for a simpler way to include only the assets needed by each flavor.</p><h3>The Fix Was in pubspec.yaml</h3><p>Instead of making the build process more complicated, I changed how we declared our assets.</p><p>The idea was straightforward: organize assets by application and configure each flavor to use its own asset directory.</p><p>For example, the configuration could look like this:</p><pre>- path: assets/app/images/<br>      flavors:<br>        - app_flavor_name</pre><p><em>Note: This illustrates the configuration idea, not a complete, universally valid Flutter </em><em>pubspec.yaml setup. The exact syntax depends on how your project manages flavors and assets.</em></p><p>The important part was separating the assets by flavor rather than making every client app include the same shared collection.</p><p>After applying the solution, we saw a significant reduction in the packaged app size.</p><p><strong>The size went from 55+ MB to around 11 MB on Google Play, a reduction of roughly 80%.</strong></p><p>That was a much bigger improvement than I expected from such a small configuration change.</p><h3>What I Learned</h3><p>This experience reinforced three lessons for me.</p><p><strong>1. Choose an approach that scales.</strong></p><p>Copying a codebase can feel convenient for the first few clients. But as the number of clients grows, maintaining separate copies becomes increasingly expensive.</p><p><strong>2. Don’t assume every asset belongs in every build.</strong></p><p>Images, fonts, and other resources contribute to an application’s size. Review what your app actually needs instead of bundling everything by default.</p><p><strong>3. Look for configuration problems before adding complexity.</strong></p><p>Sometimes, the solution isn’t another package or a more complicated build pipeline. It may be a small change in how your project is configured.</p><p>Flutter flavors helped us scale delivery from a handful of clients to more than 150. Optimizing asset inclusion helped us reduce unnecessary app size.</p><p>Both improvements came from questioning an approach that initially seemed perfectly reasonable.</p><p><strong>Sometimes, the biggest optimization isn’t writing more code. It’s making sure you’re building only what you need.</strong></p><p><em>Have you faced app-size issues while managing multiple Flutter flavors? I’d love to hear how you handled them.</em></p><p>#flutter #mobileapps #flutterdev</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6e9601f248f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Google Play Changes Flutter Developers Should Know About]]></title>
            <link>https://medium.com/@hammadx02/3-google-play-changes-flutter-developers-should-know-about-2fcf45490a6b?source=rss-b3a2b9c3e21e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fcf45490a6b</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[google-play]]></category>
            <dc:creator><![CDATA[Hammad Ali Shah]]></dc:creator>
            <pubDate>Thu, 15 Oct 2026 17:01:49 GMT</pubDate>
            <atom:updated>2026-10-15T17:01:49.180Z</atom:updated>
            <content:encoded><![CDATA[<p>Building an app is one thing. Getting it tested, published, and discovered is another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qKtZ0SJ_P2y_UEGwKFB5Cw.jpeg" /><figcaption>3 Key shits you need to know</figcaption></figure><p>Google Play is changing how developers distribute apps and how users discover them.</p><p>Here are <strong>3 updates Flutter developers should pay attention to.</strong></p><h3>1. Share Apps Without Paying for a Developer Account</h3><p>Want to share your Android app without paying for a standard Google Play developer account?</p><p>Google’s new <strong>limited distribution accounts</strong> offer a free option for developers who want to share apps with up to 20 authorized devices.</p><p>This could be useful if you’re learning Flutter, experimenting with an idea, or testing a small project with a few people.</p><p>Instead of testing everything on your own phone, you can get feedback from others and catch issues you might have missed.</p><p><strong>Keep in mind:</strong> this is for limited distribution, not a replacement for a standard account when publishing a production app.</p><h3>2. Turn Ideas Into Personal Android Apps</h3><p>Google is also introducing ways to create and run personal Android apps through Google AI Studio without registering a developer account.</p><p>Imagine wanting a simple expense tracker or workout planner for your own use. You could experiment with an idea without going through the full process of launching a public app.</p><p>For Flutter developers, this signals a broader trend: <strong>building a prototype is becoming easier.</strong></p><p>That doesn’t make Flutter less useful. When an app needs custom architecture, integrations, and long-term maintenance, choosing the right development approach still matters.</p><p>Personal apps and public Play Store releases also have different requirements.</p><h3>3. AI Is Changing How Users Discover Apps</h3><p>Users don’t always know which app they need. Sometimes, they just know the problem they want to solve.</p><p>Google’s <strong>Ask Play</strong> brings AI-powered questions and app comparisons into Google Play, helping users explore apps based on their needs.</p><p>Think about someone searching for a gym management app.</p><p>They care less about the technology behind it and more about whether it can track payments, manage members, and handle renewals.</p><p>That’s why your Play Store listing matters.</p><ul><li><strong>Write a clear title</strong> that communicates your app’s purpose.</li><li><strong>Explain the benefits</strong> instead of just listing features.</li><li><strong>Use meaningful screenshots</strong> that show the app in action.</li><li><strong>Keep descriptions natural</strong> and easy to understand.</li></ul><p>A better listing doesn’t guarantee higher rankings, but users should be able to understand your app’s value before installing it.</p><h3>What Should Flutter Developers Take Away?</h3><p>These updates are a reminder that building the app is only part of the job.</p><p><strong>Test early.</strong> Get feedback before launch.</p><p><strong>Experiment freely.</strong> Validate ideas before investing too much time.</p><p><strong>Think beyond code.</strong> Help users understand why your app is worth installing.</p><p>As Flutter developers, we spend plenty of time learning widgets, state management, APIs, and architecture. But shipping a successful app also means understanding how it reaches people.</p><p><strong>Shipping an app is one milestone. Getting people to use it is another.</strong></p><p>Which of these changes interests you the most?</p><p>#Flutter #FlutterDevelopment #GooglePlay #AndroidDevelopment</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fcf45490a6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>