<?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 Talelbriki on Medium]]></title>
        <description><![CDATA[Stories by Talelbriki on Medium]]></description>
        <link>https://medium.com/@talelbriki13?source=rss-4ada6984b5df------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*SQhK5JXejBiFavG4</url>
            <title>Stories by Talelbriki on Medium</title>
            <link>https://medium.com/@talelbriki13?source=rss-4ada6984b5df------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:04:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@talelbriki13/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[What Publishing Mobile Apps Taught Me Beyond Coding]]></title>
            <link>https://medium.com/@talelbriki13/what-publishing-mobile-apps-taught-me-beyond-coding-5067741f947f?source=rss-4ada6984b5df------2</link>
            <guid isPermaLink="false">https://medium.com/p/5067741f947f</guid>
            <category><![CDATA[app-store]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[google-play]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Talelbriki]]></dc:creator>
            <pubDate>Thu, 14 May 2026 11:51:37 GMT</pubDate>
            <atom:updated>2026-05-14T11:51:37.507Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nzjP2GtbrKJ-DAE97jlh_w.png" /></figure><p>Over the past months, I’ve had the opportunity to publish multiple mobile applications on both the Google Play Store and the Apple App Store as a Flutter developer.</p><p>At first, I thought the hard part was building the app.</p><p>I was wrong …</p><p>What surprised me the most was discovering that app deployment is an entire skill on its own. Writing the code is only half the journey — publishing, maintaining, optimizing, and getting approved can sometimes be harder than development itself.</p><p>Through this experience, I learned how different both ecosystems really are:</p><ul><li>Google Play tends to offer a much larger user base and faster iteration cycles.</li><li>The App Store, despite having stricter reviews, often brings stronger monetization and more paying users.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*efM9GcvkuAcpXSC9jHHR9g.png" /><figcaption>AppStore vs Google play</figcaption></figure><p>I also encountered challenges I never expected:</p><p><strong>App Store rejection loops :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w7hQuIJbAXHkz-EzXeKGXA.png" /><figcaption>App Store rejection loops</figcaption></figure><p>Apple reviews can be extremely strict, and sometimes very small details can lead to rejection.</p><p>Some lessons I learned the hard way:</p><p>• Screenshots should clearly showcase app functionality. Going overboard with fancy marketing designs can actually hurt approval chances if reviewers cannot understand the real features.</p><p>• If your app uses social login providers (Google, Facebook, etc.), Apple often requires “Sign in with Apple” as well.</p><p><strong>• Account-based apps should provide:</strong></p><p>- Privacy Policy</p><p>- Terms of Use</p><p>- Account deletion option</p><p>Missing any of these can trigger rejection.</p><p><strong>Subscription-based apps must include:</strong></p><ul><li>Restore Purchases functionality</li><li>Clear subscription explanations</li><li>Proper billing handling</li></ul><p>• One important thing I discovered:<br>In-App Purchases and subscriptions may fail if your business/account verification is incomplete. Make sure your Apple developer business account is verified and fully active BEFORE configuring subscriptions.</p><ul><li>Another major lesson:<br>Never let unhappy flows fail silently.<br>Every API failure, payment issue, or validation problem should display proper popups/messages to the user. Reviewers test edge cases aggressively.</li></ul><p><strong>Google Play challenges :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m29MnuUT7HiMtANyDv_CZw.png" /><figcaption>google play challenges</figcaption></figure><p>Google Play felt easier at first, but publishing requirements became much stricter for new developers.</p><p>The biggest surprise for me was the Personal Developer Account policy and closed testing process.</p><p>For new personal accounts:<br>• You may need a closed testing phase before production access<br>• You need real testers added to the testing program<br>• The testing period must remain active for at least 14 days<br>• Simply uploading builds is not enough — Google expects actual testing activity and feedback</p><p>Some important do’s and don’ts I learned:</p><p>✅ Add enough real testers early<br>✅ Keep builds stable during the testing period<br>✅ Fill store information professionally<br>✅ Prepare privacy policy links before submission</p><p>❌ Don’t spam releases unnecessarily<br>❌ Don’t leave incomplete store metadata<br>❌ Don’t underestimate policy declarations and permissions</p><p><strong>ASO (App Store Optimization) :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kMCpj_a4eTpXGCqFQwNliQ.png" /><figcaption>importance of ASO</figcaption></figure><p>I underestimated ASO at first.</p><p>Now I see it as a core part of publishing.</p><p>For the Apple App Store in particular, keywords are extremely important. The keyword field, subtitle, and metadata can significantly affect discoverability.</p><p>I’ve been learning how small changes in:</p><ul><li>app title</li><li>subtitle</li><li>keyword selection</li><li>screenshots</li><li>icon design</li><li>onboarding visuals</li></ul><p>can completely change how an app performs in search.</p><p>I also started exploring ASO tools and keyword research platforms to better understand:</p><ul><li>competitor keywords</li><li>search trends</li><li>ranking opportunities</li><li>conversion impact of screenshots</li></ul><p>On top of that, I’ve been experimenting with AI-assisted workflows (including Claude prompts/skills) to:</p><ul><li>generate keyword ideas</li><li>refine App Store descriptions</li><li>improve screenshot messaging</li><li>explore different positioning angles for the same app</li></ul><p>One thing became very clear:<br>your store page is not just information — it’s your first product impression.</p><p><strong>App Monetization :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0MknZArbfRi0xfk8HLsTaw.png" /><figcaption>rich flutter bird</figcaption></figure><p>Monetization is a product decision, not a technical one</p><p>I used to think monetization was just “adding subscriptions or ads”.</p><p>Now I see it differently.</p><p>Choosing how to monetize depends on:</p><ul><li>user behavior</li><li>app category</li><li>retention potential</li><li>perceived value</li><li>and timing of the paywall</li></ul><p>I’m still testing different approaches:</p><ul><li>subscriptions vs one-time purchases</li><li>freemium models</li><li>ad-supported flows</li><li>hybrid strategies</li></ul><p>And I’ve learned that timing matters a lot. A paywall shown too early can kill retention, while a weak monetization model can limit long-term growth.</p><p><strong>Marketing and discovery :</strong></p><p>Marketing and discovery are part of the product …</p><p>Another major realization: building a good app is not enough.</p><p>I’ve been learning that visibility starts before release.</p><p>Things I now pay attention to:</p><ul><li>how the app is presented on the store</li><li>how screenshots communicate value</li><li>how early users are brought in</li><li>how feedback is collected</li><li>how iteration happens after release</li></ul><p>Even small improvements in store visuals or descriptions can noticeably impact downloads.</p><blockquote>The biggest lesson so far</blockquote><blockquote>Publishing apps is not a final step after development.</blockquote><blockquote>It’s an ongoing process.</blockquote><blockquote>I’m still experimenting, still making mistakes, still fixing things after release, and still learning what works and what doesn’t.</blockquote><blockquote>Each deployment teaches me something new — sometimes technical, sometimes product-related, sometimes just about patience and iteration.</blockquote><blockquote>And that’s what makes this journey interesting.</blockquote><blockquote>It’s not something you “finish”. It’s something you keep refining 🚀</blockquote><blockquote>📚 Official Documentation (Must-have references)</blockquote><blockquote><a href="https://developer.apple.com/app-store/review/guidelines/?utm_source=chatgpt.com">Apple App Store Review Guidelines</a> — The official rules that define App Store approvals and rejection reasons.</blockquote><blockquote><a href="https://developer.apple.com/in-app-purchase/?utm_source=chatgpt.com">Apple Developer Documentation (Subscriptions &amp; IAP)</a> — Everything about in-app purchases, subscriptions, and StoreKit.</blockquote><blockquote><a href="https://support.google.com/googleplay/android-developer/?utm_source=chatgpt.com">Google Play Console Help</a> — Official documentation for publishing, testing, and policies.</blockquote><blockquote><a href="https://play.google.com/about/developer-content-policy/?utm_source=chatgpt.com">Google Play Developer Policy Center</a> — Full policy rules including closed testing and account requirements.</blockquote><blockquote>📈 ASO (App Store Optimization)</blockquote><blockquote><a href="https://www.apptweak.com/en/aso-blog?utm_source=chatgpt.com">App Store Optimization Guide (AppTweak Blog)</a> — One of the most complete ASO learning hubs (keywords, screenshots, conversion).</blockquote><blockquote><a href="https://www.mobileaction.co/blog?utm_source=chatgpt.com">Mobile Action ASO Resources</a> — Practical insights on keyword research and app growth.</blockquote><blockquote>App Radar ASO Blog — Great for keyword strategies and App Store ranking improvements.</blockquote><blockquote><a href="https://sensortower.com/blog?utm_source=chatgpt.com">Sensor Tower Insights</a> — Industry-level analytics on app store trends and monetization.</blockquote><blockquote>🎥 YouTube Videos (Highly informative)</blockquote><blockquote>App Store Optimization Explained (ASO Guide) — Clear explanation of ASO fundamentals and ranking factors.</blockquote><blockquote>How to Publish an App on Google Play (Step by Step) — Full walkthrough of Play Store publishing process.</blockquote><blockquote>How to Submit an App to Apple App Store (2025 Guide) — Practical App Store submission guide.</blockquote><blockquote>ASO &amp; App Growth Strategy by RevenueCat — Strong focus on monetization + subscription apps.</blockquote><blockquote>Indie App Developer Journey &amp; Lessons — Real-world experience of publishing and scaling apps.</blockquote><blockquote>💰 Monetization &amp; Subscriptions</blockquote><blockquote><a href="https://www.revenuecat.com/blog?utm_source=chatgpt.com">RevenueCat Blog (Subscription Monetization)</a> — One of the best resources for mobile subscription strategies.</blockquote><blockquote><a href="https://adapty.io/blog?utm_source=chatgpt.com">Adapty Blog (Paywalls &amp; Pricing Experiments)</a> — Real A/B testing insights for paywalls and pricing.</blockquote><blockquote>🚀 Bonus (Indie dev &amp; growth mindset)</blockquote><blockquote><a href="https://www.indiehackers.com/?utm_source=chatgpt.com">Indie Hackers Community</a> — Stories from developers building and monetizing apps.</blockquote><blockquote><a href="https://www.producthunt.com/posts/new?utm_source=chatgpt.com">Product Hunt Launch Guide</a> — Useful for launch visibility and early traction.</blockquote><blockquote>🚀 Growth &amp; Startup Strategy (Mindset + Real-world insights)</blockquote><blockquote>One thing that really changed my perspective is realizing that publishing apps is not just a technical process, but a <strong>startup-like loop of iteration, positioning, and distribution thinking</strong>.</blockquote><blockquote>These are some of the most insightful resources I found while learning how products actually grow beyond code:</blockquote><blockquote><strong>Startup Stories &amp; Founder Journeys</strong><br> Adam Lyttle<br> Adam Lyttle YouTube Channel — Real-world breakdowns of indie apps, growth strategies, and how founders think about building and scaling products.</blockquote><blockquote><strong>Paywalls, monetization &amp; growth experimentation</strong><br> Superwall<br> <a href="https://superwall.com/?utm_source=chatgpt.com">Superwall Blog &amp; Resources</a> — Deep insights into paywall design, subscription optimization, and A/B testing strategies used in real mobile apps.</blockquote><blockquote><strong>Startup case studies &amp; income breakdowns</strong><br> Starter Story<br> <a href="https://www.starterstory.com/?utm_source=chatgpt.com">Starter Story Case Studies</a> — Thousands of real startup stories showing how apps and SaaS products reach their first users and generate revenue.</blockquote><p><strong>#Flutter #MobileDevelopment #GooglePlay #AppStore #ASO #Monetization #SoftwareEngineering #iOS #Android #IndieHacking</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5067741f947f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️ Penetration Testing: From Fundamentals to Flutter Security]]></title>
            <link>https://medium.com/@talelbriki13/%EF%B8%8F-penetration-testing-from-fundamentals-to-flutter-security-beb001e1b781?source=rss-4ada6984b5df------2</link>
            <guid isPermaLink="false">https://medium.com/p/beb001e1b781</guid>
            <category><![CDATA[mobile-pentesting]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[reverse-engineering]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Talelbriki]]></dc:creator>
            <pubDate>Tue, 04 Nov 2025 14:42:47 GMT</pubDate>
            <atom:updated>2025-11-04T14:42:47.797Z</atom:updated>
            <content:encoded><![CDATA[<h3>1. What Is Penetration Testing?</h3><p>Penetration testing, or <strong>pentesting</strong>, is a controlled and simulated cyberattack on a system, application, or network with the goal of identifying and exploiting vulnerabilities <strong>before malicious actors do</strong>.</p><p>Unlike automated vulnerability scans, pentesting involves <strong>manual, creative, and scenario-based attacks</strong> to evaluate real-world exploitability and assess how deep a compromise can go once an entry point is found.</p><h3>💡 Why It Matters</h3><p>Even small security flaws can lead to catastrophic breaches, resulting in financial loss, reputational damage, and loss of user trust.<br> For modern digital products — especially mobile apps that handle personal, financial, or health data — security is no longer optional; it’s a baseline expectation.</p><h3>🧩 Pentesting vs. Other Security Assessments</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gvCJx9RW66zpeR6pH1yAQg.png" /><figcaption>Pentesting vs. Other Security Assessments</figcaption></figure><h3>⚙️ Types of Pentesting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0yLpyvIXFDi298MnMC9QMg.png" /><figcaption><strong>Black Box:</strong> Tester has no prior knowledge — simulates an external attacker.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*muOZg_K-UGMMgA-GjUdVnA.png" /><figcaption><strong>White Box:</strong> Full access to source code, architecture, and internal information.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J8F5vN05_Jp9zlnEmsrSow.png" /><figcaption><strong>Gray Box:</strong> Partial knowledge (credentials, endpoints, limited internal data).</figcaption></figure><h3>🔍 Phases of a Penetration Test</h3><ul><li><strong>Reconnaissance:</strong> Gather public information (domains, APIs, endpoints).</li><li><strong>Scanning:</strong> Identify reachable services, open ports, and vulnerabilities.</li><li><strong>Vulnerability Analysis:</strong> Test input handling, configurations, and exposure.</li><li><strong>Exploitation:</strong> Attempt to gain unauthorized access or escalate privileges.</li><li><strong>Post-Exploitation:</strong> Explore persistence, data exfiltration, and lateral movement.</li><li><strong>Reporting:</strong> Document findings, risk levels, and mitigation recommendations.</li></ul><h3>🧰 Tools &amp; Techniques</h3><ul><li><strong>SAST (Static Application Security Testing) :</strong></li></ul><p>SAST (Static Application Security Testing) consists of analyzing code without executing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fYep6Ptc2Xma2HApOzR3Yw.png" /><figcaption><strong>SAST (Static Application Security Testing)</strong></figcaption></figure><ul><li><strong>DAST (Dynamic Application Security Testing) :</strong></li></ul><p>DAST (Dynamic Application Security Testing) consists of probing a live, running application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MriDlamJf0HLqMSsZPjTeg.png" /><figcaption><strong>DAST (Dynamic Application Security Testing)</strong></figcaption></figure><ul><li><strong>Intercepting Proxies:</strong> Tools like Burp Suite or OWASP ZAP to inspect network traffic.</li><li><strong>Intercepting proxies</strong> (also called <em>man-in-the-middle</em> proxies in testing) are tools that sit between a client (for example, a mobile app) and a server and let you <strong>capture, inspect, modify, and replay</strong> the HTTP(S) traffic that flows between them. Popular examples are <strong>Burp Suite</strong> and <strong>OWASP ZAP</strong>. Pentesters use them to validate what data is sent, how authentication and sessions work, whether sensitive data leaks, and whether server-side controls can be bypassed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/317/1*EsYaajTtlZV0VAtXP7mTnw.png" /><figcaption>Burp Suite</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*GxABKC86K6pGy6cwBHYcGA.png" /><figcaption>OWASP ZAP</figcaption></figure><ul><li><strong>Hooking / Runtime Instrumentation:</strong> Tools like Frida for runtime behavior analysis.</li></ul><p><strong>Hooking</strong> (or <strong>runtime instrumentation</strong>) is the practice of attaching code to a running process so you can observe, intercept, modify, or replace function calls and data flows while the program executes. Instead of inspecting compiled binaries statically, you analyze the program <em>as it runs</em>, which is essential for uncovering protections that only appear at runtime (pinning, runtime checks, encrypted payloads, dynamic code loading, etc.).</p><p><strong>Frida</strong> is the most widely used toolkit for this: it injects lightweight JavaScript snippets into processes (apps) so you can hook methods, trace calls, read/write memory, and automate dynamic tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*LzgFVfLB9ytNAeG17aziOg.png" /><figcaption>Frida</figcaption></figure><ul><li><strong>Fuzzing:</strong> Supplying invalid or unexpected input to uncover crashes or vulnerabilities.</li></ul><p>Simply put, fuzzing is a “black box testing” method in which the application is tested from the outside in — as in a hacker trying to break in without having access to the source code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*R1MMSy4KbvfChzZEoWEkBA.png" /><figcaption>Fuzzing techniques</figcaption></figure><ul><li><strong>Binary Analysis:</strong> Examining compiled executables for security flaws.</li></ul><p><strong>Binary analysis</strong> is the practice of studying compiled programs (binaries) — ELF, PE, Mach-O, Android .so libraries, or packaged mobile app artifacts — to understand their behavior, find vulnerabilities, and verify security controls when source code is not available. It’s a core skill for advanced penetration testing, malware analysis, and vulnerability research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E963110O4NN7usM7sUxyow.png" /><figcaption>Example of decompiling android App</figcaption></figure><h3>2. Penetration Testing in Flutter Applications</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vnT2MdJu_PuIxQhHDazAFA.png" /></figure><p>Flutter introduces new challenges and attack surfaces for security professionals.<br> Although Dart code compiles to native binaries, <strong>reverse engineering and runtime analysis</strong> are still possible, making proper hardening essential.</p><h3>📱 Why Mobile Pentesting Is Unique</h3><p>Mobile apps differ from web or desktop apps because they:</p><ul><li>Run on user-controlled devices (rooting, jailbreaking, sandboxing issues).</li><li>Store sensitive data locally (SQLite, SharedPreferences, files).</li><li>Communicate with remote APIs over potentially insecure networks.</li><li>Rely on third-party plugins that may contain native code vulnerabilities.</li></ul><h3>⚔️ Common Attack Surfaces</h3><ul><li>Local data storage (unencrypted files or preferences)</li><li>Hardcoded secrets or API keys</li><li>Weak TLS configurations or lack of SSL pinning</li><li>Insecure authentication or session handling</li><li>Unsafe inter-app communication</li><li>Vulnerable third-party libraries or plugins</li></ul><h3>🧱 Standards and Methodologies</h3><p>When assessing Flutter apps, professional pentesters rely on frameworks such as:</p><ul><li><strong>OWASP MASVS:</strong> Defines security requirements for mobile apps.</li><li><strong>OWASP MASTG:</strong> Provides detailed testing methodologies and checklists.</li><li><strong>OWASP Mobile Top 10:</strong> Summarizes the most common mobile security risks.</li></ul><h3>⚙️ Pentesting Approach for Flutter Apps</h3><ol><li><strong>Define Scope:</strong> Include client-side logic, API calls, data storage, and plugins.</li><li><strong>Combine Static &amp; Dynamic Testing:</strong> Analyze both Dart code and runtime behavior.</li><li><strong>Focus on Cross-Platform Issues:</strong> Handle Android/iOS sandbox differences.</li><li><strong>Inspect API Endpoints:</strong> The backend is often the weakest link.</li></ol><h3>🚨 Common Vulnerabilities in Flutter Apps</h3><ul><li>Storing secrets in plaintext (e.g., SharedPreferences)</li><li>Hardcoded API keys in source code</li><li>Missing SSL pinning or certificate validation</li><li>Weak or missing authentication logic</li><li>Exposed sensitive logic in un-obfuscated Dart code</li><li>Insecure dependencies or outdated packages</li></ul><h3>🛡️Building Secure Flutter Apps: Best Practices</h3><ul><li>Use <strong>flutter_secure_storage</strong> for sensitive data.</li><li>Enforce HTTPS with <strong>certificate/public key pinning</strong>.</li><li>Enable <strong>code obfuscation</strong> to hinder reverse engineering.</li><li>Integrate security checks into your <strong>CI/CD pipeline</strong>.</li><li>Use tools like <strong>Guardsquare AppSweep</strong> for Flutter-specific vulnerability scanning.</li><li>Keep dependencies up to date and apply the principle of <strong>least privilege</strong>.</li></ul><h3>3. Reverse Engineering Flutter Apps (Preview)</h3><p>One of the most critical aspects of Flutter pentesting is <strong>reverse engineering</strong> — analyzing a compiled app to understand its internal logic, uncover hidden data, or assess code-level weaknesses.</p><p>Reverse engineering typically involves:</p><ul><li><strong>Decompiling Dart or native code</strong> to inspect logic and secrets.</li><li><strong>Analyzing app binaries</strong> (libapp.so, assets, or resources).</li><li><strong>Using tools like JADX, Ghidra, or Frida</strong> to explore app internals dynamically.</li></ul><p>While this technique is invaluable for discovering real risks, it also reveals how attackers can <strong>decompile, tamper, or hook</strong> into apps — which is why security through obscurity is never enough.</p><p>👉 In the <strong>next Medium article</strong>, we’ll explore <strong>reverse engineering in Flutter</strong> — diving into the tools, methods, and defenses that every mobile developer should know.</p><h3>📚 References &amp; Further Reading</h3><ol><li><a href="https://docs.flutter.dev/security">Flutter Security Documentation</a></li><li><a href="https://owasp.org/www-project-mobile-app-security">OWASP Mobile Application Security Project</a></li><li><a href="https://touchlane.com/building-a-secure-flutter-app">Building a Secure Flutter App — Touchlane</a></li><li>Security Testing in Flutter (Medium)</li><li><a href="https://www.guardsquare.com/blog/mobile-app-security-testing-flutter">Guardsquare AppSweep</a></li><li><a href="https://www.blazeinfosec.com/post/mobile-application-penetration-testing">Blaze Information Security: Mobile App Pentesting Guide</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=beb001e1b781" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ How to Integrate Allure Reporter with Flutter Testing]]></title>
            <link>https://medium.com/@talelbriki13/how-to-integrate-allure-reporter-with-flutter-testing-7d8fce1e8eeb?source=rss-4ada6984b5df------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d8fce1e8eeb</guid>
            <category><![CDATA[flutter-testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[allure-reporting]]></category>
            <dc:creator><![CDATA[Talelbriki]]></dc:creator>
            <pubDate>Wed, 17 Sep 2025 11:30:32 GMT</pubDate>
            <atom:updated>2025-09-17T11:30:32.967Z</atom:updated>
            <content:encoded><![CDATA[<p>Testing is a crucial part of building reliable Flutter apps, but anyone who has worked with flutter test knows the default console output can quickly become overwhelming. While it tells you which tests passed or failed, it doesn’t provide a clear, visual way to explore results, failures, or historical trends.</p><p>That’s where <strong>Allure Report </strong>📊 comes in. Allure transforms raw test results into interactive, visual dashboards with charts, steps, and attachments that make debugging and reporting much easier. In this article, we’ll explore how to integrate <strong>Allure Reporter with Flutter tests</strong> to bring professional-grade reporting to your development and CI/CD workflows.</p><h3>📊 What is Allure Report?</h3><p><a href="https://allurereport.org/docs/"><strong>Allure Report</strong></a> is an open-source test reporting framework that turns raw test execution data into a <strong>beautiful, interactive dashboard</strong>. Instead of scrolling endlessly through console logs, you get a <strong>visual overview of your test results</strong> with features like:</p><ul><li>✅ <strong>Pass/Fail summaries</strong> — see instantly how many tests passed, failed, or were skipped.</li><li>🧩 <strong>Categorized features</strong> — group tests by feature, story, or severity for easier tracking.</li><li>📝 <strong>Step-by-step test flow</strong> — visualize each action your test performed.</li><li>📎 <strong>Attachments</strong> — include screenshots, logs, or additional context when a test fails.</li><li>📈 <strong>Historical trends</strong> — track how your test suite evolves over time.</li></ul><p>Allure is widely adopted in the QA and DevOps world because it integrates seamlessly with popular CI/CD tools like <strong>Jenkins, GitHub Actions, GitLab CI, and TeamCity</strong>.</p><p>For Flutter developers, this means you can go beyond the plain console output and bring your test results to the same level of <strong>professional visibility</strong> you see in enterprise-grade testing setups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3kFH5KBgle2pEKQK.png" /></figure><h3>🧪 Setting Up Flutter Tests</h3><p>Before we integrate Allure Reporter, let’s recap how <strong>Flutter testing</strong> works out of the box.</p><p>Flutter gives us <strong>three main types of tests</strong>:</p><h3>1️⃣ Unit Tests</h3><p>Used for testing a single function, class, or method in isolation.</p><p>👉 Example:</p><pre>import &#39;package:flutter_test/flutter_test.dart&#39;;<br><br>int add(int a, int b) =&gt; a + b;<br><br>void main() {<br>  test(&#39;adds two numbers&#39;, () {<br>    expect(add(2, 3), 5);<br>  });<br>}</pre><p>Run with:</p><pre>flutter test</pre><h3>2️⃣ Widget Tests</h3><p>Used for testing UI components in isolation, without launching a full app.</p><p>👉 Example:</p><pre>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:flutter_test/flutter_test.dart&#39;;<br><br>void main() {<br>  testWidgets(&#39;Counter increments test&#39;, (WidgetTester tester) async {<br>    // Build widget<br>    await tester.pumpWidget(<br>      MaterialApp(<br>        home: Scaffold(<br>          body: StatefulBuilder(<br>            builder: (context, setState) {<br>              int counter = 0;<br>              return Column(<br>                children: [<br>                  Text(&#39;$counter&#39;, key: Key(&#39;counter&#39;)),<br>                  ElevatedButton(<br>                    onPressed: () =&gt; setState(() =&gt; counter++),<br>                    child: Text(&#39;Increment&#39;),<br>                  ),<br>                ],<br>              );<br>            },<br>          ),<br>        ),<br>      ),<br>    );<br><br>    // Verify initial state<br>    expect(find.text(&#39;0&#39;), findsOneWidget);<br><br>    // Tap increment button<br>    await tester.tap(find.byType(ElevatedButton));<br>    await tester.pump();<br><br>    // Verify state updated<br>    expect(find.text(&#39;1&#39;), findsOneWidget);<br>  });<br>}</pre><p>Run with:</p><pre>flutter test</pre><h3>3️⃣ Integration Tests</h3><p>Used for <strong>end-to-end testing</strong> of the entire app on a device/emulator.</p><p>👉 Example:</p><pre>import &#39;package:flutter_test/flutter_test.dart&#39;;<br>import &#39;package:integration_test/integration_test.dart&#39;;<br>import &#39;package:my_app/main.dart&#39; as app;<br><br>void main() {<br>  IntegrationTestWidgetsFlutterBinding.ensureInitialized();<br><br>  testWidgets(&#39;end-to-end login flow&#39;, (WidgetTester tester) async {<br>    app.main();<br>    await tester.pumpAndSettle();<br><br>    // Enter username<br>    await tester.enterText(find.byKey(Key(&#39;usernameField&#39;)), &#39;test_user&#39;);<br>    // Enter password<br>    await tester.enterText(find.byKey(Key(&#39;passwordField&#39;)), &#39;123456&#39;);<br>    // Tap login button<br>    await tester.tap(find.byKey(Key(&#39;loginButton&#39;)));<br>    await tester.pumpAndSettle();<br><br>    // Verify success screen<br>    expect(find.text(&#39;Welcome!&#39;), findsOneWidget);<br>  });<br>}</pre><p>Run with:</p><pre>flutter test integration_test</pre><h3><strong>Installing Allure Reporter for Flutter</strong></h3><ol><li>Add the dev dependencies :</li></ol><p>Add allure_report and test_reporter to your dev_dependencies in pubspec.yaml (keep flutter_test / integration_test as needed):</p><pre>dev_dependencies:<br>  flutter_test:<br>    sdk: flutter<br>  integration_test:<br>    sdk: flutter<br><br>  # reporter<br>  test_reporter: ^1.3.0<br>  allure_report: ^1.4.0<br><br>dependencies<br>  alchemist_test_reporter: ^1.1.0<br>  alchemist: ^0.12.1</pre><p>2) Create the reporter entry point (test/reporter.dart)</p><p>Create test/reporter.dart (this file is how test_reporter discovers which reporter to use). Minimal content:</p><pre>// test/reporter.dart<br>import &#39;package:allure_report/allure_report.dart&#39;;<br>import &#39;package:test_reporter/test_reporter.dart&#39;;<br><br>TestReporter create() {<br>  return AllureReporter();<br>}</pre><p>Put the file under test/ (or next to your tests). If this file doesn&#39;t exist, the basic console reporter will be used.</p><p>3) Configure a Global Test Entry Point (flutter_test_config.dart)</p><p>Flutter automatically looks for a file named <strong>flutter_test_config.dart</strong> at the root of your test/ directory.<br> This file is executed <em>before any test runs</em> and is perfect for setting up <strong>global configuration</strong>, such as:</p><ul><li>Custom reporters (like Allure)</li><li>Golden test handling (via Alchemist)</li><li>Test environment flags for CI/CD</li></ul><p>Here’s an example that integrates <strong>Allure Reporter</strong> with <a href="https://pub.dev/packages/alchemist"><strong>Alchemist</strong></a> for golden (UI snapshot) testing:</p><pre>// flutter_test_config.dart<br>import &#39;dart:async&#39;;<br>import &#39;package:alchemist/alchemist.dart&#39;;<br>import &#39;package:alchemist_test_reporter/alchemist_test_reporter.dart&#39;;<br>import &#39;package:allure_report/allure_report.dart&#39;;<br><br>Future&lt;void&gt; testExecutable(FutureOr&lt;void&gt; Function() testMain) {<br>  const isRunningInCi = bool.fromEnvironment(&#39;CI&#39;, defaultValue: false);<br><br>  // Wrap the golden test runner so that diffs are reported as Allure attachments<br>  goldenTestRunner = GoldenTestRunnerWithReports(<br>    inner: goldenTestRunner,<br>    onAttachmentCreated: Allure.diff, // Attach diffs to Allure<br>  );<br><br>  return AlchemistConfig.runWithConfig(<br>    config: AlchemistConfig(<br>      platformGoldensConfig: PlatformGoldensConfig(<br>        platforms: {HostPlatform.current()},<br>        enabled: !isRunningInCi, // Disable goldens in CI if needed<br>      ),<br>    ),<br>    run: () async {<br>      await testMain();<br>    },<br>  );<br>}</pre><p>4) Writing a Simple Test with Allure</p><p>Once the reporter is set up, you can start adding <strong>steps and labels</strong> to your tests.</p><p>👉 Example:</p><pre>import &#39;dart:io&#39;;<br>import &#39;package:flutter_test/flutter_test.dart&#39;;<br>import &#39;package:path/path.dart&#39; as p;<br><br>class Counter {<br>  int value = 0;<br>  void increment() =&gt; value++;<br>}<br><br><br>void main() {<br>  test(&#39;Counter increments&#39;, () {<br>    int counter = 0;<br>    counter++;<br><br>    expect(counter, 1);<br><br>    // ✅ Save result to a file<br>    final subfolder = &#39;unit&#39;;<br>    final outDir = Directory(p.join(Directory.current.path, &#39;reports&#39;, &#39;results&#39;, subfolder))<br>      ..createSync(recursive: true);<br><br>    final logFile = File(p.join(outDir.path, &#39;counter_log.txt&#39;))<br>      ..writeAsStringSync(&#39;Counter incremented to $counter&#39;);<br><br>    // ✅ Attach file<br>    print(&#39;event:attachment:${logFile.path}&#39;);<br>  });<br>}</pre><p><strong>🔎 What this does</strong></p><p>The snippet above is a <strong>unit test for a simple counter</strong> in Dart/Flutter. Here’s a breakdown:</p><p><strong>Counter logic</strong>:</p><pre>int counter = 0;<br>counter++;<br>expect(counter, 1);</pre><ul><li>Initializes a counter at 0, increments it by 1, and asserts that the final value is 1.</li><li>expect(counter, 1); ensures the test passes only if the counter correctly increments.</li></ul><p><strong>Logging results</strong>:</p><pre>final subfolder = &#39;unit&#39;;<br>final outDir = Directory(p.join(Directory.current.path, &#39;reports&#39;, &#39;results&#39;, subfolder))<br>  ..createSync(recursive: true);<br><br>final logFile = File(p.join(outDir.path, &#39;counter_log.txt&#39;))<br>  ..writeAsStringSync(&#39;Counter incremented to $counter&#39;);<br><br>print(&#39;event:attachment:${logFile.path}&#39;);</pre><ul><li>Creates a reports/results/unit folder inside your project if it doesn&#39;t exist.</li><li>Writes the test result to counter_log.txt.</li><li>Prints a special line in the console (event:attachment:&lt;path&gt;) so that tools like <strong>Allure</strong> can attach the file to the test report.</li></ul><p>5) Running Tests with the Reporter</p><p>Instead of running plain flutter test, you use the <strong>reporter wrapper</strong>:</p><pre>dart run test_reporter -- flutter test</pre><p><strong>📂 Where to find attachments</strong></p><ul><li>After running the test, check the following path in your project:ruby</li></ul><pre>&lt;project_root&gt;/reports/results/unit/counter_log.txt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/407/1*qf5xe7b4T3q35bfA5vgVGQ.png" /><figcaption><strong>test output/log</strong>,</figcaption></figure><ul><li>This file contains your <strong>test output/log</strong>, and can be attached to Allure reports.</li></ul><p><strong>📂Where Allure stores generated files (JSON &amp; attachments)</strong></p><ul><li>When you run flutter test with <strong>Allure reporter enabled</strong>, it automatically writes <strong>JSON files and attachments</strong> inside:</li></ul><pre>&lt;project_root&gt;/allure-results/</pre><ul><li>Structure example:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*gt4QTMh1VlAX8tjBQ_YhpQ.png" /></figure><ul><li>These JSON files contain <strong>test metadata, steps, status, and links to attachments</strong>.</li><li>The Allure HTML report reads these files to render a <strong>beautiful interactive report</strong>.</li></ul><blockquote><em>💡 Tip: You can open the folder in VSCode/Explorer to directly see all generated JSON and attached logs/screenshots.</em></blockquote><ul><li>6) Generating the Report</li></ul><p>Install the Allure CLI (once):</p><ul><li>macOS: brew install allure</li><li>Windows: scoop install allure</li><li>Or cross-platform: npm install -g allure-commandline</li></ul><p>Then generate or serve the report:</p><pre># Generate static HTML report<br>allure generate --clean -o allure-report allure-results<br><br># Or serve report locally<br>allure serve allure-results</pre><p>Now you’ll see a <strong>visual dashboard</strong> of your Flutter tests ✨</p><ul><li>Opens an interactive HTML report showing <strong>tests, logs, and attachments</strong>.</li><li>You can explore passed/failed tests and view the counter_log.txt attachment directly.</li></ul><h3>And that’s it! 🎉</h3><p>With just a few lines of code, you now have <strong>unit tests that log results</strong>, <strong>integration with Allure</strong> for beautiful reports, and a clear way to <strong>see exactly what passed, failed, and why</strong>.</p><p>Whether you’re working on a tiny Flutter app or a big project with multiple test types, this setup keeps your <strong>tests organized, results visible, and debugging easier</strong>.</p><p>Happy testing, and may your counters always increment correctly! 🚀</p><h3>References &amp; Resources</h3><ol><li><strong>Flutter Official Documentation — Testing</strong><br> <a href="https://docs.flutter.dev/testing">https://docs.flutter.dev/testing</a><br> Comprehensive guide for unit, widget, and integration testing in Flutter.</li><li><strong>Integration Test Package</strong><br> <a href="https://docs.flutter.dev/testing">https://pub.dev/packages/integration_test</a><br> Flutter’s official package for end-to-end app testing.</li><li><strong>Allure Framework</strong><br> <a href="https://allurereport.org/docs/">https://docs.qameta.io/allure/</a><br> Documentation for generating and visualizing test reports.</li><li><strong>Fultter allure reporter package</strong><br><a href="https://pub.dev/packages/allure_report/"> https://pub.dev/packages/allure_report/<br></a> Dart Allure Report Adapter.</li><li><strong>GitHub Example Project</strong><br><a href="https://github.com/TalelBriki/flutter_allure_integration.git"> Flutter Allure Integration Example<br></a> A fully working project demonstrating unit tests, widget tests, integration tests, and Allure report generation in Flutter.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d8fce1e8eeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Google Play’s 16KB Page Size Requirement: What Developers Need to Know]]></title>
            <link>https://medium.com/@talelbriki13/google-plays-16kb-page-size-requirement-what-developers-need-to-know-c5a951c72d36?source=rss-4ada6984b5df------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5a951c72d36</guid>
            <dc:creator><![CDATA[Talelbriki]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 10:17:55 GMT</pubDate>
            <atom:updated>2025-09-01T10:17:55.302Z</atom:updated>
            <content:encoded><![CDATA[<p>Google is rolling out a <strong>big change for Android apps</strong>: starting <strong>November 1, 2025</strong>, all new apps and updates published to <strong>Google Play</strong> that target <strong>Android 15+</strong> must support the new <strong>16KB memory page size</strong>.</p><p>This might sound highly technical, but don’t worry — let’s break it down simply, and see how it affects you as a developer.</p><h3>🔎 What is a Memory Page?</h3><p>A <strong>memory page</strong> is the smallest unit of memory that the operating system manages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Nx6N7hlrahbdL6Ev" /><figcaption>A diagram showing 4 small boxes (4KB) vs 1 larger box (16KB).</figcaption></figure><ul><li>Traditionally, Android has used <strong>4KB pages</strong>.</li><li>With Android 15, devices are shifting to <strong>16KB pages</strong>, especially on 64‑bit ARM devices.</li></ul><p>Think of it like upgrading from small boxes (4KB) to bigger boxes (16KB) for packing data. You need fewer boxes, and your app can be managed more efficiently.</p><h3>🎯 Why the Shift to 16KB?</h3><p>Google and chip makers are making this change to:</p><ul><li>✅ <strong>Faster app launches</strong> (up to 30% quicker)</li><li>✅ <strong>Lower battery consumption</strong> (~4.5% less power on startup)</li><li>✅ <strong>Faster camera startup</strong> (4.5% to 6.6% faster)</li><li>✅ <strong>Faster system boot</strong> (~0.8s improvement)</li><li>✅ <strong>Better memory management</strong> (fewer pages to track)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sJcnAvvWygE0TMEL" /><figcaption>Benefits of 16KB Pages<strong> </strong>🚀 Faster Launch, 🔋 Battery Saving, 📸 Faster Camera, ⚡ Faster Boot.</figcaption></figure><p>In short: smoother apps, better performance, and improved user experience.</p><h3>👩‍💻 Who Needs to Care?</h3><ul><li><strong>Java/Kotlin-only apps</strong> → You’re safe. No changes needed, but still test on 16KB devices.</li><li><strong>Apps with native code (C/C++, NDK, third‑party SDKs, Unity/Unreal)</strong> → You must rebuild your native libraries to support 16KB.</li></ul><p>If your app bundles .so libraries or uses native SDKs, this applies to you.</p><h3>🛠️ What Developers Need to Do</h3><p>✅<strong>Update your toolchain</strong>:</p><ul><li>Use <strong>Android Gradle Plugin ≥ 8.5.1</strong></li><li>Use <strong>NDK r28+</strong></li></ul><pre>-Wl,-z,max-page-size=16384  </pre><p>✅ <strong>Remove hardcoded page assumptions</strong> (e.g., PAGE_SIZE = 4096). Instead, use runtime queries:</p><pre>getpagesize();<br>sysconf(_SC_PAGESIZE);</pre><p>✅ <strong>Test on 16KB devices</strong>:</p><ul><li>Use Android Studio emulators with 16KB system images.</li><li>On real devices, run:</li></ul><pre>adb shell getconf PAGE_SIZE</pre><p>✅ <strong>Check third‑party SDKs/libraries</strong> (like FFmpeg, TensorFlow, Unity, etc.) — make sure they have updated 16KB support.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IdSgFxytaJlX3FZc" /><figcaption>A flowchart: <em>Update Toolchain → Rebuild Native Code → Fix Hardcoded Values → Test → Publish</em>.</figcaption></figure><h3>📅 Deadline</h3><ul><li><strong>November 1, 2025</strong> → Google Play will <strong>require 16KB page size support</strong> for new app submissions and updates targeting Android 15+.</li></ul><h3>✅ Bottom Line</h3><p>This update might feel like a low-level technical detail, but it brings <strong>big performance wins</strong>. If your app uses native code, start migrating now — don’t wait until the deadline. Java/Kotlin apps are already safe, but testing is still recommended.</p><p>👉 Adapting early means smoother launches, fewer rejections on Play, and happier users.</p><p>💡 <strong>Pro tip:</strong> Use the latest Android Studio + NDK to save yourself from manual linker flag headaches.</p><h3>📚 References</h3><ul><li><a href="https://developer.android.com/guide/practices/page-sizes">Android Developers Blog — Memory Page Size Updates</a></li><li><a href="https://play.google.com/console/about/whats-new/">Google Play Console Updates</a></li><li><a href="https://developer.android.com/ndk/downloads/revision_history">Android NDK Release Notes</a></li><li><a href="https://developer.android.com/topic/performance/overview">Android Performance Best Practices</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5a951c72d36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ What’s New in Flutter 3.35 (August 2025)]]></title>
            <link>https://medium.com/@talelbriki13/whats-new-in-flutter-3-35-august-2025-c16962c18471?source=rss-4ada6984b5df------2</link>
            <guid isPermaLink="false">https://medium.com/p/c16962c18471</guid>
            <dc:creator><![CDATA[Talelbriki]]></dc:creator>
            <pubDate>Thu, 28 Aug 2025 10:45:55 GMT</pubDate>
            <atom:updated>2025-08-28T10:45:55.982Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mMBJ4EMdoSZLIfIm" /></figure><p>Flutter 3.35, released on <strong>August 13, 2025</strong>, comes packed with powerful improvements in <strong>web development</strong>, <strong>accessibility</strong>, and <strong>developer productivity</strong>.</p><p>Whether you’re building apps for mobile, web, or desktop, this update makes Flutter smoother, more inclusive, and more future-ready.</p><p>Let’s dive into the highlights 👇</p><h3>🌐 Web Enhancements</h3><ul><li><strong>🔥 Stateful Hot Reload on Web (Default)</strong><br> No more experimental flags! Flutter web now supports <strong>stateful hot reload by default</strong>, making the dev experience closer to mobile and desktop.</li><li><strong>⚡ WebAssembly (WASM) Dry Runs</strong><br> Every JavaScript build now performs a <strong>“dry run” compilation to WebAssembly</strong>, helping detect readiness issues early.</li><li>Shows console warnings for potential incompatibilities.</li><li>Toggle with:</li></ul><p>```</p><p>— wasm-dry-run <br> — no-wasm-dry-run</p><p>```</p><p><strong>Web Enhancements</strong></p><ul><li>Stateful hot reload on the web is now enabled by default — no experimental flag required.</li><li>Introduced WebAssembly dry runs: every JavaScript build performs a ‘dry run’ compilation to WebAssembly, helping detect readiness issues early via console warnings. Toggle with — (no-)wasm-dry-run.</li></ul><p><strong>Accessibility &amp; Framework Polishing</strong></p><ul><li>Improved web semantics, including support for semantics locales.</li><li>New accessibility widgets and tools: SemanticsLabelBuilder and SliverEnsureSemantics.</li><li>Accessibility fixes across platforms: iOS (VoiceOver, text scaling), Android (TalkBack fixes), CustomPainter semantics support.</li></ul><p><strong>Productivity Boosters &amp; Documentation Updates</strong></p><ul><li>New ‘Create with AI’ guide for integrating Gemini Code Assist, GeminiCLI, and Dart &amp; Flutter MCP Server.</li><li>Flutter Widget Previewer guide to preview widgets directly in Chrome.</li><li>Android support for protecting sensitive content during screen sharing.- Updated supported platforms page</li><li>Breaking changes and migration guide available.</li></ul><p><strong>Community Feedback</strong></p><p>Reddit users on r/FlutterDev expressed excitement about improved Flutter web support.</p><p><strong>References</strong></p><p><a href="https://medium.com/flutter/whats-new-in-flutter-3-35-c58ef72e3766">What’s new in Flutter 3.35. Hot Reload, Widget Previews, and More | by Kevin Chisholm | Flutter | Aug, 2025 | Medium</a></p><p><a href="https://docs.flutter.dev/release/whats-new">What’s new in the docs | Flutter</a></p><p><a href="https://www.reddit.com/r/FlutterDev/comments/1mq94gh/whats_new_in_flutter_335/">What’s new in Flutter 3.35 : r/FlutterDev</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c16962c18471" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>