<?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 Rishabh Singh on Medium]]></title>
        <description><![CDATA[Stories by Rishabh Singh on Medium]]></description>
        <link>https://medium.com/@singhrishabh1670?source=rss-7fb186001b0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*69-BLHg4FyQGLqi5Vmn7Sw.jpeg</url>
            <title>Stories by Rishabh Singh on Medium</title>
            <link>https://medium.com/@singhrishabh1670?source=rss-7fb186001b0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:03:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@singhrishabh1670/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[How to Become an AWS Community Builder in 2026]]></title>
            <link>https://medium.com/@singhrishabh1670/how-to-become-an-aws-community-builder-in-2026-d27b5b904e3f?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d27b5b904e3f</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[awscommunitybuilder]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Tue, 20 Jan 2026 05:11:39 GMT</pubDate>
            <atom:updated>2026-01-20T05:11:39.490Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4UDxc5JqbbmnpxlY.png" /></figure><p>AWS Community Builders is a global program for cloud enthusiasts who love sharing knowledge and connecting with others in the AWS ecosystem. It gives you access to mentorship, AWS experts, exclusive events, and resources to grow technically and personally. Here’s how you can plan, apply, and increase your chances of becoming a builder.</p><h3>What Is the AWS Community Builders Program</h3><p>AWS Community Builders is an official program by Amazon Web Services for people passionate about cloud and AWS technology. As a builder, you join a global network of peers who create content, organize meetups, speak at events, and help others learn about AWS. Members get benefits such as access to AWS product teams, networking opportunities, promotional credits, private community channels, and more.</p><h3>Why You Should Become an AWS Community Builder</h3><p>Being part of this program helps you grow in several ways:</p><p>• Access to AWS product updates before many others.</p><p>• Mentorship from AWS experts.</p><p>• Networking with other builders and community leaders.</p><p>• Support for content creation and community initiatives.</p><p>• AWS credits, swag, and sometimes exclusive opportunities at AWS events.</p><h3>Who Can Apply</h3><p>The program is open to anyone who:</p><p>• Is at least 18 years old.</p><p>• Has passion for learning AWS and sharing knowledge with others.</p><p>• Has some experience with AWS services or cloud technologies.</p><p>• Enjoys creating content, participating in events, or engaging with tech communities.</p><p>There is no strict requirement for certifications, but demonstrating your involvement with AWS is helpful.</p><h3>When to Apply</h3><p>Applications usually open <strong>once a year</strong>. If the application window is not open, you can join the <strong>waitlist</strong> and receive a notification when it opens again.</p><h3>Official Apply Page</h3><p>Here is the link to the AWS Community Builders official page where you can apply or join the waitlist:</p><p><strong>👉 </strong><a href="https://aws.amazon.com/developer/community/community-builders/?utm_source=chatgpt.com"><strong>https://aws.amazon.com/developer/community/community-builders/</strong></a></p><p>When the application form is live, you will see an <strong>Apply Now</strong> button on this page.</p><h3>Step-by-Step Guide to Apply</h3><h3>Step 1: Prepare Your Portfolio</h3><p>Before applying, prepare a set of <strong>public links</strong> that showcase your AWS-related work. These could include:</p><p>• Technical blog posts on Medium, Dev.to, or personal blog.</p><p>• AWS tutorials, architecture guides, or code examples.</p><p>• YouTube videos or recorded sessions.</p><p>• GitHub repositories of your projects.</p><p>Gather your best content before starting the application.</p><h3>Step 2: Decide Your Focus Area</h3><p>During the application, you will choose one or more technical categories such as:</p><p>• Serverless<br> • DevOps &amp; CI/CD<br> • Data &amp; Analytics<br> • Machine Learning<br> • Cloud Security</p><p>Pick the category that best aligns with your experience and interests.</p><h3>Step 3: Share Your Cloud Story</h3><p>You will be asked to write a brief narrative about:</p><p>• Why you love AWS.</p><p>• How you have learned and shared your AWS knowledge.</p><p>• What you hope to achieve as a Community Builder.</p><p>Try to be genuine and clear about your goals and community impact.</p><h3>Step 4: Show Community Impact</h3><p>Provide links to:</p><p>• Blog articles, videos, tutorials.</p><p>• Events you have spoken at or helped organize.</p><p>• Social posts that helped others with AWS knowledge.</p><h3>Step 5: Complete the Form and Submit</h3><p>Finish the remaining questions about your background and community activities. After submission, applications are reviewed by the AWS team. It may take several weeks to get a response.</p><h3>How to Increase Your Chances of Acceptance</h3><p>Since the program is competitive, here are practical tips:</p><p>• <strong>Write regularly</strong>: Publish at least a few AWS-focused blog posts before you apply.</p><p>• <strong>Build real projects</strong>: Deploy AWS projects and share your architecture and code.</p><p>• <strong>Participate in tech communities</strong>: Join AWS user groups, forums, Discord or Slack channels.</p><p>• <strong>Earn a certification</strong>: AWS certifications demonstrate your commitment and understanding.</p><p>• <strong>Speak at events</strong>: Organize or present tech talks locally or online.</p><p>Collect links to these activities as evidence in your application.</p><h3>After You Apply</h3><p>You will receive an email with the decision. If accepted:</p><p>• Join community calls and mentorship sessions.</p><p>• Keep creating content and engaging with builders.</p><p>• Make meaningful contributions to help others learn AWS.</p><p>If you are not accepted this cycle, don’t be discouraged. Use the time to publish more content and refine your application for the next window.</p><h3>Final Thoughts</h3><p>Becoming an AWS Community Builder is not just about getting badges or perks. It is about growing as a cloud professional, contributing to the global tech community, and building meaningful connections. Start early by blogging, coding, and engaging with others, then apply confidently when the next window opens.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d27b5b904e3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building and Scaling Next.js Applications with AWS App Router and Serverless Infrastructure]]></title>
            <link>https://medium.com/@singhrishabh1670/building-and-scaling-next-js-applications-with-aws-app-router-and-serverless-infrastructure-8e8734fdd913?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e8734fdd913</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[nextjs]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Tue, 20 Jan 2026 04:22:07 GMT</pubDate>
            <atom:updated>2026-01-20T04:22:07.897Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KrnIWi_fCumIW55IWUvegQ.jpeg" /></figure><p>Next.js has evolved rapidly, especially with the App Router, React Server Components, and streaming. At the same time, AWS continues to refine its serverless ecosystem. Combining modern Next.js with AWS serverless services opens a powerful path for building fast, scalable, and cost efficient web applications.</p><p>This article explores a modern AWS-centric approach to deploying and scaling Next.js applications using serverless infrastructure.</p><h3>Why AWS for Modern Next.js</h3><p>Next.js applications today are no longer just static sites. They often rely on server components, edge rendering, API routes, and background jobs. AWS provides a mature platform that supports all of these needs with high reliability and global reach.</p><p>Key AWS advantages include:</p><ul><li>Global content delivery with CloudFront</li><li>Serverless compute using AWS Lambda</li><li>Edge execution with Lambda at Edge or CloudFront Functions</li><li>Secure authentication and APIs with AWS services</li></ul><h3>Architecture Overview</h3><p>A modern Next.js application on AWS can be split into three layers:</p><ol><li><strong>Frontend Delivery</strong><br> Static assets such as images, CSS, and JavaScript are served through Amazon CloudFront. This ensures low latency for users worldwide.</li><li><strong>Server Rendering and APIs</strong><br> Dynamic rendering and API routes run on AWS Lambda. The App Router allows server components to fetch data directly from backend services without exposing APIs to the client.</li><li><strong>Data and Services</strong><br> Backend services like DynamoDB, Aurora Serverless, or S3 handle persistence. Authentication can be managed with Amazon Cognito.</li></ol><h3>Using Next.js App Router with AWS Lambda</h3><p>The App Router encourages server first thinking. Components can run on the server, fetch data securely, and stream UI to the client. When deployed on AWS Lambda, this results in highly scalable rendering without managing servers.</p><p>Benefits include:</p><ul><li>Automatic scaling per request</li><li>Pay only for execution time</li><li>Built-in fault tolerance</li></ul><p>Frameworks like SST or AWS CDK simplify deploying Next.js to Lambda by handling routing, bundling, and infrastructure as code.</p><h3>Edge Rendering with CloudFront</h3><p>For pages that need ultra low latency, AWS edge solutions are a strong option. CloudFront Functions are ideal for lightweight logic such as redirects and headers. Lambda at Edge supports more complex rendering tasks.</p><p>Next.js middleware integrates well here, enabling:</p><ul><li>Geo based routing</li><li>Authentication checks at the edge</li><li>A faster time to first byte</li></ul><h3>Handling Images and Assets</h3><p>Next.js Image Optimization can be offloaded to AWS infrastructure. Images stored in S3 can be served through CloudFront with caching and compression. This reduces load on server functions and improves performance.</p><h3>Cost and Performance Considerations</h3><p>Serverless Next.js on AWS is cost efficient when traffic is variable. Cold starts are less noticeable with streaming and edge rendering. Caching strategies using CloudFront and ISR reduce compute usage further.</p><p>Best practices include:</p><ul><li>Enable caching headers aggressively</li><li>Use Incremental Static Regeneration for content pages</li><li>Prefer edge middleware for lightweight logic</li></ul><h3>Final Thoughts</h3><p>Next.js and AWS are converging toward a future where applications are globally distributed by default. By combining the App Router with AWS serverless services, developers can build applications that are fast, scalable, and secure without managing infrastructure.</p><p>This approach is well suited for startups and enterprises alike, especially teams aiming to ship quickly while maintaining production grade reliability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e8734fdd913" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Scalable Video Conferencing System for Teachora Using Jitsi Meet SDK on AWS EC2]]></title>
            <link>https://medium.com/@singhrishabh1670/building-a-scalable-video-conferencing-system-for-teachora-using-jitsi-meet-sdk-on-aws-ec2-b34c3b089374?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b34c3b089374</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-ec2]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Mon, 05 Jan 2026 17:42:45 GMT</pubDate>
            <atom:updated>2026-01-05T17:42:45.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jc4BeVpMqSjjMoKcekscJA.png" /></figure><p>Teachora is an online teaching platform that requires secure, high quality, and real time video conferencing to connect educators and learners seamlessly. To support this requirement, I deployed the Jitsi Meet SDK on an AWS EC2 instance and integrated it into the Teachora application hosted at <strong>myteachora.com</strong>.</p><p>This approach gives full control over video infrastructure, ensures privacy, and allows the platform to scale as the Teachora user base grows.</p><p>This blog explains the overall architecture, EC2 setup, Jitsi installation, and how everything works together inside the Teachora app.</p><h3>Why Jitsi Meet SDK for Teachora</h3><p>Jitsi Meet is an open source video conferencing solution that supports audio, video, chat, screen sharing, and session recording. By using the Jitsi Meet SDK, Teachora can embed video calling directly into the platform while maintaining consistent branding and user experience.</p><p>Key benefits for Teachora:</p><ul><li>No per minute video calling costs</li><li>Full control over data and privacy</li><li>Custom UI and feature configuration</li><li>Secure self hosted infrastructure</li><li>Smooth integration with web and mobile apps</li></ul><h3>System Architecture Overview</h3><p>Teachora’s video conferencing architecture is built around an AWS EC2 instance running the Jitsi Meet server. Teachers and learners connect through the Teachora app, which communicates with Jitsi using secure HTTPS and WebRTC protocols.</p><p>Main components:</p><ul><li>AWS EC2 instance running Ubuntu</li><li>Jitsi Meet server</li><li>Nginx reverse proxy</li><li>Custom domain and SSL certificate</li><li>Teachora web and mobile apps using Jitsi SDK</li></ul><h3>Step 1: Creating an EC2 Instance</h3><p>The first step is setting up an EC2 instance from the AWS Management Console.</p><p>Recommended configuration:</p><ul><li>Operating system: Ubuntu 20.04 or 22.04 LTS</li><li>Instance type: t3.medium or higher for production usage</li><li>Storage: At least 30 GB SSD</li><li>Security group configuration:</li><li>TCP port 80 for HTTP</li><li>TCP port 443 for HTTPS</li><li>UDP port 10000 for Jitsi media traffic</li><li>TCP port 22 for SSH access</li></ul><p>Once the instance is live, connect to it securely using SSH.</p><h3>Step 2: Installing Jitsi Meet on EC2</h3><p>After connecting to the server, update the system and install Jitsi Meet.</p><p>Installation flow:</p><ol><li>Configure the server hostname with your domain</li><li>Add the official Jitsi package repository</li><li>Install Jitsi Meet packages</li><li>Configure firewall rules</li><li>Enable SSL using Let’s Encrypt</li></ol><p>During setup, enter the Teachora video domain and enable SSL. A valid domain is required for WebRTC to function properly in modern browsers.</p><p>After installation, open the domain in a browser to verify the Jitsi Meet interface is running successfully.</p><h3>Step 3: Securing the Teachora Video Platform</h3><p>Security is a top priority for Teachora to protect teachers, learners, and session data.</p><p>Recommended security measures:</p><ul><li>Enable JWT based authentication</li><li>Restrict room creation to authorized Teachora users</li><li>Assign roles for teachers and learners</li><li>Disable anonymous access</li><li>Apply strict firewall and server hardening rules</li><li>Keep the server and Jitsi packages updated</li></ul><p>JWT authentication ensures that only users from <strong>myteachora.com</strong> can create or join video sessions.</p><h3>Step 4: Integrating Jitsi Meet SDK into Teachora</h3><p>Instead of redirecting users to an external meeting page, Teachora uses the Jitsi Meet SDK to embed video conferencing directly inside the application.</p><p>Integration flow:</p><ul><li>Teachora backend generates a secure JWT token</li><li>The app launches a Jitsi meeting using the SDK</li><li>The token authenticates the user and role</li><li>Teachers and learners join the same session securely</li></ul><p>The SDK enables:</p><ul><li>Custom meeting controls</li><li>Branded UI matching Teachora</li><li>Screen sharing and chat</li><li>Session events and analytics</li></ul><p>This creates a smooth virtual classroom experience fully integrated into Teachora.</p><h3>Step 5: Scaling and Performance Optimization</h3><p>As Teachora grows, the video infrastructure must scale reliably.</p><p>Best practices include:</p><ul><li>Monitoring CPU, memory, and network usage</li><li>Increasing instance size during peak hours</li><li>Using autoscaling groups for high traffic</li><li>Running separate services for recording and streaming</li><li>Optimizing video quality based on network conditions</li></ul><p>For large scale usage, multiple Jitsi servers can be deployed behind a load balancer to ensure high availability.</p><h3>Final Thoughts</h3><p>Deploying Jitsi Meet SDK on AWS EC2 is a strong foundation for Teachora’s video conferencing needs. It provides flexibility, security, and scalability while keeping operational costs under control. With proper authentication and infrastructure planning, Teachora can deliver a reliable and engaging online teaching experience through <a href="https://www.myteachora.com/"><strong>myteachora.com</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b34c3b089374" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing Push Notifications with Firebase Cloud Messaging in Flutter]]></title>
            <link>https://medium.com/@singhrishabh1670/implementing-push-notifications-with-firebase-cloud-messaging-in-flutter-568fbf08eb3d?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/568fbf08eb3d</guid>
            <category><![CDATA[notifications]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[fcm-push-notification]]></category>
            <category><![CDATA[firebase]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Fri, 28 Feb 2025 08:36:31 GMT</pubDate>
            <atom:updated>2025-02-28T08:36:31.862Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*DcLWeL3oEOOhU7lF.png" /><figcaption>Source: Internet</figcaption></figure><p>Push notifications are a crucial feature for modern apps, keeping users engaged and informed. In this blog, we’ll walk through adding push notifications to a Flutter app using <strong>Firebase Cloud Messaging (FCM)</strong>.</p><p>Let’s break it down step by step! 🛠️</p><h3>Step 1: Set Up Firebase Project</h3><ol><li><strong>Create a Firebase Project:</strong> Go to Firebase Console → Add Project → Follow the setup.</li><li><strong>Register Your App:</strong> Add your app’s package name.</li><li><strong>Download and Add the Config Files:</strong></li></ol><ul><li>For Android: Add google-services.json in android/app.</li><li>For iOS: Add GoogleService-Info.plist in ios/Runner.</li></ul><p>4. <strong>Update Android Files:</strong></p><pre>// android/build.gradle<br>classpath &#39;com.google.gms:google-services:4.4.0&#39;<br><br>// android/app/build.gradle<br>apply plugin: &#39;com.google.gms.google-services&#39;</pre><p>5. <strong>Update iOS Files:</strong></p><pre>&lt;!-- ios/Runner/Info.plist --&gt;<br>&lt;key&gt;FirebaseAppDelegateProxyEnabled&lt;/key&gt;<br>&lt;false/&gt;</pre><p>Run flutter pub add firebase_core firebase_messaging to install dependencies.</p><h3>Step 2: Initialize Firebase in Flutter</h3><pre>import &#39;package:firebase_core/firebase_core.dart&#39;;<br>import &#39;package:flutter/material.dart&#39;;<br><br>void main() async {<br>  WidgetsFlutterBinding.ensureInitialized();<br>  await Firebase.initializeApp();<br>  runApp(MyApp());<br>}</pre><h3>Step 3: Configure Firebase Messaging</h3><p>Create a service to handle notifications:</p><pre>import &#39;package:firebase_messaging/firebase_messaging.dart&#39;;<br><br>class NotificationService {<br>  final FirebaseMessaging _firebaseMessaging = FirebaseMessaging.instance;<br><br>  void initNotifications() {<br>    _firebaseMessaging.requestPermission();<br>    FirebaseMessaging.onMessage.listen((RemoteMessage message) {<br>      print(&#39;Foreground message received: ${message.notification?.title}&#39;);<br>    });<br><br>    FirebaseMessaging.onMessageOpenedApp.listen((RemoteMessage message) {<br>      print(&#39;Notification clicked: ${message.notification?.body}&#39;);<br>    });<br>  }<br>}</pre><h3>Step 4: Get and Print the Device Token</h3><p>You need the device token to send notifications:</p><pre>void getToken() async {<br>  String? token = await FirebaseMessaging.instance.getToken();<br>  print(&quot;FCM Token: $token&quot;);<br>}</pre><h3>Step 5: Update Main App</h3><p>Use the notification service in your main app:</p><pre>class MyApp extends StatelessWidget {<br>  final NotificationService _notificationService = NotificationService();<br><br>  @override<br>  Widget build(BuildContext context) {<br>    _notificationService.initNotifications();<br>    getToken();<br><br>    return MaterialApp(<br>      home: Scaffold(<br>        appBar: AppBar(title: Text(&#39;FCM Push Notifications&#39;)),<br>        body: Center(child: Text(&#39;Waiting for notifications...&#39;)),<br>      ),<br>    );<br>  }<br>}</pre><h3>Step 6: Test Notifications</h3><ol><li><strong>Run Your App:</strong> Launch the app on a real device (not emulator).</li><li><strong>Send a Test Notification:</strong> Go to the Firebase console → Cloud Messaging → New Notification → Add title/body → Send.</li><li><strong>Verify the Notification:</strong> You should see the message in the console or as a push notification.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=568fbf08eb3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Show Colorful Emojis on Flutter Web]]></title>
            <link>https://medium.com/@singhrishabh1670/how-to-show-colorful-emojis-on-flutter-web-94daeb0b6f88?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/94daeb0b6f88</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Sun, 09 Feb 2025 16:06:47 GMT</pubDate>
            <atom:updated>2025-02-09T16:06:47.026Z</atom:updated>
            <content:encoded><![CDATA[<p>Flutter web is a fantastic way to build cross-platform applications, but emojis appear in monochrome instead of their colourful versions. If you’ve encountered this and want to add vibrant, colourful emojis to your Flutter web project, this guide will walk you through the steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/0*ah5yqPy7xg7IaJWb" /><figcaption>Source: Internet</figcaption></figure><h3>Step 1: Create a Custom flutter_bootstrap.js File</h3><p>Flutter uses a JavaScript bootstrap file to initialize the app on the web. To enable colourful emojis, we’ll modify this initialization process.</p><ol><li>Inside your Flutter project, navigate to the web folder.</li><li>Create a new file named flutter_bootstrap.js.</li><li>Add the following code to flutter_bootstrap.js:</li></ol><pre>{{flutter_js}}<br>{{flutter_build_config}}<br><br>_flutter.loader.load({<br>    onEntrypointLoaded: async function(engineInitializer) {<br>        const appRunner = await engineInitializer.initializeEngine({<br>            useColorEmoji: true<br>        });<br><br>        await appRunner.runApp();<br>    }<br>});</pre><p>This script initializes the Flutter engine with the useColorEmoji: true flag, enabling colourful emoji rendering in your app.</p><h3>Step 2: Update Your index.html</h3><p>Make sure your index.html references the new flutter_bootstrap.js file.</p><ol><li>Open the web/index.html file.</li><li>Replace the existing script tag with:</li></ol><pre>&lt;script src=&quot;flutter_bootstrap.js&quot; async&gt;&lt;/script&gt;</pre><h3>This ensures that your custom bootstrap script is used when the app runs.</h3><h3>Step 3: Clean and Rebuild the Project</h3><p>After updating the bootstrap file, a simple hot reload won’t apply the changes. Follow these steps to rebuild the project from scratch:</p><ol><li><strong>Close the app</strong> if it is currently running.</li><li>Run the following commands in your terminal:</li></ol><pre>flutter clean<br>flutter pub get<br>flutter run</pre><blockquote><strong><em>Note:</em></strong><em> Hot reload will not apply these changes. You must perform a full restart by stopping and rerunning the app.</em></blockquote><h3>Final Thoughts</h3><p>After following these steps, your Flutter web app should now display colourful emojis beautifully. This simple tweak can significantly enhance the visual appeal of your application, especially if you’re building chat apps, social platforms, or any app where emojis play a big role!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94daeb0b6f88" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the Difference Between APK and AAB Android Files: A Guide for Flutter Developers]]></title>
            <link>https://medium.com/@singhrishabh1670/understanding-the-difference-between-apk-and-aab-android-files-a-guide-for-flutter-developers-35ebb8968c11?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/35ebb8968c11</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[apk]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Sat, 08 Feb 2025 08:40:33 GMT</pubDate>
            <atom:updated>2025-02-08T08:40:33.630Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*olF9QxredGovyGcp.jpeg" /><figcaption>Source: Internet</figcaption></figure><p>When developing apps with Flutter, especially for Android, you’ll encounter two primary file formats for distributing your applications: APK and AAB. While both serve the purpose of delivering your app to users, they significantly differ in how they are built, distributed, and installed. In this blog, we’ll dive deep into the distinctions between APK and AAB, helping you decide which format best suits your needs.</p><h3>What Are APK and AAB?</h3><h3>APK: Android Application Package</h3><p>APK stands for <strong>Android Package Kit</strong> or <strong>Android Application Package</strong>. It is the traditional file format used to distribute and install applications on Android devices. Think of an APK as a “zip” file that contains all the resources, code, and metadata needed to run your app.</p><h3>AAB: Android Application Bundle</h3><p>AAB stands for <strong>Android Application Bundle</strong>. Introduced by Google in 2018, AAB is a more modern format that allows developers to submit their app as a bundle of resources. Google Play then uses this bundle to generate optimized APK files tailored to the specific device configurations of users.</p><h3>Key Differences Between APK and AAB</h3><h3>1. Submission Process</h3><ul><li><strong>APK:</strong> When you create an APK file, it’s submitted to Google Play and later downloaded by users in the exact form as it was created. There’s no modification by Google Play.</li><li><strong>AAB:</strong> When you submit an AAB to Google Play, it is split into smaller APK files (known as <strong>split APKs</strong>). Each split APK corresponds to specific device configurations like screen size, architecture, and language preferences. This ensures that users only download the necessary components for their devices.</li></ul><h3>2. Installation</h3><ul><li><strong>APK:</strong> APK files can be directly installed on any Android device. This is particularly useful for sideloading apps during development or testing.</li><li><strong>AAB:</strong> AAB files <strong>cannot</strong> be installed directly on devices. Instead, they rely on Google Play to generate and serve optimized APKs to users. This means that sideloading is not possible with AAB files unless you use tools like <strong>bundletool</strong> to manually generate APKs.</li></ul><h3>3. App Size</h3><ul><li><strong>APK:</strong> APK files generally result in larger app sizes because they include all resources (e.g., images, languages, device configurations) regardless of whether they are needed on the target device.</li><li><strong>AAB:</strong> AAB files lead to smaller app sizes since Google Play generates APKs that only include device-specific resources. This optimization reduces download size and storage usage.</li></ul><h3>4. Dynamic Features</h3><ul><li><strong>APK:</strong> All feature-based resources are stored within the APK itself. If your app has optional features, they are bundled into the APK whether users need them or not.</li><li><strong>AAB:</strong> AAB supports <strong>Dynamic Delivery</strong>, which allows you to separate features into modules. These dynamic feature modules are stored on Google Play and are only downloaded when needed, improving performance and reducing initial app size.</li></ul><h3>5. Asset Packs</h3><ul><li><strong>APK:</strong> All assets, including those not needed immediately, are stored in the APK file. This can lead to bloated app sizes.</li><li><strong>AAB:</strong> AAB supports <strong>Asset Packs</strong>, allowing non-essential assets to be stored on Google Play. These assets are downloaded on-demand, further reducing the initial app size.</li></ul><h3>6. App Churn</h3><ul><li><strong>APK:</strong> Larger app sizes can lead to higher app churn rates (users uninstalling the app due to storage constraints).</li><li><strong>AAB:</strong> Smaller app sizes contribute to lower app churn rates since users are less likely to uninstall apps that consume less storage.</li></ul><h3>7. Storage Efficiency</h3><ul><li><strong>APK:</strong> Since all resources are bundled together, unnecessary files take up device storage, leading to inefficient space utilization.</li><li><strong>AAB:</strong> By only including necessary resources, AAB improves storage efficiency, leaving more space available on users’ devices.</li></ul><h3>Which Should You Choose for Your Flutter App?</h3><ul><li><strong>For Development and Testing:</strong> APKs are preferable because they can be directly installed on devices without going through Google Play. This makes testing quicker and more straightforward.</li><li><strong>For Distribution on Google Play:</strong> AAB is the recommended format. Google has made AAB the default format for new apps published on the Play Store starting from August 2021. The benefits of smaller app sizes and dynamic delivery make AAB the better choice for end-users.</li><li><strong>For Sideloading:</strong> If you plan to distribute your app outside the Play Store (e.g., via your website or other marketplaces), APK is the way to go since AAB cannot be sideloaded without additional tools.</li></ul><h3>Conclusion</h3><p>Understanding the differences between APK and AAB files is crucial for optimizing your Flutter app’s performance, storage usage, and user experience. While APKs are still useful for development and sideloading, AABs offer significant advantages for app distribution on Google Play, including smaller app sizes and dynamic feature delivery.</p><p>As a Flutter developer, embracing AAB can help you deliver better, more efficient apps to your users while staying aligned with Google’s evolving ecosystem.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35ebb8968c11" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hosting a Flutter Web Application with AWS Amplify Gen 2]]></title>
            <link>https://medium.com/@singhrishabh1670/hosting-a-flutter-web-application-with-aws-amplify-gen-2-5e33e99165a0?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e33e99165a0</guid>
            <category><![CDATA[amplify]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[hosting]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[flutter-web]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 15:14:35 GMT</pubDate>
            <atom:updated>2025-02-04T15:14:35.524Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/613/0*YpXDKuFFYhE_FKyd.png" /><figcaption>Source: <a href="https://github.com/agnostech/flutter_amplify">https://github.com/agnostech/flutter_amplify</a></figcaption></figure><h3>Introduction</h3><p>Flutter is a powerful UI toolkit that enables developers to build cross-platform applications for mobile, desktop, and web from a single codebase. With seamless web deployment capabilities, developers seek efficient hosting solutions. AWS Amplify Gen 2 introduces several new features, including an improved integration with Git workflows for both backend and hosting solutions, facilitated by Amplify Console’s enhanced UI.</p><p>In this guide, you will learn how to host a Flutter web application using Amplify Hosting with project code stored on GitHub. This tutorial applies to any supported Git provider, including BitBucket, GitLab, and CodeCommit.</p><h3>Prerequisites</h3><p>Before starting, ensure you have:</p><ul><li>An AWS account</li><li>Flutter SDK installed on your device</li><li>An account on a supported Git provider (GitHub will be used in this example)</li></ul><h3>Creating a Flutter Web Project</h3><p>Begin by creating a new Flutter project with web support using the following command:</p><pre>flutter create amplify_gen2_website --platform web</pre><p>This command generates a Flutter project with only web support enabled. Next, upload the project to GitHub using your preferred Git tool. Here’s how to do it using VSCode:</p><ol><li>Open the project in VSCode.</li><li>Open the Command Palette using Shift + Command + P (Mac) or Ctrl + Shift + P (Windows/Linux).</li><li>Select <strong>“Share on GitHub”</strong>.</li><li>Choose between a private or public repository, name your repository, and publish the project.</li><li>Once uploaded, verify the repository on GitHub.</li></ol><h3>Deploying on AWS Amplify</h3><h3>Step 1: Create a New App</h3><ol><li>Navigate to <strong>AWS Amplify</strong> in the AWS console.</li><li>Click <strong>“Create new app”</strong>.</li><li>Choose <strong>GitHub</strong> (or your preferred Git provider).</li><li>Grant AWS Amplify access to your repository.</li></ol><h3>Step 2: Configure the Build Settings</h3><ol><li>Select your repository and branch.</li><li>Update the <strong>Frontend build command</strong> to:</li></ol><pre>flutter build web</pre><p>3. Set the <strong>Build output directory</strong> to:</p><pre>/build/web</pre><p>4. Click <strong>“Next”</strong>, review the settings, and start the deployment.</p><h3>Step 3: Fixing Build Failure</h3><p>The initial build may fail due to the missing Flutter toolchain. To resolve this:</p><ol><li>Navigate to <strong>Hosting &gt; Build settings</strong> in the AWS Amplify Console.</li><li>Locate and edit the amplify.yml file with the following configuration:</li></ol><pre>version: 1.0<br>frontend:<br>  phases:<br>    preBuild:<br>      commands:<br>        - echo &quot;Installing Flutter SDK&quot;<br>        - git clone https://github.com/flutter/flutter.git -b stable --depth 1<br>        - export PATH=&quot;$PATH:$(pwd)/flutter/bin&quot;<br>        - flutter config --no-analytics<br>        - flutter doctor<br>        - echo &quot;Installing dependencies&quot;<br>        - flutter pub get<br>    build:<br>      commands:<br>        - echo &quot;Building Flutter web application with WASM support&quot;<br>        - flutter build web --wasm<br>  artifacts:<br>    baseDirectory: build/web<br>    files:<br>      - &#39;**/*&#39;<br>  cache:<br>    paths:<br>      - flutter/.pub-cache</pre><p>3. Save the changes and redeploy the application.</p><h3>Step 4: Accessing the Deployed Application</h3><p>Once deployed, AWS Amplify assigns a domain to your application. Click on the assigned domain to view your Flutter web app in action.</p><h3>CI/CD for Automatic Deployment</h3><p>To test CI/CD, make updates to your Flutter project, such as changing the app title and color scheme. Commit and push these changes to GitHub. AWS Amplify will automatically trigger a new deployment, and the updated UI will reflect on the hosted application.</p><h3>Conclusion</h3><p>In this tutorial, you learned how to host a Flutter web application using AWS Amplify Hosting with CI/CD integration. AWS Amplify Gen 2 simplifies the deployment process and provides a seamless workflow for web applications. To explore more features, check out the official <a href="https://docs.amplify.aws/"><strong>AWS Amplify Gen 2 documentation</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e33e99165a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Upload Images to Azure Blob Storage in Flutter and Fetch Public URL]]></title>
            <link>https://medium.com/@singhrishabh1670/how-to-upload-images-to-azure-blob-storage-in-flutter-and-fetch-public-url-d07bb555d248?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d07bb555d248</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Tue, 28 Jan 2025 12:54:06 GMT</pubDate>
            <atom:updated>2025-01-28T12:54:06.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*IkuyJowUlxwChDO9.png" /><figcaption>Source: Internet</figcaption></figure><p>Uploading images to Azure Blob Storage can be an essential feature in modern apps, whether for storing user photos, application assets, or other multimedia. In this article, we’ll walk through how to build a Flutter app that enables users to select an image, upload it to Azure Blob Storage, and retrieve a public URL for access.</p><h3>Prerequisites</h3><p>Before diving into the code, ensure you have:</p><ol><li><strong>Azure Blob Storage account:</strong> Set up an Azure Storage Account and create a Blob container. Follow <a href="https://learn.microsoft.com/en-us/azure/storage/blobs/storage-quickstart-blobs-portal">Microsoft’s guide</a> if you’re new to Azure.</li><li><strong>SAS Token:</strong> Generate a Shared Access Signature (SAS) token for secure access to the blob container.</li><li><strong>Flutter development environment:</strong> Install Flutter on your machine and create a new project using flutter create.</li></ol><h3>Setting Up the Flutter Project</h3><h4>Step 1: Add Dependencies</h4><p>Update your pubspec.yaml file with the required packages:</p><pre>dependencies:<br>  flutter:<br>    sdk: flutter<br>  azure_blob_flutter: ^1.0.0<br>  image_picker: ^0.8.7+3<br>  path: ^1.8.3<br>  http: ^0.15.0</pre><p>Run flutter pub get to install these packages.</p><h3>Code Walkthrough</h3><h4>Step 2: Initialize the App</h4><p>Start by creating the basic Flutter app structure with a main() function and a StatefulWidget for managing the upload process. The app contains:</p><ul><li>An image picker for selecting images from the device.</li><li>Functions for uploading the selected image to Azure Blob Storage.</li><li>A display for the upload status and the retrieved public URL.</li></ul><p>Here’s the complete code:</p><pre>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:flutter/services.dart&#39;;<br>import &#39;dart:async&#39;;<br>import &#39;dart:io&#39;;<br>import &#39;package:azure_blob_flutter/azure_blob_flutter.dart&#39;;<br>import &#39;package:image_picker/image_picker.dart&#39;;<br>import &#39;package:path/path.dart&#39; as path;<br>import &#39;package:http/http.dart&#39; as http;<br><br>void main() {<br>  runApp(const MyApp());<br>}<br>// App entry point<br>class MyApp extends StatefulWidget {<br>  const MyApp({super.key});<br>  @override<br>  State&lt;MyApp&gt; createState() =&gt; _MyAppState();<br>}<br>class _MyAppState extends State&lt;MyApp&gt; {<br>  String uploadStatus = &#39;No image selected&#39;;<br>  final ImagePicker _picker = ImagePicker();<br>  XFile? _imageFile;<br>  String? uploadedImageUrl;<br>  <br>  // Azure Configuration<br>  static const String storageAccount = &quot;YOUR_STORAGE_ACCOUNT_NAME&quot;;<br>  static const String containerName = &quot;YOUR_CONTAINER_NAME&quot;;<br>  static const String sasToken = &quot;YOUR_SAS_TOKEN&quot;;<br>  <br>  late final String blobUrl;<br>  late final AzureBlobFlutter azureBlobFlutter;<br>  @override<br>  void initState() {<br>    super.initState();<br>    blobUrl = &quot;https://$storageAccount.blob.core.windows.net&quot;;<br>  }<br>  Future&lt;void&gt; uploadToBlob(String filePath, String fileName) async {<br>    try {<br>      final bytes = await File(filePath).readAsBytes();<br>      final blobName = Uri.encodeComponent(fileName);<br>      final uploadUrl = &#39;$blobUrl/$containerName/$blobName$sasToken&#39;;<br>      final publicUrl = &#39;$blobUrl/$containerName/$blobName$sasToken&#39;;<br>      final request = http.Request(&#39;PUT&#39;, Uri.parse(uploadUrl));<br>      request.bodyBytes = bytes;<br>      request.headers.addAll({<br>        &#39;x-ms-blob-type&#39;: &#39;BlockBlob&#39;,<br>        &#39;Content-Type&#39;: &#39;image/jpeg&#39;,<br>      });<br>      final response = await request.send();<br>      if (response.statusCode == 201) {<br>        setState(() {<br>          uploadStatus = &#39;Upload successful!\nFile: $fileName&#39;;<br>          uploadedImageUrl = publicUrl;<br>        });<br>      } else {<br>        final responseBody = await response.stream.bytesToString();<br>        setState(() {<br>          uploadStatus = &#39;Upload failed: ${response.statusCode}\n$responseBody&#39;;<br>          uploadedImageUrl = null;<br>        });<br>      }<br>    } catch (e) {<br>      setState(() {<br>        uploadStatus = &#39;Upload error: $e&#39;;<br>        uploadedImageUrl = null;<br>      });<br>    }<br>  }<br>  Future&lt;void&gt; pickAndUploadImage() async {<br>    try {<br>      setState(() {<br>        uploadStatus = &#39;Selecting image...&#39;;<br>        uploadedImageUrl = null;<br>      });<br>      final XFile? image = await _picker.pickImage(<br>        source: ImageSource.gallery,<br>        maxWidth: 1024,<br>        maxHeight: 1024,<br>        imageQuality: 85<br>      );<br>      if (image == null) {<br>        setState(() {<br>          uploadStatus = &#39;No image selected&#39;;<br>        });<br>        return;<br>      }<br>      final fileName = &#39;image_${DateTime.now().millisecondsSinceEpoch}.jpg&#39;;<br>      await uploadToBlob(image.path, fileName);<br>    } catch (e) {<br>      setState(() {<br>        uploadStatus = &#39;Error: $e&#39;;<br>        uploadedImageUrl = null;<br>      });<br>    }<br>  }<br>  @override<br>  Widget build(BuildContext context) {<br>    return MaterialApp(<br>      home: Scaffold(<br>        appBar: AppBar(<br>          title: const Text(&#39;Azure Blob Upload&#39;),<br>        ),<br>        body: Center(<br>          child: Padding(<br>            padding: const EdgeInsets.all(20.0),<br>            child: Column(<br>              mainAxisAlignment: MainAxisAlignment.center,<br>              children: [<br>                if (_imageFile != null) <br>                  Image.file(File(_imageFile!.path), height: 200, width: 200),<br>                ElevatedButton(<br>                  onPressed: pickAndUploadImage,<br>                  child: const Text(&#39;Select and Upload Image&#39;),<br>                ),<br>                const SizedBox(height: 20),<br>                Text(uploadStatus, textAlign: TextAlign.center),<br>                if (uploadedImageUrl != null) ...[<br>                  const SizedBox(height: 20),<br>                  ElevatedButton(<br>                    onPressed: () {<br>                      Clipboard.setData(ClipboardData(text: uploadedImageUrl!));<br>                    },<br>                    child: const Text(&#39;Copy URL&#39;),<br>                  ),<br>                  Text(&#39;URL: $uploadedImageUrl&#39;, maxLines: 2),<br>                ],<br>              ],<br>            ),<br>          ),<br>        ),<br>      ),<br>    );<br>  }<br>}</pre><h3>Key Features Explained</h3><ol><li><strong>Image Selection</strong>: Using the image_picker package, the app allows users to select images from their gallery.</li><li><strong>Azure Blob Upload</strong>: The http package sends a PUT request to Azure Blob Storage with the image bytes and appropriate headers.</li><li><strong>Public URL Generation</strong>: The public URL is generated using the blob container and the file name.</li><li><strong>Error Handling</strong>: Informative messages help users understand the upload status or errors.</li></ol><h3>Running the App</h3><ol><li>Replace YOUR_STORAGE_ACCOUNT_NAME, YOUR_CONTAINER_NAME, and YOUR_SAS_TOKEN with your Azure credentials.</li><li>Run the app on a connected device or emulator using:</li></ol><ul><li>flutter run</li></ul><h3>Final Thoughts</h3><p>This app demonstrates the basics of integrating Azure Blob Storage with Flutter for uploading images. Extending this, you can handle advanced use cases such as user authentication, uploading multiple files, or managing larger media assets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d07bb555d248" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding App Version vs. Build Number in Flutter: When and How to Update Them]]></title>
            <link>https://medium.com/@singhrishabh1670/understanding-app-version-vs-build-number-in-flutter-when-and-how-to-update-them-ea86215824f9?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea86215824f9</guid>
            <category><![CDATA[app-version]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Mon, 20 Jan 2025 05:49:49 GMT</pubDate>
            <atom:updated>2025-01-20T05:49:49.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*biozJ3bSJP9QgIWcmShr0g.png" /></figure><p>When building and releasing apps in Flutter, understanding the difference between the <strong>app version</strong> and the <strong>build number</strong> is crucial. These two concepts play distinct roles in the development and release cycle, and knowing when and how to update them ensures a smooth development process and clear communication with users and app stores.</p><p>This guide will break down their differences, when to change them, and include a practical example at the end.</p><h3>What is an App Version?</h3><p>The <strong>app version</strong> is the public-facing identifier of your app. It indicates the current state of the app in terms of features and functionality and is visible to end users.</p><h3>App Version (e.g., 1.0.4)</h3><p><strong>Purpose</strong>:</p><ul><li>Represents the public-facing version of your app, indicating the feature set or changes in functionality.</li><li>Typically follows the <strong>semantic versioning</strong> format: MAJOR.MINOR.PATCH.</li><li><strong>MAJOR</strong>: Increment when introducing significant changes, like breaking backward compatibility.</li><li><strong>MINOR</strong>: Increment for adding features in a backward-compatible manner.</li><li><strong>PATCH</strong>: Increment for bug fixes or small changes that don’t add new features.</li></ul><p><strong>When to change</strong>:</p><ul><li><strong>MAJOR</strong>: If the app undergoes a major redesign or incompatible changes.</li><li><strong>MINOR</strong>: When new features or functionalities are introduced.</li><li><strong>PATCH</strong>: For bug fixes or small tweaks that don’t affect functionality.</li></ul><h3>Build Number (e.g., 4)</h3><p><strong>Purpose</strong>:</p><ul><li>Represents an internal identifier for the app build.</li><li>Used by app stores (like Google Play and Apple App Store) to differentiate between uploads of the same app version.</li><li>Doesn’t need to follow semantic versioning; typically just an incrementing integer.</li></ul><p><strong>When to change</strong>:</p><ul><li>Always increment the build number for each release, even if the app version remains the same.</li><li>For example, if you fix an issue in version 1.0.4 and resubmit to the store, increase the build number (e.g., 1.0.4+5).</li></ul><h3>In Flutter (pubspec.yaml):</h3><p>You define the app version and build number like this</p><pre>version: 1.0.4+4</pre><ul><li>1.0.4 → <strong>App version</strong></li><li>4 → <strong>Build number</strong></li></ul><p>When publishing to app stores:</p><ul><li><strong>Android</strong>: Build number maps to versionCode in build.gradle.</li><li><strong>iOS</strong>: Build number maps to CFBundleVersion.</li></ul><h3>Guidelines:</h3><ol><li><strong>For App Updates with Feature Changes</strong>:</li></ol><ul><li>Change <strong>both the app version</strong> (to reflect the feature update) and <strong>build number</strong>.</li></ul><p><strong>2. For Re-Uploads (Bug Fixes/Hotfixes)</strong>:</p><ul><li>Change only the <strong>build number</strong>, keeping the app version the same.</li></ul><p><strong>3. Major App Overhaul</strong>:</p><ul><li>Increment the <strong>MAJOR</strong> version and reset the <strong>build number</strong>.</li></ul><p>By maintaining this distinction, you ensure clarity for both your users (through app version) and app stores (through build number).</p><h3>Example: Practical Workflow</h3><p>Let’s say you’re developing an app called <strong>“TaskMate”</strong>.</p><ol><li><strong>Initial Release:</strong></li></ol><ul><li>App Version: 1.0.0</li><li>Build Number: 1</li><li>Reason: This is the first stable release of your app.</li></ul><p><strong>2. Adding a New Feature (e.g., Dark Mode):</strong></p><ul><li>App Version: 1.1.0</li><li>Build Number: 2</li><li>Reason: A new, backward-compatible feature was added.</li></ul><p><strong>3. Fixing a Bug in Dark Mode:</strong></p><ul><li>App Version: 1.1.1</li><li>Build Number: 3</li><li>Reason: A bug was fixed without adding new functionality.</li></ul><p><strong>4. Major Redesign:</strong></p><ul><li>App Version: 2.0.0</li><li>Build Number: 1</li><li>Reason: The app underwent a major redesign with breaking changes.</li></ul><p><strong>5. Re-submitting After Store Rejection:</strong></p><ul><li>App Version: 2.0.0</li><li>Build Number: 2</li><li>Reason: The app store rejected the submission, so you fixed the issue and resubmitted.</li></ul><p>By following this systematic approach, you ensure your app’s development lifecycle is organized, user-friendly, and compliant with app store requirements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea86215824f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Dynamic and Scalable User Interfaces with Server-Driven UI in Flutter Using Mirai]]></title>
            <link>https://medium.com/@singhrishabh1670/building-dynamic-and-scalable-user-interfaces-with-server-driven-ui-in-flutter-using-mirai-7c233c1de2f2?source=rss-7fb186001b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c233c1de2f2</guid>
            <category><![CDATA[server-driven-ui]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Rishabh Singh]]></dc:creator>
            <pubDate>Wed, 15 Jan 2025 18:41:21 GMT</pubDate>
            <atom:updated>2025-01-20T05:55:10.268Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HgjIUZrZnVij6PzlYoDrKw.png" /></figure><p>Creating user interfaces (UIs) that are dynamic, scalable, and adaptable to evolving requirements is essential in app development. As the need for cross-platform development continues to grow, developers are seeking innovative methods to design flexible UIs that can be updated seamlessly without requiring app store approvals or direct updates to the client-side application. One increasingly popular solution in the Flutter community is the Server-Driven UI (SDUI) approach.</p><p>Flutter, Google’s powerful UI toolkit, enables developers to create natively compiled apps for mobile, web, and desktop platforms from a single codebase. With SDUI in Flutter, UI components are rendered on the server and then sent to the client for display. This approach provides a robust solution for building dynamic, adaptable, and scalable UIs, making it an excellent choice for modern app development. Let’s delve into how SDUI enhances flexibility and scalability in Flutter applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NRueQeY_crepgwAcO3q2_w.jpeg" /><figcaption>Source: Internet</figcaption></figure><h3>How Does Server-Driven UI (SDUI) Work in Flutter?</h3><p>SDUI in Flutter operates through the following key steps:</p><ol><li><strong>Defining UI Components:</strong><br> UI components, such as Flutter widgets, are defined server-side using a markup language or a UI framework. These components are designed to be modular and reusable, adhering to Flutter’s widget hierarchy.</li><li><strong>Composing the UI:</strong><br> When a client requests a specific UI screen, the server dynamically assembles the screen using the predefined UI components. This composition is based on the incoming request data and business logic. The server generates the necessary Flutter widgets and their attributes to create the complete UI layout.</li><li><strong>Delivering the UI:</strong><br> The server sends the composed UI to the client in a serialized format, such as JSON. The Flutter app on the client side then interprets this data and renders the UI by reconstructing the specified widgets and their properties, without needing to define the components or layout logic locally.</li><li><strong>Updating the UI:</strong><br> When app requirements evolve, the server can update the UI components and their attributes dynamically. These updates are instantly reflected in the UI screens delivered to the client, enabling real-time changes without modifying the client-side app. This makes SDUI in Flutter an agile solution for adapting to shifting business needs.</li></ol><h3>Advantages of Server-Driven UI (SDUI) in Flutter</h3><ol><li><strong>Flexibility:</strong><br>SDUI enables dynamic updates to the UI without requiring changes to the client-side Flutter application. This adaptability allows for rapid iterations and updates to the UI without needing app store approvals or manual client-side updates. By reducing development time and effort, SDUI supports faster responses to evolving business requirements.</li><li><strong>Scalability:</strong><br>In SDUI, the server handles the composition and rendering of UI components, significantly reducing the processing burden on the client-side Flutter app. This enhances performance and scalability, especially in applications with large user bases or complex interfaces, as the server manages the intensive tasks, allowing the client app to focus on other functionalities.</li><li><strong>Reusability:</strong><br>UI components in SDUI are designed to be modular and reusable, following Flutter’s widget hierarchy. This approach ensures consistent UI across different screens and platforms while making it easier for developers to assemble new screens using pre-existing components. The result is faster UI development and maintenance, reduced redundancy, and a consistent look and feel throughout the app.</li><li><strong>Centralized Business Logic:</strong><br>SDUI centralizes business logic on the server, allowing updates to be made without altering the client-side app. This streamlined approach ensures that business logic changes are implemented more efficiently and uniformly.</li></ol><h3>About Mirai</h3><p><strong>Mirai</strong> is a robust and versatile SDUI library for Flutter, offering a declarative framework for defining UI components on the server and rendering them on the client. With its easy configuration and update capabilities, Mirai is an excellent tool for creating dynamic and scalable UI screens in Flutter applications.</p><h3>Getting Started with Mirai</h3><p>To get started with <a href="https://pub.dev/packages/mirai"><strong>Mirai</strong></a>, you first need to install the library in your Flutter project. You can do this by adding the following dependency to your pubspec.yaml file:</p><pre>dependencies:<br>  mirai: ^0.1.0</pre><p>Once installed, you need to import Mirai in your Flutter file:</p><pre>import &#39;package:mirai/mirai.dart&#39;;</pre><p>To initialize Mirai in your Flutter application, you need to replace the MaterialApp with MiraiApp as the root widget, and within the main function initialize Mirai.</p><p>Here’s an example of how you can do that:</p><pre>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:mirai/mirai.dart&#39;;<br>import &#39;home.dart&#39;;<br><br>void main() async {<br>  await Mirai.initialize();<br>  runApp(const MyApp());<br>}<br><br>class MyApp extends StatelessWidget {<br>  const MyApp({super.key});<br><br>  @override<br>  Widget build(BuildContext context) {<br>    return const MiraiApp(<br>      title: &#39;Mirai Demo&#39;,<br>      theme: MiraiTheme(primaryColor: &quot;#00a2f9&quot;),<br>      home: HomeScreen(),<br>    );<br>  }<br>}</pre><h3>JSON File (screen.json)</h3><pre>{<br>  &quot;type&quot;: &quot;scaffold&quot;,<br>  &quot;body&quot;: {<br>    &quot;type&quot;: &quot;column&quot;,<br>    &quot;mainAxisAlignment&quot;: &quot;spaceAround&quot;,<br>    &quot;crossAxisAlignment&quot;: &quot;center&quot;,<br>    &quot;children&quot;: [<br>      {<br>        &quot;type&quot;: &quot;container&quot;,<br>        &quot;alignment&quot;: &quot;center&quot;,<br>        &quot;child&quot; : {<br>          &quot;type&quot;: &quot;image&quot;,<br>          &quot;src&quot;: &quot;assets/mirai_banner.png&quot;,<br>          &quot;imageType&quot;: &quot;asset&quot;,<br>          &quot;height&quot;: 150<br>        }<br>      },<br><br>      {<br>        &quot;type&quot;: &quot;column&quot;,<br>        &quot;crossAxisAlignment&quot;: &quot;center&quot;,<br>        &quot;children&quot;:[<br>          {<br>            &quot;type&quot;: &quot;container&quot;,<br>            &quot;alignment&quot;: &quot;center&quot;,<br>            &quot;child&quot; : {<br>              &quot;type&quot;: &quot;text&quot;,<br>              &quot;data&quot;: &quot;Mohamed Abdo&quot;,<br>              &quot;style&quot;: {<br>                &quot;fontSize&quot;: 25<br>              }<br>            }<br>          },<br>          {<br>            &quot;type&quot;: &quot;container&quot;,<br>            &quot;alignment&quot;: &quot;center&quot;,<br>            &quot;child&quot; : {<br>              &quot;type&quot;: &quot;text&quot;,<br>              &quot;data&quot;: &quot;Flutter Developer&quot;,<br>              &quot;style&quot;: {<br>                &quot;color&quot;: &quot;#00a2f9&quot;,<br>                &quot;fontSize&quot;: 20<br>              }<br>            }<br>          }<br>        ]<br>      }<br>    ]<br>  }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rCqN25BaByNdHlytmAYkTw.png" /></figure><p><strong>Mirai offers three methods to parse JSON</strong> into Flutter widgets, providing flexibility in how you fetch and load JSON configurations for your server-driven UI screens. Here’s a brief overview of these methods:</p><ul><li><strong>Mirai.fromJson()</strong>: This method allows you to parse a JSON configuration directly from a string in your Flutter app. You can pass the JSON configuration as a string to this method, along with the BuildContext context and Mirai will parse the JSON and generate the Flutter widgets. For example:</li></ul><pre>String jsonConfig = &#39;{ &quot;type&quot;: &quot;scaffold&quot;, ... }&#39;;<br>Mirai.fromJson(jsonData, context),</pre><ul><li><strong>Mirai.fromAsset()</strong>: This method allows you to load a JSON configuration from a local asset file in your Flutter app. You can specify the asset path of the JSON configuration as a string to this method, and Mirai will load and parse the JSON, and generate the corresponding Flutter widgets. For example:</li></ul><pre>getWidget() async {<br>    await Mirai.fromAssets(&quot;assets/screen.json&quot;, context).then((value) {<br>      setState(() {<br>        body = value;<br>      });<br>    });<br>  }<br><br>  @override<br>  Widget build(BuildContext context) {<br>    return Container(<br>      child: body ?? const CircularProgressIndicator(),<br>    );<br>  }</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ku12tSfIkBfjKmiRiEHm3g.png" /></figure><h3>Note</h3><p>we can load the file of the JSON configuration as a string and decode it to JSON and use Mirai.fromJson().</p><p>For example:</p><pre>Future&lt;void&gt; loadJsonData() async {<br>    final jsonString = await rootBundle.loadString(&#39;assets/screen.json&#39;);<br>    setState(() =&gt; jsonData = jsonDecode(jsonString));<br>  }<br><br>Mirai.fromJson(jsonData, context),</pre><ul><li><strong>Mirai.fromNetwork()</strong>: This method lets you fetch the JSON configuration from a remote network source, such as an API endpoint. You can pass the URL of the JSON configuration as a string to this method, and Mirai will fetch and parse the JSON, and generate the corresponding Flutter widgets. For example:</li></ul><pre>final sourceFile =<br>      &quot;https://raw.githubusercontent.com/MohamedAbd0/MiraiServerUIData/main/screen.json&quot;;<br><br>Mirai.fromNetwork(<br>    MiraiRequest(<br>       url: sourceFile,<br>       method: Method.get,<br>    ),<br>),</pre><p>These methods provide different ways to fetch and load JSON configurations into your Flutter app, depending on your use case and requirements. You can choose the one that best fits your app architecture and workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_takhqrk2uT2uUoKQ9xbTA.png" /></figure><h3>Implementation of JSON file</h3><p>we will write each widget in {}and set the type value in the key of &quot;type&quot;.</p><p><em>scaffold</em></p><pre>{<br>    &quot;type&quot;: &quot;scaffold&quot;,<br>    &quot;backgroundColor&quot;: &quot;#ffffff&quot;,<br>    &quot;appBar&quot;: {},<br>    &quot;body&quot;: {}<br>    &quot;bottomNavigationBar&quot;:{}<br>}</pre><p><em>appBar</em></p><pre>&quot;appBar&quot;: {<br>      &quot;type&quot;: &quot;appBar&quot;,<br>      &quot;color&quot;: &quot;#ffffff&quot;,<br>      &quot;title&quot;: {<br>        &quot;type&quot;: &quot;text&quot;,<br>        &quot;data&quot;: &quot;Mirai Demo&quot;<br>      },<br>      &quot;leading&quot;: {},<br>      &quot;actions&quot;: []<br>    },</pre><p><em>text</em></p><pre>{<br>    &quot;type&quot;: &quot;text&quot;,<br>    &quot;data&quot;: &quot;Mirai Demo&quot;,<br>    &quot;style&quot;: {<br>        &quot;color&quot;: &quot;#00a2f9&quot;,<br>        &quot;fontSize&quot;: 20,<br>        &quot;fontWeight&quot;: &quot;w600&quot;<br>    }<br>}</pre><p><em>outlinedButton</em></p><pre>{<br>    &quot;type&quot;: &quot;outlinedButton&quot;,<br>    &quot;child&quot;: {<br>        &quot;type&quot;: &quot;text&quot;,<br>        &quot;data&quot;: &quot;BUTTON&quot;<br>    },<br>    &quot;style&quot;: {<br>        &quot;padding&quot;: {<br>            &quot;top&quot;: 8,<br>            &quot;left&quot;: 12,<br>            &quot;right&quot;: 12,<br>            &quot;bottom&quot;: 8<br>        }<br>    },<br>    &quot;onPressed&quot;: {}<br>}</pre><p><em>elevatedButton</em></p><pre>{<br>    &quot;type&quot;: &quot;elevatedButton&quot;,<br>    &quot;child&quot;: {<br>        &quot;type&quot;: &quot;text&quot;,<br>        &quot;data&quot;: &quot;Submit&quot;<br>    },<br>    &quot;style&quot;: {<br>        &quot;backgroundColor&quot;: &quot;#4D00E9&quot;,<br>        &quot;padding&quot;: {<br>            &quot;top&quot;: 8,<br>            &quot;left&quot;: 12,<br>            &quot;right&quot;: 12,<br>            &quot;bottom&quot;: 8<br>        }<br>    },<br>    &quot;onPressed&quot;: {}<br>}</pre><p><em>textButton</em></p><pre>{<br>    &quot;type&quot;: &quot;textButton&quot;,<br>    &quot;child&quot;: {<br>        &quot;type&quot;: &quot;text&quot;,<br>        &quot;data&quot;: &quot;BUTTON&quot;<br>    },<br>    &quot;style&quot;: {<br>        &quot;padding&quot;: {<br>            &quot;top&quot;: 8,<br>            &quot;left&quot;: 12,<br>            &quot;right&quot;: 12,<br>            &quot;bottom&quot;: 8<br>        }<br>    },<br>    &quot;onPressed&quot;: {}<br>}</pre><p><em>iconButton</em></p><pre>  {<br>    &quot;type&quot;: &quot;iconButton&quot;,<br>    &quot;child&quot;: {<br>      &quot;type&quot;: &quot;icon&quot;,<br>      &quot;iconType&quot;: &quot;material&quot;,<br>      &quot;icon&quot;: &quot;search&quot;<br>    }<br>  }</pre><p><em>container</em></p><pre>{<br>    &quot;type&quot;: &quot;container&quot;,<br>    &quot;width&quot;: 50,<br>    &quot;margin&quot;: {<br>      &quot;top&quot;: 10,<br>      &quot;bottom&quot;: 10,<br>      &quot;right&quot;: 8,<br>      &quot;left&quot;: 8<br>    },<br>    &quot;decoration&quot;: {<br>      &quot;color&quot;:  &quot;#011621&quot;<br>    },<br>    &quot;child&quot;:{}<br><br>}</pre><p><em>column</em></p><pre>{<br>    &quot;type&quot;: &quot;column&quot;,<br>    &quot;mainAxisAlignment&quot;: &quot;start&quot;,<br>    &quot;crossAxisAlignment&quot;: &quot;start&quot;,<br>    &quot;children&quot;: []<br>}</pre><p><em>padding</em></p><pre>{<br>    &quot;type&quot;: &quot;padding&quot;,<br>    &quot;padding&quot;: {<br>      &quot;left&quot;: 10, &quot;right&quot;: 10<br>    },<br>    &quot;child&quot;:{}<br>}</pre><p><em>image</em></p><pre>// for asset image<br>{<br>    &quot;type&quot;: &quot;image&quot;,<br>    &quot;src&quot;: &quot;assets/mirai_banner.png&quot;,<br>    &quot;imageType&quot;: &quot;asset&quot;,<br>    &quot;height&quot;: 150<br>}<br><br>// for network image<br>{<br>    &quot;type&quot;: &quot;image&quot;,<br>    &quot;src&quot;: &quot;https://image.com/image.jpeg&quot;,<br>    &quot;height&quot;: 150<br>}</pre><p><em>floatingActionButton</em></p><pre>{<br>    &quot;type&quot;: &quot;floatingActionButton&quot;,<br>    &quot;backgroundColor&quot;: &quot;#011621&quot;,<br>    &quot;foregroundColor&quot;: &quot;#ffffff&quot;,<br>    &quot;buttonType&quot;: &quot;extended&quot;,<br>    &quot;icon&quot;: {},<br>    &quot;child&quot;: {},<br>    &quot;onPressed&quot;: {}<br>}</pre><p><em>sizedBox</em></p><pre>{<br>    &quot;type&quot;: &quot;sizedBox&quot;,<br>    &quot;height&quot;: 2<br>}</pre><p><em>row</em></p><pre>{<br>    &quot;type&quot;: &quot;row&quot;,<br>    &quot;children&quot;: []<br>}</pre><p><em>listTile</em></p><pre>{<br>    &quot;type&quot;: &quot;listTile&quot;,<br>    &quot;height&quot;: 250,<br>    &quot;leading&quot;: {},<br>    &quot;title&quot;: {},<br>    &quot;subtitle&quot;: {},<br>    &quot;trailing&quot;: {}<br>}</pre><p><em>listView</em></p><pre>{<br>    &quot;type&quot;: &quot;listView&quot;,<br>    &quot;shrinkWrap&quot;: true,<br>    &quot;separator&quot;: {<br>      &quot;type&quot;: &quot;container&quot;,<br>      &quot;height&quot;: 10<br>    },<br>    &quot;children&quot;: []<br>}</pre><p><em>textField</em></p><pre>{<br>    &quot;type&quot;: &quot;textField&quot;,<br>    &quot;maxLines&quot;: 1,<br>    &quot;keyboardType&quot;: &quot;text&quot;,<br>    &quot;textInputAction&quot;: &quot;done&quot;,<br>    &quot;textAlign&quot;: &quot;start&quot;,<br>    &quot;textCapitalization&quot;: &quot;none&quot;,<br>    &quot;textDirection&quot;: &quot;ltr&quot;,<br>    &quot;textAlignVertical&quot;: &quot;top&quot;,<br>    &quot;obscureText&quot;: false,<br>    &quot;cursorColor&quot;: &quot;#FC3F1B&quot;,<br>    &quot;style&quot;: {<br>        &quot;color&quot;: &quot;#000000&quot;<br>    },<br>    &quot;decoration&quot;: {<br>        &quot;hintText&quot;: &quot;Where can we reach you?&quot;,<br>        &quot;filled&quot;: true,<br>        &quot;icon&quot;: {<br>            &quot;type&quot;: &quot;icon&quot;,<br>            &quot;iconType&quot;: &quot;cupertino&quot;,<br>            &quot;icon&quot;: &quot;phone_solid&quot;,<br>            &quot;size&quot;: 24<br>        },<br>        &quot;hintStyle&quot;: {<br>            &quot;color&quot;: &quot;#797979&quot;<br>        },<br>        &quot;labelText&quot;: &quot;Phone number*&quot;,<br>        &quot;fillColor&quot;: &quot;#F2F2F2&quot;<br>    },<br>    &quot;readOnly&quot;: false,<br>    &quot;enabled&quot;: true<br>}</pre><p><em>scrollView</em></p><pre>{<br>    &quot;type&quot;: &quot;scrollView&quot;,<br>    &quot;child&quot;: {}<br>}</pre><p><em>bottomNavigationBar</em></p><pre>{<br>    &quot;type&quot;: &quot;bottomNavigationBar&quot;,<br>    &quot;unselectedItemColor&quot;: &quot;#B489F3&quot;,<br>    &quot;items&quot;: [ ]<br>}</pre><p><em>card</em></p><pre>{<br>    &quot;type&quot;: &quot;card&quot;,<br>    &quot;elevation&quot;: 20,<br>    &quot;borderOnForeground&quot;: true,<br>    &quot;margin&quot;: {<br>        &quot;top&quot;: 20,<br>        &quot;bottom&quot;: 20,<br>        &quot;right&quot;: 20,<br>        &quot;left&quot;: 20<br>    },<br>    &quot;child&quot;: {}<br>}</pre><p><em>tabBar</em></p><pre>{<br>    &quot;type&quot;: &quot;defaultTabController&quot;,<br>    &quot;length&quot;: 3,<br>    &quot;child&quot;: {<br>      &quot;type&quot;: &quot;scaffold&quot;,<br>      &quot;appBar&quot;: {<br>        &quot;type&quot;: &quot;appBar&quot;,<br>        &quot;title&quot;: {<br>          &quot;type&quot;: &quot;text&quot;,<br>          &quot;data&quot;: &quot;Tabbar&quot;<br>        },<br>        &quot;bottom&quot;: {<br>          &quot;type&quot;: &quot;tabBar&quot;,<br>          &quot;tabs&quot;: [<br>            {<br>              &quot;type&quot;: &quot;tab&quot;,<br>              &quot;text&quot;: &quot;Red&quot;<br>            },<br>            {<br>              &quot;type&quot;: &quot;tab&quot;,<br>              &quot;text&quot;: &quot;Red&quot;<br>            },<br>            {<br>              &quot;type&quot;: &quot;tab&quot;,<br>              &quot;text&quot;: &quot;Red&quot;<br>            }<br>          ]<br>        }<br>      },<br>      &quot;body&quot;: {<br>        &quot;type&quot;: &quot;tabBarView&quot;,<br>        &quot;children&quot;: []<br>      }<br>    }<br>  }</pre><p><em>alertDialog</em></p><pre>{<br>    &quot;type&quot;: &quot;alertDialog&quot;,<br>    &quot;content&quot;: {<br>        &quot;type&quot;: &quot;padding&quot;,<br>        &quot;padding&quot;: {<br>            &quot;top&quot;: 0,<br>            &quot;left&quot;: 12,<br>            &quot;right&quot;: 12,<br>            &quot;bottom&quot;: 8<br>        },<br>        &quot;child&quot;: {<br>            &quot;type&quot;: &quot;text&quot;,<br>            &quot;data&quot;: &quot;Discard draft?&quot;,<br>            &quot;align&quot;: &quot;center&quot;,<br>            &quot;style&quot;: {<br>                &quot;fontSize&quot;: 14<br>            }<br>        }<br>    },<br>    &quot;actions&quot;: [<br>        {<br>            &quot;type&quot;: &quot;textButton&quot;,<br>            &quot;child&quot;: {<br>                &quot;type&quot;: &quot;text&quot;,<br>                &quot;data&quot;: &quot;CANCEL&quot;<br>            },<br>            &quot;onPressed&quot;: {<br>                &quot;actionType&quot;: &quot;navigate&quot;,<br>                &quot;navigationType&quot;: &quot;screen&quot;,<br>                &quot;navigationStyle&quot;: &quot;pop&quot;<br>            }<br>        },<br>        {<br>            &quot;type&quot;: &quot;sizedBox&quot;,<br>            &quot;width&quot;: 8<br>        },<br>        {<br>            &quot;type&quot;: &quot;textButton&quot;,<br>            &quot;child&quot;: {<br>                &quot;type&quot;: &quot;text&quot;,<br>                &quot;data&quot;: &quot;DISCARD&quot;<br>            },<br>            &quot;onPressed&quot;: {<br>                &quot;actionType&quot;: &quot;navigate&quot;,<br>                &quot;navigationType&quot;: &quot;screen&quot;,<br>                &quot;navigationStyle&quot;: &quot;pop&quot;<br>            }<br>        },<br>        {<br>            &quot;type&quot;: &quot;sizedBox&quot;,<br>            &quot;width&quot;: 12<br>        }<br>    ]<br>}</pre><p>we can push alertDialog by</p><pre>{<br>    &quot;type&quot;: &quot;elevatedButton&quot;,<br>    &quot;child&quot;: {<br>        &quot;type&quot;: &quot;text&quot;,<br>        &quot;data&quot;: &quot;SIMPLE ALERT&quot;,<br>        &quot;style&quot;: {<br>            &quot;color&quot;: &quot;#ffffff&quot;<br>        }<br>    },<br>    &quot;onPressed&quot;: {<br>        &quot;actionType&quot;: &quot;navigate&quot;,<br>        &quot;navigationStyle&quot;: &quot;push&quot;,<br>        &quot;navigationType&quot;: &quot;dialog&quot;,<br>        &quot;widgetJson&quot;: {<br>            &quot;type&quot;: &quot;alertDialog&quot;,<br>            &quot;content&quot;: {},<br>            &quot;actions&quot;: []<br>        }<br>    }<br>}</pre><h3>Custom Parser</h3><p>You can also specify your custom Parsers in Mirai.initialize and Dio instance.</p><pre>void main() async {<br>  final dio = Dio()<br>  await Mirai.initialize(<br>    parsers: const [<br>      ExampleScreenParser(),<br>    ],<br>    dio: dio,<br>  );<br>  runApp(const MyApp());<br>}</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c233c1de2f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>