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 • • 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 • • 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 • • 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 • • 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.