r/FlutterDev • • 5m ago

Video 8 New Games Made In Flutter

Thumbnail
youtu.be
1 Upvotes

These are new games and projects made in Fluttter either using Flutter Scene & Flame. For anyone looking for inspiration in Flutter's gamedev scene - this could be of good use


r/FlutterDev • • 5h ago

Discussion How come Flutter isn't in the conversation?

25 Upvotes

So I've just started learning dart and flutter and I'm shocked that you can have one codebase that does IOS, android, desktop applications for any OS and even Flutter web. Yet Flutter rarely seems to be in the conversation about building cross-platform apps?

Usually what I see online is people arguing about what's better between electron, react-native, Rust GPUI and even some people mentioning Kotlin multiplatform, but rarely ever Flutter? Why is this, or am I just in a bubble.


r/FlutterDev • • 5h ago

Tooling 4 AI testers on LocalSend found overflow bugs on 3 of 4 devices

0 Upvotes

Each tester is a Claude Code agent with its own Android emulator or iOS Simulator on GitHub Actions, playing a persona (device, language, text size, dark mode).

Worst find: on an iPhone SE at iOS’s largest text size, the “type a message” dialog overflows by 149 px, so you can’t type or confirm at all. At Android’s 200% font, all six Send buttons overflow.

103 issues, 69 min, $4.62 of model usage. Video of the 20 phones and the code (open source): https://github.com/pierridotite/mobile-agent-testers


r/FlutterDev • • 8h ago

Discussion Anyone else still landing on Impeller OpenGLES and now seeing why?

5 Upvotes

Impeller is the default on Android API 29+, and it prefers Vulkan then falls back to OpenGLES when Vulkan is unavailable or denylisted. Until recently, a profile/release log often only showed the banner:

Using the Impeller rendering backend (OpenGLES).

with no reason line for several common gates.

flutter/flutter#194764 (merged 2026-11-02) adds explicit fallback logs (INFO; visible with --verbose-system-logs) for branches that used to be silent or under-explained, including:

  • emulator
  • Huawei device property check
  • MediaTek vendor API level below 32
  • known bad SoC
  • Vulkan context / device selection / known-bad driver failures

On a moto g54 5G (MediaTek MT6855), the PR author saw the MediaTek vendor-SDK gate fire as the reason for OpenGLES, which matches earlier reports like #193148.

Docs still say: Impeller default on API 29+; lower Android or no Vulkan → OpenGL path with no app-side action required: https://docs.flutter.dev/perf/impeller

PR: https://github.com/flutter/flutter/pull/194764

Questions for people shipping Flutter on mid-range Android:

  1. On devices where you already see OpenGLES Impeller, does --verbose-system-logs now name a concrete gate (MediaTek vendor SDK, SoC denylist, driver dump, etc.)?
  2. Have you hit the MediaTek ro.vendor.mediatek.platform / vendor API < 32 path on shipping devices, or is that mostly a few SKUs?
  3. For triage: is INFO + --verbose-system-logs enough, or do you still wish the reason sat next to the IMPORTANT backend banner without the flag?

Not asking anyone to force Vulkan — just curious what the new reason lines look like in the wild.


r/FlutterDev • • 8h ago

Tooling Qora 1.4 is out: offline mutations now survive app restarts

Thumbnail qora.meragix.dev
2 Upvotes

A couple of weeks ago, I posted here asking how people handle offline mutations. I got some really useful answers from developers who had already dealt with this in production.

I've spent the last couple of weeks working through that feedback, and Qora 1.4.0 is now out.

For context, Qora is my server-state library for Flutter, with a pure Dart core and no code generation.

The main issue in 1.3 was simple: offline writes were kept in memory. If the OS killed the app before it came back online, those writes were gone.

I couldn't just persist the queue as it was, since mutations are closures. So I changed the queue to store data instead.

What's changed in 1.4:

  • Persistent mutations: Register a mutation once using a key and a serializer. The queue stores the key and variables, so it can restore the mutation after a restart.
  • Persist before queuing: A mutation only counts as queued once the storage write succeeds. If it fails, the mutation fails immediately.
  • Idempotency: Every mutation gets a stable mutationId. It's kept across retries and restarts, so the app can pass it to the server as an idempotency key. Delivery is still at-least-once, so server-side deduplication is needed.
  • Mutation scopes: Mutations with the same scope run in order, while different scopes can run in parallel. This means one failed record doesn't block unrelated writes.
  • Retry handling: Network errors and 5xx responses are retried with backoff. Each registered mutation also provides an isPermanent callback, since Qora doesn't deal with HTTP status codes directly.
  • Blocked mutations: When a mutation permanently fails, the rest of its scope waits. The app can let the user fix and retry it, or discard it.
  • Retry or edit: Retrying with the same payload keeps the original ID. If the variables change, Qora creates a new ID but keeps the mutation in the same queue position.
  • UI support: MutationQueueBuilder and useMutationQueue() expose pending, blocked and failed mutations, so the app can display sync status.

Here's a small example:

client.registerMutation<Todo, TodoInput>(
  'todos.save',
  mutator: (input, meta) => api.saveTodo(
    input,
    idempotencyKey: meta.mutationId,
  ),
  variables: todoInputSerializer,
  scope: (input) => 'todo:${input.id}',
  isPermanent: (error) => error is ApiException && error.statusCode < 500,
);

// At the call site, just the key is needed.
const MutationOptions<Todo, TodoInput, void>(
  mutationKey: 'todos.save',
  offlineQueue: true,
);

Some things I deliberately left out:

  • Placeholder IDs and automatic replacement with server IDs. Client-generated IDs with create-as-upsert cover the common case for now.
  • Automatic merging of edits. Qora can't safely merge arbitrary mutation variables.
  • Built-in storage adapters. The core stays pure Dart, and you can plug in Hive, SharedPreferences or SQLite through StorageAdapter.

The offline-first example has also been updated. It includes a todo app with an offline toggle, simulated restarts, a sync panel and a server that rejects some writes.

I also added widget tests for mutations surviving restarts, requests interrupted while in flight, and failed mutations being discarded.

A few people from the original discussion deserve a mention:

  • u/MentalAd1373 for the ideas around blocked mutations, storage guarantees and retrying edited writes.
  • u/MobileXapps for the idempotency and at-least-once delivery points.
  • u/bramantec for the per-record ordering and error handling suggestions.

A lot of what went into this release came directly from those discussions, so thanks again.

Links:

If you've built something similar, I'd still be interested in hearing about edge cases I might have missed.


r/FlutterDev • • 12h ago

Dart I built a coding orchestrator in Dart that works with open weight models and has a Flutter app that connects via Wifi

Thumbnail github.com
3 Upvotes

Hey community!

I built a coding orchestrator over the past few weeks, at first I wanted to build just an orchestrator for my own work but then I realized one thing, that when my Claude Code usage expires I need to fallback to something :D

So I created Term. The small funny thing about it is that it has a mascot that reacts to the status of the work you're doing.

You can do drag and drop for split screen. You can use /orchestrate and then the harness will divide the tasks on its own and delegate to sub agents.

It also has a safe mode which is a sandbox that you can use along with a local model and Docker to ensure that your model is cut off from the internet and only edits files in the current directory

You can take a complete look at the features of this harness here: https://github.com/Coffiie/agent_harness_in_dart

And yes as always, please don't shy away from giving me feedback! :) It's open source and MIT.


r/FlutterDev • • 14h ago

Article Vynody 3 is now released, and the app has been significantly improved compared to the version released several months ago.

1 Upvotes

https://github.com/axel10/vynody

Vynody is a cross-platform music player developed using Flutter, boasting extremely fast media library scanning speed and powerful cross-platform collaboration capabilities. When I last introduced Vynody here, it was still a prototype project. After several months of refinement, Vynody has seen significant improvements in performance, UI consistency, and feature completeness.

Vynody 3 adds support for Jellyfin, Navidrome, SMB, and WebDAV compared to version 1.x, as well as gesture-driven scalable list/grid items and a cooler new dynamic streaming playback page background. In terms of performance, Vynody 3 has undergone deep optimization in media library scanning speed, GPU usage during playback, and UI smoothness. Large media library scans that took several minutes in Vynody 1.x only take a few seconds in Vynody 3. List and animation stuttering issues that occurred on low-performance Android devices have also been greatly improved in version 3.x, achieving 60FPS playback even with complex UI animation changes.

If you need a music player that can sync lyrics and playlists across platforms, doesn't require account login, respects privacy and security, is stable and smooth, and allows you to focus on listening to music without worrying about other things, Vynody is definitely worth a try.


r/FlutterDev • • 17h ago

Tooling [open-source] After moving plugins to SwiftPM, my Mac had gigabytes of duplicate iOS packages across apps, so I made a Puro-style global store for SwiftPM

8 Upvotes

Since Flutter started moving iOS/macOS plugins from CocoaPods to Swift Package Manager, I noticed my disk space disappearing whenever I worked across multiple Flutter apps or Git worktrees.

Even if you use Puro or FVM to deduplicate Flutter and Pub caches, Xcode and Flutter still create an isolated SourcePackages folder for every project and worktree. I ended up with several copies of heavy native iOS SDKs (like Firebase) duplicated across DerivedData and build/.

I built a small open-source tool called spmx to solve this on my machine, and figured it might help others here too.

It works similarly to Puro/pnpm: it keeps one global store at ~/.spmx/store and uses lightweight PATH shims for flutter, xcodebuild, and swift (it plays nicely with Puro and FVM). Before a build, it clones the matching Swift package versions into your project using macOS APFS clonefile() (copy-on-write), so it takes milliseconds and uses zero extra physical disk space.

You can also run spmx link and it will scan your existing projects, show how many GB of duplicate SwiftPM packages you have, and replace them with APFS clones after you confirm.

It's macOS 13+ (APFS) only and only covers SwiftPM (not legacy ios/Pods).

Hope it saves someone else a few dozen GBs! Let me know if you hit any issues with your setup.


r/FlutterDev • • 19h ago

Discussion I built a Flutter app for exploring Morocco and finding local activities

0 Upvotes

Hey everyone! I’m a software engineering student from Morocco. For my final-year project, I built an app around a question I often have when planning a trip: once I’ve picked a place to visit, what can I actually do there?

The app lets travelers explore destinations on a map, read reviews, and sign up for activities listed by organizers. Travelers can also share their own posts and leave a review after visiting a place.

I built the mobile app with Flutter and the API with Laravel. Both are in the repo, along with setup instructions if you’d like to run it locally.

Check out the project on GitHub

If you were planning a weekend trip in Morocco, what would you want to know about a local activity before signing up?


r/FlutterDev • • 1d ago

Plugin Anyone migrating plugins to Pigeon's native interop (FFI/JNI) yet?

13 Upvotes

Flutter's stable-native-interop post landed last week, and I'm curious how plugin maintainers are approaching it in real codebases.

What's actually stable now

  • FFIgen for C and Objective-C
  • JNIgen for Java/Kotlin (Android system APIs + your AARs/JARs)

What's preview

  • Pigeon with native interop (swiftOptions: SwiftOptions(useFfi: true), kotlinOptions: KotlinOptions(useJni: true))
  • Skips the platform-channel serialization path; synchronous calls + background isolates become realistic

Docs point to shared_preferences as a reference migration — migration guide + an AI-oriented "native interop migration skill" for agents.

Questions for the room

  1. Are you starting new plugins on Pigeon+interop, or only migrating hot paths?
  2. Windows/Linux still channel-based — does that split your public API design?
  3. What broke for you? (build hooks, app directory for JNIgen, object lifetimes?)

I'm especially interested in plugins that were already Pigeon-clean — was the move "flip flags + rebuild" or a week of yak shaving?

Links:


r/FlutterDev • • 1d ago

Tooling I rebuilt iOS 26's Liquid Glass widgets in Flutter and measured each one against UIKit (Liquidum 1.0)

Thumbnail
github.com
39 Upvotes

Liquidum is my Flutter package for iOS 26's Liquid Glass. A month ago it was only a glass tab bar. Version 1.0 is out now and has the rest of UIKit's glass: glass behind any widget, groups of glass that melt together, buttons, the switch, slider and segmented control, navigation bars and toolbars, pull-down, context and edit menus, the date picker, sheets, alerts, action sheets and popovers.
I rebuilt each widget from the layers, filters and springs UIKit itself uses, read in the iOS 26.5 simulator. Then I compared it with UIKit's version over the same backgrounds and touches, frame by frame, before starting the next one.
Every comparison is in the repo with its method and what still differs. Some numbers: at rest the tab bar is about one level out of 255 away from UIKit's, sheet detents are within 0.05pt, and the alert matches UIKit's except for the clock in the status bar.
On Android, flinging a page with a dozen glass buttons and controls used to drop two thirds of its frames. Now it drops 2%, because all the glass shares its reads of the screen instead of each piece reading it on its own. It also needs Flutter 3.47 or later. That release stopped storing OpenGL ES textures flipped, so on that backend the old code drew everything behind the glass upside down.
Rough edges and limits:
Impeller only. Skia and web get plain frosted glass with no refraction.
Glass has to be painted after what it floats over, and can't go inside an Opacity or ShaderMask.
Flutter doesn't report Reduce Transparency, so you pass it in yourself.
Light that follows the device's tilt isn't done yet.
The API is stable now and follows semver, and the license is MIT. To see it move, run the showcase in the example folder (flutter run -t lib/showcase.dart) in profile or release mode. Debug builds are much slower.
flutter pub add liquidum
GitHub: https://github.com/mohamedalsamrai/liquidum
pub.dev: https://pub.dev/packages/liquidum


r/FlutterDev • • 1d ago

Article One Flutter codebase for web, iOS and Android with RevenueCat: what actually cost me time (paywall gating, per-platform voice, release plumbing)

2 Upvotes

I shipped a journaling app from a single Flutter codebase (web, iOS, Android) with Riverpod, GoRouter, RevenueCat, and a Python backend. I went through my git history to find where the time actually went. The top three:

1. Paywall gating is a state problem, not a screen

  • I used a launch-funnel package (onboarding → paywall → login → home). Its default paywall step completes when the user dismisses it, so closing the paywall let you in. I wrote my own wall that only calls onUnlocked when the user is actually entitled.
  • The funnel persists step flags forever, so "paywall completed" doesn't mean "subscribed" (expiry, refund, different account). I added a live guard: signed out → login; signed in but not entitled → paywall. The router redirects everything except /, /login and /register.
  • Web has no store purchases, so web skips the paywall but still requires login.
  • RevenueCat has to be logged in and out in step with Firebase auth, or anonymous and real users' entitlements drift apart.
  • I later made the paywall skippable ("continue with free version") behind one flag. The gate logic reads that flag in three places, so centralize it early.
  • Widget tests with a paywall on screen needed bounded pump()s instead of pumpAndSettle.

2. Voice dictation is three different problems

  • On-device speech_to_text on iOS: permission_handler needs compile-time flags in the Podfile (PERMISSION_MICROPHONE=1, PERMISSION_SPEECH_RECOGNIZER=1), or the permissions don't work.
  • Initializing the recognizer eagerly fired the iOS system dialog before my own explanation dialog. I made it lazy.
  • Apple review also made me rework the permission flow.
  • I eventually moved to server-side Whisper. That means recording to a file path on mobile but a blob: URL on web, which I handled with conditional imports (io / mobile / web / stub). I extracted it into a shared package.

3. Release plumbing

  • iOS CI signing: with CODE_SIGN_STYLE=Manual and no explicit identity, xcodebuild fell back to the iPhone Developer alias from the pbxproj. That doesn't match modern "Apple Development" certs. I read the identity from the keychain instead.
  • PlistBuddy can't read /dev/stdin, so decode the provisioning profile to a file first.
  • altool needs the .p8 on disk, not just the key ID.
  • A leftover get-task-allow entitlement had to go for distribution builds.
  • Android: Flutter 3.47 forced AGP 8.11.1 and Kotlin 2.2.20. Later bumps needed AGP 9.1.1, and one plugin needed compileSdk 37.
  • Moving between flutter/material and material_ui gave me two incompatible ThemeData types, which I patched with a bridge file.

Happy to go deeper on any of these in the comments.

Disclosure: it's my own project (PsychDiary). If you want to try the flows and tell me what you think, DM me and I'll send the link.


r/FlutterDev • • 1d ago

Plugin I built iOS-style swipe-to-dismiss keyboard for Flutter, on iOS and Android (open source)

15 Upvotes

Flutter has no interactive keyboard dismiss, where the keyboard follows your finger as you swipe a chat down. flutter/flutter#57609 has been open since 2020, and React Native has react-native-keyboard-controller. So I built keyboard_controller.

GIFs: https://github.com/ArefMozafari/keyboard_controller

  • Swipe the list down and the keyboard follows your finger. Let go low and it hides; let go high and it springs back. iOS 15+ and Android 11+, public APIs only.
  • A chat list that stays put while the keyboard moves, with an input bar that rides the keyboard.
  • Four lift modes named after apps: Telegram, ChatGPT, Claude, Perplexity.
  • AI chat behaviors: it follows a streaming answer, pins the sent prompt to the top while the answer grows, and has a jump-to-latest signal.

How it works: on iOS a hidden UIScrollView with .interactive dismiss lends its pan to the Flutter view, and keyboardLayoutGuide reports the keyboard position during the drag. On Android it drives WindowInsetsAnimationController.

pub.dev: https://pub.dev/packages/keyboard_controller

Feedback welcome.


r/FlutterDev • • 1d ago

Tooling I built free AI beta testers for mobile apps: one Claude Code agent per phone

Thumbnail
github.com
7 Upvotes

I build a mobile app alone and never had enough beta testers, so I made agents that do it. Each one gets its own iOS Simulator or Android emulator on free GitHub runners, plays a persona and writes a bug report with screenshots.

On a demo app with 11 planted bugs, 4 agents found 9 in 21 min for $0.87.


r/FlutterDev • • 1d ago

Plugin AnimationController ignores Reduce Motion on purpose. still handles it for you.

0 Upvotes

still - pubdev

*** en-US ***
Flutter already knows when someone turns on Reduce Motion or Remove Animations. It stores that choice, and stops there.

AnimationController ignores Reduce Motion on purpose. The framework’s idea is to swap the slide for a fade, but that decision is left to each widget. In practice, almost nobody does it, so the card still slides in from the bottom for people who asked for motion to stop.

I published still to solve this in one place. A MotionScope around your app decides: slide, fade, or cut. StillSwitcher, StillEntrance, StillStagger, and StillPageRoute follow that decision. Wherever you don’t use one of these widgets, nothing moves.

The package doesn’t import Material, so the same code works in a custom design system and will keep working when Material leaves the SDK.

📦 https://pub.dev/packages/still
💻 https://github.com/pedrinnhooo/still-pubdev

*** pt-BR ***
O Flutter já sabe quando alguém ativa “Reduzir movimento” ou “Remover animações”. Ele guarda essa escolha e para por aí.

O AnimationController ignora “Reduzir movimento” de propósito. A ideia do framework é trocar o slide por um fade, mas essa decisão fica a cargo de cada widget. Na prática, quase ninguém faz, e o card continua entrando de baixo para quem pediu para o movimento parar.

Publiquei o still para resolver isso em um lugar só. Um MotionScope em volta do app decide: slide, fade ou corte. StillSwitcher, StillEntrance, StillStagger e StillPageRoute seguem essa decisão. Onde você não usa um desses widgets, nada se mexe.

O pacote não importa o Material. O mesmo código funciona em um design system próprio e continua valendo quando o Material sair do SDK.

📦 https://pub.dev/packages/still
💻 https://github.com/pedrinnhooo/still-pubdev


r/FlutterDev • • 2d ago

Discussion Ran my own flutter starter kit against a 19 point launch checklist. 9 passed, 5 half done, 5 missing

0 Upvotes

So i've been building a flutter + supabase starter kit since august (auth, ai chat, paywall, the usual stuff). Honestly thought it was pretty much launch ready. Then i saw a launch checklist going around with 19 things every app should have before going live and figured ok, let's be honest and check mine.

passed (9)

* login

* logout

* password reset

* email confirmation

* loading states + empty states

* rate limiting

* RLS on every table

* no api keys in the frontend

* mobile layout

half done (5)

* error messages. Some still fall back to a raw `Error: $e` which is not exactly user friendly lol

* form validation. No email format check yet

* db backups. Supabase only does automatic backups on paid plans and i never mentioned that anywhere in the readme

* privacy policy. Only exists as a note in the readme, no link inside the app

* terms of service. Same story, readme only

missing (5)

* delete account. Apple requires this so it's basically a must

* 404 page (no errorBuilder in go_router yet)

* analytics

* error tracking

* onboarding

So 9/19, not as launch ready as i thought. Delete account is next since that one can actually get you rejected from the app store.

Curious what you guys would tackle after that. And what do you use for error tracking in flutter, sentry or something else?


r/FlutterDev • • 2d ago

Dart Relic 2 - A Dart web server that's not just 6x faster than Dart Shelf, it also beats all other popular web servers - regardless of language

Thumbnail
serverpod.dev
51 Upvotes

r/FlutterDev • • 2d ago

Plugin I removed the filter-callback boilerplate from my searchable list package (searchable_listview 2.20.0)

6 Upvotes

Hi everyone, I’m the maintainer of searchable_listview, a package for adding a search field on top of a list. I’ve been maintaining it for a few years, and the thing that always bothered me was that every list needed the same hand-written filter callback:

Old version

SearchableList<Actor>(
  initialList: actors,
  itemBuilder: (actor) => ActorItem(actor: actor),
  filter: (q) => actors
      .where((a) => a.name.toLowerCase().startsWith(q.toLowerCase()))
      .toList(),
)

In 2.20.0 you can just say which fields to search:

SearchableList<Actor>(
  initialList: actors,
  itemBuilder: (actor) => ActorItem(actor: actor),
  searchableFields: (a) => [a.name, a.lastName],
  searchStrategy: SearchStrategy.contain,
)

What’s new

  • searchableFields: pick one or several fields, and an item stays if any of them matches (case-insensitive, compared by toString()).
  • searchStrategy: startsWith (default), endsWith or contain.
  • SearchableListController: filter(), clear(), scrollToTop(), scrollTo(offset), and updateSearchStrategy() to change the strategy at runtime.
  • The controller is a ValueNotifier, so you can listen to the query, the filtered results and the status (idle, loading, data, empty, error), for example to show a live result count.
  • Fixed the InputDecoration build error on Flutter 3.47 after the material_ui split.

The filter callback is still there (but became optional) if you need custom logic when filtering. It works on all four constructors: default, .async, .expansion and .sliver.

One thing to know: 2.20.0 requires Dart 3.10+ and Flutter 3.38+. Projects on older SDKs keep resolving 2.19.5.

pub.dev: https://pub.dev/packages/searchable_listview
GitHub: https://github.com/koukibadr/Searchable-Listview
Changelog: https://pub.dev/packages/searchable_listview/changelog


r/FlutterDev • • 2d ago

Discussion PSA for anyone using sign_in_with_apple: first-time sign-ins are failing with HTTP 503 for US users (Apple's server, not your code)

18 Upvotes

My app is built with Flutter and uses the sign_in_with_apple package (8.2.0) with Supabase Auth. If your Flutter app's Apple sign-in suddenly fails for new users in the US and the plugin just throws an authorization error with no useful detail, this is probably why. Nothing in the plugin or in your Dart code is at fault.

What I saw

- First-time Sign in with Apple failed for 3 different Apple Accounts on 3 iPhones in Boston. About 20 attempts, 1 success.

- It failed on Wi-Fi and on cellular, with Hide My Email and with Share My Email.

- The same flow worked every time for testers in India, 4 out of 4.

- Returning users, who had already signed in before, were fine.

- One of the failing phones also failed in a completely different app from another developer.

What the device log shows

I had a tester plug a failing iPhone into a Mac, open Console, and filter on the akd process. The sign-in request goes out correctly, and Apple's server answers 503, twice:

akd  Performing SRP request with context
akd  Task <…> received response, status 503
akd  AppleIDAuthSupport: setError: 6:Failed to get response from server
akd  SRP authentication with server failed! Error Domain=com.apple.AppleIDAuthSupport Code=6

So the phone was connected the whole time. "Could Not Connect" is misleading. Apple's server returned "service unavailable".

What I ruled out, so you do not have to

  • The entitlement is in the signed app and in the provisioning profile.
  • The App ID has Sign in with Apple enabled as a primary App ID.
  • Nothing pending in App Store Connect or the developer portal that explains it.
  • The app never receives a credential, so it is not your auth backend or nonce handling.

How to check if this is your problem

  1. Plug the failing iPhone into a Mac and open Console.
  2. Select the iPhone, enable Info and Debug messages in the Action menu, and start streaming.
  3. Reproduce the failure, pause, and search for akd.
  4. Look for status 503 right after Performing SRP request.

What I am doing about it

  • Filed a Feedback Assistant report with the log.
  • Keeping email sign-in available so people are not locked out.
  • Adding a line to my App Review notes explaining it, so a reviewer who hits it knows it is the service.

If you are seeing the same thing, please file your own Feedback report with a log. Has anyone seen this outside the US, or seen it clear up?


r/FlutterDev • • 2d ago

Tooling I built a shader debugger for Flutter pick a variable in your .frag and see it as a heatmap in the running app

Thumbnail
github.com
6 Upvotes

Debugging a Flutter fragment shader usually means copying a value into fragColor, hot reloading, and guessing from the colors.

Other platforms have Xcode's shader debugger and RenderDoc. I built something like that for FragmentProgram shaders, as a DevTools extension.

You open your .frag in the Shader Debugger tab, click a line and pick a variable, and the running app draws that value instead of the shader's output. Scalars go through a viridis colormap and vectors show as RG or RGB. For matrices, arrays and structs you pick a column, element or field.

There's also a select mode like the widget inspector's. Click a pixel in the app (or tap it on a phone) and you get the exact value there as 32-bit floats. Every float uniform also gets sliders, so you can override uniforms while the app runs, and the heatmap and pixel reads use your overrides too.

Under the hood, the extension parses your shader with a GLSL analyzer written in pure Dart, generates an instrumented copy that writes the picked value out, saves it as a probe .frag and hot reloads. In the app you draw through DebugShader instead of FragmentShader. It swaps the probe in and copies your uniforms onto it on every paint. Your own .frag is never touched, and in profile and release builds DebugShader just draws your shader. (The analyzer is its own package, shader_debugger_core, if you want to build other shader tools on it.)

Setup: add the package, register a placeholder probe shader under flutter: shaders: in pubspec.yaml, then:

final shader = await DebugShader.fromAsset('shaders/my_effect.frag');
final size = shader.getUniformVec2('uSize');

// in paint(): set the uniforms first, then read shader.shader
size.set(width, height);
canvas.drawRect(rect, Paint()..shader = shader.shader);

It needs Flutter 3.47+. Uniforms are set by name (getUniformFloat, getUniformVec2, ...) because the probe adds uniforms of its own and values get copied over by name.

What's rough right now:

  • A value inside a loop, or in a function called more than once, shows its last write.
  • dFdx, dFdy and fwidth come out as 0 in pixel reads.
  • ImageFilter.shader and BackdropFilter shaders aren't supported.
  • Heatmaps and pixel reads don't work yet on shaders that #include their own .glsl files.
  • Launch the app from VS Code or Android Studio. DevTools can only write the probe file inside the IDE's workspace. Otherwise the tab gives you the probe to paste by hand.

Repo: https://github.com/mohamedalsamrai/shader_debugger pub.dev: https://pub.dev/packages/shader_debugger


r/FlutterDev • • 2d ago

Discussion Case Study: How I cut Flutter Web (--wasm) cold start on Slow 4G from 20s+ down to ~3-4s (fonts, Firebase WebChannel & Brotli)

57 Upvotes

I recently shipped an offline-first PWA built with Flutter Web (--wasm), and my initial GA4 metrics were brutal: mobile users on 3G/Slow 4G were bouncing at 0–2s engagement because the cold start was taking over 20 seconds (pushing ~6.1 MB over the wire / ~15.7 MB uncompressed).

After profiling the waterfall in Chrome DevTools, I found four major bottlenecks that were choking initial load - and fixing them completely changed our retention:

1. The google_fonts runtime trap (-90% font payload)

Even if you bundle fonts, google_fonts was making blocking runtime HTTP calls to fonts.gstatic.com (main.dart.mjs fetching >1.1 MB of .ttf files before rendering text).

  • Fix: Stripped google_fonts runtime fetching completely, converted Inter & JetBrains Mono to subsetted .woff2 files (116 KB total in assets/fonts/), declared them directly in pubspec.yaml, and added <link rel="preload" as="font" type="font/woff2" crossorigin> in index.html.

2. Synchronous Firebase & Firestore WebChannel blocking main()

Initializing FirebaseAuth and FirebaseFirestore in main() was loading heavy JS pipelines and holding open a channel?gsessionid=... WebChannel socket for 13+ seconds on bad connections.

  • Fix: Made cloud services 100% lazy on kIsWeb. The app mounts straight from localStorage (<1 ms), and Firebase.initializeApp() is only triggered on-demand if a user explicitly taps Sync or Sign In.

3. Explicit Wasm MIME types, Brotli & COOP**/**COEP headers

main.dart.wasm (1.7 MB) and skwasm.wasm (1.2 MB) are heavy by nature. Without explicit headers in firebase.json, streaming compilation and multithreading weren't kicking in properly.

  • Fix: Configured Content-Type: application/wasm, Cache-Control: public, max-age=31536000, immutable, and Cross-Origin-Opener-Policy: same-origin / Cross-Origin-Embedder-Policy: credentialless for skwasm, ensuring full Brotli (br) compression from edge nodes.

4. Zero-JS GPU Splash & Value-First Routing

  • Added an inline HTML/CSS loader in index.html animated strictly via transform and opacity (compositor thread) so it never freezes while the main thread compiles Wasm, fading out via onEntrypointLoaded.
  • Bypassed our /onboarding route on kIsWeb so incoming mobile traffic lands directly in the main workspace (/hub), where average session time jumped to ~7 minutes once the load bottleneck was gone.

If anyone wants to inspect the network waterfall or test skwasm cold-start behavior in DevTools, the live production build is up athttps://app.meniska.app(it's a wet-lab dilution & buffer calculator I built for myself).

Curious how other Flutter Web devs are handling initial Wasm bundle size right now - has anyone managed to shave skwasm.wasm down further, or are you still sticking to canvaskit / auto for mobile web?


r/FlutterDev • • 3d ago

Tooling intelij idea - buttons debug, stop lag badly

2 Upvotes

After updating IntelliJ Ultimate the Flutter plugin and all my SDK settings were gone.
Reinstalled and set it up again (Flutter 3.50), but now debug is painfully slow: the app sits paused ~20s before main() runs, I get "DevTools startup failure" (timeout) every time, and after quitting the app the stop button stays red for minutes. `flutter run` from the terminal is fine. Anyone seen this or know a fix?
I prefer not switch do vscode


r/FlutterDev • • 3d ago

Plugin Fliin — copy-paste Flutter UI that updates without losing your edits

Thumbnail
youtu.be
6 Upvotes

The copy-paste model (shadcn/ui style) is great until upstream ships a fix and you've already edited the files. So I built Fliin for Flutter.

dart pub global activate fliin
fliin add checkout
edit anything
fliin update checkout

update does a 3-way merge (diff3) between what you were given, what you have now, and the new version. A real conflict goes into a .fliin-new file next to yours, so your build never breaks.

A few choices:
- widgets only, no Material or Cupertino, RTL by construction
- fliin theme --primary "#0A6CFF" solves for WCAG AA on every text/background pair
- fliin verify renders each item on 16 variants (platform × theme × text scale × RTL) in a plain flutter test
- fliin mcp lets your agent search and install items
It shipped last week, and I'd love input from people who build Flutter apps every day. What slows you down on UI that a tool like this should fix?