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.

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.

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 Flutter

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 Flutter

• 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 code

• What you’ll learn: Principles for writing high-quality, maintainable Flutter code, and how modern tooling — including Widget Previews, DevTools, MCP servers, and Skills make it easier than ever to build great apps.
• Why it matters: AI can write code faster than ever, but best practices and robust tooling provide the quality control needed to keep Flutter applications maintainable over time.

Introducing the Full-stack developer series

• What you’ll learn: Not a lot, but this less-than-two-minute video is fun and introduces the four episode series.

Full-stack dev series #1 — Flutter + A2UI = GenUI

• What you’ll learn: A technical deep dive into the building blocks of Generative UI, with a top-to-bottom conversion of a text-based chatbot into an agent that creates its own UI and understands how you interact with it.
• Why it matters: Not only can GenUI turn a slow, text-based experience into a delightful one, but it opens up new user experience patterns in which static designs and route hierarchies become flexible, on-demand UI tailored to individual users and their goals.

Full-stack dev series #2 — Full-stack Dart

• What you’ll learn: How to unify your app’s tech stack and eliminate context switching by using Dart for both frontend and backend logic. This video builds a complete serverless application live, using Dart for Firebase Cloud Functions.
• Why it matters: This approach improves development velocity and reduces costs by allowing teams to share logic, tooling, and expertise across the entire application stack.

Full-stack dev series #3 — Introducing Genkit Dart

• What you’ll learn: How to create Genkit flows that power your app’s backend and frontend, and discover the essential security steps needed to protect your AI endpoints. This video covers everything from initial setup to implementing rate limits and caching to keep your project secure and cost-effective.
• Why it matters: Genkit bridges the gap between prototyping and shipping reliable AI applications. It simplifies building AI into existing code by providing a unified SDK across multiple languages and models, alongside robust debugging and monitoring tools. Genkit works as a backend, but also in your Flutter app!

Full-stack dev series #4 — Everything you don’t know about building great native apps with Flutter

• What you’ll learn: All the small additions we’ve made to Flutter to make a compelling native experience, from embracing native workflows, supporting new languages for Dart binding generation, or new rendering methods that balance the needs of host UIs and Flutter
• Why it matters: Flutter is not about finding a “lowest common denominator.” It is about providing a high-fidelity, high-performance framework that respects and enhances the native platforms it runs on.

…and that’s it!

Thank you all for joining along as we brewed up one of our favorite I/Os yet. Stay tuned for more blog posts, videos and docs about everything we announced, and all of the community events we’re attending starting next month.

That’s a wrap: Everything Flutter at Google I/O 2026 was originally published in Flutter on Medium, where people are continuing the conversation by highlighting and responding to this story.

Our team has been hard at work this Spring, preparing to meet over 30,000 of you in Las Vegas for Google Cloud Next. For those who couldn’t make it in-person, here is a breakdown of the major highlights, announcements, and experiences from the Flutter and Dart team.

Big announcements

• Full-stack Dart: The team announced a preview of Dart support for Firebase Functions. Yep, that’s right: experience using Dart for both your frontend and backend. We also introduced deeper integrations with Firebase using the Dart Admin SDK to reduce context switching and improve development velocity.
  Check out the announcement blog, and documentation, and stay tuned for a full breakout session all about this feature at Google I/O.

Onsite experiences

• GenLatte: We built an AI-powered specialty coffee shop in the center of Next, created with Flutter GenUI. Attendees ordered drinks using a GenUI Flutter app, then watched baristas make a latte and print a custom nanobanana-generated image on the foam.

• Agentic mobile & web demos galore: The expo floor was packed with energy, including three Dart and Flutter demos, showcasing Fullstack Dart, GenUI, and a special appearance by our friends over at VGV.

• The Builder hub: This served as the “home base” for the developer community on the Expo floor. It featured dedicated booths for Flutter and our friends at Firebase and Go, providing a space for developers to connect with experts and explore new tools.

Key sessions & customer stories

• Developer keynote: Emma Twersky hosted the Developer keynote, showcasing how Flutter is part of Google Cloud’s big bet on the future of agents.

• Toyota & Talabat: Real-world enterprise success was a major theme. Abdallah Shaban took the stage alongside industry leaders to showcase how Flutter is transforming their core products. Toyota shared how they are revolutionizing automotive UX using Flutter for their next-generation infotainment systems, while Talabat demonstrated how they innovate faster and scale across the Middle East using the framework.

• Generative UI Deep Dive: Yegor Jbanov and Andrew Brogdon led a session on how to move beyond text-based chatbots by giving your agents the power to create their own UI.
  Stay tuned for Google I/O where this session will be available world wide on the Flutter YouTube channel.

• Building full-stack Dart: Rody Davis and Kevin Moore shared why you should be excited about today’s biggest announcement for Dart.
  Stay tuned for Google I/O where this session will be available world wide on the Flutter YouTube channel.

Our community is thriving

• GDE Summit: Held just before the main event, this summit brought together over 350 global Google Developer Experts (GDEs) to share feedback on Flutter with the core team, including a main stage session on Flutter GenUI.
• Developer meetups: Throughout the week, the Expo Meetup Hub hosted informal gatherings. Flutter helped host the Mobile Developers meetup, and we had a blast meeting community members from around the world and sharing why we think Flutter is the best way to build.

And that’s a wrap! But not for long… Register today for Google I/O 2026 where our team has even more planned. We can’t wait to surprise you. 😉

That’s a wrap: Everything Flutter at Google Cloud Next was originally published in Flutter on Medium, where people are continuing the conversation by highlighting and responding to this story.

The Flutter team has been hard at work preparing for Google Cloud Next and Google I/O this Spring. I strongly believe in the power of community, whether digital and online, or in-person and interactive. For Flutter, that means a truly global community and hundreds of thousands of developers around the world. Some of the most impactful moments of my career have come from those — community thrives in community-led events.

As we kick off our year and the upcoming release of Dart 3.12 and Flutter 3.44, the Flutter team is setting out to meet as many of you as possible, around the globe. Our mission is to build the most productive app framework and language for high-performance, full-stack, multi-platform applications and ephemeral experiences. And doing that means hearing from you.

To be transparent and open, we’ve updated the list of events where our team will be present, or we have sponsored the presence of our Google Developer Experts. Our developer relations team is constantly engaging with developers, founders, enterprises, and builders by organizing: customer and partner advisory boards, our meetup organizer network, Flutteristas, the Flutter consultants program, Google Developer Experts, and Google Developer Group organizers.

If you’ve been looking for an opportunity to connect with the team, see a live demo, or give us feedback in person, you can find us at the following events for the rest of the year:

April

• Google Cloud Next (Las Vegas, NV) — April 22–24

May

• Flutterconf Spain (Malaga, Spain) — May 08
• Google I/O (Sunnyvale, USA) — May 19–20
• Flutter Flow Developers Conference (San Francisco, CA) — May 27–28

June

• mDevCamp (Prague, Czechia) — June 03
• Flutter Tech Summit (Warsaw, Poland) — June 09
• Config (San Francisco, CA) — June 23–25
• I/O Connect Berlin (Berlin, Germany) — June 25

July

• I/O Connect Bengaluru (Bengaluru, India) — July 14
• Fluttercon USA (Orlando, FL) — July 16–17

August

• Ai4 (Las Vegas, NV) — August 4–6
• I/O Connect China (China) — TBD
• RenderATL (Atlanta, GA) — August 12–13

September

• Flutter & Friends (Stockholm, Sweden) — Sept 3–5
• FlutterConf LATAM (Cancún, México) — September 22–23

October

• next.app devcon (Berlin, Germany) — October 7–9
• All Things Open (Raleigh, NC) — October 19–20
• Flutter Kaigi/Ninjas (Tokyo, Japan) — October 29–30
• Google for Developers events (DevFest and Build with AI) — Throughout Fall and Winter 2026.

Stay tuned and bookmark Flutter.dev’s Events page as we continue to add more events throughout the year.

Are you hosting a Flutter event or meetup not listed here? Reach out to our team to see if we can attend if we’re already in your area — we want to meet and share with as many of you as possible!

Come meet the Flutter core team on tour in 2026 was originally published in Flutter on Medium, where people are continuing the conversation by highlighting and responding to this story.

Transparency is a core goal of the Flutter open source project, and today we’re happy to share our roadmap for the next generation of apps. Our mission remains largely unchanged, we’re still working toward our long-term goal of creating the most popular, fastest growing, and highest-productivity multi-platform UI framework. You can check out the freshly updated roadmap on GitHub for all the details, and in this post we will cover the themes driving our mission.

As you dive into our plans for the year, keep in mind that this roadmap is — as it’s always been — our aspirational strategy for what’s ahead. As with any other roadmap, plans tend to shift and adapt throughout the year, so don’t be surprised if some changes happen along the way. While it primarily reflects the work our teams at Google are focusing on, the truth is that the Flutterverse is now so much bigger than any one company.

High-fidelity multiplatform: Impeller, Wasm, and beyond

Our driving mission is to continue to deliver the best multiplatform stack by focusing on native-level quality and performance. In 2026, we are completing the migration to the Impeller renderer on Android. By finally removing the legacy Skia backend on Android 10 and above, we’re ensuring smooth animations and reducing jank for every user. We continue to see Impeller as the best solution for fast startup and consistent performance.

On the web, we intend for WebAssembly (Wasm) to become the default to deliver native-quality experiences and performance. We are also committed to deep platform integration, ensuring day-zero support for Android 17 and upcoming iOS releases, alongside multi-window support for desktop where our partners at Canonical continue to make progress.

GenUI, ephemeral experiences and agentic apps

We are fundamentally changing app architecture to enable agentive UIs — interfaces that aren’t just pre-built, but adapt in real-time to user intent. This is powered by the Flutter GenUI SDK and the A2UI protocol, enabling AI models to generate rich experiences dynamically.

To support this, we are investigating evolving the Dart language by adding support for interpreted bytecode in the Dart runtime. This enables “ephemeral” code delivery, where specific portions of an app can be loaded on demand without requiring a full app store update — a critical technical step for truly agentic apps.

Full-stack Dart: Bring your tooling everywhere

We are broadening our stack to support the evolution towards full-stack and agentive apps. A major focus is Dart Cloud Functions for Firebase, providing ~10ms cold starts to ensure high-performance backend logic. We are also investigating Dart support for the Google Cloud SDK to enable you to easily connect and build your backend on Google Cloud. Additionally, we are working with the Genkit team on enabling Dart support to help you build sophisticated AI features.

AI-reimagined developer experience

AI coding agents are disrupting the way apps are built. We’ll continue to collaborate within Google to ensure Dart and Flutter have top-tier support in Gemini CLI and Antigravity, ensuring core workflows like stateful hot reload work seamlessly with AI agents.

We are also investing in MCP (Model Context Protocol) servers for Dart tooling, enabling AI agents to perform complex refactors and choose secure, performant libraries with high accuracy by “talking” directly to the Dart analyzer.

Sustainable open-source & governance

To unlock Flutter’s full potential, we are moving towards an open and sustainable operating model. This includes decoupling the Material and Cupertino design systems into standalone packages to accelerate development and allow them to evolve independently. We are also improving the extensibility of the Flutter Engine so support for new platforms can be authored “out-of-tree.”

We are deepening our commitment to the ecosystem by formalizing how we collaborate with stakeholders. Central to this is the expansion of our Consultancy Program, Insiders and Google Developer Expert (GDE) network, Customer Advisory Board (CAB), and Partners Advisory Board (PAB), which provide direct feedback to our teams.

Modern syntax & compiled performance

Dart continues to evolve as a high-performance language. In 2026, we plan to ship Primary Constructors to streamline class declarations and Augmentations to simplify code generation. We will continue to focus on improving build_runner and Dart/Wasm compilation, while refactoring the analyzer to improve performance for large-scale applications.

Bringing developers to Flutter and Dart

Our recently completed new Dart and Flutter learning pathway provides a streamlined, guided onboarding path for new builders. In 2026, we plan to continue our outreach both in-person and across digital platforms to improve the experience for developers and their AI tools.

See you at Google Cloud Next & I/O!

While this roadmap is our plan for the year, you won’t have to wait long to see the next big things from the team. Mark your calendars for Google Cloud Next 2026 in Las Vegas (April 22–24) and Google I/O 2026 (May 19–20). These will be the best moments to see Flutter in action next!

With non-Google contributors now outnumbering those of us employed by Google, there is an incredible amount of exciting work happening that isn’t even captured on this list! Accurate forecasting is always a challenge in an open source project, so please take this as a sincere statement of our intent and priorities rather than a fixed guarantee. We are unbelievably excited to keep building the future of apps alongside all of you and can’t wait to see what you’ll build!

What are you most excited for? Let us know on socials with the hashtag #Flutter2026. And if you’re excited about hearing more from us, be sure to follow us on X, check out the repos on GitHub, and keep an eye on this blog for the latest updates. Let’s build the future of apps together! 🚀

Flutter & Dart’s 2026 roadmap was originally published in Flutter on Medium, where people are continuing the conversation by highlighting and responding to this story.

Hi, Flutter community! My name is Emma Twersky, and I’m back with monthly updates from the Flutterverse. I’m so thankful for the warm welcome, and excited to be a part of this community.

This post is a bit of a two-for-one: we’re diving into hot new content from today’s livestream, “Flutter Flight Plans,” helping you take flight on some of our most requested topics. Then we’ll take a moment to reflect on what a truly landmark year 2025 has been. We’re all-in on making Dart & Flutter the best way to build amazing multi-platform apps, and we’re excited to show you what’s new and what’s next.

10 Highlights from Flutter & Dart in 2025

What a year! Let’s dig into just 10 of the top moments, although it was hard narrowing it down…

As you might know, Dart and Flutter ship quarterly updates. In 2025, we shipped eight packed stable releases:

1. Flutter 3.29 & Dart 3.7 (Feb 2025): This release was all about performance and fidelity, with big Impeller updates, the move of Dart execution to the main thread on mobile to improve native interop, and a new Dart formatter.

2. Flutter 3.32 & Dart 3.8 (May 2025): We got experimental web hot reload, Cupertino “Squircles,” stylus support on Android, cross-compilation for Dart, and null-aware elements.

3. Flutter 3.35 & Dart 3.9 (Aug 2025): Web hot reload became default, we launched experimental Widget Previews, introduced the Dart & Flutter MCP server, and announced the Material/Cupertino decoupling.

4. Flutter 3.38 & Dart 3.10 (Nov 2025): Dart added dot shorthands, web tooling improved, and Widget Previews got IDE integration! Plus, crucial iOS 26/Xcode 26 support and the UIScene migration path.

5. We laid out our vision early in the year, sharing our Flutter 2025 Roadmap Update and it’s exciting to see how much has been delivered and the continued focus on multi-platform excellence and AI integration.

… and since many of you have been asking, yes, we plan to be back in early 2026 with a similar annual post as we continue to adjust our roadmap based on your feedback. Our goal is ultimately to continue building the best cross-platform framework with the best developer experience and feature set.

6. Speaking of you… the Flutter community and ecosystem are thriving! At Google I/O, we shared that nearly 30% of new free iOS apps are built with Flutter.

We’re constantly amazed by what you’re building. In 2025, we worked with some amazing companies to showcase how they’re building and betting on Flutter and Dart in big ways, including NotebookLM, teamLab, Agape, Universal Destinations & Experiences, Reflection.app, and GE Appliances.

Some highlights from this year include:

talabat is MENA’s leading on demand delivery platform. With millions of daily users, talabat uses Flutter to connects millions of customers to food, groceries, and more across 8 countries.

Google’s NotebookLM used Flutter to meet explosive user demand, delivering a delightful 4.8-star mobile experience in under 7 months.

teamLab uses Flutter in art and digital solutions, extending experiences to over 35 million people.

Flutter is woven into Agapé Wellness’s mission to help people feel close, even when apart.

7. As we continue growing, it’s important to understand How Flutter Works. So, we made a whole series on that.

Now that we know how it works, let’s make it more flexible for the future.

8. The work to decouple design systems and move Material and Cupertino into their own packages is underway, as announced in Flutter 3.35. This is a big step for the maturity and flexibility of the ecosystem. I’ll let Justin explain exactly what this means:

9. We know speed matters… so we made build_runner faster (two or more times in some cases!). John shares how we’re accelerating Dart code generation in this great video:

10. Another thing that sped up in 2025 is the pace of AI.

AI truly took center stage in the Flutter and Dart ecosystem. The Building Agentic Apps series and our announcements at Google I/O really set the tone, and we’re ending the year with two Flutter Flight Plans to prepare for take off into the future of apps. 2025 brought a massive leap in AI-assisted development. Read all about it in our Create with AI section of the Flutter documentation.

The Dart and Flutter MCP Server is now stable, empowering tools like Gemini CLI, Antigravity, and wherever you’re building with AI.
It’s been incredible to see Gemini in Android Studio supercharge Dart and Flutter development. And the Flutter Extension for Gemini CLI? Game changer for AI-assisted app building.

We’re also announcing the Flutter AI Toolkit v1.0, now ready for your production workloads. The Flutter AI Toolkit is a set of AI-related widgets to make it easy to add an GenAI features to your Flutter app. Since our last beta release, the AI Toolkit has migrated to the Firebase AI Logic SDK, adding new features along the way, including multi-turn function calling for agentic workflows, the ability to plug-in custom speech-to-text translators, and full support for turning LLM responses into widgets.

And speaking of new tools, Google introduced Antigravity, a new IDE experience aimed at boosting developer workflows with AI. We’re partnering with teams across Google to make Flutter development a world-class experience in all of the ways that Google AI is available. Watch the Observable<Flutter> livestream for more.

I want to share one more thing that we’re most excited about heading into 2026…

11. We launched the alpha of the GenUI SDK for Flutter on pub.dev, opening doors for creating dynamic UIs with LLMs.

GenUI is here to help you generate Flutter UI from natural language or structured data, potentially speeding up your development flow significantly. I’ll let Khanh dive into the details:

It’s fantastic to see the community already building on GenUI!
Check out two community members doing just that:

• Khalid built an AI Concierge Agent using GenUI, including a great recap video. Definitely check it out!
• dartantic by Chris Sells
  The dartantic_ai package is an agent framework designed to build multi-model agentic apps that run wherever Dart runs, including mobile, web, desktop, the CLI, or on the server. With the new 2.0 release, dartantic provides a ContentGenerator for implementation in the new Flutter GenUI project. This enables you to plug in any provider or model as well as taking advantage of advanced features like server-side tools — like web search and code execution — and media generation, including out of the box support for Google’s new Nano Banana Pro.

We’re working to make our GenUI SDK an industry leader.

One way is partnering with the teams behind ADK and A2UI, offering a more template-driven approach to UI generation. Rody’s talk explores how Flutter is leveraging ADK:

What are you building over winter break?

I ended that list feeling inspired and overwhelmed. There’s so much innovation it’s sometimes hard to keep up. But luckily, the holidays are a perfect time to tinker!

We’re all excited for the holidays for different reasons, some are headed skiing, spending time with loved ones, but it’s also a chance to dig in and learn something new.

If that’s you, we’d love to see what you build. Here are some ideas we’ve brainstormed:

1. Rebuild your personal site in Jaspr — and use Antigravity to make it easier to change up your tech stack
Take an existing website and use an agent to migrate it to Jaspr in a fraction of the time it would take manually, we’ve found Antigravity is very good at this.

2. Start learning about the future of Dynamic UI with GenUI
Build a GenUI Live Sketch Pad app where typed UI descriptions are rendered in real-time by GenUI. Or, if you build something else with the SDK, let us know on socials. The package is alpha so we’re actively looking for feedback on your experience using it!

3. Build an Agentic Workflow: Install the Dart MCP server and create a workflow that takes a screenshot of your app, gets a critique from Gemini, and applies the changes with hot reload.

4. Generate UIs from Thin Air: Take your workflow one step further by using Stitch to design a UI, then ask Gemini to write the Flutter code for you.

5. Become a Flutter contributor: Make your first contribution to Flutter. Find and fix an open documentation issue or tackle a “good first bug.”

6. Crush Performance Bugs: Use DevTools to profile your app’s performance. Identify and fix a performance bottleneck using tracing and your coding agent.

7. Modernize Your Codebase: Supercharge your existing Flutter project by refactoring it with Dart 3.10’s dot shorthands for cleaner, more concise code.

8. Exploring Gemini APIs in Flutter Build a voice app showcasing different Gemini API features using the Flutter AI Playground sample app which uses the Firebase AI Logic SDK.

9. Build Your Own Code Assistant: Train an agent on your GitHub repository to automatically manage your package dependencies or perform other tedious tasks.

10. Level Up Your App with the Ecosystem: Integrate a service from a Flutter-based business like Shorebird for over-the-air updates or Serverpod for a scalable backend.

Share your winter break projects with the community using the hashtag #Flutter2026.

Thank you for being a part of Flutter in 2025, see you in 2026!

With the foundations laid in 2025, we’re incredibly excited for 2026 as we push the boundaries of multi-platform development, dive deeper into AI-driven ephemeral experiences, and empower you to build the truly full-stack, cross-platform applications of the future.

A huge THANK YOU to the incredible Flutter and Dart communities. Your passion, feedback, and contributions made 2025 amazing. We feel so lucky to be a part of this community. 💙

Wishing you all a wonderful and innovative winter break. We can’t wait to see what you back and building in 2026!

The Top Ten Highlights from Flutter & Dart in 2025 was originally published in Flutter on Medium, where people are continuing the conversation by highlighting and responding to this story.

Hi, Flutter community! My name is Emma Twersky, and I am unbelievably excited to be your new lead for Flutter and Dart DevRel. I’m not just here to talk about new features; I’m here for this community. The number one reason I’m here is for the incredible culture we have. If you haven’t read it, check out Flutter culture and how to preserve it. It’s all about being open, modest, and respectful, all while building fantastic cross-platform apps, and that’s what Flutter and Dart are all about. I’m so excited to be a part of this community, and I can’t wait to share all that we’re working on.

Speaking of fantastic cross-platform apps, our friends over at NotebookLM have been going viral with their Flutter app this year. We visited them to hear about how Flutter accelerated their launch, check it out:

In fact, you can listen to the Audio Overview of this blog post (and all its linked sources) in NotebookLM.

Still with me? Then hold onto your keyboards, because Flutter 3.38 and Dart 3.10 are now available, and they are HOT. These releases are packed with usability enhancements and improvements to our developer tooling. And yes, that includes AI.

Building the future of apps with Google AI and the “Future of apps” series

We’ve got a whole Flutter Flight Plans series dropping this month and next to show you how to build the next generation of apps with Flutter, Firebase, and Gemini.

Building dynamic UI with Flutter GenUI: The new Flutter GenUI SDK is here to help you build dynamic UI that adapts based on your user’s intent. Don’t believe me? Watch the video, “Getting started with GenUI”, then check out the genui package to see it in action.

The easiest way to build with AI: We’ve built a sample app powered by Firebase AI logic that helps you create a nice launching point for integrating AI features into your app. This sample app covers features such as using multi-modal content generation, in addition to the Gemini conversational live API. Get your hands dirty in the Flutter AI Playground.

Build multi-platform Flutter apps with Gemini CLI: Head to the docs to jump into the Flutter extension for Gemini CLI.

Productivity and platform power: What’s new in Flutter 3.38 and Dart 3.10

Now for the main event. Here’s what’s new and why you should be excited.

Dart 3.10 highlights: More expressive, concise, and robust code.

• Dot shorthands: Less typing, more coding. Instead of MainAxisAlignment.start, you can now just write .start. Check out the dot shorthands page to learn more.
• Build hooks: Now stable! Compile native code or bundle native assets directly with your Dart package. Get all the details in the hooks page or watch the Build hooks video.
• And more! There’s a new analyzer plugin system. You can use this system to write your own analysis rules and employ IDE quick fixes. Use the new Deprecated annotation for deprecating specific functionalities.

Dive into the Dart 3.10 technical blog post for the full story.

Flutter 3.38 highlights: A more refined framework, better platform integration, and slicker developer tools.

• Web enhancements: We’ve got a config file for flutter run, proxy support, and hot reload for the web. Because who has time to wait?
• Framework & UI: OverlayPortal is more powerful than ever, and predictive back gesture is now default on Android. We’re also still polishing up Material and Cupertino.
• iOS updates: Full support for iOS 26/Xcode 26, command-line deployment, and a super-important guide for migrating Flutter apps.
• Android updates: NDK r28 is here for 16KB page size compatibility, we’ve plugged a major memory leak, and updated to Java 17.
• Tooling: Big updates to the experimental Widget Previewer tool and IDEs. Go play!
• Accessibility: We’re always working to make Flutter more inclusive. Say hello to the new SliverSemantics widget and better default behaviors.

Want all the nitty-gritty details? Of course you do. Check out the Flutter 3.38 technical blog post.

Community and ecosystem spotlight

This release cycle, our community has been as active as ever, with a host of valuable contributions. Here are just a few examples:

• Windows display properties: Thanks to @9AZX, you can now get detailed display information on Windows, including monitor lists, display sizes, refresh rates, and DPI.
• New convenience constructors: @ahmeddhus added a SliverGrid.list constructor, providing a cleaner API for creating grids from a list of widgets.
• Enhanced gesture handling: @houssemeddinefadhli81 introduced an onLongPressUp callback to the InkWell widget to specifically handle the release of a long press gesture.
• More flexible widgets: @iamtoricool added a maxCount parameter to the Badge.count constructor, and @rkishan516 added a momentary variant to CupertinoSlidingSegmentedControl.
• Important fixes: We also saw crucial fixes for scrolling behavior from @manu-sncf and @yiiim, focus issues from @romaingyh, and more.

💙 Let’s be real: this community is everything. You’re the reason Flutter is what it is today, and beyond OSS contributions to Flutter’s core, we’re constantly blown away by what you create. In this release, we’re putting the spotlight on Kilian and the framework, Jaspr. Where Flutter’s web support is great for applications, Jaspr is a traditional DOM-based (HTML/CSS) web framework that is built on top of Dart. It is a great complement to Flutter web for when you want a Dart-based solution to build sites.

We were so impressed that we migrated our entire documentation infrastructure — both dart.dev and docs.flutter.dev — over to it. Pretty cool, right? We’ve asked Kilian and the team to share the full story in a future blog post, so you’ll be hearing from them soon. In the meantime, we recommend that you try it out yourself!

Get started!

So, what are you waiting for? Upgrade to Flutter 3.38 and Dart 3.10 and let’s build the future together.

• Flutter 3.38 release notes
• Dart 3.10 release notes
• Dive into the future of AI apps
• Play in the Flutter AI Playground
• Join the flutter.dev/community

Announcing Flutter 3.38 & Dart 3.10: Building the future of apps was originally published in Flutter on Medium, where people are continuing the conversation by highlighting and responding to this story.

Angular first launched in 2016 as a way to help developers build modern web applications. Throughout its history, Angular has made millions of developers successful.

Over the past several releases, we’ve focused on improving performance and developer experience on the modern web. Our momentum includes a revamp of Angular’s reactivity system, SSR, and dozens of additional features.

Later this week, we will release Angular v17, including deferred views, built-in control flow, view transitions API support, SSR enhancements and more. This renaissance deserves a modern identity that represent the velocity and stability our team is committed to.

Today, we are excited to launch Angular.dev — the future home for Angular developers.

Angular.dev — the future home for Angular development

New docs… who this?

Angular.dev will be the new site, domain and home for Angular development. Today’s launch includes new tutorials, updated documentation and guidance that will help developers build with Angular’s latest features.

In the coming months, we will continue to collect feedback and improve the site, with a ton of enhancements planned.

Angular.io will continue to be supported as a legacy resource for documentation through v17, and to ensure all old links remain functional. In v18, after collecting feedback and continuing to stabilize the site, we plan to make Angular.dev the official home for all Angular development.

New embedded tutorials

A cornerstone of the new docs is our embedded tutorials, a new way to learn Angular directly in your browser. Written with WebContainers, our tutorials now offer bite-sized steps with side-by-side running code examples to learn (or come back to 😉) Angular’s core concepts.

Introducing Angular.dev/tutorials — a new way to learn Angular concepts directly in your browser.

Today our new tutorials include two ways to get started with Angular:

• Angular.dev/tutorials/learn-angular is a quick in-browser way to learn one, or all, of Angular’s core concepts
• Angular.dev/tutorials/first-app teaches you how to go from Hello World! to your first full Angular using the CLI, including a full video course on our Angular YouTube channel

And you may have noticed, we didn’t stop at Tutorials…

Introducing Angular.dev/playground — a playground for exploring the latest Angular concepts, directly in your browser.

Start with “Hello World”, or select one of our templates and explore our newest features, including Control Flow, Signals, and more. We’ve even included a mini-game inspired by v17’s launch — how @Angular are you?

New documentation and a better UX for all levels of developer

Angular.dev teaches modern Angular development from the start.

Some highlights include:

• 📕 A new content structure, focused on teaching core Angular concepts for beginners, and digging deeper into in-depth guides for advanced developers
• 🧱 All docs and examples are built with Standalone APIs for simplified development, including a fully rewritten Components guide
• ⚡️ Core web vitals guidance written in collaboration with Chrome’s Aurora team, including guides on Image Optimization and Performance Best Practices
• 🌊 New guides for SSR and Hydration, for better app performance by default
• 🔭 More helpful API Reference & CLI references (under development)
• ⚒️ Quick edit/refresh using the Vite dev server in our tutorials
• 🚗 An updated public Roadmap
• 🔍 Better search
• + a whole lot more!

Our team remains committed to stability and backward compatibility, cornerstones of the framework’s reliability. We have updated guides on Keeping up-to-date and NgModules to ensure Angular.dev is helpful for all teams. In the future, we plan to build update.angular.io into Angular.dev, and continue to improve the documentation to further represent the latest best practices and recommendations.

Open source documentation

Angular.dev is a production app using the same v17 technologies its guides recommend — Standalone APIs, Angular Signals, prerendering, hydration, SSR/SSG, View Transitions in the router, control flow, deferred views, and the new application builder with ESBuild and Vite. We’ve also been using the app to test future Angular solutions like zoneless hydration. Our team believes in the power of open source.

Today, we are open sourcing the site so that developers can learn from and contribute to the repository.

Can I contribute?

✨ Yes please! ✨ We would love your help in improving our new site.

With the launch of a brand new site of this scale, our team expects many bugs and opportunities to improve the site and its documentation. If you’re curious about open source, this is a great project to start.

If you have suggestions, bug reports, or documentation/feature requests, please open an issue on GitHub.

Ready to contribute? Checkout our guidelines for how to get started, or click the pencil icon in the docs pages to suggest an edit in GitHub directly. Please note this will only be functional once our PR to open source the site is merged.

Next Steps

Our team will continue to work in open source to improve the site for v18. Our primary focus is improving the embedded playground stability, and our new reference infrastructure.

In the future, we will also build additional guides and a robust cookbook of tutorials, taking advantage of our new embedded playground. We also see an opportunity to create tutorials written to help map concepts from other web frameworks to Angular concepts. 😉

Read more about our current priorities in our public roadmap. We’re excited to continue building!

New look, same framework

The domain isn’t the only thing new about Angular.dev…

Today, we’re also releasing the new Angular logo and brand.

Many developers will remember the first AngularJS shield, a reference to the original HTML5, CSS3 and JavaScript shield logos it joined at the time. A lot has changed in the years since the HTML5 standard was first released, including us.

The new Angular logo represents the future of our framework, designed to signify Angular’s evolution into a modern framework. The Angular roadmap details our commitment to stability and velocity, and our work to improve developer experience and performance, with the power of a large and widely adopted framework. As Angular continues to explore and innovate on the web platform, this new logo will better represent our current efforts and future priorities.

Join Angular’s momentum forwards

Angular’s success is deeply connected to our community. We know many communities, meetups, conferences, blogs, websites, YouTube channels and developers have built their brand on top of ours. This logo is for us and our community, and it’s important that you can join us in updating your brand as well.

Today, we’re open sourcing our brand guidance, so you can join our momentum.

Visit our new Press Kit and follow our guides on how you can adapt the new logo to be your own. If you have any questions on adapting the new logo, or updating your own, please email devrel@angular.io for additional help — we can’t wait to see what you create!

Welcome to the Angular renaissance!

Thank you to the truly amazing community of developers helping launch Angular.dev.

Special thanks to Monogram (Claudio, DJ, Jordan, Leo, Oli, Patrick, Pawel, Sami, TJ) for jumping into Angular, Google Design (Jeremy, Roman, Przemek and all of GDS) for creating a beautiful new brand and identity, the Angular core team (Andrew K., Alan, Amy, Andrew J., Alex R., Alex B., Andrew S., Ben, Christina, Charles, Doug, Dylan, Emma, Jens, Jeremy, Jessica, Joey, Joost, Kevin, Kristiyan, Madleina, Mark, Minko, Miles, Paul, Pawel, Simona, Wagner, Zach) for building the next generation of documentation, our early contributor (Matthieu) for going above and beyond, IfThenCreate (Reagan) for our new playground mini-game, our incredible community of open source contributors, fellow Googlers and Angular Google Developer Experts (Amanda, Cassandra, Christian, Dima, Enea, Fatima, Jess, Jana, Jordan, Iulian, Mariia, Marissa, Mikhail, Olga, Raúl, Richie, Simon) for early feedback, testing, features and bug fixes!

Announcing Angular.dev was originally published in Angular Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.

Angular Universal (specifically @nguniversal/common) versions 16.1.0–16.1.1 depend on the impacted versions of Critters. This vulnerability is fixed in version 16.1.2.

This bug affects applications that use Angular Universal for server-side rendering (SSR). Applications that use build-time prerendering may be affected if they include user-authored data in their pre-rendered HTML. We have no evidence at this time that this bug has been exploited in the wild.

If you depend on any of the affected versions, update your Critters and Angular Universal versions immediately.

Applications that do not use Angular Universal should not be affected. Angular CLI does use Critters in its build process for non-Universal applications, however exploiting the bug in question in this scenario requires a malicious actor to already have access to modify the application source code.

We will follow up with another blog post soon with a more detailed post-mortem.

Notice of XSS issue affecting Angular Universal 16.1.0–16.1.1 was originally published in Angular Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.

Read on to learn more about everything Angular announced at I/O this year.

What’s new in Angular

Minko and Madleina share about the latest from Angular, including updates on hydration, SSR, and reactivity. Discover everything from community updates and the request for comments process to new features landing in v16 and beyond!

Rethinking Reactivity with Signals

Emma and Simona introduce you to Angular Signals, a new reactivity model in Angular. Signals equips you with more high quality tools for fine-grained reactivity, while setting you on a well lit path and providing you with guardrails to make your app performant. Learn how to start exploring the developer preview in Angular v16 today.

Getting started with Angular Signals

Ready to build with Signals? Emma and Alex walk through a real application and the Signals API. You’ll learn about the three reactive primitives introduced with Angular Signals: signal(), computed(), and effect() and how to start building with them in v16.

In addition, we also released the codelab for Getting started with Angular Signals so you can follow along and get started building with signals on your own!

And there’s more!

Angular is constantly collaborating with teams like Chrome’s Aurora, Firebase, Flutter and more, to improve developer experience for all developers. Check out the Google Developer keynote to learn more:

Curious how Angular and Flutter Web can work together? Learn more in “Evolving Flutter’s support for the web”!

Ready to deploy? Firebase can now run Angular Universal with Firebase deploy:

If you’re a web developer chances are you’re using Chrome DevTools. Brush up on the best practices for debugging your apps in “Debugging modern web applications”:

That’s just a small snapshot of everything announced at I/O 23. Find the rest of the content in the event’s program page.

See you at I/O Connect!

Emma, Mark, and the team are so excited to bring this content (and more) in-person and around the globe this summer! Make sure you check out the Web demos area to find us there together with more resources and learning opportunities.

Can’t wait to see you all online and in-person!

Angular at Google I/O 2023 was originally published in Angular Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.

This month we introduce a new blog series, ‘Modern CSS in Angular’, where we’ll take a look at modern CSS enhancements recommended for Angular developers.

This week, we tackle layouts.

Layout has made significant advancements since Angular’s early days. Based on advancements to native layout solutions and removal of support for IE11, the Angular team will stop publishing new releases of the experimental @angular/flex-layout library starting in v15.

@angular/flex-layout is a hybrid JavaScript and CSS layout system that has remained in beta in the Angular organization since v5. During that time, CSS has evolved dramatically, offering new approaches for building performant and scalable layouts. In this blog post, you’ll learn more about the recommended layout approaches in Angular.

Modern CSS layouts

The two most recommended modern CSS layout solutions are CSS Flexbox and CSS Grid.

CSS Flexbox

Flexbox is a one-dimensional layout method that allows you to arrange items in rows or columns. Items flex (expand) to fill additional space or shrink to fit into smaller spaces.

You can see a Flexbox in Angular demo here:

We recommend CSS Tricks: A Complete Guide to Flexbox to get started learning Flexbox.

In general, Flexbox is a good choice for components within your application and small-scale layouts. CSS Grid layout is intended for larger scale layouts. Learn more about the trade-offs of Flexbox and CSS Grid.

CSS Grid

CSS Grid is a two-dimensional layout system for the web. It allows you to arrange content in rows and columns. It has many features that help developers more easily build complex layouts.

You can see a CSS Grid in Angular demo here:

We recommend CSS Tricks: A Complete Guide to Grid to get started learning Grid.

Flex, grid & the future of flex-layout

A core principle of Angular is the separation of concerns. By deprecating flex-layout in favor of CSS, we continue to guide users towards more readable and maintainable code. Additionally, @angular/cdk’s layout package provides lightweight utilities to build responsive UIs. These options provide a reduced payload size and runtime cost, and improve the Lighthouse performance metrics of your site in comparison to @angular/flex-layout.

Starting today we’ll follow Angular’s deprecation practices. Since @angular/flex-layout is a beta package, Angular v15 will publish the last release of @angular/flex-layout.

While @angular/flex-layout never left beta, it gained adoption with over 300k downloads per week. To support applications that rely on the package, we’ll continue publishing security and browser incompatibility fixes for at least a year as part of the long-term support (LTS) for the package.

A plan to migrate to modern CSS

Choosing a modern layout system is based on your app’s structure. Learn more about modern layouts in Chrome’s Learn CSS course.

We are grateful to Angular community contributor and angular/flex-layout co-author Adam Plumer, who has supported the release of angular/flex-layout throughout the years. Read more in Adam’s Farewell to Flex Layout.

Adam volunteered to author migration guides for the most popular use cases — we’d love to hear which angular/flex-layout migrations you want more guidance on in this GitHub issue.

While we cannot map directly to a new layout system with automated migrations because of the complexity and dynamic use cases of the library, we can recommend four layout tools. Here’s a high-level overview:

CSS Flexbox

Flexbox is most similar to @angular/flex-layout, since @angular/flex-layout was designed to give developers an ergonomic way of applying Flexbox layouts in Angular templates. The following code example is a map of common Flexbox properties and the associated properties from @angular/flex-layout.

display: flex;
flex-direction: row // fxLayout
flex-wrap: wrap //fxLayout
box-sizing: border-box;
align-content: stretch, // fxLayoutAlign
align-items: stretch, // fxLayoutAlign
justify-content: flex-start, // fxLayoutAlign

CSS Grid

Many CSS surveys have highlighted the potential of the CSS Grid as the future of two dimensional layout. Due to modern CSS Grid being newer than the design of flex-layout, migration from flex-layout to CSS Grid is a more manual process in order to take advantage of associated properties.

@angular/cdk’s layout package

If you need layout specific utilities in your TypeScript code for dealing with viewport size, Angular also provides the @angular/cdk’s layout package.

The @angular/cdk’s layout package is mainly for use cases when you need to build responsive UI interactions in code, rather than generally creating an application layout. An example might be that for large viewports you want to display a pop-up as a dropdown attached to the trigger element, but on small viewports you want to display the pop-up as a centered dialog.

TailwindCSS

Tailwind CSS provides a template oriented approach to styling, similar to the @angular/flex-layout.

Tailwind CSS is a utility-first CSS framework packed with classes like flex, pt-4, text-center, and rotate-90 that can be composed to build any design, directly in your markup. Read more about Angular + Tailwind CSS.

We recommend exploring all four modern options when planning your migration.

Thank you

We want to take a moment to thank everyone who has contributed to the project over the years.

We’re excited to see how CSS has evolved over the years and the modern layout alternatives that it provides.

Recommending native solutions as best practice allows developers to stay on the performant path while allowing the Angular team to focus on high-impact projects that further move Angular into the future.

Until the next time, go build modern CSS (and join us next for a look at visibility)!

What CSS in Angular would you like to learn about next?

Modern CSS in Angular: Layouts was originally published in Angular Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.