<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: flutter</title>
    <description>The latest articles tagged 'flutter' on DEV Community.</description>
    <link>https://dev.to/t/flutter</link>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tag/flutter"/>
    <language>en</language>
    <item>
      <title>Turning My Game Into an Android Live Wallpaper: Fixing Flutter Impeller’s Black Screen in WallpaperService</title>
      <dc:creator>Evgenii Zinner</dc:creator>
      <pubDate>Wed, 18 Nov 2026 00:01:34 +0000</pubDate>
      <link>https://dev.to/evgenii_zinner/turning-my-game-into-an-android-live-wallpaper-fixing-flutter-impellers-black-screen-in-b71</link>
      <guid>https://dev.to/evgenii_zinner/turning-my-game-into-an-android-live-wallpaper-fixing-flutter-impellers-black-screen-in-b71</guid>
      <description>&lt;p&gt;A few days ago, I saw an idle game that ran directly as an Android live wallpaper, and it immediately clicked: that format would be a great fit for &lt;strong&gt;Crystal Cinders&lt;/strong&gt;, the simulation game I’m currently building on top of &lt;a href="https://www.ezinner.com/articles/throwing-out-the-widget-tree-building-a-2d-game-engine-underneath-flutter-sting/" rel="noopener noreferrer"&gt;&lt;strong&gt;Sting&lt;/strong&gt;&lt;/a&gt; (my custom &lt;code&gt;dart:ui&lt;/code&gt; 2D ECS engine).&lt;/p&gt;
&lt;p&gt;Instead of forcing a player to open an app just to check on a slow-burning world simulation, the world is just &lt;em&gt;there&lt;/em&gt; behind your icons every time you unlock your phone, shifting with your home screen and ticking along in real time.&lt;/p&gt;
&lt;p&gt;Since Sting already compiles to native Android binaries via Flutter’s toolchain and draws directly onto Impeller’s GPU canvas, I figured wiring it up to Android’s &lt;code&gt;WallpaperService&lt;/code&gt; would be a quick evening task.&lt;/p&gt;
&lt;p&gt;It didn't work on the first attempt. Today, Crystal Cinders is running smoothly as the live wallpaper on my phone—but getting &lt;strong&gt;Flutter 3.x with Impeller (Vulkan)&lt;/strong&gt; to actually put pixels inside an Android &lt;code&gt;WallpaperService&lt;/code&gt; required throwing out the old advice and flipping one of Flutter’s own internal Android tricks in reverse.&lt;/p&gt;
&lt;p&gt;Here is what I learned getting it working.&lt;/p&gt;

&lt;h2&gt;1. Why startRenderingToSurface Gives You a Black Screen on Impeller&lt;/h2&gt;

&lt;p&gt;If you look at &lt;code&gt;pub.dev&lt;/code&gt; for Flutter wallpaper packages, almost all of them just set static images or loop a pre-rendered video file. They don't actually run a live, interactive &lt;code&gt;FlutterEngine&lt;/code&gt; as your home screen.&lt;/p&gt;
&lt;p&gt;And if you dig up older guides from the Flutter 1.x / 2.x Skia OpenGL days—or ask an LLM how to hook a &lt;code&gt;FlutterEngine&lt;/code&gt; into Android’s &lt;code&gt;WallpaperService.Engine&lt;/code&gt;—they all tell you to grab &lt;code&gt;surfaceHolder.surface&lt;/code&gt; and pass it straight to the renderer:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;// The old Skia-era approach that fails on modern Flutter / Impeller
flutterEngine.renderer.startRenderingToSurface(holder.surface, false)&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;When I tried this, everything &lt;em&gt;looked&lt;/em&gt; fine in the logs. My Dart entrypoint (&lt;code&gt;wallpaperMain()&lt;/code&gt;) booted up, the ECS loop initialized, and &lt;code&gt;onDrawFrame&lt;/code&gt; fired at the exact physical resolution of my phone’s screen. Zero Dart exceptions, zero native crashes.&lt;/p&gt;
&lt;p&gt;And on the phone? &lt;strong&gt;A pitch-black screen.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Digging through &lt;code&gt;logcat&lt;/code&gt; showed what was actually happening:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;HWUI: Surface doesn't have any previously queued frames&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;In Flutter 3.x (with Impeller Vulkan enabled by default on Android):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A normal &lt;code&gt;FlutterActivity&lt;/code&gt; creates a &lt;code&gt;FlutterView&lt;/code&gt; wrapping a &lt;code&gt;FlutterSurfaceView&lt;/code&gt; and calls &lt;code&gt;flutterView.attachToFlutterEngine(engine)&lt;/code&gt;. That &lt;code&gt;FlutterView&lt;/code&gt; setup is what properly initializes the &lt;code&gt;RenderSurface&lt;/code&gt; pipeline for Impeller.&lt;/li&gt;
&lt;li&gt;Android’s &lt;code&gt;WallpaperService.Engine&lt;/code&gt;, however, &lt;strong&gt;has no &lt;code&gt;View&lt;/code&gt; hierarchy at all&lt;/strong&gt;. It isn't an &lt;code&gt;Activity&lt;/code&gt; or a &lt;code&gt;Window&lt;/code&gt;—it only gives you a raw &lt;code&gt;SurfaceHolder&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Calling &lt;code&gt;flutterEngine.renderer.startRenderingToSurface(holder.surface, false)&lt;/code&gt; bypasses &lt;code&gt;FlutterView&lt;/code&gt; and &lt;code&gt;RenderSurface&lt;/code&gt;. Even though Dart runs &lt;code&gt;onDrawFrame&lt;/code&gt;, Impeller never queues the rendered frame buffers onto the &lt;code&gt;Wallpaper#0&lt;/code&gt; surface.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;2. Flipping Flutter’s Own VirtualDisplay Trick in Reverse&lt;/h2&gt;
&lt;p&gt;Once I understood why Impeller was refusing to queue frames, the problem was clear: &lt;strong&gt;how do you mount a real &lt;code&gt;FlutterView&lt;/code&gt; when &lt;code&gt;WallpaperService&lt;/code&gt; doesn't have a &lt;code&gt;View&lt;/code&gt; hierarchy?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Ironically, the answer was hiding inside Flutter’s own Android engine architecture—just used in the opposite direction.&lt;/p&gt;
&lt;p&gt;When Flutter needs to render a native Android &lt;code&gt;View&lt;/code&gt; (like a &lt;code&gt;WebView&lt;/code&gt; or Google Map) &lt;em&gt;inside&lt;/em&gt; a Flutter app using Platform Views (Virtual Display mode), Flutter creates an Android &lt;strong&gt;&lt;code&gt;VirtualDisplay&lt;/code&gt;&lt;/strong&gt; and wraps the native view inside a &lt;strong&gt;&lt;code&gt;Presentation&lt;/code&gt;&lt;/strong&gt; window (&lt;code&gt;SingleViewPresentation&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;To get Flutter working inside &lt;code&gt;WallpaperService&lt;/code&gt;, you flip that exact trick inside out:&lt;/p&gt;
&lt;p&gt;Instead of bypassing &lt;code&gt;FlutterView&lt;/code&gt;, &lt;code&gt;CrystalCindersWallpaperService&lt;/code&gt; creates a hardware-backed &lt;code&gt;VirtualDisplay&lt;/code&gt; whose output target &lt;strong&gt;is&lt;/strong&gt; the wallpaper’s &lt;code&gt;SurfaceHolder.surface&lt;/code&gt;. Once Android treats the wallpaper surface as a virtual display, you open a &lt;code&gt;Presentation&lt;/code&gt; window on that display and mount a real &lt;code&gt;FlutterView&lt;/code&gt; inside it:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;WallpaperService.Engine (holder.surface)
  └── DisplayManager.createVirtualDisplay(..., surface = holder.surface, VIRTUAL_DISPLAY_FLAG_OWN_CONTENT_ONLY)
        └── Presentation(context, virtualDisplay.display)
              └── FlutterView(context)
                    └── flutterView.attachToFlutterEngine(flutterEngine)&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The moment &lt;code&gt;flutterView.attachToFlutterEngine(flutterEngine)&lt;/code&gt; runs inside that &lt;code&gt;Presentation&lt;/code&gt; window, Impeller gets the full &lt;code&gt;FlutterView&lt;/code&gt; lifecycle it expects, Vulkan queues frame buffers onto the virtual display’s surface, and those pixels go straight onto the Android home screen.&lt;/p&gt;

&lt;h2&gt;3. Four Gotchas Between "It Renders" and "It Survives on a Real Phone"&lt;/h2&gt;

&lt;p&gt;Getting the first frame on screen was half the job. Making a simulation game behave nicely as a daily wallpaper took four more details:&lt;/p&gt;
&lt;h3&gt;1. OEM Background Thread Callbacks (&lt;code&gt;Looper.getMainLooper()&lt;/code&gt;)&lt;/h3&gt;
&lt;p&gt;On Pixel phones, &lt;code&gt;WallpaperService&lt;/code&gt; callbacks usually arrive on the main thread. On several custom Android OEM ROMs, some surface callbacks fire on background threads—which immediately triggers a &lt;code&gt;@UiThread&lt;/code&gt; crash if you touch &lt;code&gt;FlutterEngine&lt;/code&gt;, &lt;code&gt;VirtualDisplay&lt;/code&gt;, &lt;code&gt;Presentation&lt;/code&gt;, or a &lt;code&gt;MethodChannel&lt;/code&gt;. Wrapping those calls in &lt;code&gt;Handler(Looper.getMainLooper())&lt;/code&gt; and setting &lt;code&gt;surfaceHolder.setFormat(PixelFormat.RGBA_8888)&lt;/code&gt; in &lt;code&gt;Engine.onCreate&lt;/code&gt; keeps it stable everywhere.&lt;/p&gt;
&lt;h3&gt;2. Pausing the Loop When You Aren't Looking (&lt;code&gt;onVisibilityChanged&lt;/code&gt;)&lt;/h3&gt;
&lt;p&gt;Running a 60 FPS ECS simulation while you're looking at your home screen is great. Running it at 60 FPS while you have another app open in front of it—or while your phone is locked in your pocket—will drain your battery in a couple of hours.&lt;/p&gt;
&lt;p&gt;In &lt;code&gt;onVisibilityChanged(visible: Boolean)&lt;/code&gt;, the service calls &lt;code&gt;engine.lifecycleChannel.appIsResumed()&lt;/code&gt; / &lt;code&gt;appIsPaused()&lt;/code&gt; and sends a &lt;code&gt;"resume"&lt;/code&gt; / &lt;code&gt;"pause"&lt;/code&gt; message over &lt;code&gt;MethodChannel("crystal_cinders/wallpaper")&lt;/code&gt; so the game loop stops scheduling frames the instant the home screen is hidden.&lt;/p&gt;
&lt;h3&gt;3. Home-Screen Swipe Parallax (&lt;code&gt;onOffsetsChanged&lt;/code&gt;)&lt;/h3&gt;
&lt;p&gt;Whenever you swipe between home-screen pages, Android fires &lt;code&gt;onOffsetsChanged&lt;/code&gt; in &lt;code&gt;WallpaperService.Engine&lt;/code&gt;. Forwarding those horizontal offsets to Dart lets the game camera pan subtly across the simulation world as you swipe through your apps.&lt;/p&gt;
&lt;h3&gt;4. Clean Teardown Between Preview and Live Wallpaper&lt;/h3&gt;
&lt;p&gt;When you open the Android Wallpaper Picker (which the game triggers directly via &lt;code&gt;WallpaperManager.ACTION_CHANGE_LIVE_WALLPAPER&lt;/code&gt; over a launcher channel in &lt;code&gt;MainActivity.kt&lt;/code&gt;), Android spins up a &lt;em&gt;preview&lt;/em&gt; engine instance alongside any existing wallpaper and destroys surfaces aggressively when switching. Dismissing the &lt;code&gt;Presentation&lt;/code&gt; window (which detaches &lt;code&gt;FlutterView&lt;/code&gt;) and releasing the &lt;code&gt;VirtualDisplay&lt;/code&gt; in &lt;code&gt;onSurfaceDestroyed&lt;/code&gt; and &lt;code&gt;onDestroy&lt;/code&gt;—before destroying the &lt;code&gt;FlutterEngine&lt;/code&gt;—prevents GPU leaks and black-screen race conditions.&lt;/p&gt;

&lt;h2&gt;What’s Next: Seamless "Tap to Enter the World"&lt;/h2&gt;

&lt;p&gt;Right now, having the simulation running live as my phone’s wallpaper feels awesome—and it immediately gave me the next idea I want to build.&lt;/p&gt;
&lt;p&gt;Instead of treating the wallpaper and the full game as two disconnected things, I want &lt;strong&gt;tapping on the live wallpaper to take you seamlessly straight into the full interactive game world&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;I haven't tested this part yet, and I’m 100% sure it has its own set of Android surprises waiting for me:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fighting the home-screen launcher over which taps belong to app icons versus the wallpaper (&lt;code&gt;onTouchEvent&lt;/code&gt; vs. &lt;code&gt;COMMAND_TAP&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Dealing with Android 10+ restrictions on launching an &lt;code&gt;Activity&lt;/code&gt; from a background &lt;code&gt;WallpaperService&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Handing off the live simulation state between the wallpaper’s &lt;code&gt;FlutterEngine&lt;/code&gt; and &lt;code&gt;MainActivity&lt;/code&gt; so the camera and world transition without a jarring reload.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That will be my next experiment—and probably the next post once I figure out what breaks first.&lt;/p&gt;

</description>
      <category>android</category>
      <category>flutter</category>
      <category>gamedev</category>
      <category>mobile</category>
    </item>
    <item>
      <title>Footings: the offline-first Flutter starter kit I extracted from my own app</title>
      <dc:creator>Majician13</dc:creator>
      <pubDate>Tue, 17 Nov 2026 20:38:48 +0000</pubDate>
      <link>https://dev.to/majician13/footings-the-offline-first-flutter-starter-kit-i-extracted-from-my-own-app-5611</link>
      <guid>https://dev.to/majician13/footings-the-offline-first-flutter-starter-kit-i-extracted-from-my-own-app-5611</guid>
      <description>&lt;p&gt;Every offline app I start rebuilds the same plumbing: a local database, a way to seed it with starter content, search, favorites, and eventually backup. I got tired of rewriting it, so I extracted the working stack from my own app — a magic index app I've been building all year — into a starter kit called Footings.&lt;/p&gt;

&lt;h2&gt;
  
  
  The core idea: two databases, not one
&lt;/h2&gt;

&lt;p&gt;Most offline tutorials use a single database. Footings uses two:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;bundled read-only seed DB&lt;/strong&gt; that ships with the app. This is your starter content.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;writable user DB&lt;/strong&gt; for everything the user creates, plus favorites.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The split matters when you ship an update. New seed content replaces the bundled DB; the user's data is never touched. The user DB migrates itself — v1 to v2 adds an images table and an &lt;code&gt;ocr_text&lt;/code&gt; column — so existing users keep everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's in the free lite version
&lt;/h2&gt;

&lt;p&gt;The lite version is MIT-licensed and on GitHub:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Word-start search, category browsing, favorites, full CRUD&lt;/li&gt;
&lt;li&gt;The two-database setup, with a seed DB you replace with your own content&lt;/li&gt;
&lt;li&gt;A clean &lt;code&gt;flutter analyze&lt;/code&gt; and passing tests&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What the full version adds
&lt;/h2&gt;

&lt;p&gt;Three features, and each one taught me something:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Google Drive backup/restore.&lt;/strong&gt; The app's data lives in Drive's app-data folder, with silent auto-backup and change detection, plus export/import through the share sheet. Buyers plug in their own OAuth client ID — nothing of mine ships in the kit. One gotcha: &lt;code&gt;google_sign_in&lt;/code&gt; is pinned at ^6.3.0, because the v7 API changes the auth flow and the &lt;code&gt;extension_google_sign_in_as_googleapis_auth&lt;/code&gt; bridge expects the v6 shape.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On-device OCR scan-to-create.&lt;/strong&gt; Take a photo of a page, and ML Kit reads the text. The text is kept for reference and search — but nothing is ever auto-filled. I learned that the hard way: my first version auto-filled the title from OCR and put a "$20" price sticker in the Title field. Manual entry after the photo, every time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Per-item photos&lt;/strong&gt; from camera or gallery, backed up along with the rest.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pricing
&lt;/h2&gt;

&lt;p&gt;The lite version is free on GitHub. The full version is $49 at launch (going to $99), one-time, unlimited personal and commercial projects.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Free lite: &lt;a href="https://github.com/Majician13/flutter-offline-starter" rel="noopener noreferrer"&gt;https://github.com/Majician13/flutter-offline-starter&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Full version: &lt;a href="https://4308559011616.gumroad.com/l/footings" rel="noopener noreferrer"&gt;https://4308559011616.gumroad.com/l/footings&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you're building an offline-first Flutter app, I'd love to hear what your data layer looks like — and what you'd want a starter kit to do that this one doesn't.&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>dart</category>
      <category>sqlite</category>
      <category>opensource</category>
    </item>
    <item>
      <title>iOS vs Android vs Flutter: What Each Choice Costs in India</title>
      <dc:creator>krishna kumar</dc:creator>
      <pubDate>Tue, 17 Nov 2026 19:02:39 +0000</pubDate>
      <link>https://dev.to/krishna_kumar_ecc1e764686/ios-vs-android-vs-flutter-what-each-choice-costs-in-india-490e</link>
      <guid>https://dev.to/krishna_kumar_ecc1e764686/ios-vs-android-vs-flutter-what-each-choice-costs-in-india-490e</guid>
      <description>&lt;p&gt;If you are building for Indian users, the platform question is usually the first one in the room, and it is not as simple as “Android is cheaper.” For the same features, a native Android app and a native iOS app cost about the same to build. What changes the bill is how many platforms you ship, and whether you write one codebase or two.&lt;/p&gt;

&lt;h2&gt;
  
  
  Android first
&lt;/h2&gt;

&lt;p&gt;Android still has most of the users in India. If your first customers are small-business buyers, local service users or anyone on a mid-range phone, launching on Google Play alone is a reasonable way to keep version one tight. The trade-off is testing: Android means many screen sizes and OS versions. That work is already baked into a normal Indian agency estimate, which is why Android is not meaningfully cheaper than iOS for the same scope.&lt;/p&gt;

&lt;h2&gt;
  
  
  When iOS is worth doing first
&lt;/h2&gt;

&lt;p&gt;iOS can be a little faster to test because there are fewer devices. It matters more if you are selling to premium buyers, or if the US or UK is part of the plan from day one. Apple’s developer programme is a yearly fee, and App Store review is stricter, but those are process costs, not a reason the build itself should be dramatically higher.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two native apps
&lt;/h2&gt;

&lt;p&gt;Building Android and iOS as two separate native apps usually costs about 1.7 to 2 times a single platform, not a clean double, because some design, backend and planning work is shared. You still have two interface codebases to write, two stores to submit, and two places to fix bugs later. Choose this when you need native performance, heavy graphics, or deep access to the phone’s hardware.&lt;/p&gt;

&lt;h2&gt;
  
  
  Flutter and React Native
&lt;/h2&gt;

&lt;p&gt;A Flutter or React Native app in India usually costs ₹2 lakh to ₹30 lakh depending on features, and often comes in 25 to 40 percent below two native apps because one codebase serves both stores. Flutter (Google) and React Native (Meta) are both mature and widely used for ecommerce, booking, edtech, fitness, delivery and internal tools. They are a poor fit when the product is a game-like experience or depends on unusual device APIs. For most business apps, they are the better value if you need both stores in the first release.&lt;/p&gt;

&lt;h2&gt;
  
  
  A web app or PWA
&lt;/h2&gt;

&lt;p&gt;A web app or progressive web app usually costs about 15 to 25 percent less than a single native app. It is the right first step when users mostly work on laptops, or when you want to test demand before paying for store apps. You do not get the same push-notification or offline behaviour as a native app, and some users will still ask where the app is. If the product needs the camera, GPS or true offline use, start on mobile.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to compare the options on paper
&lt;/h2&gt;

&lt;p&gt;The clean way is to freeze the feature list, then price the same list four ways: Android only, iOS only, Flutter for both stores, and two native apps. A free &lt;a href="https://mgtechlabs.com/mobile-app-price-cost-development-calculator-india/" rel="noopener noreferrer"&gt;app development cost calculator&lt;/a&gt; built around Indian agency rates will do that in a few minutes. It asks ten questions, including platform, and returns an indicative range in rupees and dollars plus a timeline. You can also choose “I have no idea” and let it default to a cross-platform suggestion.&lt;/p&gt;

&lt;p&gt;Put the result next to your user mix, not next to a competitor’s logo. If most of your buyers are on Android and you are still proving the idea, one platform is enough. If you already have demand in both stores, paying once for a Flutter codebase is usually cheaper than paying twice for native — and cheaper still than discovering, three months in, that you needed the other store after all.&lt;/p&gt;

</description>
      <category>android</category>
      <category>ios</category>
      <category>flutter</category>
      <category>india</category>
    </item>
    <item>
      <title>Flutter + Jetson Video: Decode Backpressure and Adaptive Stream Quality</title>
      <dc:creator>vmodal_ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 18:35:24 +0000</pubDate>
      <link>https://dev.to/vmodal_ai/flutter-jetson-video-decode-backpressure-and-adaptive-stream-quality-ofe</link>
      <guid>https://dev.to/vmodal_ai/flutter-jetson-video-decode-backpressure-and-adaptive-stream-quality-ofe</guid>
      <description>&lt;p&gt;A live stream can overwhelm a mobile client when decode, texture upload, and display cannot keep pace. The solution is end-to-end backpressure, not merely a smaller widget tree.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measure each stage
&lt;/h2&gt;

&lt;p&gt;Track bitrate, packet loss, jitter, decode time, texture upload cost, and displayed-frame age. Distinguish network delay from client decode delay.&lt;/p&gt;

&lt;h2&gt;
  
  
  Negotiate quality at the source
&lt;/h2&gt;

&lt;p&gt;If supported, let the client request lower resolution or frame rate based on sustained measurements, not a single spike.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep control traffic independent
&lt;/h2&gt;

&lt;p&gt;Video congestion should not block commands, health messages, or critical notifications. Use separate channels and priorities.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bound jitter buffering
&lt;/h2&gt;

&lt;p&gt;A larger buffer smooths jitter but increases latency. Set a maximum delay that fits the use case and expose stream health.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate sustained operation
&lt;/h2&gt;

&lt;p&gt;Test roaming, weak signal, thermal throttling, reconnects, and long playback. Check for memory growth and old frames after recovery.&lt;/p&gt;

&lt;h2&gt;
  
  
  Example implementation
&lt;/h2&gt;

&lt;p&gt;This Dart snippet illustrates one part of the design. Adapt types, transport behavior, timestamp semantics, and platform APIs to your actual system before production use.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;StreamHealth&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nc"&gt;StreamHealth&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;required&lt;/span&gt; &lt;span class="k"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;frameAgeMs&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;required&lt;/span&gt; &lt;span class="k"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;decodeMs&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;required&lt;/span&gt; &lt;span class="k"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;droppedFrames&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="kt"&gt;double&lt;/span&gt; &lt;span class="n"&gt;frameAgeMs&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="kt"&gt;double&lt;/span&gt; &lt;span class="n"&gt;decodeMs&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;droppedFrames&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

  &lt;span class="kt"&gt;bool&lt;/span&gt; &lt;span class="n"&gt;get&lt;/span&gt; &lt;span class="n"&gt;shouldRequestLowerQuality&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt;
      &lt;span class="n"&gt;frameAgeMs&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;350&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="n"&gt;decodeMs&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;40&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="n"&gt;droppedFrames&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Performance checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Measure p95/p99 behavior on target hardware, not only a desktop simulator.&lt;/li&gt;
&lt;li&gt;Bound queues and buffers; define what may be coalesced or dropped.&lt;/li&gt;
&lt;li&gt;Keep heavy parsing, image processing, and inference away from the Flutter UI thread.&lt;/li&gt;
&lt;li&gt;Track source timestamps, sequence numbers, stale-data rate, and dropped updates.&lt;/li&gt;
&lt;li&gt;Test network degradation, reconnects, sustained operation, and resource pressure.&lt;/li&gt;
&lt;li&gt;Keep control commands and critical alerts separate from replaceable telemetry.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Useful Links
&lt;/h2&gt;

&lt;p&gt;Website: &lt;a href="http://www.v-modal.com" rel="noopener noreferrer"&gt;www.v-modal.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Flutter: &lt;a href="https://github.com/v-modal/vmodal_sdk_flutter" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_flutter&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Android: &lt;a href="https://github.com/v-modal/vmodal_sdk_android" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_android&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Discord: &lt;a href="https://discord.gg/K72z28KUx" rel="noopener noreferrer"&gt;https://discord.gg/K72z28KUx&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Reddit: &lt;a href="https://www.reddit.com/r/v_modal/" rel="noopener noreferrer"&gt;https://www.reddit.com/r/v_modal/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>jetson</category>
      <category>backpressure</category>
    </item>
    <item>
      <title>Accelerating ROS 2 Perception with NVIDIA Isaac ROS</title>
      <dc:creator>vmodal_ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 18:33:26 +0000</pubDate>
      <link>https://dev.to/vmodal_ai/accelerating-ros-2-perception-with-nvidia-isaac-ros-10a1</link>
      <guid>https://dev.to/vmodal_ai/accelerating-ros-2-perception-with-nvidia-isaac-ros-10a1</guid>
      <description>&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;A ROS 2 perception graph can spend substantial time copying images&lt;br&gt;
between nodes, converting formats, and running CPU-based preprocessing&lt;br&gt;
before inference.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this guide covers
&lt;/h2&gt;

&lt;p&gt;This tutorial focuses on practical architecture and performance&lt;br&gt;
engineering for production systems. The central principle is to measure&lt;br&gt;
the complete pipeline, keep latency-sensitive work close to the&lt;br&gt;
hardware, and make failure states visible to the operator.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reference architecture
&lt;/h2&gt;

&lt;p&gt;Camera driver → ROS 2 image pipeline → Isaac ROS accelerated node(s) →&lt;br&gt;
detection/pose/SLAM output → planner/controller. Use supported&lt;br&gt;
GPU-accelerated components and compatible message formats where&lt;br&gt;
possible.&lt;/p&gt;

&lt;h2&gt;
  
  
  Implementation plan
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt; Choose the ROS 2 distribution, JetPack/Ubuntu base, and Isaac ROS
release as a compatible set.&lt;/li&gt;
&lt;li&gt; Start from a supported Isaac ROS reference workflow rather than
mixing arbitrary container images.&lt;/li&gt;
&lt;li&gt; Profile topic frequency, message size, node execution time, and
end-to-end sensor-to-result latency.&lt;/li&gt;
&lt;li&gt; Use image transport/compression and zero-copy/intra-process options
only where supported and validated.&lt;/li&gt;
&lt;li&gt; Measure the full graph under concurrent workloads, not just isolated
model inference.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Example
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# Typical first checks in a ROS 2 workspace (adapt to your installation).\nros2 topic hz /camera/image_raw\nros2 topic info /camera/image_raw\nros2 node list\nros2 topic hz /detections
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The snippets are illustrative starting points, not drop-in integrations.&lt;br&gt;
Match APIs and version requirements to the exact SDK, OS image, hardware&lt;br&gt;
revision, and runtime in your project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Performance checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  Measure end-to-end latency, not only one function or model
invocation.&lt;/li&gt;
&lt;li&gt;  Report p50 and p95/p99 latency alongside throughput, memory use, and
dropped work.&lt;/li&gt;
&lt;li&gt;  Bound queues and define what happens when consumers fall behind.&lt;/li&gt;
&lt;li&gt;  Avoid repeated frame copies and expensive work on Flutter's UI
isolate.&lt;/li&gt;
&lt;li&gt;  Test sustained workloads after the device reaches thermal
equilibrium.&lt;/li&gt;
&lt;li&gt;  Keep UI state, device state, and robot state distinct.&lt;/li&gt;
&lt;li&gt;  Add timeouts, cancellation, reconnection, and explicit stale-data
indicators.&lt;/li&gt;
&lt;li&gt;  Profile on the actual target hardware using a reproducible build.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Common pitfalls
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  Do not assume every Isaac ROS package supports every Jetson
generation or ROS 2 release.&lt;/li&gt;
&lt;li&gt;  Avoid running incompatible CUDA/container versions together.&lt;/li&gt;
&lt;li&gt;  A faster inference node does not guarantee a faster sensor-to-action
pipeline.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Hands-on exercise
&lt;/h2&gt;

&lt;p&gt;Measure input topic rate and detection output rate before and after&lt;br&gt;
enabling an accelerated component. Record dropped messages and&lt;br&gt;
end-to-end delay.&lt;/p&gt;

&lt;h2&gt;
  
  
  Further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;a href="https://docs.flutter.dev/perf/best-practices" rel="noopener noreferrer"&gt;Flutter performance best
practices&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://docs.flutter.dev/tools/devtools" rel="noopener noreferrer"&gt;Flutter DevTools&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://developer.android.com/" rel="noopener noreferrer"&gt;Android Developers&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://developer.nvidia.com/" rel="noopener noreferrer"&gt;NVIDIA Developer&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://docs.ros.org/" rel="noopener noreferrer"&gt;ROS 2 documentation&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Useful Links
&lt;/h2&gt;

&lt;p&gt;Website: &lt;a href="http://www.v-modal.com" rel="noopener noreferrer"&gt;www.v-modal.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Flutter: &lt;a href="https://github.com/v-modal/vmodal_sdk_flutter" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_flutter&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Android: &lt;a href="https://github.com/v-modal/vmodal_sdk_android" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_android&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Discord: &lt;a href="https://discord.gg/K72z28KUx" rel="noopener noreferrer"&gt;https://discord.gg/K72z28KUx&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Reddit: &lt;a href="https://www.reddit.com/r/v_modal/" rel="noopener noreferrer"&gt;https://www.reddit.com/r/v_modal/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>android</category>
      <category>edgeai</category>
    </item>
    <item>
      <title>ROS 2 to Flutter: A Practical Telemetry Bridge</title>
      <dc:creator>vmodal_ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 18:31:47 +0000</pubDate>
      <link>https://dev.to/vmodal_ai/ros-2-to-flutter-a-practical-telemetry-bridge-43dh</link>
      <guid>https://dev.to/vmodal_ai/ros-2-to-flutter-a-practical-telemetry-bridge-43dh</guid>
      <description>&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;ROS 2 topics are designed for robot software, not directly for a mobile&lt;br&gt;
Flutter app. Exposing the entire ROS graph to a phone can create&lt;br&gt;
security, bandwidth, and compatibility problems.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this guide covers
&lt;/h2&gt;

&lt;p&gt;This tutorial focuses on practical architecture and performance&lt;br&gt;
engineering for production systems. The central principle is to measure&lt;br&gt;
the complete pipeline, keep latency-sensitive work close to the&lt;br&gt;
hardware, and make failure states visible to the operator.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reference architecture
&lt;/h2&gt;

&lt;p&gt;ROS 2 nodes → selected topic adapter/bridge → authenticated gateway →&lt;br&gt;
WebSocket messages → Dart repository → Flutter widgets. Use a&lt;br&gt;
schema-controlled API and expose only the topics the app needs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Implementation plan
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt; List required topics and define message contracts before
implementing the UI.&lt;/li&gt;
&lt;li&gt; Use rosbridge or a dedicated ROS 2 gateway when appropriate, but
place it behind authentication and network controls.&lt;/li&gt;
&lt;li&gt; Convert high-rate messages into sampled summaries for display;
retain raw-rate processing inside ROS where possible.&lt;/li&gt;
&lt;li&gt; Use timestamps and sequence numbers to detect stale or out-of-order
telemetry.&lt;/li&gt;
&lt;li&gt; Make reconnect and resubscribe behavior explicit, and display data
freshness.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Example
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;RobotTelemetry&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;\&lt;span class="n"&gt;n&lt;/span&gt;  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nc"&gt;RobotTelemetry&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="n"&gt;required&lt;/span&gt; &lt;span class="k"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;receivedAt&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;required&lt;/span&gt; &lt;span class="k"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;batteryPct&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;required&lt;/span&gt; &lt;span class="k"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;mode&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;\&lt;span class="n"&gt;n&lt;/span&gt;  &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="nc"&gt;DateTime&lt;/span&gt; &lt;span class="n"&gt;receivedAt&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;\&lt;span class="n"&gt;n&lt;/span&gt;  &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="kt"&gt;double&lt;/span&gt; &lt;span class="n"&gt;batteryPct&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;\&lt;span class="n"&gt;n&lt;/span&gt;  &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="kt"&gt;String&lt;/span&gt; &lt;span class="n"&gt;mode&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;\&lt;span class="n"&gt;n&lt;/span&gt;\&lt;span class="n"&gt;n&lt;/span&gt;  &lt;span class="kt"&gt;bool&lt;/span&gt; &lt;span class="n"&gt;get&lt;/span&gt; &lt;span class="n"&gt;isStale&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nc"&gt;DateTime&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;difference&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;receivedAt&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt;\&lt;span class="n"&gt;n&lt;/span&gt;      &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nc"&gt;Duration&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;seconds&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;\&lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The snippets are illustrative starting points, not drop-in integrations.&lt;br&gt;
Match APIs and version requirements to the exact SDK, OS image, hardware&lt;br&gt;
revision, and runtime in your project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Performance checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  Measure end-to-end latency, not only one function or model
invocation.&lt;/li&gt;
&lt;li&gt;  Report p50 and p95/p99 latency alongside throughput, memory use, and
dropped work.&lt;/li&gt;
&lt;li&gt;  Bound queues and define what happens when consumers fall behind.&lt;/li&gt;
&lt;li&gt;  Avoid repeated frame copies and expensive work on Flutter's UI
isolate.&lt;/li&gt;
&lt;li&gt;  Test sustained workloads after the device reaches thermal
equilibrium.&lt;/li&gt;
&lt;li&gt;  Keep UI state, device state, and robot state distinct.&lt;/li&gt;
&lt;li&gt;  Add timeouts, cancellation, reconnection, and explicit stale-data
indicators.&lt;/li&gt;
&lt;li&gt;  Profile on the actual target hardware using a reproducible build.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Common pitfalls
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  Do not let a UI disconnect stop a robot safety node.&lt;/li&gt;
&lt;li&gt;  Do not trust messages from arbitrary clients on a flat Wi-Fi
network.&lt;/li&gt;
&lt;li&gt;  Use the ROS 2 distribution and bridge version supported by your
robot image.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Hands-on exercise
&lt;/h2&gt;

&lt;p&gt;Display battery, mode, and connection freshness. Simulate a 3-second&lt;br&gt;
network outage and verify that stale values are visibly marked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;a href="https://docs.flutter.dev/perf/best-practices" rel="noopener noreferrer"&gt;Flutter performance best
practices&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://docs.flutter.dev/tools/devtools" rel="noopener noreferrer"&gt;Flutter DevTools&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://developer.android.com/" rel="noopener noreferrer"&gt;Android Developers&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://developer.nvidia.com/" rel="noopener noreferrer"&gt;NVIDIA Developer&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://docs.ros.org/" rel="noopener noreferrer"&gt;ROS 2 documentation&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Useful Links
&lt;/h2&gt;

&lt;p&gt;Website: &lt;a href="http://www.v-modal.com" rel="noopener noreferrer"&gt;www.v-modal.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Flutter: &lt;a href="https://github.com/v-modal/vmodal_sdk_flutter" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_flutter&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Android: &lt;a href="https://github.com/v-modal/vmodal_sdk_android" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_android&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Discord: &lt;a href="https://discord.gg/K72z28KUx" rel="noopener noreferrer"&gt;https://discord.gg/K72z28KUx&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Reddit: &lt;a href="https://www.reddit.com/r/v_modal/" rel="noopener noreferrer"&gt;https://www.reddit.com/r/v_modal/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ros2</category>
      <category>flutter</category>
      <category>websocket</category>
      <category>rosbridge</category>
    </item>
    <item>
      <title>Flutter + Robotics: Resilient Reconnects and Offline Telemetry Buffers</title>
      <dc:creator>vmodal_ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 18:30:17 +0000</pubDate>
      <link>https://dev.to/vmodal_ai/flutter-robotics-resilient-reconnects-and-offline-telemetry-buffers-1on4</link>
      <guid>https://dev.to/vmodal_ai/flutter-robotics-resilient-reconnects-and-offline-telemetry-buffers-1on4</guid>
      <description>&lt;p&gt;This advanced tutorial treats Flutter as the operator-facing presentation layer while wearable SDKs, Jetson services, ROS 2 nodes, and NVIDIA-accelerated inference handle device-specific or compute-heavy work. The goal is predictable latency, bounded memory, useful observability, and graceful degradation—not simply maximizing message throughput.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Architecture note:&lt;/strong&gt; Keep safety-critical control loops on the robot. A Flutter app is not a hard real-time controller and must not be the sole safety mechanism.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  1. Define measurable service objectives
&lt;/h2&gt;

&lt;p&gt;Track freshness, event-to-display latency, throughput, frame pacing, CPU, memory, network use, battery, thermal state, dropped messages, reconnect time, and command acknowledgements. Do not use a single FPS number to represent the entire system: a smooth screen can still display stale data.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Instrument the complete path
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;sensor capture
  -&amp;gt; native/ROS processing
  -&amp;gt; gateway publish
  -&amp;gt; Flutter receive
  -&amp;gt; state accepted
  -&amp;gt; widget build
  -&amp;gt; frame rendered
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Record source and receive timestamps separately. Use monotonic clocks for elapsed durations within a process. When comparing devices, account for clock offset and uncertainty.&lt;/p&gt;

&lt;p&gt;Profile on a physical target in profile mode and inspect Flutter DevTools' Performance view. Debug-mode timing is not a reliable production baseline. See &lt;a href="https://docs.flutter.dev/tools/devtools/performance" rel="noopener noreferrer"&gt;https://docs.flutter.dev/tools/devtools/performance&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Establish a repeatable baseline
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Start from a clean launch.&lt;/li&gt;
&lt;li&gt;Connect to the robot or replay a fixed trace.&lt;/li&gt;
&lt;li&gt;Run a representative scenario for several minutes.&lt;/li&gt;
&lt;li&gt;Record frame times, memory, CPU, message rates, stale-data counts, and reconnects.&lt;/li&gt;
&lt;li&gt;Change one variable at a time.&lt;/li&gt;
&lt;li&gt;Compare p50, p95, and p99 latency, not just averages.
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;PipelineMetrics&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;received&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;accepted&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;dropped&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;stale&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;uiPublishes&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Use bounded metric windows or histograms; do not store every sample forever.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Separate acquisition from presentation
&lt;/h2&gt;

&lt;p&gt;High-rate sources should not directly trigger widget rebuilds. Use a latest-value cache for state-like data, bounded queues for events that must be preserved, and a controlled presentation cadence.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;LatestValue&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="no"&gt;T&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="no"&gt;T&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="n"&gt;_value&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;_version&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

  &lt;span class="kt"&gt;void&lt;/span&gt; &lt;span class="nf"&gt;put&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="no"&gt;T&lt;/span&gt; &lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;_value&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="n"&gt;_version&lt;/span&gt;&lt;span class="o"&gt;++&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;

  &lt;span class="no"&gt;T&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="n"&gt;get&lt;/span&gt; &lt;span class="n"&gt;value&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;_value&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;get&lt;/span&gt; &lt;span class="n"&gt;version&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;_version&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replacing an older pending value may be acceptable for battery, pose, or temperature. Commands, alarms, and audit events need a separate reliable path and explicit acknowledgement semantics.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Make buffering bounded
&lt;/h2&gt;

&lt;p&gt;Every queue needs a maximum capacity, an overflow policy, a drop/replacement counter, and an owner responsible for recovery.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Latest wins:&lt;/strong&gt; pose, preview frames, current detections.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Drop old items:&lt;/strong&gt; display-oriented streams where freshness matters.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Persist:&lt;/strong&gt; events that must survive disconnection.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reject with feedback:&lt;/strong&gt; commands that cannot safely be queued.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An unbounded telemetry or log list turns overload into memory growth rather than a visible, measurable condition.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Protect the Flutter frame budget
&lt;/h2&gt;

&lt;p&gt;Keep parsing, filtering, and transformations out of &lt;code&gt;build()&lt;/code&gt;. Split screens into independently updating sections and avoid rebuilding camera or map widgets for unrelated state changes.&lt;/p&gt;

&lt;p&gt;For CPU-heavy pure Dart work, benchmark &lt;code&gt;compute&lt;/code&gt; or a dedicated isolate with realistic payload sizes. Isolates have startup and message-transfer costs. For hardware acceleration or platform APIs, prefer a native service designed for that workload.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Keep robotics compute near the robot
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Sensors -&amp;gt; ROS 2 / accelerated nodes -&amp;gt; Jetson gateway
                                      |
                             compact UI-facing state
                                      |
                         WebSocket / MQTT / gRPC
                                      |
                              Flutter client
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;NVIDIA Isaac ROS provides accelerated, low-latency ROS 2 packages for Jetson and other NVIDIA platforms. Keep image processing, inference, and robot control on the compute side; send Flutter only the information needed for visualization and operator decisions. See &lt;a href="https://nvidia-isaac-ros.github.io/" rel="noopener noreferrer"&gt;https://nvidia-isaac-ros.github.io/&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Treat stale data as a first-class state
&lt;/h2&gt;

&lt;p&gt;Carry source timestamp, receive timestamp, sequence number/version, source identity, and optional confidence or quality. The UI must distinguish zero from unknown, disconnected, and stale. Do not show a green health indicator just because the last payload was healthy.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Validate graceful degradation
&lt;/h2&gt;

&lt;p&gt;Simulate network delay and packet loss, bursts, robot process restarts, wearable permission loss, camera interruptions, inference slowdown, low memory, and thermal throttling. Under pressure, reduce preview resolution or update frequency and pause nonessential charts—but preserve command and safety status visibility.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. Release checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Frame-time baseline captured on physical hardware&lt;/li&gt;
&lt;li&gt;[ ] p50/p95/p99 event-to-display latency measured&lt;/li&gt;
&lt;li&gt;[ ] Queues bounded and overflow observable&lt;/li&gt;
&lt;li&gt;[ ] High-frequency state coalesced before UI updates&lt;/li&gt;
&lt;li&gt;[ ] Commands and alarms use reliable semantics&lt;/li&gt;
&lt;li&gt;[ ] Clock domains and stale-data rules documented&lt;/li&gt;
&lt;li&gt;[ ] Network and reconnect behavior tested&lt;/li&gt;
&lt;li&gt;[ ] Thermal and memory pressure scenarios tested&lt;/li&gt;
&lt;li&gt;[ ] Robot safety remains independent of the mobile app&lt;/li&gt;
&lt;li&gt;[ ] Performance budgets enforced in repeatable tests&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Advanced focus: Reconnect and offline buffers
&lt;/h2&gt;

&lt;p&gt;Use exponential backoff with jitter and bounded buffers only for events that genuinely need replay. Current pose and camera frames are generally not useful to replay after reconnect. Do not blindly retry commands unless they are idempotent or have deduplication IDs. On reconnect, request a fresh snapshot and mark old values stale.&lt;/p&gt;

&lt;h2&gt;
  
  
  Implementation exercise
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Add timestamps and sequence IDs at the gateway boundary.&lt;/li&gt;
&lt;li&gt;Capture a normal-load trace and a burst-load trace.&lt;/li&gt;
&lt;li&gt;Implement a bounded buffer and an explicit overload policy.&lt;/li&gt;
&lt;li&gt;Display stale/disconnected/degraded states separately.&lt;/li&gt;
&lt;li&gt;Profile on the target device and compare p50, p95, and p99 results.&lt;/li&gt;
&lt;li&gt;Document which events may be coalesced and which must be preserved.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;The strongest performance gains usually come from controlling the whole data pipeline: acquisition, processing, filtering, transport, state updates, and rendering. Keep compute close to the hardware, bound every queue, measure freshness as well as frame rate, and keep safety-critical behavior independent of the Flutter client.&lt;/p&gt;

&lt;h2&gt;
  
  
  Useful Links
&lt;/h2&gt;

&lt;p&gt;Website: &lt;a href="http://www.v-modal.com" rel="noopener noreferrer"&gt;www.v-modal.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Flutter: &lt;a href="https://github.com/v-modal/vmodal_sdk_flutter" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_flutter&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Android: &lt;a href="https://github.com/v-modal/vmodal_sdk_android" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_android&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Discord: &lt;a href="https://discord.gg/K72z28KUx" rel="noopener noreferrer"&gt;https://discord.gg/K72z28KUx&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Reddit: &lt;a href="https://www.reddit.com/r/v_modal/" rel="noopener noreferrer"&gt;https://www.reddit.com/r/v_modal/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>robotics</category>
      <category>network</category>
    </item>
    <item>
      <title>Physical AI Performance: Build a Repeatable Sim-to-Real Workflow</title>
      <dc:creator>vmodal_ai</dc:creator>
      <pubDate>Tue, 17 Nov 2026 18:29:00 +0000</pubDate>
      <link>https://dev.to/vmodal_ai/physical-ai-performance-build-a-repeatable-sim-to-real-workflow-3jf8</link>
      <guid>https://dev.to/vmodal_ai/physical-ai-performance-build-a-repeatable-sim-to-real-workflow-3jf8</guid>
      <description>&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;Simulation can accelerate development, but performance numbers from a&lt;br&gt;
simulator do not directly predict real robot timing, sensor noise, GPU&lt;br&gt;
contention, or actuator constraints.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this guide covers
&lt;/h2&gt;

&lt;p&gt;This tutorial focuses on practical architecture and performance&lt;br&gt;
engineering for production systems. The central principle is to measure&lt;br&gt;
the complete pipeline, keep latency-sensitive work close to the&lt;br&gt;
hardware, and make failure states visible to the operator.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reference architecture
&lt;/h2&gt;

&lt;p&gt;Scenario definition → simulation and synthetic data → policy/model&lt;br&gt;
training → validation suite → ROS 2 integration → Jetson deployment →&lt;br&gt;
telemetry and real-world evaluation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Implementation plan
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt; Define task success and safety metrics before tuning performance.&lt;/li&gt;
&lt;li&gt; Keep simulation and deployment model versions, preprocessing,
coordinate frames, and thresholds traceable.&lt;/li&gt;
&lt;li&gt; Profile simulation throughput separately from policy inference
latency and control-loop timing.&lt;/li&gt;
&lt;li&gt; Test perturbations: lighting, texture, sensor noise, occlusion,
payload, and timing jitter.&lt;/li&gt;
&lt;li&gt; Deploy with a staged rollout, conservative limits, logging, and
rollback to a known-good model.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Example
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# Example release metadata to track alongside each model artifact.\nmodel_id: grasp-policy-2026-10-01\ninput_contract: rgbd_640x480_v2\ncoordinate_frame: base_link\nvalidation_suite: warehouse_pick_v4\nlatency_budget_ms: 40
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The snippets are illustrative starting points, not drop-in integrations.&lt;br&gt;
Match APIs and version requirements to the exact SDK, OS image, hardware&lt;br&gt;
revision, and runtime in your project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Performance checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  Measure end-to-end latency, not only one function or model
invocation.&lt;/li&gt;
&lt;li&gt;  Report p50 and p95/p99 latency alongside throughput, memory use, and
dropped work.&lt;/li&gt;
&lt;li&gt;  Bound queues and define what happens when consumers fall behind.&lt;/li&gt;
&lt;li&gt;  Avoid repeated frame copies and expensive work on Flutter's UI
isolate.&lt;/li&gt;
&lt;li&gt;  Test sustained workloads after the device reaches thermal
equilibrium.&lt;/li&gt;
&lt;li&gt;  Keep UI state, device state, and robot state distinct.&lt;/li&gt;
&lt;li&gt;  Add timeouts, cancellation, reconnection, and explicit stale-data
indicators.&lt;/li&gt;
&lt;li&gt;  Profile on the actual target hardware using a reproducible build.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Common pitfalls
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  Do not equate more simulation frames per second with better
real-world policy quality.&lt;/li&gt;
&lt;li&gt;  Avoid changing preprocessing between simulation and deployment
without validation.&lt;/li&gt;
&lt;li&gt;  Keep human supervision and physical safety controls in place during
field testing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Hands-on exercise
&lt;/h2&gt;

&lt;p&gt;Create a release checklist that records simulation metrics, hardware&lt;br&gt;
latency, robustness tests, and rollback instructions for one policy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;a href="https://docs.flutter.dev/perf/best-practices" rel="noopener noreferrer"&gt;Flutter performance best
practices&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://docs.flutter.dev/tools/devtools" rel="noopener noreferrer"&gt;Flutter DevTools&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://developer.android.com/" rel="noopener noreferrer"&gt;Android Developers&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://developer.nvidia.com/" rel="noopener noreferrer"&gt;NVIDIA Developer&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://docs.ros.org/" rel="noopener noreferrer"&gt;ROS 2 documentation&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Useful Links
&lt;/h2&gt;

&lt;p&gt;Website: &lt;a href="http://www.v-modal.com" rel="noopener noreferrer"&gt;www.v-modal.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Flutter: &lt;a href="https://github.com/v-modal/vmodal_sdk_flutter" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_flutter&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SDK Android: &lt;a href="https://github.com/v-modal/vmodal_sdk_android" rel="noopener noreferrer"&gt;https://github.com/v-modal/vmodal_sdk_android&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Discord: &lt;a href="https://discord.gg/K72z28KUx" rel="noopener noreferrer"&gt;https://discord.gg/K72z28KUx&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Reddit: &lt;a href="https://www.reddit.com/r/v_modal/" rel="noopener noreferrer"&gt;https://www.reddit.com/r/v_modal/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>android</category>
      <category>edgeai</category>
    </item>
    <item>
      <title>Designing a commitment device: why our Windows focus timer has no stop button, and how it notices a force-close</title>
      <dc:creator>Liza Bhadana</dc:creator>
      <pubDate>Tue, 17 Nov 2026 16:47:54 +0000</pubDate>
      <link>https://dev.to/liza_18827c15bdd387c4cd9c/designing-a-commitment-device-why-our-windows-focus-timer-has-no-stop-button-and-how-it-notices-a-p9f</link>
      <guid>https://dev.to/liza_18827c15bdd387c4cd9c/designing-a-commitment-device-why-our-windows-focus-timer-has-no-stop-button-and-how-it-notices-a-p9f</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; &lt;a href="https://apps.microsoft.com/detail/9N3F281GJT5T?cid=devto-no-quit" rel="noopener noreferrer"&gt;SeaSweep&lt;/a&gt;, a free Windows study app, makes a study session hard to quit in three layers: no stop button in the UI, a window that minimises instead of closing, and a check on the next launch that marks a killed session as failed. None of it is unbreakable. It is designed so that quitting takes a deliberate decision instead of a reflex.&lt;/p&gt;

&lt;p&gt;Students search for &lt;em&gt;a focus timer you can't quit halfway&lt;/em&gt;. Building one is a UX problem more than a technical one: how strict can a timer be before it feels like a trap?&lt;/p&gt;

&lt;h2&gt;
  
  
  Layer 1: what does the UI allow?
&lt;/h2&gt;

&lt;p&gt;The sailing screen is wrapped in &lt;code&gt;PopScope(canPop: false)&lt;/code&gt;. There is no stop, pause or "end early" button. The only way out is time.&lt;/p&gt;

&lt;p&gt;To keep that fair, the strictness is moved to &lt;strong&gt;before&lt;/strong&gt; the session:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every route (10 to 180 minutes) can be shortened with a slider down to &lt;strong&gt;5 minutes&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Starting needs a &lt;strong&gt;hold of about 1.4 seconds&lt;/strong&gt; on the sail button, so a stray click cannot launch a three-hour session.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Layer 2: what happens when the user clicks X?
&lt;/h2&gt;

&lt;p&gt;On desktop, Flutter's &lt;code&gt;window_manager&lt;/code&gt; lets you intercept close:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;windowManager&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;setPreventClose&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="nd"&gt;@override&lt;/span&gt;
&lt;span class="kt"&gt;void&lt;/span&gt; &lt;span class="nf"&gt;onWindowClose&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;store&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;active&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="k"&gt;null&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;          &lt;span class="c1"&gt;// a session is sailing&lt;/span&gt;
    &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;windowManager&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;minimize&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;    &lt;span class="c1"&gt;// X minimises instead&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="c1"&gt;// otherwise close normally&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Meanwhile a guard checks the foreground window every 0.7 seconds. During a session it closes Task Manager, the Windows Settings apps page and "Uninstall a program". The privacy text says uninstall protection only applies during a session and can be turned off in Settings when no session is sailing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Layer 3: how does it notice a force-close?
&lt;/h2&gt;

&lt;p&gt;You cannot run code after your process is killed, so the check runs on the &lt;strong&gt;next&lt;/strong&gt; launch. The guard lives inside the app process and sets a static &lt;code&gt;running = true&lt;/code&gt; when a session starts. A fresh process starts with &lt;code&gt;running = false&lt;/code&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="c1"&gt;// simplified from store.dart checkActiveVoyage()&lt;/span&gt;
&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nc"&gt;DesktopGuard&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;running&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nc"&gt;DesktopGuard&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;arrived&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;finish&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;active&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;failed&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;   &lt;span class="c1"&gt;// process restarted mid-session&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;now&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;isBefore&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;active&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;end&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;finish&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;active&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;failed&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;  &lt;span class="c1"&gt;// time is up&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;So if a saved active session exists but the guard in this process is not running, the app was killed or the laptop restarted. The session is saved as failed: zero pieces swept, no shells, and it does not extend the day streak, which only counts days with a finished session. The screen says &lt;em&gt;"Your ship lost contact and drifted home."&lt;/em&gt; It does not scold.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why not make it truly unbreakable?
&lt;/h2&gt;

&lt;p&gt;Because a user-mode Windows app cannot be, and claiming otherwise would be a lie. Admin rights, safe mode, or simply pulling the plug all work. The design goal is narrower: make the moment of temptation cost a few deliberate steps, and make the consequence visible but small.&lt;/p&gt;

&lt;h2&gt;
  
  
  What could be better?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;An "emergency" exit that is allowed but logged, for real interruptions. Right now the honest advice is: pick a short session if you might be interrupted.&lt;/li&gt;
&lt;li&gt;A clearer warning on the plan screen for sessions over two hours.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;Mechanism&lt;/th&gt;
&lt;th&gt;Can a user bypass it?&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;UI&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;canPop: false&lt;/code&gt;, no stop button&lt;/td&gt;
&lt;td&gt;no, only time ends it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Window&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;setPreventClose&lt;/code&gt; + minimise on X&lt;/td&gt;
&lt;td&gt;yes, by killing the process&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Self-protection&lt;/td&gt;
&lt;td&gt;close Task Manager / uninstall pages&lt;/td&gt;
&lt;td&gt;partly, with effort&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Consequence&lt;/td&gt;
&lt;td&gt;failed on next launch (no shells, no streak day)&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Try it:&lt;/strong&gt; &lt;a href="https://apps.microsoft.com/detail/9N3F281GJT5T?cid=devto-no-quit" rel="noopener noreferrer"&gt;SeaSweep on the Microsoft Store&lt;/a&gt; (free, no ads, Windows, Store ID 9N3F281GJT5T).&lt;/p&gt;




&lt;p&gt;&lt;em&gt;SeaSweep is made by a 5 Gyres Ambassador and supports the 5 Gyres Institute and Save The Beach. &lt;code&gt;@5gyres&lt;/code&gt; #5GyresAmbassador.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>windows</category>
      <category>ux</category>
      <category>5gyresambassador</category>
    </item>
    <item>
      <title>An allow-list inside a website blocker: how a Windows focus app keeps Wikipedia open while it closes YouTube</title>
      <dc:creator>Liza Bhadana</dc:creator>
      <pubDate>Tue, 17 Nov 2026 16:46:23 +0000</pubDate>
      <link>https://dev.to/liza_18827c15bdd387c4cd9c/an-allow-list-inside-a-website-blocker-how-a-windows-focus-app-keeps-wikipedia-open-while-it-4fbc</link>
      <guid>https://dev.to/liza_18827c15bdd387c4cd9c/an-allow-list-inside-a-website-blocker-how-a-windows-focus-app-keeps-wikipedia-open-while-it-4fbc</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; &lt;a href="https://apps.microsoft.com/detail/9N3F281GJT5T?cid=devto-allowlist" rel="noopener noreferrer"&gt;SeaSweep&lt;/a&gt;, a free Windows study app built in Flutter, reads the title of the window in front of you. If it is a browser and the title contains a study site's name, it returns early, &lt;em&gt;before&lt;/em&gt; any blocking rule runs. That one ordering decision is what lets a student block the whole browser and still read Wikipedia.&lt;/p&gt;

&lt;p&gt;Students ask a version of this all the time: &lt;em&gt;can I block distracting websites but still use Wikipedia and Khan Academy?&lt;/em&gt; Here is how we answered it in code, including the parts that are not clever.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does the app know which site is open?
&lt;/h2&gt;

&lt;p&gt;It does not read URLs. Reading another program's address bar would need a browser extension or accessibility hooks. Instead, every 0.7 seconds during a study session it asks Windows for the foreground window (&lt;code&gt;GetForegroundWindow&lt;/code&gt;), its title (&lt;code&gt;GetWindowTextW&lt;/code&gt;) and the process behind it (&lt;code&gt;QueryFullProcessImageNameW&lt;/code&gt;). Browsers put the page title in the window title, and that is enough.&lt;/p&gt;

&lt;p&gt;Browsers it recognises, by process name: &lt;code&gt;chrome.exe&lt;/code&gt;, &lt;code&gt;msedge.exe&lt;/code&gt;, &lt;code&gt;firefox.exe&lt;/code&gt;, &lt;code&gt;brave.exe&lt;/code&gt;, &lt;code&gt;opera.exe&lt;/code&gt;, &lt;code&gt;vivaldi.exe&lt;/code&gt;, &lt;code&gt;arc.exe&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What order do the checks run in?
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="c1"&gt;// simplified from desktop_guard.dart&lt;/span&gt;
&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;exe&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="s1"&gt;'taskmgr.exe'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="k"&gt;lock&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Task Manager'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;      &lt;span class="c1"&gt;// protect the app itself&lt;/span&gt;
&lt;span class="c1"&gt;// ... Settings &amp;gt; Apps and "Uninstall a program" too&lt;/span&gt;
&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;browsers&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;contains&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;exe&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;studySites&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;any&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;contains&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="k"&gt;null&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// allow-list wins&lt;/span&gt;
&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;exe&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="k"&gt;null&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;exe&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;exe&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="k"&gt;lock&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;label&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;closeWindow&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;site&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="k"&gt;null&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;browsers&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;contains&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;exe&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;contains&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;site&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="k"&gt;lock&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;label&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;closeTab&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Self-protection first.&lt;/strong&gt; Task Manager and the uninstall pages are closed during a session.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The allow-list second.&lt;/strong&gt; &lt;code&gt;wikipedia&lt;/code&gt;, &lt;code&gt;khan academy&lt;/code&gt;, &lt;code&gt;bitesize&lt;/code&gt;, &lt;code&gt;duckduckgo&lt;/code&gt; and &lt;code&gt;r/studying&lt;/code&gt;, lower-cased and matched against the lower-cased title.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Block rules last.&lt;/strong&gt; Programs by &lt;code&gt;.exe&lt;/code&gt;, websites by a word in the title.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Because step 2 runs before step 3, a user can dock &lt;strong&gt;the browser itself&lt;/strong&gt; as a program (pick &lt;code&gt;chrome.exe&lt;/code&gt; from the list of running apps). A study-site tab in front passes; any other tab in front matches the &lt;code&gt;.exe&lt;/code&gt; rule, and the &lt;strong&gt;whole window&lt;/strong&gt; gets &lt;code&gt;WM_CLOSE&lt;/code&gt;, background study tabs included. So strict mode means "keep only study tabs in that browser". It is not per-tab precision, and it should not be sold as that.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why those five sites?
&lt;/h2&gt;

&lt;p&gt;They are the sites the app's own &lt;strong&gt;Sources&lt;/strong&gt; screen opens. Sources searches the Wikipedia API and builds search links for Khan Academy, BBC Bitesize, DuckDuckGo (PDF notes) and r/studying. If the app sends you somewhere to study, it would be absurd to close that tab. The allow-list is that promise, kept in one constant.&lt;/p&gt;

&lt;h2&gt;
  
  
  How is a tab closed without closing the browser?
&lt;/h2&gt;

&lt;p&gt;Focus the window (&lt;code&gt;SetForegroundWindow&lt;/code&gt;), then synthesise Ctrl+W with &lt;code&gt;keybd_event&lt;/code&gt;. A blocked program gets &lt;code&gt;PostMessageW(hwnd, WM_CLOSE)&lt;/code&gt; instead, the same message as clicking its X. After a lock, the guard waits four seconds before it can lock again, so lock screens do not stack.&lt;/p&gt;

&lt;h2&gt;
  
  
  What are the honest limits?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Title matching is fuzzy in both directions.&lt;/strong&gt; A YouTube video whose title contains "Khan Academy" passes the allow-list. A distracting site whose title does not contain a blocked word is not caught.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Only the foreground window is checked.&lt;/strong&gt; Audio from a background tab keeps playing until you bring it forward.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The allow-list is fixed.&lt;/strong&gt; A student cannot add their school's learning site yet, so for them "dock the whole browser" is too strict. That is the most obvious next feature.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It is not a security tool.&lt;/strong&gt; Someone determined can get around any user-mode blocker. The goal is friction at the moment of temptation, not a lock.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Quick reference
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Check&lt;/th&gt;
&lt;th&gt;Matches on&lt;/th&gt;
&lt;th&gt;Action&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Self-protection&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;taskmgr.exe&lt;/code&gt;, Settings apps, Uninstall&lt;/td&gt;
&lt;td&gt;close window&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Allow-list&lt;/td&gt;
&lt;td&gt;browser + title contains a study site&lt;/td&gt;
&lt;td&gt;do nothing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Docked program&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;.exe&lt;/code&gt; name&lt;/td&gt;
&lt;td&gt;close window&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Docked website&lt;/td&gt;
&lt;td&gt;browser + title contains the site word&lt;/td&gt;
&lt;td&gt;close tab (Ctrl+W)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Try it:&lt;/strong&gt; &lt;a href="https://apps.microsoft.com/detail/9N3F281GJT5T?cid=devto-allowlist" rel="noopener noreferrer"&gt;SeaSweep on the Microsoft Store&lt;/a&gt; (free, Windows, Store ID 9N3F281GJT5T).&lt;/p&gt;




&lt;p&gt;&lt;em&gt;SeaSweep is made by a 5 Gyres Ambassador and supports the 5 Gyres Institute and Save The Beach. &lt;code&gt;@5gyres&lt;/code&gt; #5GyresAmbassador. Earlier in this series: &lt;a href="https://dev.to/liza_18827c15bdd387c4cd9c/how-to-block-video-games-on-pc-while-studying-matching-launchers-by-exe-and-game-sites-by-tab-34ma"&gt;how to block video games on PC while studying&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>productivity</category>
      <category>windows</category>
      <category>5gyresambassador</category>
    </item>
    <item>
      <title>Bahá’í Reader for everyone: rebuilt with Flutter</title>
      <dc:creator>Tim Apple</dc:creator>
      <pubDate>Tue, 17 Nov 2026 15:54:35 +0000</pubDate>
      <link>https://dev.to/ninepointlabs/bahai-reader-for-everyone-rebuilt-with-flutter-2fgc</link>
      <guid>https://dev.to/ninepointlabs/bahai-reader-for-everyone-rebuilt-with-flutter-2fgc</guid>
      <description>&lt;p&gt;&lt;a href="https://bahaireader.org/" rel="noopener noreferrer"&gt;Bahá’í Reader&lt;/a&gt;, the offline prayer book and Writings reader, started out as a GTK app for Linux. We've rebuilt it with Flutter, so the same reader now runs on &lt;strong&gt;Linux, Windows and Android&lt;/strong&gt;. Version 1.0 is the first release of the new app.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Flutter
&lt;/h2&gt;

&lt;p&gt;Let's get one thing out of the way: we're still Omarchy users. Most of what we make at Nine Point Labs is built for Linux and Omarchy first, and that isn't changing.&lt;/p&gt;

&lt;p&gt;Bahá’í Reader is a little different. A prayer book is something you reach for on whatever is in front of you: the family laptop, a phone at a devotional gathering, the computer at work. The people who could use it aren't all running Linux, and an app full of prayers and the Writings should be shared with whoever needs it. Flutter lets us keep one codebase and ship it to many platforms, so a fix or a new feature reaches everyone at once.&lt;/p&gt;

&lt;h2&gt;
  
  
  Same reader, new home
&lt;/h2&gt;

&lt;p&gt;Before switching, we listed every feature of the GTK app and worked through them one by one, so the move wouldn't cost anyone the things they rely on. What you know is still here:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Offline, and private.&lt;/strong&gt; English is bundled. Other languages download only when you ask, and nothing else ever uses the network. No accounts, no analytics, no telemetry.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The library and search.&lt;/strong&gt; Writings grouped by book, prayers grouped by category, and a search that ignores accents and apostrophes, so "Bahaullah" finds "Bahá’u’lláh".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Highlights, notes and saved passages&lt;/strong&gt;, plus &lt;strong&gt;Copy with citation&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Today and the obligatory prayers.&lt;/strong&gt; The Badí‘ date (changing at sunset), sun times for your city, your obligatory prayer's window with a private "Said today", the next Feast and Holy Day, the Fast, the passage of the day and the Alláh-u-Abhá counter.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Light, Dark and Sepia&lt;/strong&gt;, and on Omarchy it still follows your live theme.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you used the GTK app on Linux, the first start brings over your highlights, notes, saved passages, collections, reading places and settings. The old app's files are only read, never changed, so nothing is lost if you go back.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it runs today
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Linux&lt;/strong&gt;, where we use it every day: the &lt;code&gt;.deb&lt;/code&gt;, &lt;code&gt;.rpm&lt;/code&gt;, Arch/Omarchy package, AppImage and Flatpak bundle are all there, or install it with autonomix-cli.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Windows&lt;/strong&gt; (64-bit): an installer that doesn't need administrator rights, or a zip. Last night I tested it on Windows myself, and it works well. It isn't code-signed yet, so SmartScreen may warn you the first time; choose &lt;strong&gt;More info&lt;/strong&gt;, then &lt;strong&gt;Run anyway&lt;/strong&gt;. Reminders aren't sent on Windows yet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Android&lt;/strong&gt; (7 and up, phones and tablets): an APK you install from the download page. The phone opens on a Today tab, and reminders arrive even with the app closed.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What's left: macOS and iOS
&lt;/h2&gt;

&lt;p&gt;The Flutter project already has the starting pieces for macOS and iOS, but neither has been built or tested. Building for Apple platforms needs a Mac, and we don't have one yet. When we get one, macOS and iOS are next. Until then we'd rather say "not yet" than ship something we haven't tried.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get it
&lt;/h2&gt;

&lt;p&gt;Downloads for every platform are on &lt;a href="https://bahaireader.org/" rel="noopener noreferrer"&gt;bahaireader.org&lt;/a&gt; and the &lt;a href="https://github.com/ninepointlabs/bahai-reader/releases" rel="noopener noreferrer"&gt;GitHub releases page&lt;/a&gt;. On Linux, autonomix-cli keeps it up to date:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;autonomix-cli add https://github.com/ninepointlabs/bahai-reader
autonomix-cli install bahai-reader
&lt;span class="c"&gt;# or, if you already track it:&lt;/span&gt;
autonomix-cli update
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The source is &lt;a href="https://github.com/ninepointlabs/bahai-reader" rel="noopener noreferrer"&gt;on GitHub&lt;/a&gt;. The code is MIT licensed; the texts and translations are not, and &lt;code&gt;DATA-NOTICE.md&lt;/code&gt; has the details. This is a free, independent community app, not an official publication of a Bahá’í institution.&lt;/p&gt;

&lt;p&gt;Thank you to everyone who has prayed, read and studied with Bahá’í Reader so far. It's a joy to be able to share it with more people.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally posted on &lt;a href="https://blog.ninepointlabs.com/2026/11/bahai-reader-for-everyone/" rel="noopener noreferrer"&gt;blog.ninepointlabs.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>linux</category>
      <category>opensource</category>
      <category>android</category>
    </item>
    <item>
      <title>How we built MemberKeep: renewal dates that don't drift and a revenue number you can trust</title>
      <dc:creator>Stacklyn Labs</dc:creator>
      <pubDate>Tue, 17 Nov 2026 14:00:00 +0000</pubDate>
      <link>https://dev.to/stacklyn_labs/how-we-built-memberkeep-renewal-dates-that-dont-drift-and-a-revenue-number-you-can-trust-30b6</link>
      <guid>https://dev.to/stacklyn_labs/how-we-built-memberkeep-renewal-dates-that-dont-drift-and-a-revenue-number-you-can-trust-30b6</guid>
      <description>&lt;p&gt;A member joins a gym on January 31. They pay monthly. When is their next renewal?&lt;/p&gt;

&lt;p&gt;February 28, obviously. And the one after that? If your answer is March 28, you've just written the bug we spent a surprising amount of time on.&lt;/p&gt;

&lt;p&gt;MemberKeep is our offline Flutter app for businesses with recurring members: gyms, clubs, coworking spaces, coaches, freelancers. It tracks members, plans, renewal dates and expected monthly revenue, all on the device. Here's how three of its core parts work, and why we built them that way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Renewals are counted from the join date
&lt;/h2&gt;

&lt;p&gt;The naive way to renew is "take the last renewal date and add one cycle":&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="c1"&gt;// simplified: the drifting version&lt;/span&gt;
&lt;span class="n"&gt;DateTime&lt;/span&gt; &lt;span class="nf"&gt;nextRenewal&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;DateTime&lt;/span&gt; &lt;span class="n"&gt;previous&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="n"&gt;DateTime&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;previous&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;year&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;previous&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;month&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;previous&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;day&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Dart's &lt;code&gt;DateTime&lt;/code&gt; rolls overflow forward, so January 31 plus a month lands in early March. Clamp it to the end of February and you get the 28th. Then the next step starts from the 28th, and the member's billing day is now the 28th forever. Nobody notices until a client asks why their invoices moved.&lt;/p&gt;

&lt;p&gt;So MemberKeep doesn't chain renewals. Every renewal is calculated from the join date, and only clamped when the month is too short:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="c1"&gt;// simplified&lt;/span&gt;
&lt;span class="n"&gt;DateTime&lt;/span&gt; &lt;span class="nf"&gt;addMonthsClamped&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;DateTime&lt;/span&gt; &lt;span class="n"&gt;anchor&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;months&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="n"&gt;first&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;DateTime&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;anchor&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;year&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;anchor&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;month&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;months&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="n"&gt;lastDay&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;DateTime&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;first&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;year&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;first&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;month&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;day&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;DateTime&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;first&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;year&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;first&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;month&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;min&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;anchor&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;day&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;lastDay&lt;/span&gt;&lt;span class="p"&gt;));&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// nth monthly renewal for a member&lt;/span&gt;
&lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="n"&gt;due&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;addMonthsClamped&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;member&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;joinedOn&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A member who joined on January 31 renews on February 28, then March 31. That's the behaviour the app ships with, and version 2.0.0 also made Renew Now follow the plan's own cycle instead of assuming monthly.&lt;/p&gt;

&lt;p&gt;Two related decisions fell out of this. Auto-renew is set per member, and overdue dates move forward when the app starts. And if you change a plan's billing cycle, the app recalculates its members' renewal dates, but warns you first, because that's a change you want to make on purpose.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1yygo5qwv51zmug407x6.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1yygo5qwv51zmug407x6.webp" alt="MemberKeep member profile with renewal date, auto-renew toggle and PDF invoice button" width="800" height="583"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  One number for revenue, whatever the cycle
&lt;/h2&gt;

&lt;p&gt;Plans can bill daily, weekly, monthly or yearly. The dashboard shows a single figure: expected monthly revenue from active members. If you just add up prices, a yearly plan and a daily plan get summed as if they were the same thing.&lt;/p&gt;

&lt;p&gt;The fix is boring and that's the point. Every cycle is converted to a monthly amount before anything is added. In Riverpod 3 with &lt;code&gt;riverpod_generator&lt;/code&gt;, that's a small derived provider:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="c1"&gt;// simplified; conversion factors are illustrative&lt;/span&gt;
&lt;span class="n"&gt;extension&lt;/span&gt; &lt;span class="kd"&gt;on&lt;/span&gt; &lt;span class="n"&gt;BillingCycle&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kt"&gt;double&lt;/span&gt; &lt;span class="kd"&gt;get&lt;/span&gt; &lt;span class="n"&gt;perYear&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt; &lt;span class="k"&gt;switch&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;this&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;BillingCycle&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;daily&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;365&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="n"&gt;BillingCycle&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;weekly&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;52&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="n"&gt;BillingCycle&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;monthly&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;12&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="n"&gt;BillingCycle&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;yearly&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="p"&gt;};&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="nd"&gt;@riverpod&lt;/span&gt;
&lt;span class="kt"&gt;double&lt;/span&gt; &lt;span class="nf"&gt;expectedMonthlyRevenue&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;Ref&lt;/span&gt; &lt;span class="n"&gt;ref&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="n"&gt;members&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;ref&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;watch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;activeMembersProvider&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;members&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;fold&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mf"&gt;0.0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;sum&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="n"&gt;price&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;priceOverride&lt;/span&gt; &lt;span class="o"&gt;??&lt;/span&gt; &lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;plan&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;price&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;sum&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;price&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;m&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;plan&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;cycle&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;perYear&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;12&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Notice &lt;code&gt;priceOverride&lt;/code&gt;. A member can have their own price, and leaving it blank falls back to the plan price. The Analytics tab converts prices the same way for its donut chart of revenue by plan category. Getting those two numbers to agree was one of the fixes in version 2.0.0.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2ereax0rgbqyv5gvw6b0.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2ereax0rgbqyv5gvw6b0.webp" alt="MemberKeep revenue dashboard with expected monthly revenue and member search" width="800" height="583"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The data is encrypted, and the key isn't next to it
&lt;/h2&gt;

&lt;p&gt;Member records are names, emails, phone numbers and what people pay. There's no server, so the phone is the only place they live. We wanted that data to be unreadable if someone copied the app's files.&lt;/p&gt;

&lt;p&gt;Members, plans and settings sit in an AES-encrypted Hive CE database. The key is generated once and kept in the platform's secure storage (Keychain on iOS, Keystore on Android) through &lt;code&gt;flutter_secure_storage&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="c1"&gt;// simplified&lt;/span&gt;
&lt;span class="n"&gt;Future&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;Box&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;Member&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;openMembers&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="kd"&gt;async&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;storage&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;FlutterSecureStorage&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
  &lt;span class="kd"&gt;var&lt;/span&gt; &lt;span class="n"&gt;key&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;storage&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;read&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nl"&gt;key:&lt;/span&gt; &lt;span class="s"&gt;'db_key'&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="kc"&gt;null&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;key&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;base64UrlEncode&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;Hive&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;generateSecureKey&lt;/span&gt;&lt;span class="p"&gt;());&lt;/span&gt;
    &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;storage&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;write&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nl"&gt;key:&lt;/span&gt; &lt;span class="s"&gt;'db_key'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;value:&lt;/span&gt; &lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;Hive&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;openBox&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;Member&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;(&lt;/span&gt;
    &lt;span class="s"&gt;'members'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;encryptionCipher:&lt;/span&gt; &lt;span class="n"&gt;HiveAesCipher&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;base64Url&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;decode&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;)),&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On top of that there's an optional app lock. The PIN (4 or 6 digits) is stored as a salted PBKDF2 hash, never as the digits. After 5 wrong attempts the app waits 30 seconds, and the wait doubles up to 30 minutes. Biometrics work where the device supports them, and the app locks again after 30 seconds in the background.&lt;/p&gt;

&lt;p&gt;Backups follow the same thinking. They're password-protected &lt;code&gt;.mkbkp&lt;/code&gt; files using AES-256-GCM, so a backup sitting in someone's Downloads folder isn't a plain list of your members. Restore shows a preview first and rolls back if it fails.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it doesn't do
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No backend, no sync.&lt;/strong&gt; Data stays on one device. Moving to a new phone means making a backup and restoring it there.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It ships with ads.&lt;/strong&gt; There are AdMob interstitials with a Google UMP consent form. &lt;code&gt;AppConfig.enableAds&lt;/code&gt; turns them off completely.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The web preview is just the interface.&lt;/strong&gt; Ads, local notifications, biometrics and secure storage need a real Android or iOS device.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reminders stay on the phone.&lt;/strong&gt; Renewal reminders are local notifications with no push server behind them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Under the hood: Flutter 3.47, Dart 3.13, Riverpod 3, Hive CE, Android 7.0 (minSdk 24) and iOS 15 and up, English and Spanish, 37 currencies, 55 unit and widget tests and a GitHub Actions workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Web preview: &lt;a href="https://guide.stacklynlabs.com/memberkeep/preview/" rel="noopener noreferrer"&gt;https://guide.stacklynlabs.com/memberkeep/preview/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Android APK: &lt;a href="https://drive.google.com/file/d/12IZt7--xt76IhG8WDU3_aSvdRffKIbaj/view?usp=sharing" rel="noopener noreferrer"&gt;https://drive.google.com/file/d/12IZt7--xt76IhG8WDU3_aSvdRffKIbaj/view?usp=sharing&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Product page: &lt;a href="https://stacklynlabs.com/product/memberkeep/" rel="noopener noreferrer"&gt;https://stacklynlabs.com/product/memberkeep/&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The source code is $29 on the product page.&lt;/p&gt;

&lt;p&gt;How does your app handle the January 31 member? Chained renewals, anchored to the join date, or something else entirely?&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>dart</category>
      <category>showdev</category>
      <category>riverpod</category>
    </item>
  </channel>
</rss>
