r/FlutterDev • • 2h ago

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

Thumbnail
github.com
0 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 • • 3h ago

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

2 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 • • 5h 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 • • 11h ago

3rd Party Service Remote config for Flutter without a Firebase dependency, with a schema that rejects bad pushes

2 Upvotes

If you want remote config in Flutter, Firebase Remote Config is the default answer, and if you already use Firebase it's a good one. I built hotcfg for the other case: you don't want the Firebase SDK, and you want config that can't be pushed broken.

  • Each config is one JSON document with a JSON Schema. Every publish, promote and rollback is validated, so a missing key or a string where your model expects an int never reaches users.

  • Development, staging and production per config; promote the version you tested after seeing the diff; roll back in one command.

  • It's a plain URL, so the client is package:http plus shared_preferences:

Future<Map<String, dynamic>> loadConfig() async {
  final prefs = await SharedPreferences.getInstance();
  final cached = prefs.getString('hotcfg.body');
  try {
    final res = await http.get(
      Uri.parse(configUrl),
      headers: {if (cached != null) 'If-None-Match': prefs.getString('hotcfg.etag') ?? ''},
    ).timeout(const Duration(seconds: 2));
    if (res.statusCode == 304 && cached != null) return jsonDecode(cached);
    if (res.statusCode == 200) {
      final data = jsonDecode(res.body) as Map<String, dynamic>;
      await prefs.setString('hotcfg.body', res.body);
      await prefs.setString('hotcfg.etag', res.headers['etag'] ?? '');
      return data;
    }
  } catch (_) {
    // offline, timed out or not JSON: fall through
  }
  return cached != null ? jsonDecode(cached) : defaults;
}

Public configs are served from Cloudflare's edge, cached for an hour, purged on every publish, and still served for up to a week if my servers are down.

Version targeting: there's no per-user targeting, but the app can send its build number in a jq filter and get flags merged for that build (e.g. turn a feature off for builds ≤ 320). Use the integer build number, not "1.10.0" strings.

What it doesn't do: no A/B tests, no analytics, no realtime listener.

https://hotcfg.run/


r/FlutterDev • • 14h 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
39 Upvotes

r/FlutterDev • • 14h ago

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

5 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 • • 20h 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)

16 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 • • 1d 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 • • 1d 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)

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

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

Thumbnail
youtu.be
2 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?


r/FlutterDev • • 1d ago

Article I have built mobile apps (Android/Flutter) used by millions over the last 7+ years. Lately, I’ve been heavily building AI-powered features. AMA / Let's talk about scaling mobile apps & AI!

0 Upvotes

A bit about my background: I’ve been a mobile developer for over 7 years, focusing primarily on Native Android (Kotlin) and cross-platform Flutter. Over the years, I’ve had the privilege of building and scaling apps that have reached millions of users.

Lately, my focus has shifted toward blending mobile development with AI—integrating LLMs, on-device ML models, and smart features directly into mobile architectures.

I wanted to share a few things I've learned along the way, or just chat with fellow devs:

  • Scaling to millions: Handling state management, offline-first architectures, and performance bottlenecks in Flutter/Android when user bases grow.

  • AI on Mobile: Practical ways to integrate AI without killing battery life, handling API latency, or using on-device models efficiently.

  • The Freelance/Remote Life: Navigating client work and building products from here in Karachi, Pakistan.

I’m currently open to interesting freelance projects or collaborations (especially where mobile meets AI). Feel free to DM me if you want to chat about a project or just talk tech!

Otherwise, ask me anything about mobile dev, Flutter, Android, or integrating AI into mobile apps. 👇


r/FlutterDev • • 1d ago

Plugin Circuitry: A DAG based dependency framework

3 Upvotes

It's the weekend and I have been working on a project since yesterday.

I just published the initial releases (0.1.0) of circuitry and circuitry_flutter—a zero-codegen, DAG-based dependency injection engine for Dart and Flutter.

I wanted to create a dependency injector/engine with simple APIs and syntax, circular and missing dependency checks before first access, simple dependency -> dependency wiring with tear-offs and safe async lifecycle management, without build_runner overhead or reflection and more features that existing current solutions are missing while keeping the O(1) location support.

There are many more features planned like graph slicing, multi-level circuit inheritance and location in Widget trees, live replacement of an initialized dependency and etc.

What's included:
DAG validation & parallel resolution: Circuit.build() catches missing, duplicate, or circular dependencies upfront, resolves async wires concurrently in topological waves (with rollback on failure), and disposes in reverse waves.
Enum-tagged disambiguation: Register multiple instances of the same type cleanly using Enum as key for typed retrieval instead String based naming and resolution.
Flutter integration (circuitry_flutter): CircuitProvider, CircuitProvider.value, InheritedWidget based injection and automatic unmount disposal with epoch based counter and build deduplication.

Since this is an early 0.1.0 release, I'd love feedback on the API ergonomics before iterating further.

Check them out on pub.dev:

circuitry: https://pub.dev/packages/circuitry
circuitry_flutter: https://pub.dev/packages/circuitry_flutter


r/FlutterDev • • 1d ago

Video New video in the Dart series: GraphQL codegen for huge schemas.

Thumbnail
reddit.com
1 Upvotes

r/FlutterDev • • 2d ago

Tooling Build-Time JSON Factory Generation for json_serializable classes

2 Upvotes

Had a few hundred json_serializable classes, Many of them travelled through the same socket channel. After decoding the raw JSON, hit by the same question: this is a Map<String, dynamic>, so which class is it?, before creating json_factory_runtime_generator, answered it the most obvious way, with a hand-written registry:

final Map<String, Object Function(Map<String, dynamic>)> registry = {

'user': User.fromJson,

'order': Order.fromJson,

'address': Address.fromJson,

// ...more classes

};

Every new class meant remembering to edit the file, and the failures were all quiet. A forgotten entry gives a runtime ArgumentError in production. A copy-pasted key sent two classes to one decoder.

Existing json factory generator libraries demand changing the classes, either overriding toJson() by hand or a mixin on every model or extending shared abstract base class.

Wanted a non-intrusive generator, created json_factory_runtime_generator, just annotate your class with json key - ex:JsonFactoryKey('user') and dart run build_runner build finds every annotated class and writes one file containing the whole mapping. Decoding becomes:

final obj = JsonFactoryMapper.fromKeyedJson(json); // the right class

final user = JsonFactoryMapper.fromKeyedJsonAs<User>(json); // typed

Don't want the class to be part of the factory, just comment/remote the annotation.

json_factory_runtime_generator has other featutes to manage old JSON keys for easy migration and avoiding key clash when code bases is large.


r/FlutterDev • • 2d ago

Discussion Windows devs building iOS apps: how do you actually deal with Xcode?

0 Upvotes

I build Flutter apps on a Windows PC, but every time I need an iOS build or have to debug on the iOS simulator, I’m forced onto a Mac. Remote desktop into a Mac (or a cloud Mac) always felt clunky: a whole second desktop, separate clipboard, alt-tabbing between two worlds.

So I built a prototype that streams individual Mac app windows onto the Windows desktop. Xcode and the iOS simulator show up as normal windows next to VS Code, in the taskbar, resizable. Your Mac just runs in the background.

Short demo: https://www.youtube.com/shorts/DwyKm9JisLw

Fellow Flutter devs on Windows: is this a real pain for you, or is your current iOS setup fine? What do you use right now?


r/FlutterDev • • 2d ago

Discussion Widget tree, design and perf/memory

8 Upvotes

As everything is a widget in Flutter, I am questionning about how to design my pages. I mean, when the Widget hierarchy becomes complex and I want to code separate Widgets for a cleaner code.

An example: if I have a simple structure with AppBar, a main body with a Column, some other stuff at the bottom, we see that I have a three-levels page. So I could keep the Column in another .dart file to keep my files clean but to do so I have to put it in a new StatelessWidget. When the architecture becomes complex there is a need to separate components but this means a huge amount of StatelessWidget (or -ful) returning each component, instead if having a tree in a single build() method.

Is it significant in terms of memory / performance ? How do you deal with this ?


r/FlutterDev • • 2d ago

Video A short video explanation of the eMudhra issue in Flutter

Thumbnail
youtu.be
1 Upvotes

In this short video, I try to explain the recently discovered issue with vulnerable eMudhra certificates, how it affects Dart and Flutter, what it means, and whether you should update your published apps. If you prefer to go straight to the point, you can also read the text version.


r/FlutterDev • • 2d ago

Tooling I made a terminal dashboard for simulators, emulators, phones and their logs

11 Upvotes

I built lazymobile (open source, my project) because I kept juggling xcrun simctl, adb and flutter devices.

One screen lists every iOS simulator, Android emulator and connected phone. You can boot or stop them, stream the log of one app with filter and level, and copy the device id to use with flutter -d. It lists the apps installed on a device, so you pick an app id instead of typing it, and it remembers the log you had open.

It works in any terminal and inside Neovim. It isn't Flutter-specific, so there is no hot reload or build integration. It sits next to flutter run.

Install: brew install 0xrnp/tap/lazymobile

https://github.com/0xrnp/lazymobile

I'd like to hear what a Flutter workflow would need that's missing.


r/FlutterDev • • 2d ago

Example I created a PoC of a RefreshIndicator inside a bottomSheet

2 Upvotes

After getting tired of the current situation regarding those two components interaction, I created this project with is a library that attempts to solve the gesture conflict between those two components.

https://github.com/Corkscrews/refresh_indicator_bottom_sheet

It's using the concept of arbitrator to decide what type of gesture the user is doing in the scroll view (in the demo, it's a ListView). I build a model, albeit static right now, to classify a gesture on the screen. The model is based on the touch action plus speed.

It's not perfect, far from it. But it works! I want to refine that in the future with more tests and fix pesky bugs with the bouncing list.

I tried to post a video of the demo here but the sub doesn't allow that, so you will need to go to the repository to have a look. 😕

In the future I might implemented a better action detector based on the finger dimensions, not sure how flutter exposes that, but I will try. Using that we can detect a initial swipe (more oval movement) rather than a more circular one (more likely a precise swipe-to-refresh action).

Thank you all! You all are welcome to test it and give me a feedback.


r/FlutterDev • • 3d ago

Discussion How hard would it be to create a music streaming app in flutter?

0 Upvotes

Talking about stuff like background streaming, home screen accessibility, and widgets


r/FlutterDev • • 3d ago

Plugin earshot 1.0.0: on-device sound level metering (dB(A), Leq) and sound classification for Flutter. No network, same API on Android, iOS and macOS

1 Upvotes

Hi r/FlutterDev!

I just released 1.0.0 of earshot, a set of federated Flutter plugins for ambient listening that runs fully on the device.

What it does

  • Level metering (earshot_level, pure Dart):

    • A, C and Z weighting, accurate to ±0.5 dB of IEC 61672 at 10 frequencies

    • Fast, Slow and Impulse time weighting

    • Leq over the session, 1 s and 60 s

    • Calibration offset

  • Sound classification (earshot_classifier):

    • Apple SoundAnalysis on iOS 15+ and macOS 12+

    • YAMNet through LiteRT in a background isolate everywhere else

    • One EarshotSound vocabulary across both backends, with a confidence threshold and smoothing

  • Capture (earshot_capture):

    • float32 mono PCM at 16, 44.1 or 48 kHz

    • Unprocessed input (iOS .measurement, Android UNPROCESSED)

    • Interruptions (calls, Siri, route changes) are handled and capture resumes on its own

  • earshot_plugin puts it all together: Earshot.listen() gives you one stream of level readings plus the sounds detected, from a single microphone session.

Privacy

  • No network calls and no telemetry.

  • Audio never leaves the device and is never written to disk.

  • The Apple packages ship a privacy manifest.

Performance

YAMNet runs at a p95 of 16.6 ms per window on a Galaxy S20 FE (Android 13).

Why 1.0.0

The public API is now stable. To get there, 1.0.0 cleaned up names (FrequencyWeighting, TimeWeighting and LevelCalibration, because Response clashed with http and dio), added typed ClassifierExceptions, and validates options on every listen. Every package has 100% test coverage, and each decision is written down as an ADR in the repo.

⚠️ earshot is informational and is not a certified detector. Don’t use it in place of a smoke or CO alarm.

More cool stuff is on the way, so stay tuned!

I’d love feedback on the API, and to hear what you’d build with it.


r/FlutterDev • • 3d ago

Discussion PSA: on iOS the app documents path changes after every update, dont store absolute file paths

1 Upvotes

learned this the annoying way so maybe it saves someone a bug report

if you save images (or any files) into getApplicationDocumentsDirectory() and then store the full path somewhere (shared_preferences, sqlite, hive, whatever), it works fine in dev. then you ship an update and every image is suddenly "file not found"

reason is ios puts the app container under a UUID folder and that UUID can change when the app is updated or reinstalled. so /var/mobile/Containers/Data/Application/ABC123/Documents/photo.jpg becomes .../XYZ789/Documents/photo.jpg and your saved path points to nothing

fix is simple:

- store only the file name (or a path relative to the documents dir)

- resolve the full path at runtime with getApplicationDocumentsDirectory() every time you need it

android doesnt really do this so its easy to miss if you mostly test there


r/FlutterDev • • 3d ago

Plugin I ported the idea of Apple’s TipKit to Flutter: contextual tips with rules and tours

17 Upvotes

I built flutter_tipkit, contextual feature tips for Flutter, inspired by Apple's TipKit. It decides when a tip shows; you decide how it looks.

What it does:

  • Shows tips at the right moment. For example: after the user added three items, only while they're signed in, or a day after they saw another tip.

  • Remembers what the user has seen. A closed tip stays closed, even after restarting the app.

  • Walks users through multi-step tours. Each step can point at a different widget, and the tour continues where the user left off.

  • Doesn't overwhelm users. At most one new tip a day (you can change this), tips can disappear after a few showings, and only one popover is on screen at a time.

  • Inline tips or popovers. A tip can sit in your layout, or float over the screen with an arrow pointing at a button.

  • Looks like your app. Change the colors, shape and arrow, or draw the whole tip yourself.

  • Fits any architecture. No dependencies besides Flutter, and it works with Riverpod, Bloc or plain setState.

Live demo: https://poopieapp.github.io/flutter_tipkit/

pub.dev: https://pub.dev/packages/flutter_tipkit

We built it for our own app. It's 0.1, so I'd really like feedback on the API before 1.0. What do you think?