# Dart Dart is a client-optimized programming language for developing fast, multi-platform applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kodebits Day 92: Collection For Loop \[FREE\] DevFeed: [Kodebits Day 92: Collection For Loop \[FREE\]]() Original publisher: [Read original article]() Published: 2026-09-14T18:00:05Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Dart]() Tags: [article](), [dart](), [free]() ### AI overview A short free Kodeco challenge for practicing collection for loops in Dart. ### Source excerpt Practice collections with a short dart challenge. ## How to Implement LEGO Architecture in Flutter \[Full Handbook\] DevFeed: [How to Implement LEGO Architecture in Flutter \[Full Handbook\]]() Original publisher: [Read original article]() Author: Atuoha Anthony Published: 2026-09-11T15:08:19Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [Code](), [Dart](), [App]() Tags: [architecture](), [dart](), [dependency-injection](), [flutter](), [flutter-aware](), [handbook](), [how-to]() ### AI overview A Flutter handbook that introduces LEGO Architecture: building code from independently connected pieces. It also relates this approach to Clean Architecture and covers Dart contracts and dependency injection. ### Source excerpt 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 ## Kodebits Day 79: Collection If \[FREE\] DevFeed: [Kodebits Day 79: Collection If \[FREE\]]() Original publisher: [Read original article]() Published: 2026-08-20T16:00:46Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Dart]() Tags: [article](), [dart](), [development](), [free](), [learn]() ### AI overview A short Dart challenge focused on practicing collection if statements. ### Source excerpt Practice collection if with a short dart challenge. ## An insider argues that Google remains committed to Flutter and Dart DevFeed: [An insider argues that Google remains committed to Flutter and Dart]() Original publisher: [Read original article]() Author: Randal L. Schwartz Published: 2026-08-19T16:02:19Z Content type: opinion Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Dart](), [Google](), [multiplatform](), [WebAssembly]() Tags: [cross-platform](), [dart](), [devrel](), [flutter](), [google](), [mobile-app-development](), [programming](), [software-development](), [wasm](), [webassembly]() ### AI overview This commentary argues, from the author's stated experience as a Flutter Google Developer Expert, that Google remains committed to Flutter and Dart despite restructuring-related concerns and reduced public communication. It cites renewed advocacy and investment in rendering, Dart ergonomics, WebAssembly compilation, and multiplatform performance. ### Source excerpt Every few months, like clockwork, the tech blogosphere gets flooded with the same recycled headline: "Is Flutter Dying?", "Why CTOs Are Quietly Leaving Flutter", or "Why Google is Killing Its Cross-Platform Bet." As someone who has been a Flutter Google Developer Expert for eight years now -- literally from day one of the GDE program -- and a five-decade software industry veteran, I usually just chuckle at the clickbait. "Flutter is dead." -- Said every six months since 2018. Meanwhile: Flutter is kicking tail on every single measurable scale. The alarmist articles point to standard corporate reorganizations, shifting tech job boards, and "state management fatigue" as evidence of Flutter's demise. But having watched this ecosystem evolve from an experimental alpha into an enterprise powerhouse, the reality on the ground is the exact opposite. Here is the real insider story on what's actually happening with Dart and Flutter. 1. The Inside Story: What Happened at Google? When tech companies restructured engineering teams recently, the internet spun a wild narrative that "Google put Flutter on life support." Having direct access to internal teams, I watched the commitment to Dart and Flutter remain steadfast within the organization. However, there was a temporary disconnect: internal engineering activity was roaring, but external communications and public advocacy had slowed down, leaving an information vacuum that clickbait writers eagerly filled. I personally called out to team leaders and senior VPs that this perception gap needed immediate correction. And the leadership responded strongly: Revitalized DevRel & Advocacy: A renewed surge in active community engagement, tutorials, and public roadmaps. Enterprise Adoption Transparency: Showcasing massive internal and external production milestones. Aggressive Core Investment: Deep work on the Impeller rendering engine, Dart 3.x ergonomics, WebAssembly (Wasm) compilation, and native multiplatform performance. Flutter is no ## Building AI Agents in Dart with the Genkit Dart SDK DevFeed: [Building AI Agents in Dart with the Genkit Dart SDK]() Original publisher: [Read original article]() Author: Abhishek Doshi Published: 2026-08-10T23:16:05Z Content type: tutorial Language: en Sources: [Google Developer Experts - Medium]() Topics: [Dart](), [Genkit](), [AI Development](), [Flutter](), [Cloud Functions](), [Firebase](), [SDKs]() Tags: [ai](), [ai-agent](), [ai-agents](), [ai-development](), [cloud-functions](), [dart](), [firebase](), [flutter](), [generative-ai-tools](), [genkit](), [sdk]() ### AI overview This tutorial introduces the Genkit Dart SDK for building AI agents natively in Dart and deploying them to Cloud Functions for Firebase. It explains agent orchestration, conversational state, history, streams, models, tools, flows, and multi-agent delegation. ### Source excerpt Because your Flutter app deserves a brain, and you deserve to never look at a Python traceback again. Let's be honest. We all love Dart. It's clean, it's safe, and it powers our beloved Flutter. But until recently, if you wanted to build serious, multi-step AI agents, the industry basically told you to pack your bags, leave your cozy typed ecosystem, and go write Python. Gross 🤮 Thankfully, Google finally heard our collective sighs and dropped the Genkit Dart SDK. Now, you can build full-stack, hyper-intelligent AI agents natively in Dart and deploy them straight to Cloud Functions for Firebase. No context-switching. No spinning up a random Node.js microservice just to talk to an LLM. Grab your coffee (or your energy drink of choice). Let's look at how Genkit turns your Dart code into an absolute powerhouse. https://medium.com/media/91c2efa4198c043f3f400f216214650e/hrefThe Shift: From "Dumb Chatbots" to "Autonomous Overlords" Building traditional chatbots or strict multi-step UI flows often feels like playing one of those terrible, rigid video games that block you at a level until you do exactly what the developers scripted. Agentic AI, by contrast, is the ultimate open-ended sandbox. An agent doesn't just blindly answer a prompt. It analyzes what the user wants, figures out which tools it needs to achieve the goal, and dynamically orchestrates the steps to get there. With Genkit's new Agents API, all the messy plumbing: maintaining conversational state, keeping track of history, and parsing streams, is handled behind a single API. You just focus on giving it a brain. The Holy Trinity: Models, Tools, and Flows To stop your AI from just hallucinating fan-fiction, Genkit uses a few core primitives. Think of this as the toddler-proofing stage of AI development. Models (ai.generate()): The actual brain. Whether you are using Gemini, Claude, or OpenAI, the API stays exactly the same. Tools (defineTool): This is how you give your AI hands. By defining strict input schemas ## Where I'm Writing Now: The Complete 14-Part BlocSignal Series on DEV.to DevFeed: [Where I'm Writing Now: The Complete 14-Part BlocSignal Series on DEV.to]() Original publisher: [Read original article]() Author: Randal L. Schwartz Published: 2026-08-10T16:00:59Z Content type: opinion Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Dart](), [reactive](), [Dependency injection](), [OpenTelemetry](), [Web Development]() Tags: [bloc](), [blocsignal](), [dart](), [dependency](), [dev](), [developer-community](), [development](), [flutter](), [series](), [signal](), [state-management](), [tracing](), [writing]() ### AI overview The author announces that DEV.to and the Google Developer Experts organization on DEV.to are now the primary publishing hubs for new technical writing. The article presents a 14-part BlocSignal series covering Dart and Flutter state management, architecture, interoperability, dependency injection, tracing, and web development. ### Source excerpt If you've been following my articles here on Medium over the years, thank you! I wanted to share a quick update on where I'm primarily publishing my new technical deep dives, architectural guides, and Flutter/Dart tutorials. Going forward, my primary writing hub is DEV.to (@randalschwartz) and the official Google Developer Experts (GDE) organization on DEV.to. DEV.to provides a vibrant developer community, native Dart syntax highlighting, and a built-in Series feature that links connected articles into structured, multi-part curricula. 🚀 The New Series: BlocSignal Architecture & Practice Over the last month, my team and I launched BlocSignal -- a production-grade state management framework for Dart and Flutter that bridges BLoC's enterprise discipline with Signals' 0ms synchronous reactivity. We've published a comprehensive 14-part series on DEV.to covering everything from core state machine philosophy and Riverpod/Provider interop to dependency injection, OpenTelemetry tracing, and Jaspr web development. Here is the complete roadmap of all 14 articles available to read right now on DEV.to: 🏛 1. Core Architecture & Philosophy Introducing BlocSignal: Unidirectional Data Flow Meets Reactive Signals The origin story: bridging BLoC semantics with Rody Davis's signals v7 primitives for 0ms microtask queue latency. BLoC meets Signals: How to Pitch BlocSignal to Your Dev Leads How to navigate technical team reviews and explain the enterprise value of synchronous signal graphs. How We Achieved Full BLoC API & Protocol Parity in BlocSignal 0.2.0 A deep dive into BlocProvider, BlocBuilder, BlocListener, BlocConsumer, and context.select parity. Beyond ProviderNotFound: How BlocSignal Rethinks State Location and Synchronous Propagation Solving scope lookups and understanding why synchronous signal updates prevent frame tearing. From Raw Signals to BlocSignal: Taming Reactivity for Enterprise Scale How encapsulating signals inside Cubit/Bloc containers stops global signal "spagh ## Call for Contributors: OpenTelemetry for Dart and Flutter DevFeed: [Call for Contributors: OpenTelemetry for Dart and Flutter]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-13T08:20:00Z Content type: opinion Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [Dart](), [Flutter](), [telemetry](), [SDKs](), [cross-platform]() Tags: [contributors](), [cross-platform](), [dart](), [flutter](), [opentelemetry](), [sdk](), [telemetry]() ### AI overview OpenTelemetry is seeking contributors to establish an official Dart and Flutter SIG and develop a maintained OpenTelemetry SDK. An existing implementation, dartastic_opentelemetry and its API package, is being considered for donation and supports traces, metrics, and logs across multiple targets. ### Source excerpt Why OpenTelemetry for Dart and Flutter? Dart is a full-stack language and the language of Flutter, one of the most popular frameworks for building cross-platform applications. Data shows over 20% of current app store submissions are Flutter apps. Dart is null safe and type safe, compiles to fast binaries, and is increasingly used for backend services as well. Yet Dart remains the last top-15 programming language without an officially maintained OpenTelemetry SDK. Earlier community implementations are no longer maintained, leaving Dart and Flutter developers without a supported path to capture telemetry from their servers and apps. ## Migrating a Flutter Application from CocoaPods to Swift Package Manager DevFeed: [Migrating a Flutter Application from CocoaPods to Swift Package Manager]() Original publisher: [Read original article]() Author: iamgirya (Яндекс) Published: 2026-07-13T07:01:51Z Content type: tutorial Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [Flutter](), [cocoapods](), [swift-package-manager](), [iOS](), [Dart](), [macOS](), [Package manager]() Tags: [cocoapods](), [dart](), [flutter](), [ios](), [ios-development](), [macos](), [swift](), [swift-package-manager](), [swiftpm]() ### AI overview A practical guide to migrating Flutter applications from CocoaPods to Swift Package Manager. It covers dependency-graph analysis, plugin migration, dependency resolution, incremental migration, duplicate transitive dependencies, and successful iOS or macOS builds, including scripts for analysis and plugin conversion. ### Source excerpt Flutter активно движется в сторону Swift Package Manager (SPM) и, как и весь Swift-мир, постепенно отказывается от CocoaPods. Сам Flutter описывает миграцию в два шага: включить флаг flutter config --enable-swift-package-manager и запустить сборку. Если после этого приложение собирается и в консоли появляется предложение deintegrate CocoaPods -- вы счастливчик. Если нет, добро пожаловать под кат. Привет! Меня зовут Даниил Гиренко, я Flutter-разработчик в Яндекс Про. Проект по переводу нашего супераппа с CocoaPods на Swift Package Manager оказался одним из самых сложных и долгих в моей карьере программиста. Весь мой пережитый ужас опыт я решил выразить в этой статье, чтобы решившиеся на миграцию разработчики (или агенты) понимали, какие подводные камни их ждут. Буду рад, если ваш проект займёт недели, а не месяцы, как у меня. В этой статье -- полноценный гайд по миграции любого Flutter-приложения. Разберём граф зависимостей, научимся мигрировать плагины, зарезолвим зависимости и доберёмся до успешного билда. Внутри есть готовые скрипты для анализа и автоматического перевода плагинов, множественные нюансы миграции и рассказы о моих костылях. Читать далее ## Vibe once, run anywhere with Antigravity and Flutter DevFeed: [Vibe once, run anywhere with Antigravity and Flutter]() Original publisher: [Read original article]() Author: Craig Labenz Published: 2026-06-29T16:01:02Z Content type: article Language: en Sources: [Flutter - Medium]() Topics: [Flutter](), [AI-assisted coding](), [cross-platform](), [Artificial Intelligence](), [Dart](), [Large Language Model]() Tags: [agentic](), [agentic-engineering](), [ai](), [antigravity](), [code](), [coding-agents](), [cross-platform](), [dart](), [flutter](), [flutter-app-development](), [game-development](), [google-antigravity]() ### AI overview This article describes how a team used Google's Antigravity and Flutter to build and launch DashLander, a moonlander-style game set on procedurally generated asteroids. It explains how coding agents handled assets, code, testing, marketing, and deployment, and why Flutter's cross-platform model and Dart's strong typing can support agentic development. ### Source excerpt co-authored with Rody Davis Coding agents and the way we use them has already dramatically evolved since their arrival just a handful of months ago. Initially, the focus was heavily on observation -- reviewing every single output line by line. But as models rapidly increased in capability, the industry shifted toward true agentic engineering. Today, developers, PMs, and designers are wearing multiple hats, focusing on lofty conceptual goals and letting agents tackle the individual components. To explore this new frontier, our team wanted to build an experience that showcased this exact workflow. We wanted to build a game, generate its assets, write the marketing page, and deploy the whole thing, all using Google's premiere AI-native platform: Antigravity. Antigravity brings the best of Google into one place, using a tight feedback loop of planning, acting, and verifying. It creates artifacts, writes code, runs tests, and even clicks buttons in your UI to ensure it actually completed the task correctly. The result of our agentic adventure is DashLander -- a moonlander-style game set on procedurally generated asteroids. Here is the story of how we built it. Why Flutter in the AI era? A lot of people might be thinking: If agents can write native code, why not just have them write Android, iOS, and web apps entirely separately? That is a valid question; and is what originally inspired the concept of Flutter as a "Vibe once, run anywhere" UI toolkit. Having a single source of truth is just as important for AI as it is for humans. By having an agent write a single, cross-platform app, teams can eliminate the subtle bugs that inevitably creep in between different languages or platform-specific paradigms. Furthermore, Dart's strong typing gives LLMs excellent feedback. Languages with looser typing systems require dramatically more analysis by the LLM to know whether a given piece of code is correct across all scenarios. Flutter and Dart, on the other hand, use their analysis ## That's a wrap: Everything Flutter at Google I/O 2026 DevFeed: [That's a wrap: Everything Flutter at Google I/O 2026]() Original publisher: [Read original article]() Author: Emma Twersky Published: 2026-05-28T15:43:11Z Content type: article Language: en Sources: [Flutter - Medium]() Topics: [Flutter](), [Google](), [Dart](), [releases](), [ide]() Tags: [2026](), [dart](), [flutter](), [flutter-app-development](), [google](), [google-i-o](), [googleio](), [ios](), [macos](), [releases]() ### AI overview A recap of Flutter and Dart announcements and presentations from Google I/O 2026, including Flutter 3.44, Dart 3.12, Agentic Hot Reload, GenUI, Impeller rendering improvements, platform updates, and related developer sessions. ### Source excerpt Flutter recap at Google I/O 2026! What a week! Google I/O 2026 is officially in the books. It's time to recap the whirlwind of updates for the Flutter and Dart communities. https://medium.com/media/d0d2e640108865de13df503f39550e39/href The onsite star was a full-sized specialty coffee shop in the absolute center of Google I/O, built entirely with Flutter GenUI, where nanobanana-generated artwork was printed right on the coffee foam. Just a few generated foam coffee art lattes at I/O But don't worry if you weren't able to make it to Shoreline. We recorded every moment and more, now available for on-demand viewing on the Flutter YouTube channel. 📺 Watch every session From keynote to tech session, we can't wait for you to see every moment of Flutter from I/O 2026. 🌟 What's new in Flutterhttps://medium.com/media/8990b6ee337f71dd5fe4b546e415b28e/href A few of the highlights: Flutter 3.44 & Dart 3.12: These releases brought major advancements with Agentic Hot Reload, GenUI with a showcase from Li-Te Cheng on the DeepMind team, Toyota has embedded Flutter in the 2026 RAV4, improved rendering performance with Impeller, decoupling of Material and Cupertino UI from the framework, Swift Package Manager is on by default for iOS and macOS, Canonical now leads the Flutter desktop roadmap, and significant updates to platform-specific fidelity with HCPP. 🌟 Vibe once, run anywhere with Antigravity and Flutterhttps://medium.com/media/09b6dd58a4887dc5633ea68bfd9b4f22/href What you'll learn: A technical introduction to Antigravity, a new IDE focused on building with agents. You will learn how to leverage "vibe-based" development to create experiences that adapt and run across all platforms seamlessly. Why it matters: It provides the architectural roadmap for shifting from "hard-coded" layouts to "vibe-based" generative experiences, allowing your app to adapt to user needs on the fly. How to write really good Flutter codehttps://medium.com/media/9f58da82d9e2e2741f0dca7f94fd8ad5/href Wha ## Flutter's multiplatform value for agentic development DevFeed: [Flutter's multiplatform value for agentic development]() Original publisher: [Read original article]() Author: Michael Thomsen Published: 2026-05-18T18:42:10Z Content type: article Language: en Sources: [Flutter - Medium]() Topics: [Flutter](), [multiplatform](), [Artificial Intelligence](), [Dart](), [Development](), [Large Language Model]() Tags: [agentic](), [agentic-ai](), [agentic-development](), [ai](), [code](), [consistency](), [dart](), [flutter](), [flutter-app-development](), [llms](), [mobile-app-development](), [multiplatform](), [reuse]() ### AI overview The article explains how Flutter's single shared codebase can support multiplatform app development and agent-driven workflows. It argues that writing features once in Dart gives AI assistants unified context, reduces token usage and hallucination risk, and helps maintain consistency across platforms. It also describes reported benefits including code reuse, native compilation, and strongly typed Dart code. ### Source excerpt The fundamental value of multiplatform development with Flutter lies in building apps that support multiple platforms with just a single, shared source codebase, allowing developer teams to work in unison across all platforms. This is crucial in an AI-driven world where enhanced consistency, reduced token usage, and fast market reach become vital. By maintaining a single codebase, builders can focus their AI assistants on one unified context, drastically reduce token overhead, and minimize AI hallucinations. Instead of asking AI to translate features across fragmented, platform-specific languages, builders can leverage AI to write it once in Dart and instantly deploy it everywhere. Dash secretly hanging out in an alley doing agentive thingsThe existing value proposition Multiplatform development relies on enabling a single, shared source codebase. In our first-party Flutter apps, between 95% and 99% of the source code is shared. This massive code reuse unlocks several benefits: Faster time to market across multiple platforms because a team only needs to maintain one codebase. Guaranteed consistency across platforms, giving companies a single, consistent feature set to support across all their customers, regardless of their platform of choice. Native performance and stability because Flutter code is compiled to each platform's native machine code. Semantic guardrails increase security because the Dart language is strongly typed. The agentic value proposition While LLMs are good at translating requirements into code, using them to build separate native apps for each platform scales poorly. Replicating features across different languages using LLMs multiplies generation time and token usage, and can quickly lead to implementations drifting apart. Flutter's single-source solution eliminates these problems. But beyond just code sharing, Flutter's specific architecture makes it the ideal framework for agent-driven development. This emerging value proposition is driven by ## Introducing Skills for Dart and Flutter DevFeed: [Introducing Skills for Dart and Flutter]() Original publisher: [Read original article]() Author: Mariam Hasnany Published: 2026-05-06T18:19:09Z Content type: release Language: en Sources: [Flutter - Medium]() Topics: [Agent Skills](), [Dart](), [Flutter](), [Agent Skill](), [MCP](), [MCP Server](), [AI-assisted coding]() Tags: [agent-skill](), [agent-skills](), [agents](), [ai](), [ai-agent](), [ai-agents](), [ai-development](), [coding](), [coding-agents](), [dart](), [efficiency](), [flutter](), [flutter-app-development](), [libraries](), [mcp](), [mcp-server](), [skills](), [tests](), [tools]() ### AI overview Flutter is introducing Agent Skills for Dart and Flutter to give AI tools domain-specific expertise for professional development tasks. The task-oriented skills provide tailored instructions for workflows such as adaptive layouts and enhance the Dart MCP server, aiming to improve accuracy and reduce token usage. ### Source excerpt Introducing prepackaged Dart and Flutter Skills!Improving AI with domain expertise AI agents are generalists, but when it comes to professional Flutter development, "general" isn't enough. To build production-grade apps, you need an assistant that understands the nuance of localization, the latest Dart language features, and how to add integration tests. Today, we're introducing Agent Skills for Flutter and Dart -- a new way to give your AI tools domain-specific expertise. Beyond the knowledge gap One of the primary challenges in AI development is the "knowledge gap." Flutter and Dart can launch new features more quickly than LLMs can update their fixed training data. As a part of how we are thinking about AI, we are looking for ways to not only address the knowledge gap but also ensure the agent applies that knowledge to achieve the task accurately and efficiently following the most optimal workflows. A little over a year ago, Model Context Protocols (MCP) were the way to provide more AI domain-specific expertise. While MCP gives an agent access to specialized tools, an Agent Skill teaches the agent how to use those tools for a specific task. Think of it this way: MCP provides the hammer and nails (the tools), while a Skill provides the blueprint and the professional know-how to build the house. Skills improve context efficiency through "progressive disclosure". This is similar to how deferred loading works in Flutter, where apps can load libraries when needed, coding agents load Skills when they are relevant to what you're trying to do . For Flutter and Dart, these Skills provide tailored instructions for common workflows, and enhance the tools provided in the Dart MCP server to reduce the knowledge gap, which improves accuracy and lowers token usage. A task-oriented approach Our early experimentation revealed that Skills that only provide documentation don't add as much value as we initially assumed. Since Flutter's comprehensive and well written documentation is ## Announcing Dart support in Cloud Functions for Firebase DevFeed: [Announcing Dart support in Cloud Functions for Firebase]() Original publisher: [Read original article]() Author: Kevin Moore; Rody Davis Published: 2026-05-06T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Cloud Functions](), [Dart](), [Firebase](), [Flutter](), [Firebase CLI](), [Serverless](), [Google Cloud Platform (GCP)]() Tags: [admin-sdk](), [cloud-functions](), [cloud-run](), [dart](), [dart-on-the-server](), [emulator-suite](), [firebase](), [firebase-cli](), [firestore](), [flutter](), [google-cloud](), [launch](), [serverless]() ### AI overview Firebase announced experimental support for Dart in Cloud Functions for Firebase, allowing developers to use Dart and shared tooling across Flutter clients and backend functions. The article also describes AOT compilation, asynchronous I/O, Firebase CLI deployment, and local testing with the Firebase Emulator Suite. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Jaspr: Why web development in Dart might just be a good idea DevFeed: [Jaspr: Why web development in Dart might just be a good idea]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-04-15T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [Dart](), [Framework](), [Flutter](), [Web Development](), [Open Source](), [Google]() Tags: [css](), [dart](), [flutter](), [framework](), [google](), [jaspr](), [open-source](), [web-development]() ### AI overview This article introduces Jaspr, an open source web framework for building dynamic, fast-loading, SEO-friendly websites in Dart. It explains the framework's origins, its Flutter-like developer experience, and its use of native HTML and CSS. Google selected Jaspr to rebuild the official Dart and Flutter websites. ### Source excerpt by Kilian Schulte, Netlight Jaspr, the open source web framework, is built on Dart Most developers know Dart as the language that powers Flutter, the multi-platform app framework. But the Dart ecosystem has so much more to offer. For example: Jaspr, a web framework that provides a familiar Flutter-like experience, but is made for building fast, SEO-friendly, and dynamic websites natively in Dart. Dart on the web is not a new idea. Initially, Dart was designed to run natively in browsers, similar to JavaScript. Google even developed AngularDart, a pure-Dart version of the popular JS framework. And although this is no longer supported, it resulted in some surprisingly powerful web tooling for Dart. Back in 2016, teams at Google chose Dart for its strong type safety and excellent development experience, and it has only improved since then. However, all of this was unknown to me when I started building Jaspr in 2022. As a web developer who had transitioned to Flutter, I had grown to love Dart and wanted to explore using it for web development. So Jaspr started as a personal challenge: What would a modern web framework look like if it was built entirely in Dart? Creating Jaspr as an open source project has been one of the most challenging, but also rewarding journeys of my career. Starting out as a solo maintainer is definitely hard work, but it comes with absolute creative freedom. I can explore unconventional ideas, design APIs exactly how I envision them, and integrate modern features seen in other frameworks. All without being slowed down by processes or roadmaps. I poured more than three years of late nights and weekends into the framework. That dedication finally paid off in a way I had never imagined: Google selected Jaspr to completely rebuild and power the official Dart and Flutter websites. Architecture & design To understand how Jaspr actually works, let's look at its underlying design. Jaspr is primarily targeted at Flutter developers venturing into web devel ## Dart Client for Genkit DevFeed: [Dart Client for Genkit]() Original publisher: [Read original article]() Author: Nozomi Koborinai Published: 2025-10-23T10:49:27Z Content type: tutorial Language: en Sources: [Firebase Developers - Medium]() Topics: [Genkit](), [Dart](), [client library](), [Flutter](), [AI Development](), [Cloud Functions](), [Cloud Run]() Tags: [ai-development](), [apis](), [client-library](), [dart](), [firebase](), [flutter](), [genkit](), [google-cloud-platform](), [http](), [open-source](), [server-sent-events-sse](), [streaming]() ### AI overview This article introduces a Dart client library for calling Genkit flows deployed on a server from Flutter or other Dart applications. It explains that the library handles Genkit request and response conventions, reduces repeated HTTP client code, supports authentication mechanisms, and simplifies streaming responses through Server-Sent Events. The client can call flows implemented with Genkit JS, TypeScript, or Go when their server endpoints are accessible. ### Source excerpt Introducing the Dart Client for GenkitCalling Genkit Flows from Flutter/DartDart client for Genkit I'm a big fan of Firebase and often choose Flutter as my front-end framework. Since Google I/O 2024, I've been continuously exploring Genkit. Developed by the Firebase team, Genkit is an open-source framework from Google that simplifies the definition of AI-powered processing sequences on the server-side as Flows. Genkit | Open-source AI development framework by Google However, calling a server-defined flow from a Dart/Flutter client application required some extra effort. To bridge this gap, I developed the Dart client for Genkit package. genkit | Dart package Note: This library is not for defining Genkit flows themselves. It is specifically designed for easily and securely calling flows deployed on a server from a Dart client.Library overview As mentioned above, this library is a dedicated client for easily calling Genkit flows deployed on a server (e.g., as Web APIs on platforms like Cloud Functions for Firebase, Cloud Run, or GKE). It is not for implementing Genkit flows in Dart. The challenges before Previously, calling a Genkit flow from Dart/Flutter required manually implementing an HTTP client according to a set of conventions. For example, here's a typical piece of code using the dio package to call an image generation flow defined in Genkit. Future generateImage({required String imageDescription}) async { try { final response = await dio.post( 'https:///generateImage', data: { 'data': { 'imageDescription': imageDescription, }, }, ); if (response.statusCode == 200) { return response.data['result']['url'] as String; } throw Exception('Failed to generate image: ${response.statusCode}'); } on DioException catch (e) { throw Exception('Failed to generate image: ${e.message}'); } } This code presents several challenges: When sending a request, the input must be wrapped in {'data': ...}, and when receiving a response, the result must be ex ## Speculative Optimizations for WebAssembly using Deopts and Inlining DevFeed: [Speculative Optimizations for WebAssembly using Deopts and Inlining]() Original publisher: [Read original article]() Author: Daniel Lehmann and Matthias Liedtke Published: 2025-06-24T00:00:00Z Content type: article Language: en Sources: [V8]() Topics: [WebAssembly](), [V8](), [JIT](), [Google Chrome](), [Compiler](), [JavaScript](), [Dart]() Tags: [benchmarks](), [code](), [compiler](), [dart](), [google-chrome](), [internals](), [javascript](), [jit](), [webassembly]() ### AI overview This V8 blog post describes speculative call_indirect inlining and deoptimization support for WebAssembly, shipped with Google Chrome M137. The optimizations use runtime feedback to generate better machine code, improving WebAssembly execution, especially for WasmGC programs. Dart microbenchmarks showed average speedups above 50%, while larger applications and benchmarks improved by 1% to 8%. ### Source excerpt In this blog post, we explain two optimizations for WebAssembly that we recently implemented in V8 and that shipped with Google Chrome M137, namely speculative call_indirect inlining and deoptimization support for WebAssembly. In combination, they allow us to generate better machine code by making assumptions based on runtime feedback. This speeds up WebAssembly execution, in particular for WasmGC programs. On a set of Dart microbenchmarks for example, the speedup by the combination of both optimizations is more than 50% on average, and on larger, realistic applications and benchmarks shown below the speedup is between 1% and 8%. Deoptimizations are also an important building block for further optimizations in the future. Background # Fast execution of JavaScript relies heavily on speculative optimizations. That is, JIT-compilers make assumptions when generating machine code based on feedback that was collected during earlier executions. For example, given the expression a + b, the compiler can generate machine code for an integer addition if past feedback indicates that a and b are integers (and not strings, floating point numbers, or other objects). Without making such assumptions, the compiler would have to emit generic code that handles the full behavior of the + operator in JavaScript, which is complex and thus much slower. If the program later behaves differently and thus violates assumptions made when generating the optimized code, V8 performs a deoptimization (or deopt, for short). That means throwing away the optimized code and continuing execution in unoptimized code (and collecting more feedback to possibly tier-up again later). In contrast to JavaScript, fast execution of WebAssembly hasn't required speculative optimizations and deopts. One reason is that WebAssembly programs can already be optimized quite well because more information is statically available as e.g., functions, instructions, and variables are all statically typed. Another reason is that ## Understanding Futures and await in Dart and Flutter DevFeed: [Understanding Futures and await in Dart and Flutter]() Original publisher: [Read original article]() Author: Marvin März Published: 2025-05-27T08:28:16Z Content type: tutorial Language: en Sources: [QuickBird Studios Blog]() Topics: [Dart](), [Flutter](), [event driven](), [Concurrency]() Tags: [asynchronous](), [await](), [concurrency](), [dart](), [event-driven](), [flutter](), [future](), [post]() ### AI overview This tutorial explains how Futures and await work in Dart and Flutter, including their interaction with Dart's single-threaded event loop, asynchronous I/O, and common pitfalls. ### Source excerpt Futures in Dart might seem straightforward at first glance, but dig a little deeper, and you'll find they can be more intricate than you initially thought. Ever wondered how these asynchronous operations truly play with Dart's single-threaded event loop? Or perhaps you've stumbled upon some of the common pitfalls that can trip up even experienced Flutter developers? Fear not, because we're about to embark on a journey to unravel the mysteries of Futures in Dart and Flutter. The post Why Await? Futures in Dart & Flutter appeared first on QuickBird Studios. ## Flutter SDKs for Firebase Data Connect DevFeed: [Flutter SDKs for Firebase Data Connect]() Original publisher: [Read original article]() Author: Maneesh Tewani Published: 2024-12-12T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Flutter](), [Firebase](), [SDKs](), [Dart](), [GraphQL]() Tags: [dart](), [firebase](), [flutter](), [graphql](), [postgresql](), [sdks](), [sql-connect]() ### AI overview Firebase introduces native Dart Flutter SDKs for Firebase Data Connect, including generated, type-safe access to Cloud SQL data. The article explains configuration, schema operations, authentication guidance, and using the SDK in a Flutter app. ### Source excerpt News, tutorials, and updates from the Firebase team. ## New Chainguard Images October 2024: Swift, Dart, and more DevFeed: [New Chainguard Images October 2024: Swift, Dart, and more]() Original publisher: [Read original article]() Published: 2024-11-14T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [container images](), [Swift](), [Dart]() Tags: [chainguard](), [chainguard-images](), [container-images](), [cve](), [dart](), [fips](), [jaeger](), [linkerd](), [swift](), [zero-cves]() ### AI overview Chainguard's October 2024 update announces 126 new CVE-free container images, including offerings for Swift, Dart, Linkerd, and Jaeger, along with new FIPS-enabled images and a notice about upcoming Developer tier changes. ### Source excerpt Go over all the new Chainguard container images released in October, including new offerings for Swift, Dart, Linkerd, Jaeger, and more. ## Dart Macros for Flutter: A Guide to Compile-Time Code Generation DevFeed: [Dart Macros for Flutter: A Guide to Compile-Time Code Generation]() Original publisher: [Read original article]() Author: Marvin März Published: 2024-11-04T12:33:03Z Content type: tutorial Language: en Sources: [QuickBird Studios Blog]() Topics: [Dart](), [Flutter](), [Code generation](), [build times](), [Development](), [configuration](), [Programming]() Tags: [beta-channel](), [build-times](), [code-generation](), [compilation](), [configuration](), [dart](), [development](), [examples](), [flutter](), [guide](), [how-to](), [language](), [post](), [terminal](), [vscode]() ### AI overview A guide to Dart macros for Flutter that explains how they provide compile-time code generation as an alternative to build_runner. It covers setup, beta-channel requirements, Dart version configuration, JSON serialization, and the feature's current limitations and expected rollout. ### Source excerpt Dart macros bring a whole new way to handle code generation for Flutter, offering a simpler, faster alternative to build_runner. No more slow builds or manual updates--macros generate code instantly during compilation, helping you save time and reduce repetitive code. In this guide, we'll show you how to set up and use macros, build custom examples, and understand their pros and cons, so you can make the most of this powerful new feature in your Flutter projects. The post R.I.P. build_runner: A Deep Dive Into Macros in Dart & Flutter appeared first on QuickBird Studios. ## Building offline-first mobile apps with Supabase, Flutter and Brick DevFeed: [Building offline-first mobile apps with Supabase, Flutter and Brick]() Original publisher: [Read original article]() Author: Tim Shedor; Tyler Shukert Published: 2024-10-08T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [App](), [data](), [Code generation](), [Dart]() Tags: [apps](), [cache](), [code-generation](), [dart](), [data](), [flutter](), [mobile](), [offline](), [sqlite]() ### AI overview A tutorial on using Brick with Flutter and Supabase to build offline-first mobile apps backed by local caches such as SQLite. It covers synchronization, caching, generated adapters and migrations, and repository-based queries. ### Source excerpt Brick is an all-in-one data manager for Flutter that handles querying and uploading between Supabase and local caches like SQLite. Using Brick, developers can focus on implementing the application without worrying about translating or storing their data. ## Building On-call: Building a multi-platform on-call mobile app DevFeed: [Building On-call: Building a multi-platform on-call mobile app]() Original publisher: [Read original article]() Author: Rory Bain Published: 2024-07-15T15:06:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [multiplatform](), [Kotlin Multiplatform](), [Flutter](), [React](), [Android](), [iOS](), [Kotlin](), [Dart](), [Swift](), [SDKs](), [User experience (UX)]() Tags: [dart](), [flutter](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [javascript](), [kotlin](), [mobile](), [multiplatform](), [on-call](), [outage](), [platform](), [post-mortem](), [react](), [react-native](), [slack-incident](), [ui](), [ux]() ### AI overview The article describes how incident.io evaluated technologies for a greenfield, multi-platform On-call mobile app. It compares native Swift and Kotlin apps with Kotlin Multiplatform, Flutter, and React Native, discussing platform-specific development, shared code, rendering, native UI components, and adherence to OS UI and UX standards. ### Source excerpt What does it take to build a greenfield mobile app in 2024? When we launched On-call earlier this year, we had to find out. ## Using Dart FFI and C for Objective-C and Swift Interoperability in Flutter iOS Apps DevFeed: [Using Dart FFI and C for Objective-C and Swift Interoperability in Flutter iOS Apps]() Original publisher: [Read original article]() Author: Marvin März Published: 2023-12-11T15:43:49Z Content type: tutorial Language: en Sources: [QuickBird Studios Blog]() Topics: [Dart](), [Flutter](), [interoperability](), [iOS](), [Swift](), [Objective-C](), [C](), [Code]() Tags: [c](), [dart](), [flutter](), [interop](), [interoperability](), [ios](), [objective-c](), [platform](), [post](), [swift]() ### AI overview This guide explains how Dart 2.18's Objective-C/Swift Interop lets Flutter applications call native iOS code from Dart through Dart FFI and C. It discusses limitations of platform channels, including duplicated boilerplate and maintenance concerns, and introduces the interop approach. ### Source excerpt Dart 2.18 introduced Objective-C/Swift Interop. In this comprehensive guide, we explore how to seamlessly integrate native iOS code into your Flutter app using Dart FFI and C as an interoperability layer. The post Platform Channels are Dead! Objective-C/Swift Interop is Here! appeared first on QuickBird Studios. ## Bootstrap 5.3.2 DevFeed: [Bootstrap 5.3.2]() Original publisher: [Read original article]() Author: Julien Déramond Published: 2023-09-14T14:30:00Z Content type: release Language: en Sources: [Bootstrap.com]() Topics: [Bootstrap](), [Dark Mode](), [Dart](), [Documentation](), [npm]() Tags: [bug-fixes](), [compatibility](), [dark-mode](), [dart](), [documentation](), [npm](), [release](), [v5]() ### AI overview Bootstrap v5.3.2 is a release focused on bug fixes, documentation improvements, and color mode enhancements. It fixes Dart Sass deprecation warnings and collapse targets using multiple IDs, improves contrast in light and dark modes, adds color customization, and updates documentation and community links. ### Source excerpt Bootstrap v5.3.2 is here with bug fixes, documentation improvements, and more follow-up enhancements for color modes. Keep reading for the highlights! Highlights Passing a percentage unit to the global abs() is deprecated since Dart Sass v1.65.0. It resulted in a deprecation warning when compiling Bootstrap with Dart Sass. This has been fixed internally by changing the values passed to the divide() function. The divide() function has not been fixed itself so that we can keep supporting node-sass cross-compatibility. In v6, this won't be an issue as we plan to drop support for node-sass. Using multiple ids in a collapse target wasn't working anymore and has been fixed. Color modes Increased color contrast of form range track background in light and dark modes. Fixed table state rendering for color modes with a focus on the striped table in dark mode to increase color contrast. Allow color customization for color modes. Docs Added alternative CDNs section in Getting started -> Download. Added Discord and Bootstrap subreddit links in README and Getting started -> Introduction: Discord maintained by the community Bootstrap subreddit Get the release Head to https://getbootstrap.com for the latest. It's also been pushed to npm: [Next page]()