<?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 Waseem Arain on Medium]]></title>
        <description><![CDATA[Stories by Waseem Arain on Medium]]></description>
        <link>https://medium.com/@waseemarain_98671?source=rss-bb2557ea447b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*F27Jq3_mlOAXAMTOqbDSHw.png</url>
            <title>Stories by Waseem Arain on Medium</title>
            <link>https://medium.com/@waseemarain_98671?source=rss-bb2557ea447b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:49:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@waseemarain_98671/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[From Commit to TestFlight and Google Play: Building a Flutter CI/CD Pipeline]]></title>
            <link>https://medium.com/@waseemarain_98671/from-commit-to-testflight-and-google-play-building-a-flutter-ci-cd-pipeline-92f9b49edf69?source=rss-bb2557ea447b------2</link>
            <guid isPermaLink="false">https://medium.com/p/92f9b49edf69</guid>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[action]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Waseem Arain]]></dc:creator>
            <pubDate>Fri, 11 Sep 2026 18:04:48 GMT</pubDate>
            <atom:updated>2026-09-11T18:04:48.450Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How I automated testing, signing, validation, and mobile releases for both iOS and Android.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5wytvVShEH3VAMg83G6gYQ.png" /></figure><p>Shipping a mobile application should not mean repeating the same manual release process every time a new version is ready.</p><p>Recently, I completed a CI/CD pipeline for a Flutter application that automates the journey from source code to <strong>TestFlight</strong> and <strong>Google Play</strong>.</p><p>The workflow now follows a simple principle:</p><blockquote><strong><em>Commit → Build → Test → Validate → Deploy</em></strong></blockquote><p>The result is not just faster releases. It is a more predictable, traceable, and reliable release process.</p><h3>Why I Wanted to Automate the Release Process</h3><p>A typical Flutter release involves much more than running a build command.</p><p>Before a production version reaches users, I normally need to:</p><ul><li>check out the correct source code</li><li>install dependencies</li><li>run static analysis</li><li>execute automated tests</li><li>prepare signed Android and iOS builds</li><li>validate generated artifacts</li><li>securely restore platform credentials</li><li>upload the iOS build to TestFlight</li><li>publish the Android build to Google Play</li></ul><p>When these steps are performed manually, the process depends heavily on the developer remembering every detail correctly.</p><p>That creates unnecessary risk.</p><p>A wrong build number, forgotten test, incorrect signing configuration, outdated artifact, or missing release step can delay a deployment.</p><p>The goal of CI/CD was therefore not simply:</p><blockquote><em>“Make releases faster.”</em></blockquote><p>The real goal was:</p><blockquote><strong><em>Make every release follow the same trusted process.</em></strong></blockquote><h3>The Release Pipeline</h3><p>The automated workflow is structured around a series of quality gates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r3zV9yvarlqZwvr-7HG_gQ.png" /><figcaption>GitHub Actions workflows for automated TestFlight and Google Play releases.</figcaption></figure><pre>Commit / Release Tag<br>        ↓<br>Checkout Source<br>        ↓<br>Set Up Flutter<br>        ↓<br>Install Dependencies<br>        ↓<br>Analyze Code<br>        ↓<br>Run Tests<br>        ↓<br>Build Signed App<br>        ↓<br>Validate Artifact<br>      ↙     ↘<br>TestFlight  Google Play</pre><p>Each stage has a specific responsibility.</p><p>If an important step fails, the release stops before reaching users.</p><p>That is one of the biggest benefits of automation: the pipeline does not only deliver software — it protects the delivery process.</p><h3>1. Checking Out the Exact Source</h3><p>The workflow starts by checking out the repository revision associated with the release.</p><p>This gives every generated build a clear relationship with the source code that produced it.</p><p>In practical terms:</p><pre>Commit → Build → Release</pre><p>If an issue appears after deployment, I can trace the released application back to the exact source revision used by CI.</p><p>That traceability becomes increasingly important as applications, teams, and release frequencies grow.</p><h3>2. Setting Up a Pinned Flutter SDK</h3><p>A reliable CI pipeline should not depend on whichever Flutter version happens to be available on the runner.</p><p>The workflow therefore sets up a pinned Flutter SDK before dependency installation and build steps begin.</p><p>This helps make the build environment predictable and reduces the chance of an unexpected framework upgrade changing the result of a release.</p><p>For mobile teams, reproducibility matters just as much as automation.</p><h3>3. Installing Dependencies in a Clean Environment</h3><p>The next step restores and installs the Flutter dependencies required by the project.</p><p>Running dependency installation inside CI is important because the build should not depend on packages or configuration that happen to exist on a developer’s local machine.</p><p>A clean build environment improves reproducibility.</p><p>The same source code should produce the same expected result regardless of who starts the release.</p><h3>4. Static Analysis as an Early Quality Gate</h3><p>Before producing any release artifact, the pipeline runs Flutter and Dart analysis.</p><p>This allows the workflow to catch problems before expensive build and deployment steps begin.</p><p>Static analysis can identify issues such as:</p><ul><li>type problems</li><li>invalid API usage</li><li>lint violations</li><li>potential implementation mistakes</li><li>code that no longer matches project rules</li></ul><p>Failing here is much better than discovering the same problem after generating a production build.</p><h3>5. Running Automated Tests Before Deployment</h3><p>The next stage executes the project’s automated tests.</p><p>This is an important distinction in CI/CD architecture.</p><p>A pipeline should not mean:</p><blockquote><em>“Automatically build whatever is in the repository.”</em></blockquote><p>A better pipeline means:</p><blockquote><em>“Verify that the application meets our checks before allowing it to move toward production.”</em></blockquote><p>Tests turn the release workflow into a quality gate rather than simply a build script.</p><p>As test coverage grows, the value of this stage grows with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tcUkzz_XsDyNEJZX9WTV3g.png" /><figcaption>The iOS release workflow progressing through validation, signing, testing, artifact creation, and TestFlight deployment.</figcaption></figure><h3>6. Handling Mobile Signing Securely</h3><p>Mobile CI/CD becomes more complex when application signing enters the workflow.</p><p>Both Android and iOS require production credentials.</p><p>For iOS, the release workflow needs to deal with Apple signing credentials and App Store Connect authentication.</p><p>For Android, the production build requires the release signing configuration used by the application.</p><p>The important principle is simple:</p><blockquote><em>Production credentials should never be committed directly to the repository.</em></blockquote><p>They should be stored as protected CI secrets and restored only when the workflow needs them.</p><p>This gives the automation access to the required credentials without exposing them in source control.</p><h3>7. Building the Signed iOS Artifact</h3><p>Once analysis and tests pass, the iOS workflow can move into the signed build stage.</p><p>The pipeline creates the production IPA using the signing configuration provided securely during the workflow.</p><p>After the build completes, the workflow locates the generated IPA and can preserve it as a workflow artifact.</p><p>Keeping the artifact is useful for:</p><ul><li>debugging failed deployments</li><li>auditing releases</li><li>reproducing release investigations</li><li>downloading the exact build generated by CI</li></ul><p>The key idea is that the artifact is produced by the pipeline, not manually on a developer machine.</p><h3>8. Validating the IPA Before Upload</h3><p>A successful compilation does not automatically mean an iOS application is ready for App Store Connect.</p><p>The generated IPA should still be validated.</p><p>This provides another checkpoint for problems related to:</p><ul><li>signing</li><li>provisioning</li><li>entitlements</li><li>application metadata</li><li>App Store Connect requirements</li></ul><p>There is an important difference between:</p><blockquote><em>“The application built successfully.”</em></blockquote><p>and</p><blockquote><em>“The application is ready to distribute.”</em></blockquote><p>Validation helps close that gap.</p><h3>9. Automatically Publishing to TestFlight</h3><p>Once the iOS artifact passes the required checks, the workflow uploads it to TestFlight.</p><p>This removes one of the most repetitive parts of the iOS release process.</p><p>Instead of manually creating an archive, exporting it, and uploading it for every release, the CI pipeline performs the delivery through a controlled process.</p><p>A release can now move from the repository to TestFlight with significantly less manual intervention.</p><h3>10. Automatically Publishing to Google Play</h3><p>The Android side follows the same philosophy.</p><p>After the production artifact has been generated and validated, the workflow can publish it to the configured Google Play release destination.</p><p>That gives the project one release architecture supporting both mobile platforms:</p><pre>Flutter Application<br>               ↓<br>          CI/CD Pipeline<br>          ↙           ↘<br>     TestFlight    Google Play</pre><p>One source repository.</p><p>One repeatable release process.</p><p>Two mobile platforms.</p><h3>Release Tags and Version Traceability</h3><p>Version management is also part of the release workflow.</p><p>For example:</p><pre>v1.2.3+28</pre><p>The application version identifies the release while the build number uniquely identifies the generated mobile build.</p><p>Connecting versioning with CI/CD makes it easier to answer important questions later:</p><ul><li>Which version was released?</li><li>Which build produced it?</li><li>Which commit created that build?</li><li>Which workflow run deployed it?</li><li>Which artifact was sent to the store?</li></ul><p>Good CI/CD makes those answers easy to find.</p><h3>A Simplified GitHub Actions Structure</h3><p>The exact implementation depends on the project, signing strategy, and store configuration, but conceptually the release workflow looks like this:</p><pre>name: Mobile Release</pre><pre>on:<br>  push:<br>    tags:<br>      - &quot;v*&quot;</pre><pre>jobs:<br>  release:<br>    runs-on: macos-latest</pre><pre>    steps:<br>      - name: Checkout repository<br>        uses: actions/checkout@v4</pre><pre>      - name: Set up Flutter<br>        run: echo &quot;Set up the pinned Flutter SDK used by the project&quot;</pre><pre>      - name: Install dependencies<br>        run: flutter pub get</pre><pre>      - name: Analyze Dart code<br>        run: flutter analyze</pre><pre>      - name: Run tests<br>        run: flutter test</pre><pre>      - name: Build signed mobile artifacts<br>        run: echo &quot;Build signed iOS and Android release artifacts&quot;</pre><pre>      - name: Validate artifacts<br>        run: echo &quot;Run platform-specific validation&quot;</pre><pre>      - name: Publish release<br>        run: echo &quot;Upload to TestFlight and Google Play&quot;</pre><p>I intentionally keep signing credentials and store authentication out of the repository and provide them to CI through protected secrets.</p><p>The workflow definition documents the release process, while the secrets remain protected.</p><h3>What Changed After Automation</h3><p>The biggest change was not simply that the builds became faster.</p><p>The <strong>release process itself became infrastructure</strong>.</p><p>Instead of relying on a developer to manually execute every production step, the workflow now provides a repeatable path from source code to distribution.</p><p>The practical improvements include:</p><h3>Consistency</h3><p>Every release follows the same sequence of steps.</p><h3>Quality Gates</h3><p>Static analysis and tests execute before deployment.</p><h3>Traceability</h3><p>Releases can be connected to workflow runs, versions, commits, and artifacts.</p><h3>Security</h3><p>Production credentials remain inside protected CI secrets instead of source control.</p><h3>Less Manual Work</h3><p>Repeated build, validation, and upload operations are automated.</p><h3>Reliability</h3><p>There are fewer opportunities for small manual mistakes to affect a production release.</p><p>This is where CI/CD starts becoming an architectural capability rather than just a convenience.</p><h3>CI/CD Is Really About Confidence</h3><p>Speed is often the first benefit associated with CI/CD.</p><p>But for me, the more important benefit is <strong>confidence</strong>.</p><p>Without automation, the release question can become:</p><blockquote><em>“Did I remember every step?”</em></blockquote><p>With a well-designed pipeline, the question becomes:</p><blockquote><em>“Did the pipeline pass?”</em></blockquote><p>That is a much stronger engineering model.</p><p>The deployment process becomes documented in code, repeatable across releases, and protected by automated checks.</p><h3>There Is Still More to Improve</h3><p>A CI/CD pipeline is not something I consider permanently finished.</p><p>It can continue evolving with the application.</p><p>Useful next improvements may include:</p><ul><li>stronger unit and integration test coverage</li><li>automated release notes</li><li>environment-specific deployments</li><li>staged Google Play rollouts</li><li>automatic changelog generation</li><li>notifications when a release succeeds or fails</li><li>stronger artifact retention policies</li><li>deployment approvals for production</li><li>better observability around release duration and failures</li><li>automated rollback or recovery strategies where appropriate</li></ul><p>The important part is having a reliable foundation that can grow with the product.</p><h3>Final Thoughts</h3><p>For Flutter applications targeting both Android and iOS, CI/CD becomes increasingly valuable as the product matures.</p><p>Developers should spend their time improving applications, fixing problems, and building features — not repeatedly performing the same release procedure.</p><p>The objective is not automation for the sake of automation.</p><p>The objective is <strong>predictable delivery</strong>.</p><blockquote><em>Build. Test. Validate. Deploy. Repeat.</em></blockquote><p>That is the kind of release process I want behind every production mobile application.</p><p><strong>Waseem Akram Arain</strong><br><em>Senior Flutter Developer | Mobile Architect</em></p><h3>Medium Tags</h3><p>Flutter · CI/CD · DevOps · Mobile Development · Software Engineering</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92f9b49edf69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Multi-Display Magic in Android: Sending Messages to a Second Screen]]></title>
            <link>https://medium.com/@waseemarain_98671/multi-display-magic-in-android-sending-messages-to-a-second-screen-cd8225a9f3db?source=rss-bb2557ea447b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd8225a9f3db</guid>
            <dc:creator><![CDATA[Waseem Arain]]></dc:creator>
            <pubDate>Fri, 11 Apr 2025 19:30:57 GMT</pubDate>
            <atom:updated>2025-04-11T19:30:57.619Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever wondered how Android handles secondary displays? Whether it’s a smart mirror, a car dashboard, or an external monitor, Android provides powerful APIs to present unique content on external screens.<br>In this post, I’ll walk you through a simple, yet powerful, <a href="https://github.com/waseemarain4u/MultiDisplayApplicationAndroid">Multi-Display Android Application</a> that demonstrates how to send messages from your main display to a second screen in real-time. The app is built using native Android and leverages the Presentation API to handle external displays seamlessly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*ISbIubrlLMyD5QzNMmU6mw.png" /><figcaption>Main and Second Display</figcaption></figure><h4>💡 Use Case</h4><p>Imagine an app running on a tablet that’s connected to an external display, like a projector or a monitor. The primary user (on the tablet) types in messages, and those messages appear instantly on the secondary display. Perfect for use in kiosks, digital signage, presentations, or even gaming dashboards.</p><h4>🧱 Architecture Overview</h4><p>This app contains three main components:<br>1.<strong>MainActivity</strong> — Hosts the primary UI with input controls.<br>2.<strong>SecondDisplayPresentation</strong> — A custom Presentation class that manages UI rendering on the secondary display.<br>3.<strong>MessageAdapter</strong> — A simple RecyclerView adapter to show incoming messages.</p><h3>🎯 Core Functionality</h3><h4>1. Detecting and Showing a Secondary Display</h4><p>Using the DisplayManager, we check for available displays other than the default one.</p><pre>val displayManager = getSystemService(Context.DISPLAY_SERVICE) as DisplayManager<br>val secondDisplay = displayManager.displays.firstOrNull { it.displayId != Display.DEFAULT_DISPLAY }</pre><pre>presentation = SecondDisplayPresentation(this, secondDisplay)<br>presentation?.show()</pre><h4>2. Sending Messages</h4><p>The main display has an EditText and a Send button. When clicked, it checks if the presentation is active and pushes the message to it:</p><pre>presentation?.addMessage(message)</pre><h4>3. Rendering Messages on the Second Display</h4><p>The SecondDisplayPresentation sets up a RecyclerView to list the messages. It dynamically adds messages using:</p><pre>messages.add(message)<br>adapter.notifyItemInserted(messages.size - 1)</pre><h4>🖼️ UI Preview</h4><p><strong>Main Screen</strong>: A button to launch the presentation, a text input field, and a send button.<br><strong>Second Display</strong>: A dark-themed message list that updates in real-time.</p><h4>💻 Try It Yourself</h4><p>You can clone the project and run it on an Android device that supports secondary display output (like via HDMI or casting).</p><p>🔗 GitHub Repo:<br> 👉 <a href="https://github.com/waseemarain4u/MultiDisplayApplicationAndroid">https://github.com/waseemarain4u/MultiDisplayApplicationAndroid</a></p><h4>🧠 Final Thoughts</h4><p>The Presentation API might be one of Android’s lesser-used features, but it opens up tons of possibilities—from smart dashboards to educational apps. This project is a minimal yet practical demonstration of how simple it is to handle multi-display scenarios.</p><p>Give it a try, fork the repo, and feel free to contribute or raise issues. And if you found this helpful, don’t forget to ⭐️ the repo!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd8225a9f3db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Custom Interactive Star Rating Widget in Flutter]]></title>
            <link>https://medium.com/@waseemarain_98671/building-a-custom-interactive-star-rating-widget-in-flutter-31c7ed9fb261?source=rss-bb2557ea447b------2</link>
            <guid isPermaLink="false">https://medium.com/p/31c7ed9fb261</guid>
            <dc:creator><![CDATA[Waseem Arain]]></dc:creator>
            <pubDate>Tue, 10 Dec 2024 18:18:13 GMT</pubDate>
            <atom:updated>2024-12-10T18:18:13.309Z</atom:updated>
            <content:encoded><![CDATA[<p>In this post, we will walk through the process of creating a custom Flutter widget for a star-based rating system. Whether you’re building an app where users need to rate products, services, or content, this widget can be a perfect solution. It allows users to click on stars to select their rating, which then updates and displays in real-time.</p><p>In this post, we will walk through the process of creating a custom Flutter widget for a star-based rating system. Whether you’re building an app where users need to rate products, services, or content, this widget can be a perfect solution. It allows users to click on stars to select their rating, which then updates and displays in real-time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gENa26kPo_-G3JZyseY54A.png" /></figure><h3>What’s Inside the Widget?</h3><ul><li><strong>Custom Star Shape</strong>: The stars are custom-drawn using CustomClipper to give them a unique, interactive look.</li><li><strong>Interactive Rating</strong>: Users can tap on a star, select their rating, and the widget will update instantly.</li><li><strong>Callback Function</strong>: The parent widget receives the updated rating via a callback, making it easy to use the selected value.</li></ul><p>Let’s dive into how it works!</p><h3>Key Features</h3><ul><li><strong>Custom Star Shape</strong>: Instead of relying on basic icons, this widget uses a custom clipper to draw a star.</li><li><strong>Real-time Rating</strong>: When a user taps on a star, the rating is updated instantly.</li><li><strong>Flexible Configuration</strong>: You can set the number of stars (maximum rating), an initial rating, and a callback function to handle the selected rating.</li><li><strong>Custom Border</strong>: The border of each star is drawn using a CustomPainter, giving you full control over the appearance.</li></ul><h3>How to Use the Rating Widget</h3><p>To start using this widget in your Flutter app, follow these simple steps.</p><h3>Step 1: Add the Widget to Your Project</h3><p>First, copy the RatingWidget, StarClipper, and StarBorderPainter classes into your project.</p><h3>Step 2: Use the Rating Widget</h3><p>You can now easily integrate the widget into your UI like this:</p><pre>RatingWidget(<br>  title: &#39;Rate this item&#39;, // The rating question or label<br>  initialRating: 3.0, // Set an initial rating (0.0 to 5.0)<br>  onRatingSelected: (rating) {<br>    print(&#39;Selected Rating: $rating&#39;); // Handle the updated rating<br>  },<br>)</pre><h3>Parameters:</h3><ul><li><strong>title</strong>: A label or question asking the user to rate an item (e.g., &quot;Rate this item&quot;).</li><li><strong>maxRating</strong>: The maximum number of stars. The default value is 5.</li><li><strong>initialRating</strong>: The initial rating that is pre-selected when the widget loads.</li><li><strong>onRatingSelected</strong>: A callback function that receives the updated rating when a user selects a star.</li></ul><h3>Example UI:</h3><p>Here’s an example of how this would look in your app:</p><pre>MaterialApp(<br>  debugShowCheckedModeBanner: false,<br>  home: Scaffold(<br>    appBar: AppBar(title: Text(&#39;Rating Widget&#39;)),<br>    body: Center(<br>      child: RatingWidget(<br>        title: &#39;Rate this item&#39;,<br>        initialRating: 3.0,<br>        onRatingSelected: (rating) {<br>          print(&#39;Selected Rating: $rating&#39;);<br>        },<br>      ),<br>    ),<br>  ),<br>)</pre><h3>Behind the Scenes: How It Works</h3><h3>Custom Star Shape</h3><p>We created the star shape using a CustomClipper. This allows us to define a star path with polar coordinates, which we then use to clip a widget. By alternating between an outer and an inner radius, we create the star’s distinctive look.</p><p>Here’s the StarClipper class that defines the star shape:</p><pre>class StarClipper extends CustomClipper&lt;Path&gt; {<br>  @override<br>  Path getClip(Size size) {<br>    final path = Path();<br>    final center = Offset(size.width / 2, size.height / 2);<br>    final outerRadius = size.width / 2;<br>    final innerRadius = outerRadius / 2.5;<br>    final angle = pi / 5;<br><br>    for (int i = 0; i &lt; 10; i++) {<br>      final isOuter = i.isEven;<br>      final radius = isOuter ? outerRadius : innerRadius;<br>      final x = center.dx + radius * cos(i * angle - pi / 2);<br>      final y = center.dy + radius * sin(i * angle - pi / 2);<br>      if (i == 0) {<br>        path.moveTo(x, y);<br>      } else {<br>        path.lineTo(x, y);<br>      }<br>    }<br>    path.close();<br>    return path;<br>  }<br><br>  @override<br>  bool shouldReclip(covariant CustomClipper&lt;Path&gt; oldClipper) =&gt; false;<br>}</pre><h3>Custom Painter for the Border</h3><p>The StarBorderPainter class takes care of painting the border of each star. It uses CustomPainter to draw the outline of the star with a specified color. You can customize the border style (e.g., thickness, color) easily.</p><pre>class StarBorderPainter extends CustomPainter {<br>  final Color borderColor;<br><br>  StarBorderPainter({required this.borderColor});<br><br>  @override<br>  void paint(Canvas canvas, Size size) {<br>    final paint = Paint()<br>      ..color = borderColor<br>      ..style = PaintingStyle.stroke<br>      ..strokeWidth = 2.0;<br><br>    final path = StarClipper().getClip(size);<br>    canvas.drawPath(path, paint);<br>  }<br><br>  @override<br>  bool shouldRepaint(covariant CustomPainter oldDelegate) =&gt; false;<br>}</pre><h3>Customizing the Widget</h3><ul><li><strong>Star Size</strong>: You can adjust the size of the stars by modifying the width and height values in the Container widget.</li><li><strong>Border Color</strong>: You can change the color of the star’s border by updating the borderColor parameter when creating a StarBorderPainter.</li><li><strong>Rating Logic</strong>: If you need to change the way the rating behaves (for example, make it allow half-stars), you can modify the _handleRatingUpdate method to suit your needs.</li></ul><h3>Conclusion</h3><p>This custom Flutter widget is a simple, flexible way to implement a star rating system in your app. With the power of CustomClipper and CustomPainter, you can create unique, interactive UI elements while keeping the code clean and maintainable.</p><p>Feel free to modify and enhance the widget to fit your specific needs. Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31c7ed9fb261" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Flutter is better?]]></title>
            <link>https://medium.com/@waseemarain_98671/why-flutter-is-better-eafb30b89e25?source=rss-bb2557ea447b------2</link>
            <guid isPermaLink="false">https://medium.com/p/eafb30b89e25</guid>
            <dc:creator><![CDATA[Waseem Arain]]></dc:creator>
            <pubDate>Wed, 21 Jun 2023 10:57:25 GMT</pubDate>
            <atom:updated>2023-06-21T11:19:34.276Z</atom:updated>
            <content:encoded><![CDATA[<p>Flutter, developed by Google, is a popular cross-platform framework known for its numerous advantages over other frameworks. Here are some reasons why Flutter is often considered better than other cross-platform frameworks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*3-M8z7qtE32OgRGQEBSX-Q.png" /></figure><ol><li>Single Codebase: Flutter allows developers to write a single codebase that can be used to create applications for multiple platforms, including iOS, Android, web, and desktop. This means you don’t have to maintain separate codebases for different platforms, which significantly reduces development time and effort.</li><li>Fast Development: Flutter offers a hot reload feature that allows developers to see the changes made in the code almost instantly, without requiring a full app restart. This greatly speeds up the development process, as developers can iterate quickly and see the results in real-time.</li><li>Native Performance: Flutter uses a rendering engine called Skia to create its user interfaces, which enables it to produce highly performant and visually appealing UIs. Flutter apps are compiled to native code, allowing them to run directly on the device’s hardware, resulting in excellent performance and responsiveness.</li><li>Rich UI: Flutter provides a rich set of customizable UI widgets that conform to the design guidelines of both iOS and Android. These widgets can be easily customized to create beautiful and consistent user interfaces across different platforms.</li><li>Access to Native Features: Flutter offers excellent native integration, allowing developers to access device-specific features and APIs easily. It provides a comprehensive set of plugins that enable interaction with platform-specific functionalities, such as camera, geolocation, sensors, and more.</li><li>Strong Community and Support: Flutter has a large and active community of developers, which means you can find numerous resources, tutorials, and open-source packages to aid your development process. The community also provides valuable support and assistance through forums, chat groups, and documentation.</li><li>Cost-effectiveness: Developing with Flutter can be cost-effective, as you only need to maintain a single codebase for multiple platforms. This reduces the need for separate teams or specialized developers for each platform, resulting in time and cost savings.</li><li>Future-proofing: Flutter is backed by Google, which means it has strong long-term support and is likely to receive regular updates, improvements, and new features. This makes it a reliable choice for developing cross-platform applications.</li></ol><p>While Flutter has numerous advantages, it’s important to consider your specific project requirements and the expertise of your development team before choosing any framework.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eafb30b89e25" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>