# Flutter

Flutter is an open-source framework for building natively compiled, multi-platform applications from a single codebase.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## The $1,100 Surprise: A Flutter Developer's Guide to Securing Google Maps API Keys

DevFeed: [The $1,100 Surprise: A Flutter Developer's Guide to Securing Google Maps API Keys](<https://devfeed.tech/articles/the-1-100-surprise-a-flutter-developer-s-guide-to-securing-google-maps-api-keys-139420.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/the-1-100-surprise-a-flutter-developers-guide-to-securing-google-maps-api-keys-5afd85023477?source=rss----86fb29d7cc6a---4>)

Author: Bornak Paul

Published: 2026-11-17T22:07:07Z

Content type: tutorial

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [Google Maps](<https://devfeed.tech/topics/google-maps.md>), [Google](<https://devfeed.tech/topics/google.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [billing](<https://devfeed.tech/tags/billing.md>), [browser](<https://devfeed.tech/tags/browser.md>), [build](<https://devfeed.tech/tags/build.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-platform](<https://devfeed.tech/tags/cloud-platform.md>), [console](<https://devfeed.tech/tags/console.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [disaster](<https://devfeed.tech/tags/disaster.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [gcp](<https://devfeed.tech/tags/gcp.md>), [git](<https://devfeed.tech/tags/git.md>), [google](<https://devfeed.tech/tags/google.md>), [google-cloud-platform](<https://devfeed.tech/tags/google-cloud-platform.md>), [google-maps](<https://devfeed.tech/tags/google-maps.md>), [ios](<https://devfeed.tech/tags/ios.md>), [keys](<https://devfeed.tech/tags/keys.md>), [mobile-security](<https://devfeed.tech/tags/mobile-security.md>)

### AI overview

The excerpt attributes unexpected Google Maps Platform bills of $842 and $1,120 to one unrestricted API key reused across Flutter Android, iOS, and Web and exposed through shared Git repositories and browser inspection. A shared key lets someone who obtains it use the account's Maps services, and compromise leaves no way to revoke access without affecting all three platforms. The excerpt identifies separating and restricting keys as the intended fix, but cuts off before giving implementation steps.

### Source excerpt

A cautionary tale on how copy-pasting a single unrestricted Google Maps API key across Android, iOS, and Flutter Web led to massive billing spikes -- and how to fix your GCP security in 10 minutes. The Invoice That Made Our Hearts Drop It arrived quietly in our inbox on a Tuesday morning: a Google Cloud Platform invoice showing an unexpected charge of $842. The following month, another arrived for $1,120. Our app hadn't suddenly gone viral. Our active user numbers hadn't spiked. Yet, our Google Maps Platform consumption was skyrocketing. When we opened the GCP console to investigate, the realization hit us like a bucket of ice water: we were using a single, completely unrestricted Google Maps API key across our entire Flutter codebase. Because Flutter makes multi-platform delivery so effortless, it had been all too easy to take the same API key and drop it into android/app/src/main/AndroidManifest.xml, ios/Runner/AppDelegate.swift, and web/index.html. It was checked into Git repositories shared with past contractors, active devs, and former team members. Worse yet, anyone who opened Chrome Developer Tools on our Flutter Web build could grab our key in plain text. If this sounds uncomfortably familiar, you're not alone. In this post, we'll look at why the "one key for all Flutter targets" anti-pattern is a financial disaster and how to properly isolate and restrict your keys. The Flutter Multi-Platform Trap When building with Flutter, it's tempting to create a single key named flutter-maps-key and reuse it everywhere. Here is why that approach fails catastrophically: Flutter Web Exposes Keys to the World: Flutter Web builds render directly in the browser. Anyone inspecting your web/index.html or network requests can steal your key and use it to power their own apps or scraping scripts on your dime. Revocation Paralysis: If your key is compromised, deleting it instantly bricks your Android app, iOS app, and Web app simultaneously. You cannot fix the Web vulnerability w

## Rust Leaves Top 10 in TIOBE Index, Making Room for Go

DevFeed: [Rust Leaves Top 10 in TIOBE Index, Making Room for Go](<https://devfeed.tech/articles/rust-leaves-top-10-in-tiobe-index-making-room-for-go-134466.md>)

Original publisher: [Read original article](<https://developers.slashdot.org/story/26/11/15/0710240/rust-leaves-top-10-in-tiobe-index-making-room-for-go>)

Author: EditorDavid

Published: 2026-11-15T15:34:00Z

Content type: news

Language: en

Sources: [Slashdot](<https://devfeed.tech/sources/slashdot.md>)

Topics: [Dart](<https://devfeed.tech/topics/dart.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [Visual Basic](<https://devfeed.tech/topics/visual-basic.md>), [Perl](<https://devfeed.tech/topics/perl.md>)

Tags: [assembly](<https://devfeed.tech/tags/assembly.md>), [c](<https://devfeed.tech/tags/c.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [dart](<https://devfeed.tech/tags/dart.md>), [development](<https://devfeed.tech/tags/development.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [features](<https://devfeed.tech/tags/features.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [framework](<https://devfeed.tech/tags/framework.md>), [go](<https://devfeed.tech/tags/go.md>), [google](<https://devfeed.tech/tags/google.md>), [index](<https://devfeed.tech/tags/index.md>), [java](<https://devfeed.tech/tags/java.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [julia](<https://devfeed.tech/tags/julia.md>), [programming](<https://devfeed.tech/tags/programming.md>), [rust](<https://devfeed.tech/tags/rust.md>), [tiobe](<https://devfeed.tech/tags/tiobe.md>), [top](<https://devfeed.tech/tags/top.md>)

### AI overview

In November's TIOBE Index, Go took the #10 spot from Rust, which fell to #11 despite its share rising from 1.44% to 1.63%; it remained above its #14 position a year earlier. Java moved back to #3 ahead of C++, though the excerpt says their difference was insignificant. Python led by a wide margin, and C ranked ahead of Java and C++. Dart entered the top 20 as Julia left; the excerpt attributes Dart's popularity mainly to Flutter and its cross-platform, single-codebase development ecosystem. R and SQL entered the top 10 as Visual Basic lost two places, while Assembly re-entered the top 20. The figures illustrate that small month-to-month share changes can shift rankings.

### Source excerpt

"In November's edition of the TIOBE Index, Rust has dropped out of Top 10," writes I-Programmer, noting that Rust ceded the #10 position to Go. "At the same time, another Google-originated language, Dart, has entered the top 20 ousting Julia after only one month." TIOBE explains Dart's popularity is mainly being driven by Flutter, Google's framework for building cross-platform mobile applications. In fact, Flutter has become one of the major technologies for cross-platform mobile app development. The Dart language itself is not particularly unique, although it incorporates many modern programming language features. Its success is largely driven by the strength of the Flutter ecosystem and the convenience of developing applications for multiple platforms using a single codebase... [In November's ranking] Visual Basic has also lost two places, making room for R and SQL in the Top 10. Further down the ranking, Assembly has re-entered the Top 20. So TIOBE ranks the top 10 languages in November as Python, C, Java, C++, C#, JavaScript, R, SQL, Visual Basic, and Go. But I-Programmer points out that "At the top of the table, Java is back in the top 3, after over three years in 4th position," pushing C++ down to #4. Are some changes more significant than others? If you think of the ratings as shares of a pie divided into 100 pieces, there is one huge slice -- Python, accounting for a over a fifth of the pie, then comes C with a slice slightly less than half of Python's. Java and C++ then have smaller slices... and C#'s share is around half of their average size. Over half the pie has now been shared between just five languages... -- Next 5 (#6-10): 10.17% (JavaScript, R, SQL, Visual Basic, Go) -- Next 10 (#11-20): 11.12% (Rust, PHP, Fortran, Scratch, Perl, MATLAB, Assembly, Swift, Delphi, Dart) -- Next 30 (#21-50): 12.81% -- Final 50 (#51-100): 12.93% [So in this month's chart...] Java has overtaken C++, but as you can see from this month's Top 10 chart they are in lock step and

## Direct Native Interop in Flutter 3.50: Let's understand it!

DevFeed: [Direct Native Interop in Flutter 3.50: Let's understand it!](<https://devfeed.tech/articles/direct-native-interop-in-flutter-3-50-let-s-understand-it-131176.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/native-interop-6aef2eae745e?source=rss----86fb29d7cc6a---4>)

Author: Abhishek Doshi

Published: 2026-11-12T18:47:17Z

Content type: article

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [async](<https://devfeed.tech/tags/async.md>), [background](<https://devfeed.tech/tags/background.md>), [dart](<https://devfeed.tech/tags/dart.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [flutter-3-50](<https://devfeed.tech/tags/flutter-3-50.md>), [flutter-app-development](<https://devfeed.tech/tags/flutter-app-development.md>), [interop](<https://devfeed.tech/tags/interop.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [native](<https://devfeed.tech/tags/native.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [platform](<https://devfeed.tech/tags/platform.md>), [preview](<https://devfeed.tech/tags/preview.md>), [production](<https://devfeed.tech/tags/production.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [swift](<https://devfeed.tech/tags/swift.md>), [thread](<https://devfeed.tech/tags/thread.md>), [toast](<https://devfeed.tech/tags/toast.md>)

### AI overview

Flutter 3.50 makes direct native interop production-ready through JNIgen for Java/Kotlin and FFIgen for Objective-C; Swift works when exposed through Objective-C with `@objc`. Generated, type-safe Dart bindings let apps call native APIs directly, synchronously, and from background isolates, avoiding platform-channel message serialization and boilerplate. The excerpt demonstrates JNIgen setup and a direct Android toast call, and describes using FFIgen with Objective-C headers on iOS. Pigeon's Native Interop integration remains a preview, limited to Android, iOS, and macOS, with no `@TaskQueue` support. Direct calls require care with JNI object references, thread placement, native type checks, and R8/ProGuard; JNIgen also requires an initial Android app build. The source advises keeping stable platform channels and considering interop for new integrations or calls needing synchronous results or better performance.

### Source excerpt

It's time to say goodbye to platform channel boilerplate and call native code directly from Dart! Flutter 3.50 is here, and one feature I'm personally very excited about is direct native interop going stable! If you have ever written a platform channel, you know the drill. A channel name string in Dart. The same string again in Kotlin. The same again in Swift. And if any one of them doesn't match, you find out at runtime with a MissingPluginException. We all have been there 😅 With Flutter 3.50, that changes. Let's understand what it is and how to use it! What is Direct Native Interop? Until now, the standard way to talk to Android or iOS from Flutter was platform channels. Your Dart code sends a message, it gets serialized, it reaches the native side, native code does the work, and the reply comes back the same way. Every call is async and pays this cost. Direct native interop means your Dart code calls Java, Kotlin, or Objective-C APIs directly, using type-safe Dart bindings generated for you. In simple words, calling a native API becomes just like calling a normal Dart function. No channel names, no MethodCall switch, no Future for something that should be a simple function call. What's new in Flutter 3.50? JNIgen (for Java and Kotlin) is now production-ready. FFIgen (for Objective-C) is now production-ready. Swift works too, as long as your Swift code is exposed to Objective-C using @objc. A Pigeon Native Interop (Preview) that generates type-safe bindings on top of both. You can call native code synchronously, and even from background isolates. PS: This was possible because of the thread merge that started in Flutter 3.29. Dart code now runs on the platform's main thread on Android and iOS (and later on desktop too), so there is no wall between Dart and native anymore. How to use it? Let's take the classic "show a toast" example. Earlier, with a platform channel, you had to write Dart: const channel = MethodChannel('com.example/toast'); Future<void> showToast(St

## How Flutter's Material and Cupertino Decoupling is Changing Cross-Platform UI Development

DevFeed: [How Flutter's Material and Cupertino Decoupling is Changing Cross-Platform UI Development](<https://devfeed.tech/articles/how-flutter-s-material-and-cupertino-decoupling-is-changing-cross-platform-ui-development-122374.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/how-flutters-material-and-cupertino-decoupling-is-changing-cross-platform-ui-development-da944fbb9977?source=rss----86fb29d7cc6a---4>)

Author: Ella Wilson

Published: 2026-11-07T21:48:16Z

Content type: article

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [Material Design](<https://devfeed.tech/topics/material-design.md>), [material-components](<https://devfeed.tech/topics/material-components.md>), [liquid glass](<https://devfeed.tech/topics/liquid-glass.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [cross-platform-ui](<https://devfeed.tech/tags/cross-platform-ui.md>), [decoupling](<https://devfeed.tech/tags/decoupling.md>), [design-systems](<https://devfeed.tech/tags/design-systems.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [flutter-app-development](<https://devfeed.tech/tags/flutter-app-development.md>), [flutter-ui](<https://devfeed.tech/tags/flutter-ui.md>), [framework](<https://devfeed.tech/tags/framework.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [material](<https://devfeed.tech/tags/material.md>), [regression-testing](<https://devfeed.tech/tags/regression-testing.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

### AI overview

Flutter 3.47 introduced independently versioned `material_ui` and `cupertino_ui` packages, allowing supported Material and Cupertino updates without waiting for a core SDK release. This can give teams more control over platform-specific UI changes, subject to SDK and dependency compatibility. The packages remain Flutter-rendered widgets, so they do not provide native behavior automatically; teams still need to validate conventions, accessibility, animations, and interactions. Migration risks include third-party or shared APIs exposing legacy widget types, which Dart treats as distinct from types in the standalone libraries. Audit dependencies and shared widgets, check compatibility, and review localization and UI behavior. Compatibility bridges can help with inherited theme and localization context but do not resolve public API type mismatches. The excerpt says improvements to style-neutral widgets remain ongoing and are not automatically available through the standalone packages.

### Source excerpt

Flutter has long enabled developers to build Android and iOS applications from a shared codebase while supporting platform-specific interfaces through Material and Cupertino widgets. However, because these design libraries were bundled with the Flutter SDK, even minor framework-provided UI improvements could require a complete SDK upgrade, potentially introducing unrelated changes and additional regression testing. In August 2026, Flutter 3.47 addressed this limitation by introducing independently versioned material_ui and cupertino_ui packages. Officially announced in September 2026, this architectural change allows Flutter's design libraries to evolve separately from the core framework, with implications for platform-specific UI updates, custom design systems, and long-term application maintenance. How Decoupling Changes Cross-Platform UI Development For developers, the change affects more than package updates. It also influences how platform-specific interfaces evolve, how custom design systems are built, and how UI dependencies are managed across applications. 1. Faster Adoption of Platform-Specific UI Changes Google's Material 3 Expressive and Apple's Liquid Glass introduce new visual treatments and interaction patterns. Flutter's standalone design libraries let teams implement these evolving design systems without waiting for the next Flutter SDK update. Applications maintaining separate Android and iOS interfaces can incorporate supported design updates through the relevant package, subject to SDK and dependency compatibility. This gives teams greater control over when to adopt new platform conventions without requiring coordinated changes to both UI libraries. However, decoupling does not automatically deliver native UI behavior. Material and Cupertino remain Flutter-rendered widget libraries, and developers must still implement appropriate platform conventions and validate accessibility, animations, and interactions. 2. Better Foundations for Custom Design

## Flutter Better in Java

DevFeed: [Flutter Better in Java](<https://devfeed.tech/articles/flutter-better-in-java-109732.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/flutter-better-in-java/>)

Author: Shai Almog

Published: 2026-10-30T00:00:00Z

Content type: comparison

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Android](<https://devfeed.tech/topics/android.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [JavaFX](<https://devfeed.tech/topics/javafx.md>), [Swing](<https://devfeed.tech/topics/swing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [maven-plugin](<https://devfeed.tech/topics/maven-plugin.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [dart](<https://devfeed.tech/tags/dart.md>), [faster](<https://devfeed.tech/tags/faster.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [java](<https://devfeed.tech/tags/java.md>), [javafx](<https://devfeed.tech/tags/javafx.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [memory](<https://devfeed.tech/tags/memory.md>)

### AI overview

Codename One can import Flutter apps from their original Dart source and build them as Codename One apps. In the October 29 CI comparison of Flutter Gallery release builds, Codename One led on all 26 measured metrics; on Android it used 4.7 MB of executable code versus 20.6 MB and started in about a third of the time. The importer copies app code and assets, adds a Dart runtime implemented through Java transpilation, and builds with Maven without requiring the Dart or Flutter SDK. The result is not pixel-identical: some text wrapping and avatar shapes differ, Dart support is experimental, some callbacks or parameters are ignored, and only one large app has been verified. The author advises testing every relied-on interaction. Android timings use an emulator; iOS start-up and memory and web start-up were not measured. The post attributes the smaller native builds partly to ahead-of-time Java compilation and dead-code elimination, while noting the compatibility layer itself adds overhead.

### Source excerpt

Codename One now builds Flutter apps from their Dart source, and the result starts faster, uses less memory and ships less code than Flutter's own release build. This week also covers KMP, Swing and JavaFX, Android apps and more.

## Flutter vs React Native: How I Choose, and When I Go Native

DevFeed: [Flutter vs React Native: How I Choose, and When I Go Native](<https://devfeed.tech/articles/flutter-vs-react-native-how-i-choose-and-when-i-go-native-105766.md>)

Original publisher: [Read original article](<https://proandroiddev.com/flutter-vs-react-native-how-i-choose-and-when-i-go-native-e147c70eb0c8?source=rss----c72404660798---4>)

Author: Ramiz Raja

Published: 2026-10-29T01:58:07Z

Content type: comparison

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [React Native](<https://devfeed.tech/topics/react-native.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Expo](<https://devfeed.tech/topics/expo.md>), [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [dart](<https://devfeed.tech/tags/dart.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [healthcare](<https://devfeed.tech/tags/healthcare.md>), [here](<https://devfeed.tech/tags/here.md>), [impeller](<https://devfeed.tech/tags/impeller.md>), [ios](<https://devfeed.tech/tags/ios.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [native](<https://devfeed.tech/tags/native.md>), [product](<https://devfeed.tech/tags/product.md>), [production](<https://devfeed.tech/tags/production.md>), [public](<https://devfeed.tech/tags/public.md>), [react-native](<https://devfeed.tech/tags/react-native.md>), [rendering](<https://devfeed.tech/tags/rendering.md>), [repo](<https://devfeed.tech/tags/repo.md>), [sample](<https://devfeed.tech/tags/sample.md>), [screens](<https://devfeed.tech/tags/screens.md>), [vs](<https://devfeed.tech/tags/vs.md>)

### AI overview

For existing native apps that need screens added, the author favors React Native; for new apps, they lean toward Flutter with teams lacking web experience and React Native with JavaScript or React teams, probably using Expo. They recommend native development when the product centers on one platform or its newest features. Flutter draws its own widgets, using Impeller where supported and a legacy OpenGL fallback on some Android devices; React Native creates platform views at runtime. The author reports production Flutter releases to both stores but no React Native-only store release, so their React Native recommendation for new apps is based on documentation rather than equivalent shipping experience. They offer no performance benchmark and suggest comparing release builds on users' slower devices for frame drops, cold starts and install size. Their Flutter app used plugins for much platform functionality, plus one custom calendar channel and three app-owned native source files; its release pipeline also required substantial work.

### Source excerpt

You have one app to build, two stores to ship it to, and a team that cannot write it twice. That is when Flutter vs React Native (or React Native vs Flutter, depending on which camp asks) comes up. The short answer, with the reasons below: Adding screens to a native app you already have: React Native. A new app, a team without a web background: Flutter. A new app, a JavaScript or React team: React Native, probably with Expo. The product lives inside one platform's features: neither. Go native. My experience is uneven, so here it is up front. I shipped a production Flutter app to both stores. My React Native work was inside native apps, an SDK and a sample. I also ship native Android and iOS apps. What I have actually shipped in each Flutter. Carewell is a Swiss healthcare staffing app, live on Google Play and on the App Store. I was the main mobile engineer, with 539 commits between February and October 2026. I also rebuilt the Android CI/CD and built the iOS release pipeline from zero, GitHub Actions to TestFlight and Play. It is a client repo, so I describe it and do not link the source. React Native. My experience here is narrower: A public sample, ReactNativeShoppingApp, that runs on iOS and Android. One React Native component embedded inside the native Android app at Yahoo Sports. The app was native, and React Native was a part of it. A React Native SDK contribution at Portal, where the JavaScript API wraps a native Android SDK. I have not taken a React Native-only app, Expo or not, through to a store release. Weigh the React Native parts below accordingly. Flutter vs React Native: how each one draws the screen Flutter draws its own widgets. Its architectural overview says: "Flutter has its own implementations of each UI control, rather than deferring to those provided by the system." On native platforms, "the Dart code that paints Flutter's visuals is compiled into native code, which uses Impeller for rendering." Impeller is the default on iOS and on Android A

## Flame Gallery: Drop-in Mini Games for Flutter Apps

DevFeed: [Flame Gallery: Drop-in Mini Games for Flutter Apps](<https://devfeed.tech/articles/flame-gallery-drop-in-mini-games-for-flutter-apps-105646.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/flame-gallery-drop-in-mini-games-for-flutter-apps-6df3476482fb?source=rss----86fb29d7cc6a---4>)

Author: Veli Bacık

Published: 2026-10-28T17:02:27Z

Content type: article

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Phaser](<https://devfeed.tech/topics/phaser.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [browser-game](<https://devfeed.tech/topics/browser-game.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [android](<https://devfeed.tech/tags/android.md>), [apps](<https://devfeed.tech/tags/apps.md>), [await](<https://devfeed.tech/tags/await.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [browser](<https://devfeed.tech/tags/browser.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [ci](<https://devfeed.tech/tags/ci.md>), [dart](<https://devfeed.tech/tags/dart.md>), [drop-in](<https://devfeed.tech/tags/drop-in.md>), [flame](<https://devfeed.tech/tags/flame.md>), [flame-engine](<https://devfeed.tech/tags/flame-engine.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [game-development](<https://devfeed.tech/tags/game-development.md>), [games](<https://devfeed.tech/tags/games.md>), [html5](<https://devfeed.tech/tags/html5.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [library](<https://devfeed.tech/tags/library.md>), [loyalty](<https://devfeed.tech/tags/loyalty.md>), [maestro](<https://devfeed.tech/tags/maestro.md>), [mini](<https://devfeed.tech/tags/mini.md>)

### AI overview

Flame Gallery is an MIT-licensed Flutter/Flame library for adding configurable mini-games through an awaited `FlameGallery.show` call. It returns a typed `GameResult` and streams game events, allowing host apps to use scores and stats for rewards or analytics. The four separate game packages cover slicing, lane running, match-three, and rhythm play; shared core code handles menus, phases, overlays, and results. The excerpt describes custom themes, assets, menus, and difficulty, with audio supplied by the host through an interface. Compared with HTML5 games in a WebView, the article says games render with Flutter, ship assets in the app bundle for offline use, and avoid a JavaScript bridge. It also details per-game image caches cleared on close, deterministic gameplay randomness, pure-Dart logic tests, Flame flow tests, and Maestro end-to-end tests. Planned work includes native iOS/Android add-to-app support, Android back-gesture polish, and profile-mode frame-time measurements.

### Source excerpt

One line, one game Marketing asks for "a little game in the app" every few months: a summer campaign, a loyalty reward, a daily challenge. Each time, a team builds a one-off screen that nobody wants to maintain afterwards. Flame Gallery turns that into one dependency and one call: final result = await FlameGallery.show(context, game: const FruitSlice()); The call pushes a full screen game with start, pause and game over menus, and completes with a GameResult you can turn into points, coupons or analytics. It is open source (MIT), built on Flame, and you can play it in your browser right now. In numbers: 6 packages on pub.dev - 4 games - about 6,000 lines of library code - unit and game tests in every package - 6 Maestro end-to-end flows on iOS and Android. From WebView games to native power For years, the mini game inside a mobile app was usually an HTML5 game: JavaScript running in a WebView. It works, but you can feel it. Here is what changes when the game is drawn by Flutter itself: Rendering. A WebView game runs a browser engine inside your app. Flame Gallery draws with Flutter's own engine, the same one drawing the rest of your UI. First load. No pages, scripts or assets to download. Everything ships in the app bundle and works offline. Touch and frame rate. No extra layers between the finger and the frame. Gestures and frames are handled natively by Flutter. Score back to the app. No JavaScript bridge and string messages. You get a typed Dart GameResult from an await. Look and feel. No separate web styling to keep in sync. The game uses your app's Theme, font and colors. Who maintains it. Not a separate web team: the same Flutter team, the same CI. That is the core idea: campaign games get the same native performance as the rest of your app, and the integration is one awaited function call instead of a bridge. Four games, four Flame techniques Every game package has the same inside: src/logic/ is pure Dart with unit tests, src/component/ holds one Flame compon

## Migrating A Flutter Project to Built In Kotlin

DevFeed: [Migrating A Flutter Project to Built In Kotlin](<https://devfeed.tech/articles/migrating-a-flutter-project-to-built-in-kotlin-105647.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/migrating-a-flutter-project-to-built-in-kotlin-e0e41f2ea11a?source=rss----86fb29d7cc6a---4>)

Author: tomerpacific

Published: 2026-10-28T15:42:03Z

Content type: tutorial

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Android](<https://devfeed.tech/topics/android.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [built-in](<https://devfeed.tech/tags/built-in.md>), [dart](<https://devfeed.tech/tags/dart.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>)

### AI overview

Migrating a Flutter project to built-in Kotlin requires Flutter 3.44 or later and, for AGP 9 support, updates to the Android build configuration. The article says to use Flutter's stable channel, upgrade Flutter, set the minimum Flutter version in pubspec.yaml, remove the applied Kotlin Android plugin from the app build file, replace kotlinOptions with the Kotlin compilerOptions block, and update gradle.properties. Android Studio Otter 3 is identified as the first version supporting AGP 9. Dependencies must also support built-in Kotlin; otherwise, the author recommends replacing them or delaying migration. A pure Dart script can inspect a project and propose edits, but changes require approval, manual steps remain, and dependency blockers may persist. Its sample report also cautions that duplicate settings.gradle files can make findings misleading.

### Source excerpt

🙌 TL;DR I created a dart script to automatically migrate your Flutter project with ease. You can find it at the bottom of this article. If your application or plugin supports Flutter version >= 3.44, then you might consider migrating it to use Built In Kotlin support. This is needed in order to support Android Gradle Plugin (AGP) versions >= 9. If you are not supporting Flutter version >= 3.44 or if your project is not currently using AGP >= 9, you don't need to do this right now, but you might want to consider it. I have undergone this migration process with one of my applications, and would like to share the process I had to go through, so you may have an easier going though it. ✋ If you have a Flutter plugin that is a pure Dart plugin (meaning no native Android code), then you don't need to do anything regarding the migration and you can leave it as is.Setting up Flutter >= 3.44 The first thing you need to do in order to migrate your application/plugin is to make sure you are on a Flutter version that supports it. That means, to upgrade your local Flutter version to at least 3.44. Before you upgrade the version, make sure you are on the stable channel in Flutter. You can do so by opening up a terminal and typing: flutter channel If the output shows you that you are on the stable channel, you can proceed to upgrade by typing: flutter upgrade This will upgrade your Flutter version to the latest one in the stable channel. After doing this, we need to also declare in our pubspec.yaml file what our minimum supported Flutter version is: environment: sdk: ^3.2.0 flutter: '>=3.44.0'Upgrading AGP >= 9 (the manual approach) To upgrade the Android Gradle Plugin version to be >= 9, you need to open the android folder of your Flutter project. Make sure you have at least Android Studio Otter 3 since that is the first version that supports AGP 9. Once you have opened the project, you can use the AGP Upgrade Assistant under the Tools menu option. Now, there are several changes you need

## No Flutter NFC Package Could Do Both, So I Built One

DevFeed: [No Flutter NFC Package Could Do Both, So I Built One](<https://devfeed.tech/articles/no-flutter-nfc-package-could-do-both-so-i-built-one-103676.md>)

Original publisher: [Read original article](<https://proandroiddev.com/no-flutter-nfc-package-could-do-both-so-i-built-one-8a3031ecb4c6?source=rss----c72404660798---4>)

Author: Akash Shahriar

Published: 2026-10-27T23:23:27Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [nfc](<https://devfeed.tech/tags/nfc.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [usb](<https://devfeed.tech/tags/usb.md>)

### AI overview

Existing Flutter packages split built-in NFC support from USB smart-card readers on Android, leaving apps to combine separate APIs and implement USB card detection and identification themselves. The author's open-source nfc_hub, not yet on pub.dev in the excerpt, forks ccid's USB transport and presents one API for Android's built-in antenna and USB readers. It combines platform-specific sources with shared transport interfaces and card-family drivers; USB polling detects card arrival and removal, while ATR data and, on ACR122U readers, PN532 commands support identification. The design specifies exactly-once delivery, serialized callbacks, and sessions that survive errors. Reported fixes address unresolved USB permission calls, phantom cards, connection leaks, duplicate delivery, probes interrupting DESFire command chains, and slow phone-side tag I/O. The author uses fake-platform tests for protocol and timing behavior and a hardware checklist for reader-specific behavior. Version 0.8.0 is described as planned, Android-only; NFC-V support is a stated next step.

### Source excerpt

One API for Android's built-in antenna and USB card readers, and the bugs that only real hardware showed me. It started with a simple-sounding requirement. Read an NFC card in a Flutter app on Android. Sometimes the card is tapped on the device's own antenna. Sometimes it sits on a USB reader plugged into the device, because the device has no antenna, or because a reader on a cable is where people actually put their card. To a person, it is the same card. To the code, it is two completely different conversations. The built-in antenna speaks Android's NFC API: NfcAdapter, reader mode, Tag objects, NfcA, IsoDep, MifareClassic. Android discovers the card for you and tells you what it is. The USB reader speaks CCID, a smart-card protocol over USB bulk transfers, wrapped around PC/SC APDUs, wrapped around commands for the NFC chip inside the reader. Nobody tells you a card arrived. Nobody tells you what kind of card it is. You get an ATR, a string of bytes, and you work it out. I assumed someone had already solved this. So I went shopping. What is out there Here is the Flutter NFC landscape as pub.dev shows it today (October 2026): nfc_manager -- Last release: April 2026 - What it covers: Built-in NFC on Android and iOS. Raw platform tag handles; NDEF lives in a separate package - Pub points: 160 flutter_nfc_kit -- Last release: October 2026 - What it covers: Built-in NFC on Android and iOS, with tag metadata, NDEF and transceive. Web works only with special dual-interface USB devices - Pub points: 160 ccid -- Last release: August 2026 - What it covers: USB smart-card readers with a PC/SC-style API: connect, send APDU, get bytes back - Pub points: 160 flutter_pcsc -- Last release: October 2021 - What it covers: PC/SC readers on desktop only. No Android - Pub points: 140 nfc_in_flutter -- Last release: July 2020 - What it covers: Built-in NDEF only. Not Dart 3 compatible - Pub points: 40 flutter_nfc_reader -- Last release: October 2019 - What it covers: Built-in NDEF reading. N

## Sentry's Flutter SDK 10.0: Streaming Traces and More Accurate Crash-Free Rates

DevFeed: [Sentry's Flutter SDK 10.0: Streaming Traces and More Accurate Crash-Free Rates](<https://devfeed.tech/articles/sentry-s-flutter-sdk-10-0-streaming-traces-and-more-accurate-crash-free-rates-87111.md>)

Original publisher: [Read original article](<https://blog.sentry.io/flutter-sdk-10/>)

Author: Gino Buenaflor

Published: 2026-10-14T09:00:00Z

Content type: release

Language: en

Sources: [Sentry](<https://devfeed.tech/sources/sentry-blog.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Android](<https://devfeed.tech/topics/android.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [app-startup](<https://devfeed.tech/tags/app-startup.md>), [crash](<https://devfeed.tech/tags/crash.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [network](<https://devfeed.tech/tags/network.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Sentry Flutter SDK 10.0 makes streaming traces the default and changes crash-free session classification so unhandled errors that do not crash the app no longer count as crashes. It also adds dedicated startup traces on Android and iOS, simplifies logs and metrics setup, expands capture of Dio network failures, and masks Flutter widgets marked sensitive in Replay and screenshots. The release requires Dart 3.12 and Flutter 3.44, among other platform minimums.

### Source excerpt

Flutter SDK 10.0: streaming traces by default, accurate crash-free rates, dedicated app startup traces, and expanded Dio network error capture.

## Reducing Android scope-sync overhead in Sentry Flutter

DevFeed: [Reducing Android scope-sync overhead in Sentry Flutter](<https://devfeed.tech/articles/reducing-android-scope-sync-overhead-in-sentry-flutter-77356.md>)

Original publisher: [Read original article](<https://blog.sentry.io/flutter-android-scope-sync/>)

Author: Gino Buenaflor

Published: 2026-10-08T00:00:00Z

Content type: article

Language: en

Sources: [Sentry](<https://devfeed.tech/sources/sentry-blog.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [Android](<https://devfeed.tech/topics/android.md>), [Expo](<https://devfeed.tech/topics/expo.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [sentry](<https://devfeed.tech/tags/sentry.md>)

### AI overview

The article explains how Sentry Flutter reduced Android scope-sync processing time by eliminating duplicate normalization and encoding JSON directly to bytes. In benchmarks, the combined changes reduced processing time by 27-30% for the measured scope payloads. The improvements shipped in sentry_flutter 9.26.0 and later.

### Source excerpt

How Sentry Flutter uses a worker isolate for Android SDK operations and reduces duplicate normalization and JSON encoding overhead.

## Shipaton Made Me Realize I Was Building the Wrong Way

DevFeed: [Shipaton Made Me Realize I Was Building the Wrong Way](<https://devfeed.tech/articles/shipaton-made-me-realize-i-was-building-the-wrong-way-61147.md>)

Original publisher: [Read original article](<https://hackernoon.com/shipaton-made-me-realize-i-was-building-the-wrong-way?source=rss>)

Author: Muhammad Abdullah

Published: 2026-09-28T14:16:53Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [AI interaction best practices](<https://devfeed.tech/topics/ai-interaction-best-practices.md>), [Interaction Design](<https://devfeed.tech/topics/interaction-design.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-ui-design](<https://devfeed.tech/tags/ai-generated-ui-design.md>), [app-onboarding-design](<https://devfeed.tech/tags/app-onboarding-design.md>), [book-of-me](<https://devfeed.tech/tags/book-of-me.md>), [constraint-driven-design](<https://devfeed.tech/tags/constraint-driven-design.md>), [developer](<https://devfeed.tech/tags/developer.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [flutter-ui-animation](<https://devfeed.tech/tags/flutter-ui-animation.md>), [mobile-app-prototyping](<https://devfeed.tech/tags/mobile-app-prototyping.md>), [monetization](<https://devfeed.tech/tags/monetization.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [revenuecat-for-flutter](<https://devfeed.tech/tags/revenuecat-for-flutter.md>), [shipaton](<https://devfeed.tech/tags/shipaton.md>)

### AI overview

The developer of Book of Me describes how a software product competition changed their approach to building a journal app. They explain that attractive AI-generated designs did not account for interactions or Flutter constraints, and that observing other apps prompted them to consider monetization, onboarding, design, and user experience. After struggling to reproduce an iOS paper-curl effect in Flutter, they shifted toward creating original interactions suited to their resources.

### Source excerpt

Book of Me's developer explains how AI mockups, Flutter limitations, and failed imitation led to original journal interactions built around calmer design.

## Flutter Gemma: The hidden gem of cross-platform local AI

DevFeed: [Flutter Gemma: The hidden gem of cross-platform local AI](<https://devfeed.tech/articles/flutter-gemma-the-hidden-gem-of-cross-platform-local-ai-60026.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/flutter-gemma-the-hidden-gem-of-cross-platform-local-ai-cffdaaf007de?source=rss----86fb29d7cc6a---4>)

Author: Mobile@Exxeta

Published: 2026-09-25T19:59:46Z

Content type: article

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Local AI](<https://devfeed.tech/topics/local-ai.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [gemma](<https://devfeed.tech/topics/gemma.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [acceleration](<https://devfeed.tech/tags/acceleration.md>), [ai](<https://devfeed.tech/tags/ai.md>), [android](<https://devfeed.tech/tags/android.md>), [apple](<https://devfeed.tech/tags/apple.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [embeddings](<https://devfeed.tech/tags/embeddings.md>), [engine](<https://devfeed.tech/tags/engine.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [flutter-app-development](<https://devfeed.tech/tags/flutter-app-development.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [gemini-nano](<https://devfeed.tech/tags/gemini-nano.md>), [gemma](<https://devfeed.tech/tags/gemma.md>), [generation](<https://devfeed.tech/tags/generation.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [inference](<https://devfeed.tech/tags/inference.md>), [ios](<https://devfeed.tech/tags/ios.md>), [litert](<https://devfeed.tech/tags/litert.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llms](<https://devfeed.tech/tags/llms.md>), [local-ai](<https://devfeed.tech/tags/local-ai.md>), [local-llm](<https://devfeed.tech/tags/local-llm.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>)

### AI overview

Flutter Gemma v1.x enables shared Flutter code for local LLM product features while leaving inference to platform-specific engines: MediaPipe supports .task/.bin models and LiteRT-LM supports .litertlm models, with different platform availability. The demo covers text generation, structured analysis, embeddings, SQLite-based RAG, and multi-turn chat. It requires supported converted model formats; quantized models reduce size and RAM needs but may lose quality, and actual inference memory can exceed download size. Results with Qwen3 0.6B were useful for short rewriting and classification, but entity extraction was unreliable and chat quality limited by hallucinations and context length. Gecko 256 supported English similarity matching in the demo. The authors present Flutter as practical for shared-codebase features without strict real-time demands, while recommending native development for performance-critical or hardware-specific needs; complex text tasks remain error-prone.

### Source excerpt

Build Flutter mobile apps with cutting-edge local LLM featuresPhoto by Google DeepMind from Pexels One codebase, multiple platforms, and all using local LLMs -- can this work without compromises? When thinking about integrating local LLM features into your app, you will also start thinking about performance soon. The answer to performance is often "build native". It makes perfect sense considering with LLMs you'll want GPU access and NPU acceleration. All that is platform-specific. And yet, Flutter Gemma v1.x takes a modular approach to resolve this conflict. In this article we'll show you exactly how this works using a real demo app for Android and iOS with six feature areas: setup, text generation, analysis, embeddings, RAG capabilities, and chat. Why Cross-platform for on-device AI? For classical business use cases, the argument for having one codebase is well-known: Write logic once and deploy on multiple platforms like iOS and Android. For features including local models, this becomes more important because model handling and prompting strategies come on top of classical UI frontend development. Things you really don't want to maintain in more than one place. The inference itself stays platform-specific. Native runtimes, GPU, and NPU access differ fundamentally between Android and iOS. Android relies on open acceleration APIs such as NNAPI and GPU delegates via LiteRT, used to run Gemini Nano on modern Android devices. Apple devices use Core ML and the Neural Engine to run the Foundation Model inside a closed, vendor-specific stack. A good cross-platform layer bridges this gap without hiding it. The developer is still in control of which engine runs on which platform. For real-time applications where performance is critical, native development remains the way to go. However, for most product features related to on-device local LLMs, Flutter is becoming an increasingly viable choice. The Ecosystem: Cross-platform options for local LLMs Before diving deep into Flu

## How Flutter Supports Mobile AI Agents Through Shared State and Execution Logic

DevFeed: [How Flutter Supports Mobile AI Agents Through Shared State and Execution Logic](<https://devfeed.tech/articles/how-flutter-supports-mobile-ai-agents-through-shared-state-and-execution-logic-59350.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-flutter-supports-mobile-ai-agents-through-shared-state-and-execution-logic?source=rss>)

Author: Murli Pawar

Published: 2026-09-24T11:44:21Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [mobile-app-development](<https://devfeed.tech/topics/mobile-app-development.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [cross-platform](<https://devfeed.tech/topics/cross-platform.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Dart](<https://devfeed.tech/topics/dart.md>)

Tags: [agent-state-machines](<https://devfeed.tech/tags/agent-state-machines.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-agents-in-mobile-apps](<https://devfeed.tech/tags/ai-agents-in-mobile-apps.md>), [app-development](<https://devfeed.tech/tags/app-development.md>), [blocking](<https://devfeed.tech/tags/blocking.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [dart](<https://devfeed.tech/tags/dart.md>), [dart-streams](<https://devfeed.tech/tags/dart-streams.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [developers](<https://devfeed.tech/tags/developers.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [execution](<https://devfeed.tech/tags/execution.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [flutter-ai-agents](<https://devfeed.tech/tags/flutter-ai-agents.md>), [flutter-app-development](<https://devfeed.tech/tags/flutter-app-development.md>), [governance](<https://devfeed.tech/tags/governance.md>), [idempotent-tool-execution](<https://devfeed.tech/tags/idempotent-tool-execution.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-agent-architecture](<https://devfeed.tech/tags/mobile-agent-architecture.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [state](<https://devfeed.tech/tags/state.md>), [streaming](<https://devfeed.tech/tags/streaming.md>)

### AI overview

This tutorial explains how Flutter can support mobile AI agents through shared application logic and state management. It discusses cross-platform behavior drift, streaming responses, multi-step state dependencies, tool use, approvals, error recovery, governance, and maintainability.

### Source excerpt

Learn how Flutter simplifies enterprise Agentic mobile app development with shared logic, streaming state, hybrid AI inference, governance, and Dart.

## I'm Building Book of Me, a Journal That Won't Let You Rewrite the Past

DevFeed: [I'm Building Book of Me, a Journal That Won't Let You Rewrite the Past](<https://devfeed.tech/articles/i-m-building-book-of-me-a-journal-that-won-t-let-you-rewrite-the-past-58013.md>)

Original publisher: [Read original article](<https://hackernoon.com/im-building-book-of-me-a-journal-that-wont-let-you-rewrite-the-past?source=rss>)

Author: Muhammad Abdullah

Published: 2026-09-22T12:29:17Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [App](<https://devfeed.tech/topics/app.md>), [interface](<https://devfeed.tech/topics/interface.md>), [layout](<https://devfeed.tech/topics/layout.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [book-of-me](<https://devfeed.tech/tags/book-of-me.md>), [design](<https://devfeed.tech/tags/design.md>), [developer](<https://devfeed.tech/tags/developer.md>), [digital-journaling](<https://devfeed.tech/tags/digital-journaling.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [flutter-development](<https://devfeed.tech/tags/flutter-development.md>), [indie-app-development](<https://devfeed.tech/tags/indie-app-development.md>), [mobile-app-monetization](<https://devfeed.tech/tags/mobile-app-monetization.md>), [product](<https://devfeed.tech/tags/product.md>), [revenuecat-integration](<https://devfeed.tech/tags/revenuecat-integration.md>), [shipaton](<https://devfeed.tech/tags/shipaton.md>), [text-pagination](<https://devfeed.tech/tags/text-pagination.md>)

### AI overview

A solo developer describes building Book of Me, a non-editable digital journal in Flutter. The article covers the product concept, its book-inspired interface, and the shift from a two-page layout to a single-page phone experience.

### Source excerpt

I built Book of Me, a journal you can't edit, in Flutter. Here are the pagination bugs, dropped features, and RevenueCat lessons from my Shipaton 2026 build.

## Flet 1.0 Released: Build Production Web, Desktop and Mobile Apps in Python Only

DevFeed: [Flet 1.0 Released: Build Production Web, Desktop and Mobile Apps in Python Only](<https://devfeed.tech/articles/flet-1-0-released-build-production-web-desktop-and-mobile-apps-in-python-only-55636.md>)

Original publisher: [Read original article](<https://www.marktechpost.com/2026/09/20/flet-1-0-released-build-production-web-desktop-and-mobile-apps-in-python-only/>)

Author: Michal Sutter

Published: 2026-09-20T20:50:56Z

Content type: release

Language: en

Sources: [MarkTechPost](<https://devfeed.tech/sources/marktechpost.md>)

Topics: [Mobile](<https://devfeed.tech/topics/mobile.md>), [Python](<https://devfeed.tech/topics/python.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [Web](<https://devfeed.tech/topics/web.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Pytest](<https://devfeed.tech/topics/pytest.md>), [Android](<https://devfeed.tech/topics/android.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Windows](<https://devfeed.tech/topics/windows.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [ai-shorts](<https://devfeed.tech/tags/ai-shorts.md>), [ai-tool](<https://devfeed.tech/tags/ai-tool.md>), [android](<https://devfeed.tech/tags/android.md>), [applications](<https://devfeed.tech/tags/applications.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [ci](<https://devfeed.tech/tags/ci.md>), [editors-pick](<https://devfeed.tech/tags/editors-pick.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [for-devs](<https://devfeed.tech/tags/for-devs.md>), [framework](<https://devfeed.tech/tags/framework.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [new-releases](<https://devfeed.tech/tags/new-releases.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [packages](<https://devfeed.tech/tags/packages.md>), [python](<https://devfeed.tech/tags/python.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [staff](<https://devfeed.tech/tags/staff.md>), [tech-news](<https://devfeed.tech/tags/tech-news.md>), [technology](<https://devfeed.tech/tags/technology.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Flet 1.0 is an open-source Python framework for building production web, desktop, and mobile applications using Flutter-rendered interfaces without requiring Dart, Swift, Kotlin, or JavaScript. The release adds cross-platform packaging, layered testing, bundled Python versions, mobile-ready packages, performance improvements, and in-process communication between Python and Dart.

### Source excerpt

Flet 1.0 shipped on September 15, 2026, and the team now calls the framework ready for production apps. We look at what changed: a layered CI suite that drives packaged apps on real devices, bundled Python 3.12, 3.13 and 3.14, more than 100 mobile ready packages, faster control diffing, and dart-bridge in process communication. We also cover the one migration trap that will bite 0.28 users. The post Flet 1.0 Released: Build Production Web, Desktop and Mobile Apps in Python Only appeared first on MarkTechPost.

## Engineering Real-Time Mobile Personalization Across iOS, Android, React Native, and Flutter

DevFeed: [Engineering Real-Time Mobile Personalization Across iOS, Android, React Native, and Flutter](<https://devfeed.tech/articles/engineering-real-time-mobile-personalization-across-ios-android-react-native-and-flutter-52417.md>)

Original publisher: [Read original article](<https://engineering.salesforce.com/engineering-real-time-mobile-personalization-across-ios-android-react-native-and-flutter/>)

Author: Scott Nyberg

Published: 2026-09-11T20:36:38Z

Content type: article

Language: en

Sources: [Salesforce](<https://devfeed.tech/sources/salesforce-engineering-blog.md>)

Topics: [Mobile](<https://devfeed.tech/topics/mobile.md>), [personalization](<https://devfeed.tech/topics/personalization.md>), [real-time](<https://devfeed.tech/topics/real-time.md>), [Android](<https://devfeed.tech/topics/android.md>), [cross-platform](<https://devfeed.tech/topics/cross-platform.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [React Native](<https://devfeed.tech/topics/react-native.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [data](<https://devfeed.tech/topics/data.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [ios](<https://devfeed.tech/tags/ios.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [personalization](<https://devfeed.tech/tags/personalization.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [react](<https://devfeed.tech/tags/react.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

A Salesforce engineering Q&A explains how a team built real-time mobile personalization across iOS, Android, React Native, and Flutter. It addresses technology fragmentation, cross-channel identity, data integrity, constrained rendering, privacy and consent, deployment cycles, and marketer autonomy.

### Source excerpt

In our Engineering Energizers Q&A series, we highlight the engineering minds driving innovation across Salesforce. Today, we spotlight Sneha Singla, a director of software engineering, whose team confronted a brutal engineering contradiction: making one real-time mobile personalization architecture work across four fundamentally different technology stacks without breaking native layouts, corrupting customer identities, exposing unnecessary profile [...] The post Engineering Real-Time Mobile Personalization Across iOS, Android, React Native, and Flutter appeared first on Salesforce Engineering Blog.

## Diffs vs Whole Files: What Code Editing Agents Should Rewrite

DevFeed: [Diffs vs Whole Files: What Code Editing Agents Should Rewrite](<https://devfeed.tech/articles/diffs-vs-whole-files-what-code-editing-agents-should-rewrite-56071.md>)

Original publisher: [Read original article](<https://www.developersdigest.tech/blog/diffs-vs-whole-files-code-editing-agents>)

Author: Developers Digest

Published: 2026-09-10T00:00:00Z

Content type: article

Language: en

Sources: [Developers Digest](<https://devfeed.tech/sources/developers-digest.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [Dart](<https://devfeed.tech/topics/dart.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [dart](<https://devfeed.tech/tags/dart.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [file](<https://devfeed.tech/tags/file.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [rewrite](<https://devfeed.tech/tags/rewrite.md>)

### AI overview

A code-editing paper reports that generating whole files outperformed iterative diff edits on Flutter and Dart tasks, while suggesting that editing strategies should be selected based on task locality.

### Source excerpt

A new code-editing paper finds full-file generation beating iterative diff edits on Flutter/Dart tasks. The useful takeaway is not to abandon diffs, but to route by task locality.

## Compromised Flutter package on pub.dev contains XCSSET malware

DevFeed: [Compromised Flutter package on pub.dev contains XCSSET malware](<https://devfeed.tech/articles/compromised-flutter-package-on-pub-dev-contains-xcsset-malware-51614.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/compromised-flutter-package-on-pub-dev-contains-xcsset-malware>)

Author: Ilyas Makari

Published: 2026-09-08T16:12:00Z

Content type: article

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [ransomware](<https://devfeed.tech/topics/ransomware.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [Dart](<https://devfeed.tech/topics/dart.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [High Profile Threats](<https://devfeed.tech/topics/high-profile-threats.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Xcode](<https://devfeed.tech/topics/xcode.md>)

Tags: [attacks](<https://devfeed.tech/tags/attacks.md>), [dart](<https://devfeed.tech/tags/dart.md>), [dev](<https://devfeed.tech/tags/dev.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [github](<https://devfeed.tech/tags/github.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [infection-chain](<https://devfeed.tech/tags/infection-chain.md>), [macos](<https://devfeed.tech/tags/macos.md>), [malware](<https://devfeed.tech/tags/malware.md>), [supply-chain-attacks](<https://devfeed.tech/tags/supply-chain-attacks.md>), [threats](<https://devfeed.tech/tags/threats.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

A compromised Flutter package published on pub.dev contained XCSSET malware. The infection originated on the maintainer's machine and affected build files in the package, while the Dart library code remained clean. The article explains that most dependency users were not affected, but locally building the example app could trigger malicious build hooks.

### Source excerpt

We detected XCSSET malware inside a compromised Flutter package on pub.dev. Here is a full breakdown of the infection chain, propagation modules, and stealer logic we found inside. Category: Vulnerabilities & Threats

## I've Been a Flutter GDE for 8 Years. Here's the Ground Truth on "Flutter is Dying"

DevFeed: [I've Been a Flutter GDE for 8 Years. Here's the Ground Truth on "Flutter is Dying"](<https://devfeed.tech/articles/i-ve-been-a-flutter-gde-for-8-years-here-s-the-ground-truth-on-flutter-is-dying-23052.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/ive-been-a-flutter-gde-for-8-years-here-s-the-ground-truth-on-flutter-is-dying-6ffc50ca4088?source=rss----86fb29d7cc6a---4>)

Author: Randal L. Schwartz

Published: 2026-08-19T16:02:19Z

Content type: opinion

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [blocsignal](<https://devfeed.tech/topics/blocsignal.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [advocacy](<https://devfeed.tech/tags/advocacy.md>), [community-engagement](<https://devfeed.tech/tags/community-engagement.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [dart](<https://devfeed.tech/tags/dart.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [gde](<https://devfeed.tech/tags/gde.md>), [google](<https://devfeed.tech/tags/google.md>), [google-developer-expert](<https://devfeed.tech/tags/google-developer-expert.md>), [impeller](<https://devfeed.tech/tags/impeller.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [native](<https://devfeed.tech/tags/native.md>), [performance](<https://devfeed.tech/tags/performance.md>), [platform](<https://devfeed.tech/tags/platform.md>), [production](<https://devfeed.tech/tags/production.md>), [programming](<https://devfeed.tech/tags/programming.md>), [roadmaps](<https://devfeed.tech/tags/roadmaps.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [state-management](<https://devfeed.tech/tags/state-management.md>)

### AI overview

The author argues that Flutter is not dying, but maturing, and attributes pessimistic headlines partly to a gap between ongoing internal engineering work and slower public advocacy at Google. The article cites renewed DevRel, production milestones, and investment in Impeller, Dart 3.x, WebAssembly, and multiplatform performance. It suggests fewer Flutter job listings may reflect enterprises consolidating existing iOS and Android teams, while junior applicants face competition from experienced native developers. It describes state management as evolving from streams and code generation toward synchronous Signals and BlocSignal. The author also cites app-store presence and platform reach as signs of adoption, though the supplied text provides no independent measurements to verify those claims.

### Source excerpt

Every few months, like clockwork, the tech blogosphere gets flooded with the same recycled headline: "Is Flutter Dying?", "Why CTOs Are Quietly Leaving Flutter", or "Why Google is Killing Its Cross-Platform Bet." As someone who has been a Flutter Google Developer Expert for eight years now -- literally from day one of the GDE program -- and a five-decade software industry veteran, I usually just chuckle at the clickbait. "Flutter is dead." -- Said every six months since 2018. Meanwhile: Flutter is kicking tail on every single measurable scale. The alarmist articles point to standard corporate reorganizations, shifting tech job boards, and "state management fatigue" as evidence of Flutter's demise. But having watched this ecosystem evolve from an experimental alpha into an enterprise powerhouse, the reality on the ground is the exact opposite. Here is the real insider story on what's actually happening with Dart and Flutter. 1. The Inside Story: What Happened at Google? When tech companies restructured engineering teams recently, the internet spun a wild narrative that "Google put Flutter on life support." Having direct access to internal teams, I watched the commitment to Dart and Flutter remain steadfast within the organization. However, there was a temporary disconnect: internal engineering activity was roaring, but external communications and public advocacy had slowed down, leaving an information vacuum that clickbait writers eagerly filled. I personally called out to team leaders and senior VPs that this perception gap needed immediate correction. And the leadership responded strongly: Revitalized DevRel & Advocacy: A renewed surge in active community engagement, tutorials, and public roadmaps. Enterprise Adoption Transparency: Showcasing massive internal and external production milestones. Aggressive Core Investment: Deep work on the Impeller rendering engine, Dart 3.x ergonomics, WebAssembly (Wasm) compilation, and native multiplatform performance. Flutter is no

## Building AI Agents in Dart with the Genkit Dart SDK

DevFeed: [Building AI Agents in Dart with the Genkit Dart SDK](<https://devfeed.tech/articles/full-stack-ai-in-dart-because-learning-python-is-for-snakes-22850.md>)

Original publisher: [Read original article](<https://medium.com/google-developer-experts/ai-in-dart-5070243b0407?source=rss----a67bd6fa7d58---4>)

Author: Abhishek Doshi

Published: 2026-08-10T23:16:05Z

Content type: tutorial

Language: en

Sources: [Google Developer Experts](<https://devfeed.tech/sources/google-developer-experts-medium.md>)

Topics: [Dart](<https://devfeed.tech/topics/dart.md>), [Genkit](<https://devfeed.tech/topics/genkit.md>), [AI Development](<https://devfeed.tech/topics/ai-development.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [Cloud Functions](<https://devfeed.tech/topics/cloud-functions.md>), [Firebase](<https://devfeed.tech/topics/firebase.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-development](<https://devfeed.tech/tags/ai-development.md>), [cloud-functions](<https://devfeed.tech/tags/cloud-functions.md>), [dart](<https://devfeed.tech/tags/dart.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [generative-ai-tools](<https://devfeed.tech/tags/generative-ai-tools.md>), [genkit](<https://devfeed.tech/tags/genkit.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

### AI overview

This tutorial introduces the Genkit Dart SDK for building AI agents natively in Dart and deploying them to Cloud Functions for Firebase. It explains agent orchestration, conversational state, history, streams, models, tools, flows, and multi-agent delegation.

### Source excerpt

Because your Flutter app deserves a brain, and you deserve to never look at a Python traceback again. Let's be honest. We all love Dart. It's clean, it's safe, and it powers our beloved Flutter. But until recently, if you wanted to build serious, multi-step AI agents, the industry basically told you to pack your bags, leave your cozy typed ecosystem, and go write Python. Gross 🤮 Thankfully, Google finally heard our collective sighs and dropped the Genkit Dart SDK. Now, you can build full-stack, hyper-intelligent AI agents natively in Dart and deploy them straight to Cloud Functions for Firebase. No context-switching. No spinning up a random Node.js microservice just to talk to an LLM. Grab your coffee (or your energy drink of choice). Let's look at how Genkit turns your Dart code into an absolute powerhouse. https://medium.com/media/91c2efa4198c043f3f400f216214650e/hrefThe Shift: From "Dumb Chatbots" to "Autonomous Overlords" Building traditional chatbots or strict multi-step UI flows often feels like playing one of those terrible, rigid video games that block you at a level until you do exactly what the developers scripted. Agentic AI, by contrast, is the ultimate open-ended sandbox. An agent doesn't just blindly answer a prompt. It analyzes what the user wants, figures out which tools it needs to achieve the goal, and dynamically orchestrates the steps to get there. With Genkit's new Agents API, all the messy plumbing: maintaining conversational state, keeping track of history, and parsing streams, is handled behind a single API. You just focus on giving it a brain. The Holy Trinity: Models, Tools, and Flows To stop your AI from just hallucinating fan-fiction, Genkit uses a few core primitives. Think of this as the toddler-proofing stage of AI development. Models (ai.generate()): The actual brain. Whether you are using Gemini, Claude, or OpenAI, the API stays exactly the same. Tools (defineTool): This is how you give your AI hands. By defining strict input schemas

## Where I'm Writing Now: The Complete 14-Part BlocSignal Series on DEV.to

DevFeed: [Where I'm Writing Now: The Complete 14-Part BlocSignal Series on DEV.to](<https://devfeed.tech/articles/where-i-m-writing-now-the-complete-14-part-blocsignal-series-on-dev-to-23055.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/where-im-writing-now-the-complete-14-part-blocsignal-series-on-dev-to-2b27b47b00c8?source=rss----86fb29d7cc6a---4>)

Author: Randal L. Schwartz

Published: 2026-08-10T16:00:59Z

Content type: opinion

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [Dart](<https://devfeed.tech/topics/dart.md>), [reactive](<https://devfeed.tech/topics/reactive.md>), [Dependency injection](<https://devfeed.tech/topics/dependency-injection.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>)

Tags: [bloc](<https://devfeed.tech/tags/bloc.md>), [blocsignal](<https://devfeed.tech/tags/blocsignal.md>), [dart](<https://devfeed.tech/tags/dart.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dev](<https://devfeed.tech/tags/dev.md>), [developer-community](<https://devfeed.tech/tags/developer-community.md>), [development](<https://devfeed.tech/tags/development.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [series](<https://devfeed.tech/tags/series.md>), [signal](<https://devfeed.tech/tags/signal.md>), [state-management](<https://devfeed.tech/tags/state-management.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [writing](<https://devfeed.tech/tags/writing.md>)

### AI overview

The author announces that DEV.to and the Google Developer Experts organization on DEV.to are now the primary publishing hubs for new technical writing. The article presents a 14-part BlocSignal series covering Dart and Flutter state management, architecture, interoperability, dependency injection, tracing, and web development.

### Source excerpt

If you've been following my articles here on Medium over the years, thank you! I wanted to share a quick update on where I'm primarily publishing my new technical deep dives, architectural guides, and Flutter/Dart tutorials. Going forward, my primary writing hub is DEV.to (@randalschwartz) and the official Google Developer Experts (GDE) organization on DEV.to. DEV.to provides a vibrant developer community, native Dart syntax highlighting, and a built-in Series feature that links connected articles into structured, multi-part curricula. 🚀 The New Series: BlocSignal Architecture & Practice Over the last month, my team and I launched BlocSignal -- a production-grade state management framework for Dart and Flutter that bridges BLoC's enterprise discipline with Signals' 0ms synchronous reactivity. We've published a comprehensive 14-part series on DEV.to covering everything from core state machine philosophy and Riverpod/Provider interop to dependency injection, OpenTelemetry tracing, and Jaspr web development. Here is the complete roadmap of all 14 articles available to read right now on DEV.to: 🏛 1. Core Architecture & Philosophy Introducing BlocSignal: Unidirectional Data Flow Meets Reactive Signals The origin story: bridging BLoC semantics with Rody Davis's signals v7 primitives for 0ms microtask queue latency. BLoC meets Signals: How to Pitch BlocSignal to Your Dev Leads How to navigate technical team reviews and explain the enterprise value of synchronous signal graphs. How We Achieved Full BLoC API & Protocol Parity in BlocSignal 0.2.0 A deep dive into BlocProvider, BlocBuilder, BlocListener, BlocConsumer, and context.select parity. Beyond ProviderNotFound: How BlocSignal Rethinks State Location and Synchronous Propagation Solving scope lookups and understanding why synchronous signal updates prevent frame tearing. From Raw Signals to BlocSignal: Taming Reactivity for Enterprise Scale How encapsulating signals inside Cubit/Bloc containers stops global signal "spagh

## GenUI Beyond Chat: Designing a Grammar Book with Flutter GenUI -- Part 1

DevFeed: [GenUI Beyond Chat: Designing a Grammar Book with Flutter GenUI -- Part 1](<https://devfeed.tech/articles/genui-beyond-chat-designing-a-grammar-book-with-flutter-genui-part-1-23051.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/genui-beyond-chat-building-a-grammar-book-with-flutter-and-caching-the-a2ui-output-with-firebase-ecab7b093ccc?source=rss----86fb29d7cc6a---4>)

Author: Cagatay Ulusoy

Published: 2026-08-03T15:15:45Z

Content type: article

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Tutorial](<https://devfeed.tech/topics/tutorial.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [a2ui](<https://devfeed.tech/topics/a2ui.md>), [Internationalization (i18n)](<https://devfeed.tech/topics/i18n.md>), [Localization (l10n)](<https://devfeed.tech/topics/localization.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [a2ui](<https://devfeed.tech/tags/a2ui.md>), [ai](<https://devfeed.tech/tags/ai.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [generative-ui](<https://devfeed.tech/tags/generative-ui.md>), [genuis](<https://devfeed.tech/tags/genuis.md>), [grammar](<https://devfeed.tech/tags/grammar.md>), [language-learning](<https://devfeed.tech/tags/language-learning.md>), [personalization](<https://devfeed.tech/tags/personalization.md>)

### AI overview

The article describes a Finnish grammar course built with Flutter GenUI, where learners browse localized curricula and move through interactive pages instead of receiving a long chat response. It separates lesson design into three parts: a curriculum and lesson briefs define what to teach, a system prompt defines how to teach it, and a catalog of registered Flutter components constrains how lessons can appear. Lessons follow Concept -> Mechanism -> Use -> Application, with components for recognition, production, and recall. The model composes A2UI messages from catalog items; Flutter owns rendering, responsiveness, theme, accessibility, and interaction behavior. The author says a roughly 40-component catalog balances pedagogical variety against repeated input-token cost, favoring distinct component roles and letting Flutter handle presentation choices such as table versus cards. Localized curriculum labels are generated from canonical English while preserving Finnish examples and stable lesson IDs. Part 1 covers the design boundaries; lesson batching and Firestore caching are deferred to Part 2.

### Source excerpt

Last year on #FlutterFlightPlans live stream, I asked the Flutter team a question that has stayed with me: Are there any use cases for Generative UI other than chat responses? Can you share some inspiration? Seth Ladd answered, "Let's see what is beyond chat together." 🚀 Since that moment, exploring GenUI beyond chat has been my primary focus. https://medium.com/media/7c53d065806a0337fcf3a8db1412ec82/href I shared my first journey with GenUI in an article series: a small GenUI framework built with Gemini structured outputs, and a migration to Flutter GenUI SDK and A2UI surfaces. Then I tried a different kind of use case: a Finnish 🇫🇮 grammar course inside my Finnish it language-learning app. In this feature, the learner browses a curriculum in their own language, opens one small grammar topic, and moves through a sequence of Flutter pages. https://medium.com/media/3ac419e10db257e4f9652bdfb9ad5165/hrefProblem Definition I had four constraints: I do not speak Finnish, and I am not a language teacher. I don't have time to manually plan and structure a grammar book's worth of micro-lessons in every language. I want interactive application UI, not a long Markdown response. Hyper-personalization is crucial. The explanation should begin from the learner's language. A Turkish learner can approach Finnish vowel harmony through Turkish vowel harmony; an English learner needs another bridge since it has no similar concept. Vowel harmony lessons in English and TurkishThe same rule does not feel equally foreign That fourth constraint is more than UI localization. Turkish speakers will find two familiar concepts in Finnish grammar: attaching grammatical markers directly to the ends of nouns, and changing suffix vowels to match the root word. For example, expressing "in" or "at" requires the exact same mental process in both languages: Turkish: ev + -de = evde (in the house) Finnish: talo + -ssa = talossa (in the house) An English speaker has a completely different starting point.

## Everything You Need to Know About Patrol in 2026

DevFeed: [Everything You Need to Know About Patrol in 2026](<https://devfeed.tech/articles/everything-you-need-to-know-about-patrol-in-2026-23049.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/everything-you-need-to-know-about-patrol-in-2026-097c09ce8a7e?source=rss----86fb29d7cc6a---4>)

Author: LeanCode

Published: 2026-07-24T02:52:52Z

Content type: article

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [UiAutomator](<https://devfeed.tech/topics/uiautomator.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [automation](<https://devfeed.tech/tags/automation.md>), [automation-testing](<https://devfeed.tech/tags/automation-testing.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [e2e](<https://devfeed.tech/tags/e2e.md>), [e2e-testing](<https://devfeed.tech/tags/e2e-testing.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [flutter-app-development](<https://devfeed.tech/tags/flutter-app-development.md>), [framework](<https://devfeed.tech/tags/framework.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [ios](<https://devfeed.tech/tags/ios.md>), [junit](<https://devfeed.tech/tags/junit.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [native](<https://devfeed.tech/tags/native.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [package](<https://devfeed.tech/tags/package.md>), [permission](<https://devfeed.tech/tags/permission.md>), [ui-testing](<https://devfeed.tech/tags/ui-testing.md>)

### AI overview

Patrol combines Flutter widget testing with native UI automation so a single end-to-end test can cover Flutter screens and elements outside the Flutter runtime, such as permission prompts, notifications, and other native UI. Its Dart tests run with Flutter testing APIs alongside native runners--XCUITest on iOS and UIAutomator on Android--which communicate over localhost. The excerpt describes Patrol 4.0 support for Android, iOS, and Web, plus a VS Code extension for running and debugging tests and Patrol MCP tools for AI-assisted test execution and inspection. Native test infrastructure enables compatibility with device farms and JUnit reporting; test bundling, sharding, parallel execution, artifact collection, and duration reporting support larger runs. The excerpt also presents Patrol Finders as a more concise alternative to Flutter's built-in finders, with waits for dynamic UI. It does not provide a full feature-by-feature account of Web support or the listed integrations.

### Source excerpt

Author: Katarzyna Szulc from LeanCode Patrol has come a long way from being "just another Flutter testing tool." Today, it powers end-to-end testing across Android, iOS, and Web, integrates with native testing infrastructure, runs on cloud device farms, offers AI-powered testing capabilities, and continues to push the boundaries of what's possible in the Flutter ecosystem. No matter if you've been following Patrol for a while or you're simply looking for the best way to handle Flutter E2E testing, this article is the perfect place to catch up. What exactly is Patrol? Let's break it down Developed by LeanCode, Patrol is a powerful, open-source, multiplatform E2E UI testing framework for Flutter apps that overcomes the limitations of integration_test by handling native interactions. Let's dig deeper into that. Flutter's greatest strength also creates one of its biggest testing challenges. Unlike native apps, Flutter renders its entire UI using its own graphics engine instead of platform-native components. This enables a consistent, pixel-perfect experience across devices, but it also means that native UI automation tools often see a Flutter app as little more than a single canvas. They simply cannot interact with Flutter widgets. The official solution is the integration_test package, which gives tests direct access to the Flutter widget tree. As long as everything happens inside Flutter, it works well. But real apps rarely stay there. System permission dialogs, biometric prompts, notifications, WebViews, and other native UI all exist outside the Flutter runtime, making them inaccessible to integration_test. Patrol bridges this gap. It lets tests interact with both Flutter widgets and native UI elements in a single test. Because Patrol builds on native frameworks such as JUnit and XCTest, it also integrates seamlessly with existing CI pipelines, device farms, and the broader mobile testing ecosystem. If you are new to automating E2E testing in Flutter, you can start by

[Next page](<https://devfeed.tech/topics/flutter.md?cursor=WyIyMDI2LTA3LTI0VDAyOjUyOjUyKzAwOjAwIiwgIjExNWQ4MmU2LTQwZjItNGVkZS05NmIyLWU5MDQxMTZkNmU5OSJd>)