本站已进行升级,老用户可以通过找回密码登录。

24h Intel · 81 條

Flutter 24小時情報 GitHub 熱門倉庫與技術資訊

每日彙總 Flutter / Dart GitHub 熱門倉庫,以及 Dev.to、freeCodeCamp、Hacker News、Medium、Reddit 的近期技術資訊,追蹤 24 小時 Stars 增量與社群討論。

更新於 11/19 下午10:086 個來源

GitHub

20 條

Dart 與 Flutter 相關倉庫熱度

Dev.to

12 條

開發者文章與專案分享

Flutter or React Native? How we choose for client apps
11/19 下午10:00

Flutter or React Native? How we choose for client apps

Silver Scintilla

Clients often arrive having already been told which framework they should use. The honest answer is that both Flutter and React Native are solid choices in 2026, and the decision usually comes down to four practical questions rather than technical superiority. If you have React developers, or a React website, React Native lets them work on the mobile app too. The language is the same, patterns are familiar, and some logic can be shared with the web. If you have no JavaScript team, that advantage disappears, and Flutter's more structured approach is often easier to keep tidy over years of changes. Flutter draws every pixel itself. That makes it excellent for distinctive, animation-heavy designs that must look identical on both platforms. React Native uses the platform's own components, so apps tend to feel native by default and follow each platform's conventions with less effort. For an app that should feel like a normal iPhone or Android app, that is an advantage. Both handle camera, location, notifications, payments and Bluetooth well, usually through existing plugins. The difference appears with unusual hardware or SDKs, where you may need native code. Check availability for your specific needs before choosing — we do this during discovery rather than after. This is the question most often skipped. Consider which framework the people maintaining the app will know, how easy it is to hire for it in your market, and how disruptive framework upgrades have been historically. Both projects are actively maintained and upgrade paths are manageable, but they do need planning. Cross-platform is the efficient default for most business apps. We suggest native Swift or Kotlin when the app depends on heavy graphics or processing, when it must adopt brand-new platform features the moment they launch, or when it is tightly built around one platform's ecosystem, such as a Watch-first fitness product. One codebase is cheaper than two, but the saving is bigger in maintenance than in the first build. Every future feature, fix and OS update is done once instead of twice. That compounding saving is usually the strongest argument for cross-platform. If you are weighing this up for a specific product, we are happy to give an honest recommendation, including "stay native" when that is the right answer. Originally published on the Silver Scintilla blog.

flutterreactnativemobilecrossplatform
Building CleanSync: why the rupee sign shaped our PDF code, and why ads ship switched off
11/19 下午10:00

Building CleanSync: why the rupee sign shaped our PDF code, and why ads ship switched off

Stacklyn Labs

The job is done. The cleaner is packing the vacuum into the car, and the client wants the invoice before they leave. On WhatsApp, please. That moment drove more of CleanSync's design than any feature list. CleanSync is our offline Flutter app for independent cleaners, small agencies and property managers: jobs with a timer and checklist, client properties, PDF estimates and invoices, and profit and expense tracking. No backend, no Firebase project, no accounts. Everything lives in a Hive CE database on the phone. Below are the questions we kept asking while building it, and what we decided. A PDF generated on a phone only knows the fonts you give it. The pdf package's built-in fonts don't cover symbols like ₹, so a cleaner in India gets a box where the currency should be. It's the kind of bug a developer in a euro or dollar market never sees in testing. We bundle Noto Sans and use it as the PDF's base font, so €, £ and ₹ print correctly: // simplified Future<pw.Document> newInvoiceDoc() async { final data = await rootBundle.load('assets/fonts/NotoSans-Regular.ttf'); final font = pw.Font.ttf(data); return pw.Document(theme: pw.ThemeData.withFont(base: font)); } The UI font, Outfit, is bundled too. The project uses google_fonts, but only with bundled files, so nothing is downloaded at runtime. That's what lets the app work without a connection from the very first launch, not just after it has cached something. Sharing goes through the phone's own share sheet, which means WhatsApp, email or whatever the cleaner uses. In the web preview the PDF is saved as a file instead. A cleaning invoice is partly a receipt and partly evidence. "Did you do the oven?" is a real question clients ask. So the checklist does two jobs. While working, ticking every task marks the job Completed automatically. Afterwards, the invoice includes a checklist audit showing which tasks were done, along with a unique number like INV-20261022-A1B2. // simplified: a provider method void toggleTask(Job job, int index) { job.checklist[index].done = !job.checklist[index].done; if (job.checklist.every((t) => t.done)) { job.status = JobStatus.completed; } job.save(); // Hive CE object notifyListeners(); } State is plain Provider: PropertyProvider, SettingsProvider and StatsProvider over typed Hive CE models. Jobs also carry a start, pause and reset timer whose time is saved with the job, and a pre-job estimate PDF uses the same checklist with an estimated total. Not in our view. Version 1.1.2 made that the default. The project still includes the Google Mobile Ads SDK for optional interstitials. But AdConfig.enabled is false out of the box. With it off, the app shows no ads, shows no consent form and makes no ad requests. Release ad unit IDs are clear placeholders, and no ad is requested while a placeholder is set. The source contains no AdMob IDs belonging to us; the App ID is Google's official sample ID, which the SDK needs to start. When a developer does turn ads on, the rules are deliberately tight. An ad may appear only after a job is completed, at most 2 per session, at least 3 minutes apart, with a Google UMP consent form where the law requires it. // simplified class AdGate { int _shown = 0; DateTime? _last; bool canShowAfterJob() { if (!AdConfig.enabled) return false; if (AdConfig.interstitialId.startsWith('YOUR_')) return false; if (_shown >= 2) return false; final last = _last; if (last != null && DateTime.now().difference(last) < const Duration(minutes: 3)) { return false; } return true; } void markShown() { _shown++; _last = DateTime.now(); } } Why after a completed job? Because that's the one moment nobody is in the middle of something. An interstitial on top of the job timer would be awful. The in-app privacy policy only mentions AdMob when ads are enabled, and an ADS.md file covers setup and how to remove the SDK completely. In a few small files, each with one job. App name, company, support email and website are in one BrandConfig file. All colours are named tokens in one theme file. Ad settings sit separately in AdConfig. The launcher icon and splash are generated from your own image with flutter_launcher_icons and flutter_native_splash. No team features. No backend and no user accounts, so there's no shared job list between cleaners. Data lives on one phone, and moving it means a .zip backup (photos included). The web build is a developer preview. No notifications, ads or share sheet there. No ad credentials. If you want ads, you bring your own AdMob account, App IDs and ad unit IDs. Reminders are mobile-only. Job reminders are local notifications one hour before each pending job, on Android and iOS. Stack: Flutter 3.47 or newer, Dart 3.13 or newer, Provider, Hive CE, Android with Flutter's default SDK levels and iOS 15.0 and up, 29 unit and widget tests. Web preview: https://guide.stacklynlabs.com/cleansync/preview/ Android APK: https://dri

flutterdartshowdevprivacy
What is Focus on Windows 11, and why doesn't it block apps? Notifications vs the window in front
11/19 下午09:52

What is Focus on Windows 11, and why doesn't it block apps? Notifications vs the window in front

Liza Bhadana

Short answer: Focus on Windows 11 is a timed session that turns on Do not disturb and pauses taskbar flashing and badges. It handles incoming distractions (notifications). It does not close or block apps, so it cannot stop outgoing ones, the moment you open YouTube yourself. That second job needs a program that watches the window in front of you, which is what SeaSweep, a free Windows study app, does during a study session. "What is focus on Windows 11?" appeared in Google's People Also Ask for focus-app searches on two separate reads this month, and "Can Focus disable apps?" sits next to it for "does windows 11 focus session block apps". The confusion is understandable: the feature is called Focus, so people expect it to keep them focused. Here is what it actually controls, and where the line is. According to Microsoft Support, a focus session by default: shows a focus timer; turns on Do not disturb automatically; temporarily turns off flashing and badges of apps on the taskbar; sends a notification when the session ends (you can also end it early). You start one from the clock or notification bell on the taskbar (Windows key + N), from the Clock app ("Start focus session", with optional breaks), or from Settings → System → Focus. Microsoft sums it up as temporarily blocking notifications, sounds and alerts. Every item on that list is about signals coming in. None is about what you are allowed to open. Because it is a notification feature, not an access-control feature. Microsoft's page describes no option to close, lock or hide an app. During a session, Discord, Steam and every browser tab work exactly as before. They just stay quiet until you look at them. That split is easy to state as a table: Distraction Example Windows 11 Focus A foreground-window blocker Incoming a Discord ping, a badge on the taskbar muted not its job Outgoing you open YouTube "for one video" nothing happens the tab is closed Escape hatch you open Task Manager to quit nothing happens closed too (in SeaSweep) It has to look at what is on screen and act on it. In SeaSweep the whole check is one small function on a timer. A simplified excerpt from desktop_guard.dart: // every 0.7 s while a voyage sails final w = _Win.foreground(); // GetForegroundWindow + process name + title if (w == null || w.isSelf) return; final hit = _match(w); // docked app? docked site? Task Manager? if (hit == null) return; if (DateTime.now().difference(_lastLock) < const Duration(seconds: 4)) return; locked.value = LockEvent(hit.$1, hit.$2, () => _close(w, hit.$3)); The user sees an "is locked" screen, then the docked tab is closed (Ctrl+W) or the docked app's window is closed. A few study sites (Wikipedia, Khan Academy, BBC Bitesize, DuckDuckGo, r/studying) are left alone when they are the tab in front, even in a docked browser. The important design point is scope: this only runs during a voyage, a session of 10 to 180 minutes that the user can shorten to 5 before starting. Outside a voyage nothing is watched or closed. SeaSweep doesn't: nothing in its source changes Windows notification settings. Whatever the trade-offs, the practical result is that the two features stack instead of competing: Start a Windows focus session for the incoming side. Start a SeaSweep voyage of the same length for the outgoing side. My view as the writer: changing a system-wide setting is a bigger ask of a user than closing the apps they picked themselves, so leaving notifications to Windows is the less surprising choice. A user-mode app cannot be unbreakable. Killing SeaSweep is possible; the voyage is then recorded as failed on the next launch. Matching is by process name and tab title, so a site with an unusual title can slip through. It is Windows only, and it blocks only during a voyage, never permanently. Windows 11 Focus = timer + Do not disturb + quiet taskbar. It does not block apps. A blocker has to watch the foreground window and close what you docked. Use both: Focus for notifications, a voyage for the apps you would open yourself. Try it: SeaSweep on the Microsoft Store (free, no ads, Windows, Store ID 9N3F281GJT5T). Source for Windows Focus: Microsoft Support, "Focus: Stay on Task Without Distractions in Windows", read 18 November 2026. SeaSweep is made by a 5 Gyres Ambassador and supports the 5 Gyres Institute and Save The Beach. @5gyres #5GyresAmbassador.

windowsproductivityflutter5gyresambassador
The chat list should move like the chat: animated message previews
11/19 下午08:20

The chat list should move like the chat: animated message previews

Frank Milvus

Animated chat previews Flutter draws in the chats list are the first thing a person sees after opening the app, yet for a long time ours were plain text. The conversation itself had motion — animated emoji in bubbles — while the list that summarised it stayed completely still. Fixing that turned out to be less about animation and more about parsing, prefixes and two tabs that quietly render the same rows. This is what the second pass taught us, and why the safest implementation is the one that refuses to animate too much. The message bubble is the easy case. A message is either one emoji or it is not, so the bubble can make a single decision and swap one glyph for one animation. A preview is different. It is a compressed line of text that must communicate a whole message in the width of a row. It can be a single emoji, an emoji in the middle of a sentence (nice 🔥), several emoji in a row, a sender prefix, or a draft. If the chat feels alive and the list looks like a database report, the mismatch is noticeable. So the new rule is broader: every registered emoji in the preview animates, wherever it appears. Unregistered emoji and ordinary text stay exactly as they were. There is no special casing for the whole-message case, because the preview is not a message bubble and should not pretend to be one. You cannot find emoji by splitting a string into code units. A single visible emoji can be several code points: a base character, a variation selector, a zero-width joiner, or a whole ZWJ sequence. Splitting naively gives you fragments, and fragments produce nonsense. Dart's characters package gives the right unit: a grapheme cluster, which is what a reader perceives as one character. The preview walks the content grapheme by grapheme, buffering ordinary text and flushing it whenever a registered emoji appears: for (final grapheme in content.characters) { final asset = animatedEmojiAssetFor(grapheme); if (asset == null || animated >= maxInlineEmoji) { buffer.write(grapheme); continue; } flushText(); spans.add( WidgetSpan( alignment: PlaceholderAlignment.middle, child: Semantics( label: grapheme, child: AnimatedEmoji(asset: asset, size: 18), ), ), ); animated++; } flushText(); The result is a Text.rich with a mix of TextSpan and WidgetSpan children. Text keeps the row's style; an emoji becomes a tiny square animation. If nothing in the content matches the registry, the widget returns the original plain Text with its one-line ellipsis, so the common case pays no new cost. The grapheme walk is also why variation selectors behave. A heart that arrives with U+FE0F and a heart without it both normalise to the same registry entry, and neither leaves a stray invisible character in the text buffer. A preview is one line, and one line can hold a dozen emoji. Each animated emoji is a separate looping Lottie widget with its own ticker and its own composition. Ten of them in one row is not a richer preview; it is a battery test. The cap is four animated emoji per preview. The fifth and later stay as text glyphs, even if they are registered. That is deliberately not "animate the first four and drop the rest": the rest remain visible, just static, so the message still reads correctly. Four is a judgment call rather than a measured optimum. It is enough to convey a reaction burst, and low enough that a single row cannot spawn an unbounded number of animations. The important part is that the bound exists in the widget rather than in a comment asking future contributors to be careful. The preview line often starts with a name. Getting that prefix right is most of the work, because it differs by chat type. For a direct message, an incoming message shows the content alone. An outgoing message keeps the localised Me: prefix, so the list distinguishes "them" from "you" without an avatar label. The prefix stays a plain text span; only the part after it is inspected for emoji. That means a person named Me cannot accidentally animate, and a prefix ending in an emoji-looking character is still just text. Groups are a little more involved. A group preview comes in as Alice: hello, so the tile splits at the first colon and space. If the last message was mine, the sender name is replaced with the localised "me" label; otherwise the original name is kept. Either way, the prefix is rebuilt as a text span and the content is passed to the animation parser: final colon = preview.indexOf(': '); if (colon == -1) return (prefix: '', content: preview); return ( prefix: isMe ? '${l10n.me}: ' : preview.substring(0, colon + 2), content: preview.substring(colon + 2), ); The same widget is used by the friend tile and the group tile, so there is one implementation of this split and one place to fix it. The obvious next question is whether the preview needs its own setting. It does not. The existing switch is called Animate emoji-only messages, and its subtitle now mentions the chat-list

showdevflutteranimationperformance
From transcript to tasks: how automatic action-item extraction actually works
11/19 下午08:11

From transcript to tasks: how automatic action-item extraction actually works

Jason Morris

I'm the maker of MeetNote — an AI meeting-notes app (free on Google Play) that records calls, transcribes them, and turns them into decisions and action items. Here's what I learned building the extraction side of it. Every meeting ends the same way: someone says "I'll send that over," someone else nods, and by Monday nobody remembers who promised what. The transcript has the answer — but a 45-minute transcript is not a to-do list. This is how we think about turning raw meeting text into decisions and action items that people actually follow up on. Speech-to-text is a solved-ish problem. Modern models handle multiple speakers, accents, and background noise well enough that the transcript is rarely the bottleneck. The hard part starts after the words are on the page: a transcript is a stream of half-finished sentences, interruptions, and corrections ("no wait, I meant Thursday, not Tuesday"). The first real step is cleaning: diarization (who said what), timestamping, and resolving those self-corrections so the downstream logic works on what people actually meant, not what they first blurted out. Most meeting tools lump everything into "summary." But a decision and an action item are different objects, and conflating them is why follow-ups fail: A decision is a settled fact: "We're launching on the 24th." It needs a record, not an owner. An action item is a commitment: a task, an owner, and (ideally) a due date. "Haider will send the revised pricing by Friday" is three fields, not one sentence. Extracting them means looking for different signals. Decisions usually sit near agreement language ("let's go with…", "agreed", "final call"). Action items sit near commitment language ("I'll…", "can you…", "by Friday") — and the owner is often the speaker, not the person named. The trickiest field is the owner. In real meetings, the owner is implied more often than stated. "Someone should update the deck" has no owner; "I'll take the deck" does, and it's the speaker. A good extractor has to resolve pronouns and speaker identity together — which is exactly why speaker labels matter before any AI summarization runs. When no owner can be resolved, the honest move is to flag it as unassigned rather than guess. A wrong owner is worse than no owner: it creates false confidence that someone is on it. A to-do list that lives in a separate app dies in a separate app. The reason action items should sync into the tools teams already live in — task managers, chat, docs — is that the follow-up happens where the work happens, not where the meeting happened. An export button is a graveyard; a sync is a workflow. Structure before summary. Pulling decisions, questions, and tasks as structured fields first makes the summary better, not worse — the summary can reference the structured items instead of re-deriving them from raw text. Searchable beats summarized. The single most-used feature is not the summary; it's searching the transcript ("what did we decide about pricing?"). Timestamps + speakers make search useful. Keep the human in the loop. AI extraction is a draft, not a verdict. Letting people edit an action item before it syncs is the difference between a tool people trust and one they quietly stop opening. Meetings will keep happening. The goal was never to replace them — it's to make sure the work agreed in them actually leaves the room. MeetNote is free on Google Play — it records and transcribes calls, then turns them into AI notes, decisions, and action items synced with ClickUp, Slack, and Notion. https://www.meetnotepro.com/

showdevaiproductivityflutter
Why I Built a Free Surah Yaseen App in Flutter
11/19 下午07:42

Why I Built a Free Surah Yaseen App in Flutter

Raza

I built Surah Yaseen — Audio & Offline, a free Flutter app by Minha Apps, because I wanted a simple way to read, listen and understand Surah Yaseen every day. Surah Yaseen is the 36th chapter of the Quran, with 83 verses. The app has: clear Arabic text, high-quality MP3 audio with play, pause and repeat, Urdu and English translations, full offline reading, auto-scroll, bookmarks, daily reminders, and sharing. It works completely offline once installed, no account needed. I built it in Flutter so one codebase serves Android now, with iOS to follow. Download it free on Google Play: https://play.google.com/store/apps/details?id=com.minha_apps.surah_yaseen Also read the guide: https://surah-yaseen-app.blogspot.com/2026/11/surah-yaseen-heart-of-quran-how-to-read.html And the listening guide: https://surahyaseenapp.wordpress.com/2026/11/19/how-to-listen-to-surah-yaseen-every-day-audio-translation-and-offline-reading/

flutterandroidquranislamicapp
Flutter JSON Parsing: fromJson, Null Safety and Code Generation
11/19 下午01:24

Flutter JSON Parsing: fromJson, Null Safety and Code Generation

Muhammad Naeem

Almost every Flutter app talks to an API, and almost every API speaks JSON. Dart has no reflection in Flutter, so you can't hand a JSON string to a library and get a typed object back by magic. You either write the mapping yourself or generate it. This post covers both, in the order you'll meet them: jsonDecode, a hand-written model, the null safety traps, nested objects and lists, json_serializable, freezed, and the error messages that show up when something doesn't match. jsonDecode from dart:convert turns a JSON string into plain Dart values: Map<String, dynamic> for objects, List<dynamic> for arrays, and String, int, double, bool or null for the rest. import 'dart:convert'; void main() { const body = '{"id": 7, "name": "Ayesha", "email": null}'; final data = jsonDecode(body) as Map<String, dynamic>; print(data['name']); // Ayesha print(data['id'].runtimeType); // int } You could pass data around your app and read data['name'] everywhere. Don't. Every read is untyped, a typo in a key returns null instead of a compile error, and when the API changes you find out from a crash report. Convert it to a class once, at the edge of your app. The standard pattern is a fromJson factory constructor and a toJson method: class User { const User({required this.id, required this.name, this.email}); final int id; final String name; final String? email; factory User.fromJson(Map<String, dynamic> json) => User( id: json['id'] as int, name: json['name'] as String, email: json['email'] as String?, ); Map<String, dynamic> toJson() => { 'id': id, 'name': name, 'email': email, }; } Usage: final user = User.fromJson(data); print(user.email); // null print(jsonEncode(user.toJson())); // {"id":7,"name":"Ayesha","email":null} The as casts are the important part. They are where the type check happens, and they are where your app will throw if the API sends something you didn't expect. That is a good thing: it fails at the parsing line, with a clear message, instead of three screens later. If you don't want to type these classes by hand, paste a real response into my JSON to Dart converter. It produces this same style of model (plain Dart, json_serializable or freezed), runs in your browser, and doesn't send your JSON anywhere. Dart's null safety only protects you after the data is inside a typed field. The cast from dynamic is where you decide what's allowed to be null, and getting that decision wrong is the most common source of crashes. JSON has one number type. Dart has two. jsonDecode('450') gives you an int, and jsonDecode('450.0') gives you a double. Many APIs send prices as 450 one day and 450.5 the next, so this will eventually crash on a phone: price: json['price'] as double, // throws when the API sends 450 Read every double through num instead: price: (json['price'] as num).toDouble(), One detail that makes this bug sneaky: on Flutter web compiled to JavaScript (the default build), int and double are both JavaScript numbers, so 450 as double succeeds. The same line compiled with dart compile js printed 450, while the Dart VM threw. If you test mainly on web, you can ship this bug to Android and iOS without seeing it once. Reading a key that isn't in the map returns null, the same as a key whose value is null. So json['email'] as String? handles both cases. A field that's required in your class but missing from the response throws: type 'Null' is not a subtype of type 'String' in type cast For each field, decide which of three things it is: Always present: non-nullable type, plain cast (as String). Sometimes missing, and null means something: nullable type (String?, as String?). Sometimes missing, but there's a sensible default: nullable cast plus ??. status: json['status'] as String? ?? 'pending', Don't make everything nullable just to stop crashes. You'll trade one crash at parse time for ! operators and null checks spread through your UI code. Be strict where the API contract is strict, and loose only where it really is optional. From my own work: on a government survey app I'm working on (I can't share details), records were getting stuck on some enumerators' devices and never reached the server. I went through the Postman responses, the Grafana logs and the field notes, and found the cause: in a few scenarios a record was missing an ID in the local database, so the JSON the app sent was not what the server expected, and the server rejected it every time the app retried. Making the parser more lenient would only have hidden the problem. Instead I added an auto-repair step that restores any missing survey ID in the local database before upload, so the server accepts the JSON and the stuck records go through. The lesson: when JSON fails, check the data you're serialising, not just the parsing code. Some backends send "id": "42" in one endpoint and "id": 42 in another. If you can't get the backend fixed, read it with a small he

flutterdartjsonmobile
A ten-second Flutter pause with a visible Skip button
11/19 下午01:18

A ten-second Flutter pause with a visible Skip button

AlyDoit

Tap Amen in AlyDoit’s Flutter app Selah and a separate screen offers a breathing ring, a ten-second countdown, and a Skip button. The visible exit is the detail that makes it work as an optional pause. The chat records Amen before pushing the pause route. If the person chose to keep the prayer, the app saves that too. Then the chat awaits the pause route. When it closes, the chat records completion and scrolls to the new entry. That order gives Skip one job. It closes the pause with the prayer decision already saved. A separate route also gives the countdown a clear lifetime. Flutter’s Navigator documentation A reversible five-second animation controller scales the ring, while a one-second timer updates the number. When the countdown finishes, the timer uses the same close method as Skip. The screen cancels the timer and disposes the animation controller when the route goes away. The countdown and button also explain what will happen without requiring someone to infer it from the ring. Flutter’s AnimationController documentation For a similar interaction, test Skip just before the final tick, system Back during the fade, and leaving and resuming the app during the countdown. If the exit can race the timer, make closing a one-time action. Where elapsed time needs to be exact, compare against a deadline because periodic callbacks can arrive late. Dart’s Timer.periodic documentation This article was generated by an AI agent for AlyDoit using Selah’s source code. The test cases are suggestions.

flutterux
Building an OfferUp-Style Local Marketplace: Geospatial Search, Photo-First Listings and a Phased Build Plan
11/19 下午01:02

Building an OfferUp-Style Local Marketplace: Geospatial Search, Photo-First Listings and a Phased Build Plan

Journeyhorizon

OfferUp looks simple from the outside: take a photo, set a price, and someone nearby messages you. That simplicity is exactly what makes it hard to rebuild. Every step that feels effortless to the user hides a technical decision about geospatial queries, media handling, messaging or trust. This is a developer-focused breakdown of what a local, mobile-first resale marketplace actually needs, based on Journeyhorizon's guide on how to build a marketplace like OfferUp. I've reorganized it around the systems you'll design, with a phased build plan and a list of traps at the end. OfferUp has grown to 56 million monthly active users. It didn't get there by shipping every feature. It got there by obsessing over friction in three moments: Listing: a photo-first flow where creating a listing feels like taking a picture. Discovering: browsing by proximity, so what you see is what you could pick up today. Transacting: making a deal with a stranger feel safe enough to actually meet. The guide's short version: the core architecture has to handle real-time geospatial queries, secure payments, identity verification and a robust messaging system for transactions between strangers. Let's take those one at a time. The source suggests a fairly conventional stack, and there's nothing wrong with conventional here: Layer Suggested option Why it fits Backend Node.js or Python Mature ecosystems for APIs, queues and integrations Mobile React Native or Flutter One codebase for iOS and Android Database PostgreSQL with geospatial extensions Proximity queries without a separate geo service The mobile choice matters more than it looks. A local marketplace is mobile-first by nature: listing happens through the camera and browsing happens on the move. Treating mobile as a wrapper around a web app is the wrong starting point. If you're weighing frameworks, a cross-platform option like Flutter for mobile app development gives you one codebase while keeping camera, location and push notifications native-feeling. The core query is "show me relevant items within N miles of me, ranked sensibly." With PostgreSQL and a geospatial extension, a first version is just a radius query plus a ranking rule: -- sketch: items near the user, newest first SELECT id, title, price FROM listings WHERE status = 'active' AND ST_DWithin(location, :user_point, :radius_meters) ORDER BY created_at DESC LIMIT 50; That's enough to launch. What changes as you grow: Indexing: add a spatial index early. Proximity queries without one get slow fast. Privacy: never expose a seller's exact location. Store precise coordinates, display an approximate area. Ranking: start with distance and recency, then add signals like category interest and engagement once you have behavior data. Freshness: sold items must disappear quickly. Stale listings in a local marketplace waste a buyer's trip and lose their trust. The listing flow is your supply engine. If it takes more than a minute, sellers quit halfway. Engineering priorities: Camera-first entry point that starts with a photo rather than a form Upload in the background while the user fills in title and price Server-side resizing and compression so the feed loads quickly on mobile data Sensible defaults for category and condition to keep required fields minimal The guide notes that advanced features such as AI-powered categorization are things an MVP can skip. Design the pipeline so you can add them later as an async step without changing the user flow. People are meeting strangers, often in parking lots or other public places, to exchange money for goods. Trust is non-negotiable, and much of it lives in your messaging and identity systems: In-app messaging tied to a listing, so conversations have context and can be reviewed if something goes wrong Identity verification to raise the cost of creating throwaway accounts Ratings after a completed deal, so reputation builds over time Reporting and moderation tools with a real workflow behind them, not just a button Sophisticated fraud detection is also listed as something an MVP can postpone. Log the events you'd need for it (account age, message patterns, report history) from day one so you can build it later. One of the more useful points in the source: you don't need in-app payments on day one. Many local marketplaces, including OfferUp in its early days, started cash-only. In-app payments add complexity and compliance requirements. Launch with messaging and meetup coordination, validate the core loop, then add optional payments. When you do add payments, the revenue logic the guide recommends is restrained: featured listings and fees on shipped transactions, without aggressive monetization that degrades the core experience. From the source guide: Full build: 6–9 months from concept to launch, including app store submission. MVP: about 4–5 months, without features like AI categorization or advanced fraud detection. Rushed build: compressing to 3–4 months usually creates

mobileflutterpostgresstartup
Flutter Push Notifications with Firebase: Full Guide
11/19 上午11:01

Flutter Push Notifications with Firebase: Full Guide

Muhammad Uzair

Push notifications are table stakes for any serious mobile app — and Firebase Cloud Messaging (FCM) remains the default choice for Flutter. But between Android 13+ permission changes, iOS APNs quirks, and the three app states (foreground, background, terminated), getting them right takes more than the 5-minute quickstart suggests. This is the complete guide I wish I had. Add the packages: \yaml \ Initialize Firebase before runApp\, and register the background handler before anything else: \`dart // MUST be a top-level function — not a class method @pragma('vm:entry-point') Future main() async { \ The @pragma('vm:entry-point')\ annotation is critical — without it, tree-shaking removes your handler in release builds and background messages silently stop working. This is the #1 "works in debug, broken in production" cause I see in audits. Add google-services.json\ to android/app/\. Apply the plugin in android/app/build.gradle.kts\: \kotlin \ For Android 13+, notification permission is runtime — request it explicitly (see step 4). In the Firebase console: Project Settings → Cloud Messaging → APNs Authentication Key — upload your .p8\ key from Apple Developer. (Use a key, not certificates — keys don't expire yearly.) In Xcode: enable Push Notifications and Background Modes → Remote notifications capabilities. That's it for FCM — no AppDelegate\ changes needed with recent firebase_messaging\ versions. iOS Simulator cannot receive push notifications. You must test on a physical device. This wastes everyone's first afternoon — now it won't waste yours. iOS always needs explicit permission. Android needs it only on 13+: \`dart final settings = await messaging.requestPermission( if (settings.authorizationStatus == AuthorizationStatus.authorized) { \ Pro tip: don't ask on first launch. Ask after the user experiences value — e.g., after their first order ships or first message arrives. Apps that ask at the right moment see 2-3x higher opt-in rates. The token identifies the device. Get it, and listen for refreshes: \`dart // Tokens refresh — always listen and update your backend \ Send the token to your backend mapped to the user account, not just the device — otherwise logged-out devices keep receiving someone else's notifications. This is where most implementations fall apart. You need all three: \`dart // B. BACKGROUND — app minimized // C. TERMINATED — app killed // Taps on notifications (background state) \ For heads-up notifications while in the foreground, pair FCM with flutter_local_notifications\ and create an Android notification channel: \dart \ Firebase Console → Cloud Messaging → Send test message: paste the FCM token, send. Fastest loop for manual testing. Test all three states every time: foreground, background, killed. They behave differently and each has broken in production for someone. Test on low-end Android devices, not just your flagship — OEM battery optimizers (Xiaomi, Huawei, Oppo) aggressively kill background FCM. Document this for your users with a "disable battery optimization" help screen if notifications are core to your app. Background handler missing @pragma('vm:entry-point')\ → silent failure in release Not handling token refresh → notifications stop after token rotation iOS: testing on simulator → nothing will ever arrive Data-only messages on iOS → need content-available: true\ and won't wake a force-quit app Sending to token instead of user → wrong person gets notified after logout No deep-link handling on tap → notification opens the app to the wrong screen Push notifications done right feel like magic; done wrong they're the #1 source of 1-star reviews. Follow the three-state pattern above, test on real devices, and respect the user's attention — every notification should earn its interruption. Need FCM, deep linking, or a full notification system built into your Flutter app? That's exactly what I do — get in touch. Originally published at uzairxdev.online

flutterfirebasefcmnotifications
Build a Bead Sort Puzzle Game in Flutter
11/19 上午11:00

Build a Bead Sort Puzzle Game in Flutter

Muhammad Uzair

When I built Bead Charms: Pixel Sort Puzzle, I started from a craft table. Fuse beads, a lavender pegboard, an iron and a sheet of ironing paper: tap tubes of beads, fill a pixel art picture on the pegboard, then iron it into a keychain charm. The game now has over 100 original pixel art charms across 8 collections, and every level is checked by a solver so there is always a way through. You can see the finished app in the Bead Charms case study. This guide shows how to build the same game in Flutter: the tube-and-pegboard mechanic, the tray, a solver, difficulty that grows step by step, and the ironing payoff. A bead sort puzzle game in Flutter is a puzzle game where the player taps a tube of fuse beads and the top run of matching beads flies onto a pegboard to fill a pixel art picture. Every peg has a target color, and the player sorts the beads by color until the picture is complete. Then the game plays the craft payoff: ironing paper slides over the pegboard, the iron glides across, each bead melts, the paper curls as it peels, and a jump ring and keyring drop on. Bead Charms works exactly this way: 100-plus pixel art charms across 8 collections — Classics, Spooky, Pets, Snacks, Plants, Garden, Winter and Harvest. The mechanic is a cousin of the water sort puzzle, but the pegboard changes the rules: in a water sort game, a tube is either the source or the destination. Here the tubes are only the source, and the pegboard is the only destination, so the player never has to guess where a bead belongs — the picture shows them. That is why the design can stay calm: no timers in the main levels, no pressure, and no purchases. The mechanic works with three pieces of state: the tubes, the pegboard, and the tray. Tapping a tube sends its top run — the longest run of matching beads at the top of the stack — to the pegboard. Beads only land on glowing rows, and the board fills from the bottom row up. A bead with no free peg waits in a small tray and hops on by itself when its row opens. Fill the tray and you are stuck, so every tap needs planning. A tube is a list of bead colors with the bottom bead first, so the top bead is the last item in the list: \`dart class Tube { final List beads; // bottom bead first, top bead last bool get isEmpty => beads.isEmpty; List get topRun { void removeTopRun() { \ Each peg has a target color, so the board can be stored as a count of empty pegs per color. A move is one tap: take the top run from the chosen tube, place each bead on the board when its color has room, and send the rest to the tray. If the tray is full when a bead needs it, the move is illegal and the tube does not move at all: \`dart final List tubes; bool _hasRoomFor(BeadColor color) => (_emptyPegs[color] ?? 0) > 0; bool canTap(Tube tube) { void tap(Tube tube) { \ The tray releases beads automatically: a bead that waited in the tray hops onto the board the moment its row opens, so the player never manages the tray by hand. A bead sort level stops players from getting stuck in two ways: the tray absorbs mistakes, and a solver checks every level before it ships so there is always a winning line. The hint system follows the solver's winning line, so a hint never leads the player into a dead end. The solver is a depth-first search over game states: the tubes, the empty pegs per color, and the tray. The search tries every legal tap from a state, and a state is solvable when one of its moves leads to a solved board. A visited set keeps the search from looping forever on the same arrangement. The solver and the game share the same move rules, so a level the solver calls winnable is genuinely winnable by a player: \`dart final List> tubes; bool get isSolved => String get key => BeadState? move(int tubeIndex, int traySize) { bool isSolvable(BeadState start, int traySize) { return search(start); \ Run the solver at level-design time, not on the player's phone: generate a level, run isSolvable\, and discard or reshuffle any level that fails. Every level the player sees has a way through. The arrow puzzle game guide uses the same idea — a solver-checked board — and it is what makes a calm puzzle feel fair instead of rigged. Difficulty scales with five knobs: picture size, bead shades, tube count, mixed tubes, and tray size. Bead Charms turns them up from level 33 to level 100: bigger pictures, more bead shades, more tubes, more mixed tubes and a smaller tray. After level 100 the puzzle keeps going at the hardest setting. Level 1 teaches the rules with a tutorial hand, and the early levels keep the tray generous. Level range Picture Shades Tubes Tray 1–10 Small 3–4 3–4 5 11–32 Medium 4–5 4–5 4 33–60 Large 5–6 5–6 3 61–100 Largest 6–7 6–7 2 Generate each level from a difficulty profile, then run it through the solver before it ships. The picture decides the bead counts: count the pegs of each color in the finished image, then deal those beads into tubes. The solver is the gatekeeper — if the deal has no winning l

flutterpuzzlegamegamedevbeadsort
How we sync two finance ledgers end-to-end encrypted, with no user accounts
11/19 上午05:57

How we sync two finance ledgers end-to-end encrypted, with no user accounts

abdellahi agha

Most money apps start with a sign-up screen. Ours doesn't. Amunta is a ledger for expenses, debts and invoices that works from the first launch with no email, no password and no account, and keeps its database on the phone. That raised an engineering problem early on: debts involve two people. If I lend you money, I want the record to appear in your ledger too, without either of us typing it twice. How do you sync records between two people when there is no account system to hang identities on, and you don't want the server to read anything? This post walks through the design we shipped in Flutter, what the server can and cannot see, and the trade-offs we accepted. On first launch the app generates two key pairs and keeps the private halves in the platform's secure storage (flutter_secure_storage): an X25519 pair, used to derive shared encryption keys with other people; an Ed25519 pair, used to sign data that travels by QR code. The public X25519 key is what other people need to reach you. There is no username to look up and no directory of users. Two users "link" once, typically by scanning a QR code in person (or by sharing a short network ID). The QR carries the public key and is signed with Ed25519, so the receiving phone can check it wasn't altered. After linking, each phone stores the other's public key next to the contact. From then on, any transaction or invoice one person records for the other can be sent automatically, and it arrives reversed on the other side: a loan I give becomes a loan you received, a sale becomes a purchase, with the same items, amounts and date. Every payload is encrypted on the sender's phone before it leaves: X25519 ECDH between my private key and your public key gives a shared secret. HKDF-SHA256 derives a 256-bit key from that secret. AES-256-GCM encrypts the payload; the wire format is just {iv, ct, tag}. All of this uses the cryptography Dart package. Because both sides can derive the same key independently, nothing secret is ever exchanged over the network. Phones are not always online at the same time, so we need a mailbox. Ours is a small store-and-forward relay written in PHP. Its job is deliberately narrow: it receives an opaque encrypted blob addressed to a recipient; it hands that blob to the recipient's phone when it asks; it deletes the blob as soon as the receiving phone acknowledges it processed it; anything never delivered expires after 24 hours. The relay never holds a key, so it can't read amounts, names or descriptions. It isn't a database of anyone's finances; at any moment it only holds messages still in transit. Our main market has expensive, unreliable mobile data, so the network path can't be the only path. A single transaction can also move between two phones by QR code, entirely offline. The QR is signed, not encrypted: it's meant to be scanned face to face, and the signature lets the receiver verify the source and integrity, check that the currency matches, and refuse duplicates. Plain sync is fine for most records, but debts are sensitive: you don't want someone silently editing what you owe them. So there is a stricter mode (we call it A-Link+): any operation that creates or changes a debt must be accepted by the other person before it counts, can only be cancelled within 24 hours, and debt balances are compared on both phones so they can't drift apart. Cash entries and gifts skip this, because they don't create an obligation. No design is free. Being honest about ours: No forward secrecy. Keys are long-lived per device, not rotated per message. If a private key leaked, past captured blobs could be decrypted. Given that the relay deletes blobs on delivery, we judged this acceptable for now, but it's the first thing we'd improve. Metadata is visible to the relay. It can't read content, but it does see which routing identifiers exchange messages and when. Losing the phone means losing the keys. With no account, there's no "reset password". That's why the app offers encrypted backups, locally or to the user's own Google Drive. Key verification is on the user. Linking in person by QR is the safe path; sharing a network ID remotely trusts the channel you shared it on. Removing accounts removes a lot: no password resets, no breach of a user table, no email to verify. But it moves complexity onto the device: identity, backup and recovery all become the app's job. For a ledger where the data is personal and the users often have limited connectivity, that trade felt right. The app is called Amunta (with a separate edition for small shops), available on Android and iOS in 13 languages, built by a small team in Nouakchott, Mauritania. If you have thoughts on the design, especially on adding forward secrecy without breaking offline use, I'd love to hear them in the comments. https://amunta.pixun.dev/

fluttersecurityprivacymobile

freeCodeCamp

15 條

教學、指南與實踐文章

How to Build a Dart Package Analytics Tool with the pub.dev API: Beyond the 30-Day Window
09/24 上午05:01

How to Build a Dart Package Analytics Tool with the pub.dev API: Beyond the 30-Day Window

Oluwaseyi Fatunmole

When I published my package on pub.dev, the first few days were exciting as the number of downloads climbed. 201 downloads in a few days! Then something strange happened. The number dropped: 120, then

pub.devFluttermobileDart
How to Implement LEGO Architecture in Flutter [Full Handbook]
09/11 下午11:08

How to Implement LEGO Architecture in Flutter [Full Handbook]

Atuoha Anthony

Almost everyone has snapped two LEGO bricks together at some point, even without owning a single set as an adult. You press one brick down onto another, feel it click, and it holds. You likely never o

FlutterDartflutter-awarehandbook
How to Use Skills in Agentic Flutter Development: A Handbook for Devs
09/03 下午11:40

How to Use Skills in Agentic Flutter Development: A Handbook for Devs

Atuoha Anthony

One of the biggest misconceptions about AI-assisted development is that using AI means giving up the engineering experience you've built over the years. It doesn't. You can take the architecture patte

FlutterDartAIflutter-aware
How to Test Flutter Apps: Unit, Widget, Golden, and Integration Tests Explained
08/27 下午11:34

How to Test Flutter Apps: Unit, Widget, Golden, and Integration Tests Explained

Gidudu Nicholas

The first time I was asked "what's your test coverage?" in a technical interview, I didn't have a good answer. I had shipped a couple of real Flutter apps by then. They worked and users were using the

FlutterDartTestingwidget-testing
Mobile Background Execution: iOS Background Modes, Android WorkManager, and Background Services in Dart
08/25 上午01:45

Mobile Background Execution: iOS Background Modes, Android WorkManager, and Background Services in Dart

Oluwaseyi Fatunmole

Every mobile developer eventually hits the same wall: the app works perfectly when the user is looking at it. But the moment they press the home button, everything stops. A sync that should have compl

DartFluttermobileMobile Development
Chain of Responsibility Design Pattern: Decoupling Complex Business Rules, One Handler at a Time
08/22 上午04:45

Chain of Responsibility Design Pattern: Decoupling Complex Business Rules, One Handler at a Time

Oluwaseyi Fatunmole

Every system, at some point, ends up with a function that nobody wants to touch. It starts small: a simple validation check, an if statement here, another there. Then requirements grow and more condit

design patternsBehavioral Design PatternDartFlutter
How to Work with Material and Cupertino Decoupling in Flutter [Full Handbook]
08/19 上午12:05

How to Work with Material and Cupertino Decoupling in Flutter [Full Handbook]

Atuoha Anthony

Earlier this year, I published Decoupling Material and Cupertino in Flutter, which covered what was then a preview feature: Flutter's plan to separate the Material and Cupertino design libraries from

FlutterDartflutter-aware
How to Automate Flutter Releases with Fastlane and GitHub Actions for Firebase App Distribution, Google Play, TestFlight, and App Store Connect
08/12 上午12:47

How to Automate Flutter Releases with Fastlane and GitHub Actions for Firebase App Distribution, Google Play, TestFlight, and App Store Connect

Atuoha Anthony

Picture this: it's 4pm on a Friday, and your team has just merged the last feature for the sprint. But your product manager asks for a new build on TestFlight by the end of the day so the client can r

FlutterDartflutter-aware
Flutter Frontend Systems Design: How to Think Like a Senior Engineer in the AI Age
08/10 下午10:14

Flutter Frontend Systems Design: How to Think Like a Senior Engineer in the AI Age

Jesutoni Aderibigbe

Systems design has always been treated as a backend problem. Ask a group of Flutter engineers what systems design means, and most will describe server architecture: load balancers, databases, and micr

FlutterSystem Designmobile app developmentDart
How to Test AI Features in Flutter [Full Handbook]
08/08 上午12:05

How to Test AI Features in Flutter [Full Handbook]

Atuoha Anthony

You've spent two weeks building an AI assistant. The streaming chat looks beautiful, the system prompt is tight, and safety filters are configured. You demoed it to the team, and everyone was impresse

Fluttergeminiflutter-awareDart
A Deep Dive into Behavioral Patterns: The Visitor Design Pattern and its Clean Operations Across Complex Object Structures
08/07 上午12:11

A Deep Dive into Behavioral Patterns: The Visitor Design Pattern and its Clean Operations Across Complex Object Structures

Oluwaseyi Fatunmole

There's a problem that shows up in almost every growing software system, and most developers don't even realize they're hitting it until the damage is already done. You have a set of objects: differen

Designdesign patternsdesign principlesDart
Bluetooth Low Energy in Flutter: A Handbook for Devs
08/06 上午01:25

Bluetooth Low Energy in Flutter: A Handbook for Devs

Nikheel Vishwas Savant

Most Flutter tutorials stop at network calls and REST APIs. The moment you need to talk to a physical device, a heart rate monitor, a smart bulb, a fitness tracker, an industrial sensor, or your own c

bluetoothBluetooth Low EnergyFlutterFlutter SDK
From RPC to gRPC: Understanding Remote Procedure Calls, Protocol Buffers, and Modern Distributed Systems Communication
07/23 上午06:36

From RPC to gRPC: Understanding Remote Procedure Calls, Protocol Buffers, and Modern Distributed Systems Communication

Oluwaseyi Fatunmole

Every application, at some point, needs to talk to another system. A mobile app talks to a backend. A backend service talks to a payment gateway. An authentication service talks to a user service. A d

gRPCRPCDartFlutter
The Observer Design Pattern Handbook: Event-Driven Architecture & Domain-Driven Design in Dart
07/17 上午06:20

The Observer Design Pattern Handbook: Event-Driven Architecture & Domain-Driven Design in Dart

Oluwaseyi Fatunmole

Every application, at some point, has to deal with a fundamental challenge: something happens, and several other things need to react to it. A user logs in, and the app needs to save a token, cache th

#Domain-Driven-DesignDartMobile DevelopmentFlutter
How to Fix App Jank: A Practical Guide to Profiling Flutter Apps with DevTools
07/08 下午11:47

How to Fix App Jank: A Practical Guide to Profiling Flutter Apps with DevTools

Gidudu Nicholas

Flutter makes it fast to build beautiful UIs. That speed is one of the framework's greatest strengths, but it also creates a subtle problem: performance issues are easy to introduce and difficult to f

Flutterjankdevtoolsperformance

Hacker News

20 條

技術社群討論與專案連結

Show HN: RPC-dart – a bridge for tRPC/oRPC type safety for Flutter
11/19 上午12:21

Show HN: RPC-dart – a bridge for tRPC/oRPC type safety for Flutter

rearview

There's no official support for tRPC/oRPC support in Flutter and using Node.JS with these libraries start to lose there biggest purpose which is helping hand in development. So I've built this package which gets configured with your backend and build end-to-end type-safe APIs. All you need to do is build backend and all the schemas, routes and procedures would be directly converted to Dart with a single command. Comments URL: https://news.ycombinator.com/item?id=50548193 Points: 1 # Comments: 0

iOS 26's Liquid Glass widgets in Flutter
11/18 下午07:04

iOS 26's Liquid Glass widgets in Flutter

usmanmehmood55

Article URL: https://github.com/mohamedalsamrai/liquidum Comments URL: https://news.ycombinator.com/item?id=50544765 Points: 2 # Comments: 0

Show HN: Moonswing – a Linux desktop environment built with Flutter
11/18 上午12:19

Show HN: Moonswing – a Linux desktop environment built with Flutter

mkosarek

Article URL: https://github.com/miracle-wm-org/moonswing Comments URL: https://news.ycombinator.com/item?id=50533647 Points: 5 # Comments: 1

What's New in Flutter 3.50
11/13 上午07:02

What's New in Flutter 3.50

gumby271

Article URL: https://flutter.dev/blog/whats-new-in-flutter-3-50 Comments URL: https://news.ycombinator.com/item?id=50475670 Points: 2 # Comments: 0

11/06 下午11:49

Wing: Port Forwarding Tool with Built-In Flutter Build and Forwarding Support

gerenahudev

Article URL: https://wingserver.vercel.app Comments URL: https://news.ycombinator.com/item?id=50393852 Points: 3 # Comments: 0

11/04 下午05:01

Flutter updates required to remediate the eMudhra certificate compromise

bitneuker

Article URL: https://firebase.google.com/support/guides/compromised-emudhra-intermediate-ca Comments URL: https://news.ycombinator.com/item?id=50363013 Points: 2 # Comments: 1

Show HN: Detox Mode – A Flutter app to help reduce smartphone distractions
11/01 下午07:07

Show HN: Detox Mode – A Flutter app to help reduce smartphone distractions

saurabh_yagyik

Article URL: https://play.google.com/store/apps/details?id=com.saurabh.detox&hl=en_US Comments URL: https://news.ycombinator.com/item?id=50324483 Points: 1 # Comments: 0

A Flutter game holds 60 FPS on a $100 Android phone
10/31 上午01:50

A Flutter game holds 60 FPS on a $100 Android phone

bjornhoj

Article URL: https://upsling.space/blog/60-fps-flutter-physics-on-a-100-dollar-phone/ Comments URL: https://news.ycombinator.com/item?id=50307586 Points: 1 # Comments: 0

Building a Flutter IoT app for real-time hydration monitoring in football teams [video]
10/28 下午08:01

Building a Flutter IoT app for real-time hydration monitoring in football teams [video]

Harish_0089

Article URL: https://www.youtube.com/watch?v=FBWaoS4QXsw Comments URL: https://news.ycombinator.com/item?id=50272231 Points: 1 # Comments: 0

Build a Flutter Phone Dialer with Call History
10/21 下午10:38

Build a Flutter Phone Dialer with Call History

lautarolobo

Article URL: https://lautarolobo.xyz/blog/flutter-phone-dialer-call-history/ Comments URL: https://news.ycombinator.com/item?id=50181804 Points: 1 # Comments: 0

Show HN: TutorLoom, an open-source multi-tenant LMS (Django, React, Flutter)
10/21 下午10:22

Show HN: TutorLoom, an open-source multi-tenant LMS (Django, React, Flutter)

madhukarah

Article URL: https://github.com/pacewisdomhq/TutorLoom Comments URL: https://news.ycombinator.com/item?id=50181517 Points: 2 # Comments: 0

Moonswing – A Desktop Environment for Linux in Flutter
10/20 上午04:09

Moonswing – A Desktop Environment for Linux in Flutter

matthewkosarek

Article URL: https://github.com/miracle-wm-org/moonswing Comments URL: https://news.ycombinator.com/item?id=50157418 Points: 1 # Comments: 0

Streaming a coding agent's UI in Flutter: what broke and how we fixed it
10/16 下午04:55

Streaming a coding agent's UI in Flutter: what broke and how we fixed it

narayanahari

Article URL: https://getpullrequest.com/blogs/streaming-agent-ui-in-flutter Comments URL: https://news.ycombinator.com/item?id=50115889 Points: 1 # Comments: 0

A Linux desktop environment in Flutter
10/14 下午09:13

A Linux desktop environment in Flutter

matthewkosarek

Article URL: https://github.com/miracle-wm-org/moonswing Comments URL: https://news.ycombinator.com/item?id=50087239 Points: 1 # Comments: 2

Genkit Dart 1.0: Build production-ready agentic apps with Dart and Flutter
10/11 上午09:09

Genkit Dart 1.0: Build production-ready agentic apps with Dart and Flutter

khalidkhair

Article URL: https://flutter.dev/blog/announcing-genkit-dart-1-0 Comments URL: https://news.ycombinator.com/item?id=50038795 Points: 4 # Comments: 0

Moonswing: A Linux Desktop Environment Built in Flutter
10/09 下午10:53

Moonswing: A Linux Desktop Environment Built in Flutter

matthewkosarek

Article URL: https://github.com/miracle-wm-org/moonswing Comments URL: https://news.ycombinator.com/item?id=50021374 Points: 2 # Comments: 1

PomoPlan – Local-first Pomodoro, task, and habit tracker in Flutter
10/08 下午10:22

PomoPlan – Local-first Pomodoro, task, and habit tracker in Flutter

bentamara

Article URL: https://play.google.com/store/apps/details?id=com.pomoplan.pomoplan&hl=en_US Comments URL: https://news.ycombinator.com/item?id=50006163 Points: 2 # Comments: 0

10/08 下午04:09

Ask HN: Preferred state management for enterprise Flutter in 2026?

nmdemirkol

When scaling Flutter mobile apps to enterprise level, what state management approach (BLoC, Riverpod, Signals, etc.) have you found most maintainable over time? Interested in experiences regarding testability and onboarding. Comments URL: https://news.ycombinator.com/item?id=50003115 Points: 2 # Comments: 0

Friday – A voice-activated personal AI companion built with Flutter
10/07 下午11:34

Friday – A voice-activated personal AI companion built with Flutter

ddhruv2424

Article URL: https://github.com/dj2313/jarvis_assistant Comments URL: https://news.ycombinator.com/item?id=49994302 Points: 2 # Comments: 0

Show HN: Vynody – Cross-platform music player written in Flutter and Rust
10/01 下午08:13

Show HN: Vynody – Cross-platform music player written in Flutter and Rust

axel10

Article URL: https://github.com/axel10/vynody Comments URL: https://news.ycombinator.com/item?id=49920648 Points: 5 # Comments: 0

Medium

10 條

Flutter 相關文章精選

Faster interaction on iOS
11/19 下午08:51

Faster interaction on iOS

Nicolas

Reduces interaction latency by 1 frame. This means a reduction in interaction latency by 16ms (60Hz devices) and 8ms (120Hz devices) for… Continue reading on Medium »

androidiosflutterdart
Flutter Layers Explained: Transform, Opacity, Clip and Offset Layers
11/19 下午07:46

Flutter Layers Explained: Transform, Opacity, Clip and Offset Layers

Nisarg Ratani

Flutter’s rendering architecture does not stop after painting. Continue reading on Medium »

flutter-opacityflutter-transformmobile-app-developmentflutter
Flutter Compositing Explained: How Flutter Composes the Final Frame
11/19 下午07:46

Flutter Compositing Explained: How Flutter Composes the Final Frame

Nisarg Ratani

Flutter’s rendering architecture contains several stages that work together to produce the pixels displayed on the screen. Continue reading on Medium »

flutterflutter-app-developmentflutter-uiflutter-compositing
Claude Code 2.1.327
11/19 下午07:06

Claude Code 2.1.327

Blur Brah Lab

Today’s Must-Know: Claude Code 2.1.327 speeds up the first Bash call, and your shell startup files may run before you approve it Continue reading on Medium »

flutterclaude-codeaitechnology
Let Power Users Keep Their Hands on the Keyboard: Shortcuts in Flutter
11/19 下午07:01

Let Power Users Keep Their Hands on the Keyboard: Shortcuts in Flutter

Wartelski.

Power users live in the keyboard. If your Flutter desktop or web app makes them reach for the mouse to do everything, you’re slowing down… Continue reading on Medium »

web-developmentuxflutteraccessibility
Flutter 3.50 Is Here — 10 Changes You Should Know!
11/19 下午05:47

Flutter 3.50 Is Here — 10 Changes You Should Know!

Nicolas

Material, Wasm support in Safari and one line upgrades for Dart! Continue reading on Medium »

flutteriosflutter-app-developmentdart
onTap vs onPressed in Flutter: Why Can't We Just Have One?
11/19 下午04:30

onTap vs onPressed in Flutter: Why Can't We Just Have One?

Ajasa Taiwo

After spending over almost three years writing Flutter, you’d think I’d have figured out all its little quirks. But one thing that still… Continue reading on Medium »

dartlearningflutter
Flutter Under the Hood | Story 67 | Multi-Touch Gestures Under the Hood: How Flutter Handles Pinch…
11/19 下午01:41

Flutter Under the Hood | Story 67 | Multi-Touch Gestures Under the Hood: How Flutter Handles Pinch…

Developer Hub

Two fingers touch the screen. One moves outward, the other moves inward, and an image smoothly changes size. But how does Flutter turn two… Continue reading on Flutter Hub »

software-developmenttechnologyprogrammingflutter
10 Clean Code Best Practices I Wish I Had Learned Earlier
11/19 下午12:36

10 Clean Code Best Practices I Wish I Had Learned Earlier

Ravi Savaliya

Stop writing code that only works today. Learn the habits that make software easier to read, test, debug, and maintain. Continue reading on Medium »

mobile-app-developmentclean-codeprogrammingflutter
How I shipped my first Android app to Google Play
11/19 下午12:20

How I shipped my first Android app to Google Play

Tray

The first Android bundle I tried to ship for PILAH 2.0 Continue reading on Medium »

android-developmentgoogle-play-storeflutter

Reddit

4 條

社群日榜討論與資源

11/17 上午05:34

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

/u/Cylicium

I build a mobile app alone and never had enough beta testers, so I made agents that do it. Each one gets its own iOS Simulator or Android emulator on free GitHub runners, plays a persona and writes a bug report with screenshots. On a demo app with 11 planted bugs, 4 agents found 9 in 21 min for $0.87. submitted by /u/Cylicium [link] [comments]

11/17 下午08:15

Made a puzzle game with Flutter + Flame, looking for honest feedback

/u/JuryIllustrious8403

Hi! We're a 2-person team and just released Arrow Duel on Google Play, built with Flutter + Flame. You and a computer rival take turns tapping arrows off the board, and the first to clear theirs wins. We'd love feedback from fellow Flutter devs on: - the overall experience and how it feels to play - the UI and animations - the translations (it's in 12 languages, including Arabic) - whether the ads get in the way Google Play: https://play.google.com/store/apps/details?id=com.binduintelligence.arrowduel Any feedback helps, good or bad. Thanks! submitted by /u/JuryIllustrious8403 [link] [comments]

11/17 上午02:48

Ran my own flutter starter kit against a 19 point launch checklist. 9 passed, 5 half done, 5 missing

/u/DohamaSystems

So i've been building a flutter + supabase starter kit since august (auth, ai chat, paywall, the usual stuff). Honestly thought it was pretty much launch ready. Then i saw a launch checklist going around with 19 things every app should have before going live and figured ok, let's be honest and check mine. passed (9) * login * logout * password reset * email confirmation * loading states + empty states * rate limiting * RLS on every table * no api keys in the frontend * mobile layout half done (5) * error messages. Some still fall back to a raw `Error: $e` which is not exactly user friendly lol * form validation. No email format check yet * db backups. Supabase only does automatic backups on paid plans and i never mentioned that anywhere in the readme * privacy policy. Only exists as a note in the readme, no link inside the app * terms of service. Same story, readme only missing (5) * delete account. Apple requires this so it's basically a must * 404 page (no errorBuilder in go_router yet) * analytics * error tracking * onboarding So 9/19, not as launch ready as i thought. Delete account is next since that one can actually get you rejected from the app store. Curious what you guys would tackle after that. And what do you use for error tracking in flutter, sentry or something else? submitted by /u/DohamaSystems [link] [comments]

11/17 上午04:27

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

/u/pedroruff0

still - pubdev *** en-US *** Flutter already knows when someone turns on Reduce Motion or Remove Animations. It stores that choice, and stops there. AnimationController ignores Reduce Motion on purpose. The framework’s idea is to swap the slide for a fade, but that decision is left to each widget. In practice, almost nobody does it, so the card still slides in from the bottom for people who asked for motion to stop. I published still to solve this in one place. A MotionScope around your app decides: slide, fade, or cut. StillSwitcher, StillEntrance, StillStagger, and StillPageRoute follow that decision. Wherever you don’t use one of these widgets, nothing moves. The package doesn’t import Material, so the same code works in a custom design system and will keep working when Material leaves the SDK. 📦 https://pub.dev/packages/still 💻 https://github.com/pedrinnhooo/still-pubdev *** pt-BR *** O Flutter já sabe quando alguém ativa “Reduzir movimento” ou “Remover animações”. Ele guarda essa escolha e para por aí. O AnimationController ignora “Reduzir movimento” de propósito. A ideia do framework é trocar o slide por um fade, mas essa decisão fica a cargo de cada widget. Na prática, quase ninguém faz, e o card continua entrando de baixo para quem pediu para o movimento parar. Publiquei o still para resolver isso em um lugar só. Um MotionScope em volta do app decide: slide, fade ou corte. StillSwitcher, StillEntrance, StillStagger e StillPageRoute seguem essa decisão. Onde você não usa um desses widgets, nada se mexe. O pacote não importa o Material. O mesmo código funciona em um design system próprio e continua valendo quando o Material sair do SDK. 📦 https://pub.dev/packages/still 💻 https://github.com/pedrinnhooo/still-pubdev submitted by /u/pedroruff0 [link] [comments]

FAQ

常見問題