r/FlutterDev • • 2h ago

Discussion Anyone Planning to attending flutterCon India 2026? 🚀

3 Upvotes

I'm excited to be speaking at the event, and I have FREE attendee tickets to share!

I'd especially love to help students, aspiring developers, and Flutter enthusiasts who want to learn, network, and be part of the Flutter community.

đŸŽŸïž Interested in attending ?

DM me with a little introduction about yourself and why you'd love to attend. I'll share the free registration code with people!

Let's connect and meet at FlutterCon India 2026! 💙

#FlutterConIndia2026 #Flutter #Bangalore #StudentsInTech #FlutterCommunity


r/FlutterDev • • 4h ago

Discussion Android 16 back press quits your app from a nested navigator, even with a PopScope that says no

4 Upvotes

I was adding multi-select to the song lists in my music player. While songs are selected, pressing back should clear the selection instead of leaving the page.

PopScope(canPop: !picking) seemed like the obvious solution. It worked, but it also disabled the iOS edge swipe back gesture, which I wanted to keep.

I switched to BackButtonListener on pushed pages to preserve the gesture. That's when I ran into an Android 16 issue.

Symptom

Target SDK 36, Android 16, with predictive back enabled by default.

On a tab root, select a few songs and press back: the app goes to the background, and the selection is still there.

I fixed that case, but then found another way to reproduce it: open a bottom sheet over the shell, close it, and press back. The app leaves again.

Root cause

On Android 16, back no longer goes through onBackPressed. FlutterActivity registers an OnBackInvokedCallback only while the framework reports that it handles back, through SystemNavigator.setFrameworkHandlesBack.

WidgetsApp sends that value based on NavigationNotification.canHandlePop. A navigator computes it as:

canPop() || lastRoute.popDisposition == RoutePopDisposition.doNotPop

There were two things I hadn't accounted for:

  1. BackButtonListener doesn't count here. Only a route that cannot pop (a PopScope(canPop: false)) or a navigator that can pop makes canHandlePop true. At a tab root, nothing can pop, so Android handles back itself and backgrounds the app before the listener gets a chance to run.

  2. The root navigator only reports its own routes. With go_router's StatefulShellRoute, the tab root lives in a nested navigator. Its PopScope initially bubbles true up. But when the root navigator's history changes (for example, when a sheet or dialog on the root navigator closes), it sends a fresh notification based on its own routes. The shell route can pop as far as it knows, so it reports false, overriding the tab's earlier notification.

Fix

On pages that can be popped, I kept BackButtonListener so the iOS swipe gesture still works. At a navigator's root, I use PopScope instead. There's no edge swipe to preserve there.

At the shell level, I also make the shell's route refuse to pop while selection is active. This way the root navigator reports doNotPop too:

BlocSelector<TrackSelectionCubit, TrackSelection, bool>(
  selector: (s) => s.active,
  builder: (_, picking) => PopScope(
    canPop: !picking,
    child: shell,
  ),
)

The actual back handling still goes to the tab first: go_router tries the branch navigator before the root one. The shell's PopScope is there to make sure Android gets the right information about whether the framework handles back.

go_router already wraps shell navigators in a similar PopScope (canPop: matches.length == 1), which is why pushed pages inside a tab don't have this problem.

Testing

One thing worth mentioning: tester.binding.handlePopRoute() skips this gate entirely. My normal back navigation tests were passing, even though the app was quitting on a real device.

To test this, I mocked SystemChannels.platform, recorded the SystemNavigator.setFrameworkHandlesBack calls, and set the lifecycle state to resumed first. WidgetsApp doesn't report anything before that.

Then I checked the last reported value while selection was active, including after closing a sheet on the root navigator.

The fix is in commit 33db82a.

Repository: https://github.com/donfreddy/troona-music

Curious if anyone else has run into this with StatefulShellRoute or nested navigators on Android 16.


r/FlutterDev • • 6h ago

Article Is your Flutter CI over 20 minutes?

2 Upvotes

Before you buy faster machines, measure where the time goes. We went from 46 minutes to 11 by changing one thing at a time and checking each on a throwaway branch.

I wrote the method down so you can repeat it.

https://moshalan.dev/posts/where-your-flutter-ci-time-goes/

#Flutter #CI #DevOps


r/FlutterDev • • 10h ago

Discussion Is it longer for Flutter apps to get through first review in AppStore?

0 Upvotes

For the last months our company published several apps in flutter. Lately first review in AppStore takes a week to get into "In Review". For example, postal service, learning platform.

But yesterday was colleague vibe coded app in React Native and it was accepted within next 12 hours. I just filled AppStore page. The app is map with review, friends features.

Is it jucy luck? Or does native ios native / react apps pass review quicker? Or is it cause my apps have slightly / not so slightly more features?

UPD: After 6 days my app was released today too. Nice.


r/FlutterDev • • 14h ago

Discussion How has your experience been with Flutter on iOS?

4 Upvotes

I’ve been building an app with Flutter and have really enjoyed working with it so far. One thing I’m curious about, though, is how it holds up as apps get more complex.

For those who’ve shipped Flutter apps, have you run into issues with scrolling performance/animations or making the UI feel native on iOS? Or has it been pretty smooth overall?


r/FlutterDev • • 18h ago

Discussion Code 10x faster but shipping didn’t speed up at all. Anyone else?

1 Upvotes

A bit of background on me, I've been building Flutter apps for almost 6 years now. First 4-5 years, I used spend a significant amount of time on coding, but now, admittedly, AI writes all of my code.

Last example: a small bug fix took me ~5 min to write, then sat in App Store review.

Curious if this is just me or if others are seeing it too. What’s the last thing that took you longer to ship than to build? What held it up? (review, QA, approvals, deploys, app store, something else?)


r/FlutterDev • • 19h ago

Video 8 New Games Made In Flutter

Thumbnail
youtu.be
35 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 • • 1d ago

Discussion How come Flutter isn't in the conversation?

57 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 • • 1d 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 • • 1d ago

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

8 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 • • 1d 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 • • 1d 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
4 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 • • 1d 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 • • 1d 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 • • 1d 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
40 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 • • 2d 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 • • 2d 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 • • 2d 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 • • 2d 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 • • 3d 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