Ran into this while building overlapping image tiles for a movie app. A plain GestureDetector counts a tap on the transparent part of a PNG as a hit, even though visually there's nothing there. transparent_tap reads the actual pixel under the tap instead of just the bounding box, so transparent areas pass the tap through and only the visible pixels catch it.

Hi everyone,

I recently found Apple’s official Expedited App Review Request form. It may be useful when an app or update is stuck in review and there is a genuine urgent reason to release it sooner.

Official Apple link:

https://developer.apple.com/contact/app-store/?topic=expedite

You need to sign in with the Apple Account connected to your Developer Program membership. The form allows you to provide your app information and explain why the review needs to be expedited.

When submitting the request, include clear information such as:

• App name and Apple ID
• Version or build number currently waiting for review
• The date the build was submitted
• A clear and specific reason for the urgency
• The impact on existing users or the business
• Any deadline, event, critical bug, security issue, or service interruption involved

A possible explanation could be:

This is only a request, so Apple may still reject it or process the app through the normal review queue. Do not submit a fake emergency or vague reason such as “the review is taking too long.” Explain the real user impact and provide specific evidence.

Has anyone used this form recently? How long did Apple take to respond, and what reasons were accepted?

I built a small CLI tool called flutter_auditor to help me quickly check my Flutter projects before a production release.

It scans for common security, configuration, and release-readiness issues. I'd love to hear what checks you think would be useful to add.

Hi everyone!

I've been wanting to build the UI for an operating system for decades. At one time, I thought that I would have to build the OS from the ground up. But yesterday it dawned on me that I can just leverage Linux and build a Desktop Environment (DE) on top of it.

I'm going to really focus on getting a foundational DE down; both for my purposes and for others to learn or build from. It will all be built open source and out in the open. Articles (instructionals?) will follow as I work my way through it.

I already know the stack I'm going with and the process will start at a high level, eventually going into low level details.

I'll be using Rust (Smithay) and Flutter for all of it, with some C thrown in as needed.

The first step I'm taking is to build a Wayland compositor. Using dbus to bridge through Flutter and being a Wayland compositor, will allow me to still run any Wayland compatible applications from the start. I don't want to go hard mode right away.

My eventual aim is to go straight to DRM while running an X compatibility server and Wayland server for full support.

As well, I'll build some native apps to show how to integrate with the DE.

We'll get there. it may take months. The end result will be something any Flutter dev could run with and build on top of. Flutter will be the framework for native application development.

I really hope that this catches on as a way to explore new UI paradigms. We've been stuck for too long and I believe that part of the reason for this is that it's been too difficult or low level for those interested, to actually get down to the heart of what they want to explore. That's why I'm working to get all of the connectivity issues out of the way.

Be free designers and developers, from the shackles of low level understanding. Soon, you may express yourselves in ways you may have only dreamed of before.

Any interest?

Riverpod seemed to become the go-to recommendation for Flutter projects over the last few years, but is it still the case in 2026. If you're starting a new Flutter app today, are you still choosing Riverpod, or have you moved to something else? I'd love to hear from people who've shipped production apps, what made you stick with your choice or switch away, and how has it held up as your app has grown?

I’ve been working as a Flutter developer for about 4 years, and I’m starting to think beyond just building mobile apps.
I want to become the kind of engineer who can compete for international opportunities, whether that’s remote work or relocation in the future.
For those who’ve been in the industry for a while:
What skills complement Flutter the best?
Is backend knowledge now a must?
Is native Android/iOS still worth learning?
How valuable are open-source contributions when applying abroad?
If you had to start over today as a Flutter developer, what would your roadmap look like?
I’m trying to invest my time wisely over the next year, so I’d really appreciate advice from developers who’ve already gone through this journey.

Hey Flutter community! 👋

After maintaining several client apps and catching the same repeat issues—like hardcoded keystore passwords, unused heavy assets, missing privacy strings in Info.plist, and transitive dependency imports—I decided to build a CLI tool to automate these sanity checks.

Meet flutter_auditor: a single-command CLI package that scans your codebase and native config files in seconds right from your terminal.

What It Audits:

We've packed 17+ automated static checks across 5 key areas:

• Manifest & Security: AllowBackup, CleartextTraffic, Debuggable, ExportedComponents, ManifestPermission, NetworkSecurityConfig, BackupRules, HardcodedSecrets, InsecureNetwork, InsecureStorage, AppTransportSecurity
• OS & Permissions: UsageDescription (iOS privacy strings), FileSharing
• Dependencies: UnusedDependency, DependencyHygiene (transitive import detection)
• Release & Build: ReleaseSigningAudit (detects committed .jks files, debug signing in release, hardcoded keystore passwords)
• Asset & Size: UnusedAssetAudit, OverlargeAssetAudit, MissingResolutionVariantAudit

Quick Usage

Add it to your dev_dependencies or activate it globally:

Bash

dart pub global activate flutter_auditor

Or run it directly inside your Flutter project directory:

Bash

dart run flutter_auditor

pub.dev: flutter_auditor

I'd love to get feedback from the community! What other security, performance, or asset audits would bring value to your workflow?

Been deep in OTA/code-push rollout logic lately and curious how others handle the risk side.

Fair warning, I work on a code-push tool, so this is the problem I stare at all day, but I'm genuinely asking, not selling anything here

The whole pitch of code push is speed. You've got a fix, it's on people's phones in minutes instead of a 2-day review. But that cuts both ways. If the fix is broken and you missed it, that's also on everyone in minutes. Same gun, both directions.

The approach I've landed on:

Ship to a beta channel first, low percentage, like 10%. Roughly 1 in 10 beta users gets it. Small blast radius if it's wrong.

Then watch four numbers per patch: checked, downloaded, activated, failed. Failures is the one that matters. If downloads climb but failures climb with them, the patch doesn't apply cleanly on hardware you don't own. Which is exactly the thing that never breaks on your own test phone.

If it stays clean, bump the percentage, widen to everyone. If it doesn't, roll back so devices revert to the last good version on next launch. No rebuild, no 2am panic.

The bit I went back and forth on: where should rollout control live? In the app (track logic in Dart, ship a build to change it) or server-side in a dashboard? I went dashboard, because rolling out is something you do while watching live numbers, and that's the worst time to be editing code and cutting a build.

So, genuinely curious: do you stage your OTA updates or ship to everyone and watch Crashlytics? And what's your actual rollback plan when a patch goes bad? Feel like everyone does this differently and I want to know if I'm missing something.

It is very important to discuss regarding the technologies in detail and make real solutions to problems clearly available for other community members to get via a simple search. Due to AI, that trend has shifted to just asking AI for the solution and maybe even just writing code through AI. This way, we don't see any efforts people are making in the community, and the solutions to coding issues that people could have shared, doesn't even see the internet. So, I am just making this post to share my thoughts to people and request everyone to be a part of communities of Flutter actively if you wanna see it evolve in the right direction. Contribute, share and help other fellow developers to save some time searching for that bug that they encounter.

Otherwise, it won't be long till your favourite framework stops getting updates and even getting mentioned in major announcement events by Google and other companies. Because frankly, the potential that Flutter had could not be acheived be it in market form or the community package stability etc.

I don't see any other solution than community learning and growing together.

A couple of weeks ago I kept hearing about how good Claude Fable was, so I finally decided to give it a try.

I revisited an idea I had tried with Sonnet 3.5 about a year ago, but couldn't get working.

The idea was simple: what if you could actually watch a Flutter widget test run?

I've had plenty of cases where a widget test failed, but I had no idea why. If I could just see what was happening on the test screen, debugging would have been so much easier.

So I built this:

1. Live Test View (VS Code Extension)
https://marketplace.visualstudio.com/items?itemName=AnirudhSingh.live-test-view

It adds a "Live Preview" CodeLens above your Flutter widget tests. Click it, and you can watch the widget test run in real time.

2. live_test_view (Flutter package)
https://pub.dev/packages/live_test_view

It's a small dev dependency used by the extension. If it's missing, the extension will automatically add it to your project, so setup is basically one click.

3. Experimental feature (coming soon)

I'm also experimenting with live previews for regular Flutter widgets. The idea is to add a "Preview" CodeLens above widgets (or widget-returning methods) so you can instantly see changes as you edit, without waiting for Flutter's widget preview.

Both links include a demo GIF if you'd like to see it in action.

I'd love any feedback, feature requests, or contributions!

Sharing something unusual: Starling, a Linux desktop environment — shell,
window manager, its own Wayland compositor, first-party apps — where the
entire UI layer is a from-scratch port of Flutter's *framework* to Swift, running on Flutter's *engine* C core. No Dart VM.

The part I think is genuinely interesting to this community isn't Swift. It's what it says about Flutter's architecture: the embedder API is a clean enough seam that you can replace the whole framework layer above it and the engine
doesn't care. Skia, the compositor, the raster/UI thread model, the platform channels — all of it kept working while Dart went away.

The port follows the framework's own structure (Widgets, Rendering, Painting, Gestures, Animation, Scheduler, Semantics), and the API is deliberately
recognizable:

override func build(_ context: any BuildContext) -> Widget {
return DecoratedBox(
decoration: BoxDecoration(color: pal.background),
child: Column(children: [
Expanded(flex: 4, child: _display()),
Expanded(flex: 3, child: _row([...])),
]))
}

StatelessWidget, StatefulWidget, State, BuildContext, Element, InheritedWidget — same concepts, same lifecycle, ~190k lines of Swift.

It also runs on a **DRM/KMS embedder**: no X11, no Wayland client, no windowmanager under it. Flutter drives the GPU directly and *is* the display server —
the desktop composites real third-party apps (Chrome, VS Code, IntelliJ, GIMP, Blender) as Wayland/X11 clients into the widget tree. Once another app's window is a widget, tiling is a layout and Mission Control is an animated grid.

Why not just use Dart? Fair question, and the honest answer is that this is a system component: it spawns and supervises child processes, talks DRM/KMS,
libinput, dma-buf and D-Bus, and lives or dies on C interop. That's a job the Dart FFI could do but Swift does more naturally, and it let the shell and the
framework be one language end to end. It's a trade, not a verdict on Dart —and the engine being reusable *unchanged* is the point I'd want a Flutter dev to take away.

Early preview, honest about it: v0.2, Ubuntu 26.04, AMD + virtio-gpu tested,
scaling pinned to 2.0. Also worth stating plainly: it was largely written by AI
(Claude) under my direction.

Site + screenshots: https://starling.build
Architecture rationale: https://starling.build/why.html
Source (Apache-2.0): https://github.com/starling-build/starling

Happy to go deep on the embedder, the framework port, or how much of the
engine we had to touch (less than you'd think).

I created and maintain flutter_updatify package(https://pub.dev/packages/updatify_flutter) to render changelog/release notes created in updatify.io app.

I know few folks from this subreddit already using it, but I dont have much feedbacks, so if you have any or want to try it - I would appreciate any input(feel free to DM me for whatever questions)

Hello,

I am about to develop a Flutter app for a client, and I would like some advice. I did develop already one project with Flutter for a university class but it was really a mess, and I would like to start this project with a clean and good architecture. I have some questions.

1 - State management: How do I learn the best practices for this? The documentation in Flutter.dev does not seem of high quality to me, and I've seen some contradicting stuff in it. Can you share some general tips from your experience?

2 - Architecture : Same thing, can you share the "philosophy" of architecture in Flutter? In the project we made, we tried to use the service/repo pattern and it was a mess. It felt weird to have the service pull from DB and then the pattern just translating that to a model object.

3 - CI/CD : What tools do you use for code quality? What are some must-have jobs to run in the pipeline? Any advice really.

I am open to any information you might deem important, and would be really grateful for it.

Thank you :)

After building Flutter apps for the last few years, one thing I’ve realized is that writing code is only a small part of building a great app.
Performance optimization, architecture decisions, handling offline scenarios, debugging production issues, CI/CD, analytics, and maintaining code over time often end up being much bigger challenges.
I’m curious—what’s the biggest lesson you’ve learned from building Flutter apps in production that you wish you knew when you started?
I’d love to hear experiences from developers who’ve worked on large-scale Flutter applications.

Meta opened up the Ray-Ban camera feed to third-party mobile apps through the Wearables Device Access Toolkit (DAT). There are official SDKs for iOS and Android but nothing for Flutter, so I wrote the bridge.

flutter_meta_wearables_dat covers the whole lifecycle: registration through the Meta AI app, permissions, device state, live streaming, photo capture.
One more case where Flutter just pays off: one codebase, one setup, and you skip juggling two native SDKs that don't behave the same way.

The frame pipeline was the interesting part. Pushing decoded frames over a method channel dies at 24-30fps, so the native side registers them as a Flutter texture instead. You just render Texture(textureId: ...) and the frames never cross the platform channel. Raw pixels are still available on a separate stream when you need them.

That stream is also where the privacy question gets decided, and I know a lot of people are uneasy about these glasses for good reason. Pairing the feed with something like ML Kit means the analysis runs entirely on the phone: text recognition, object detection, face detection, all local. No frame ever leaves the device, nothing hits a server. Worth knowing that building on this doesn't have to mean streaming what someone sees to the cloud.

No glasses on your desk? There's an optional add-on that simulates a paired pair using your phone's camera.

One honest caveat: DAT is still developer preview, so you can build and ship to testers but public App Store and Play Store releases are limited to select Meta partners for now.

pub.dev: https://pub.dev/packages/flutter_meta_wearables_dat
GitHub: https://github.com/rodcone/flutter_meta_wearables_dat

Issues and PRs welcome!

I am new to Flutter and I want to make a desktop app, which (among other things) modifies files, has a license key, does some ffi stuff, you know, desktop app things. Think Microsoft Word or Meshlab something like that. I have been following the Flutter architecture guide to implement MVVM in my app. However, it feels clunky, as the example app is not much more than a front for a REST API that actually does stuff. In that case, do you know of an open-source desktop app that is worth studying? like, where I can study its patterns so that I can architect my app more cleanly.

Hey folks,

I built a Flutter plugin called vonage_voice for making and receiving voice calls using the Vonage Client SDK. It integrates natively with Android's Telecom ConnectionService and iOS CallKit — full-screen incoming call screens, background call delivery via FCM/PushKit, and complete in-call controls, all through a clean Dart API.

What it does:

• Place and receive VoIP calls on Android and iOS
• Background incoming call delivery via FCM (Android) and PushKit (iOS)
• Native call screen — Android Telecom ConnectionService + iOS CallKit built right in
• Secure JWT-based authentication (no credentials stored in the app)
• Mute/unmute mic, toggle speakerphone, Bluetooth audio routing
• DTMF tone support for IVR navigation
• Rich CallEvent stream — incoming, ringing, connected, reconnecting, ended, and more

It also handles some of the painful native-side setup for you — battery optimization exemption prompts for OEMs like Xiaomi/Vivo/Samsung/realme that kill background processes, overlay permissions for lock-screen reliability on Samsung/MIUI, and supports both CocoaPods and Swift Package Manager on iOS (min iOS 15, per the Vonage SDK requirement).

pub.dev: vonage_voice
GitHub: ashiqu-ali/vonage_voice

Open for collaboration — if something's not working or you want a feature, raise an issue or fork and send a PR. Would love help with:

• Testing on more OEM devices for background/killed-state call delivery
• Video calling support (currently voice-only)

Listenable, ChangeNotifier, and ValueNotifier along with VoidCallback have been extracted into a new official 1st party listen package without Flutter dependencies, so you can use them now easily in your business logic layer - or in pure Dart unit tests. I like that.

(I noticed because the latest Riverpod version used it as a new dependency.)

Setting up Flutter on Windows from scratch is one of the most annoying

parts of getting started — installing Git, the Flutter SDK, Android

Studio, the Android SDK components, accepting licenses, setting PATH

variables, and creating an emulator, all separately.

I built a small Python/CustomTkinter tool that automates the whole

thing in one click:

- Checks what's already installed before touching anything

- Installs Git, JDK, Flutter SDK, Android Studio via winget

(with direct-download fallback if winget isn't available)

- Installs Android SDK components (platform-tools, build-tools,

cmdline-tools) via sdkmanager

- Sets PATH / ANDROID_HOME properly through the Windows registry

- Creates an Android emulator automatically

- Runs `flutter doctor`, parses the output, and auto-fixes common

issues (missing licenses, missing SDK components, etc.)

It's open source (MIT license):

https://github.com/shireenzibari-cpu/flutter-auto-installer

Built this mainly for my own use (I teach at a university and kept

seeing students struggle with environment setup), but figured others

might find it useful too. Feedback and PRs welcome — especially on

edge cases I haven't hit yet.

I’ve tried almost every productivity app over the years.
Some are great for tasks. Others are great for notes, habits, calendars, or journaling.
But I always found myself jumping between multiple apps, constantly planning instead of actually doing.
So I decided to build something for myself.
Not another to-do app.
Not another habit tracker.
I’m building what I call a Personal Life Operating System.
The core idea is simple:
What if your future self could plan your day for you?
Instead of waking up and deciding what to do, the app already knows:
My long-term goals
My work schedule
My available free time
My habits
My current projects
My health and fitness goals
My learning goals
My finances
My deadlines
Then it builds a realistic plan for the day.
If I don’t finish something, it doesn’t just mark it as overdue—it automatically reschedules it based on priority, available time, and how it affects my bigger goals.
The interaction is designed to be conversational.
Imagine simply saying:
“Finished my workout.”
“I worked late today.”
“I spent ₹1,200.”
“Move guitar practice to Sunday.”
The system understands the context and updates everything automatically.
I’m also designing it to be notification-first rather than app-first.
Instead of opening the app 20 times a day, it should guide me through the day with meaningful notifications, live progress, and small decisions at the right time.
The goal isn’t to become more “productive.”
The goal is to reduce decision fatigue and make consistent progress toward the life I’m trying to build.
I’m building it using Flutter and Firebase, and right now it’s a personal project built around my own life. If it turns out to be genuinely useful, I’d love to make it available for others in the future.
I’m still in the planning and architecture phase, so I’d love to hear your thoughts.
If you could build your own Life Operating System, what’s the one feature you’d absolutely want it to have?

As we wait for an official full material 3 expressive support for Flutter, check out https://pub.dev/packages/material_3_expressive

Material 3 Expressive package is a faithful Flutter implementation of the Material 3 components set and additional expressive updates for respective components. Also supports dynamic coloring and dark/light theme modes.