If there is one thing I miss from the past it is when search engines searched for the words you typed

I replied to all of these points in the proposal doc so I’ll stop repeating myself.

I’m assuming most folks will use AI to generate the AI assets in which case these assets can easily account for more of the package bundle than the source, tests, and README for example. According to the proposal: “Packages do not have a maximum size limit as well to mitigate this”.

They contribute to package bloat which isn’t ideal but at least devtools are in service of everyone.

Yes it is. Screenshots and example apps benefit everyone. AI specific docs don’t.

There are a few fundamental differences here:

1. static analysis is a foundational part of Dart
2. linters don’t cost extra to use
3. linters are deterministic and reliable
4. google doesn’t profit from the use of lint rules

The same can’t be said for AI assets/agents.

You can’t ignore this proposal entirely because as it is written

1. it will result in package bloat for everyone regardless of whether they use agents
2. it will make package discovery worse on pub
3. it will put additional pressure/burden on all package authors

Adding extra work on package maintainers' plates doesn't seem like a good way to encourage OSS devs to produce & maintain the great parts of the Flutter ecosystem.

Then I guess we just have to agree to disagree 😅. Making LLM output less bad is not the responsibility of package maintainers or package managers imo. You have to consider the side effects of opening this door and the long term effects it will have on the ecosystem.

Same 😕

Those can be written externally and linked to from the pubspec.yaml just like we have the “documentation” field. I shouldn’t need to download and cache AI docs if I’m not using them.

🙁

If the only thing this does is encourage package maintainers to write LLM-specific docs then I would argue either the package docs and examples need to be improved (which doesn’t require any of the changes in this proposal) or we should not be promoting LLMs as the solution to every problem.

Leave your feedback on the doc to let the team know! 🙏💙

Comment on the document 🙏💙

Packaged AI Assets (PUBLICLY SHARED) SUMMARY Enable packages to directly expose documentation, prompts, or other features to AI Agents Author: Jake MacDonald (@jakemac53) Go Link: flutter.dev/go/packaged-ai-assetsPrototype: https://gi...

Making LLM output less bad is NOT the responsibility of package maintainers.

Looks like the future of pub will be AI generated content for AI consumption.

Is this really what the community wants?

docs.google.com/document/d/1...

hit 'em where it hurts!! 🥰✨

Check out Erick’s latest game built with Flutter and Bloc 🎉💙

New year, new bloc release 🥂

Just released MultiBlocObserver, a quality of life improvement in v9.2.0 of package:bloc 🎉

MultiBlocObserver allows you to register multiple, specialized BlocObserver instances seamlessly 👇

Flutter + Bloc in 35 lines 👇

✅ decoupled UI and logic
🧪 highly testable
⚡️ reactive without subscriptions
🏙️ scalable
👀 predictable
🔍 observable
✨ simple
🛡️ safe
💙 noninvasive

Get Started ↓
bloclibrary.dev

Thanks! 💙

Thanks so much for the kind words! 💙

Thanks so much! 💙

Thanks so much! 💙

Today is my last day at @shorebird.dev. I’ve had a great time working with the team and building some awesome tech but I’ve decided to move on to my next adventure.

Don’t worry, I’m not going anywhere — I’ll still be active in the Flutter/Dart community 💙

Yes because you don’t always have control over the name with dot shorthand. I’d be fine if they just applied to enums but something like fn(.new()) is very hard to read imo. You need to look at the function signature to understand what .new() is referring to.

I’m personally not a huge fan of Dart’s new dot shorthand syntax. It makes code harder to read, there’s no lint rule to standardize one way or the other, and it just adds more complexity to a language which I love for its simplicity.

Hey, folks! The Flutter team is doing a livestream next week, which will include a Q&A. Anything you'd like to ask the engineering, DevRel, and product leads?

Questions about the roadmap, new features, the craziest place they've seen someone get Flutter running, all of these are valid topics. 😀

mason_cli v0.1.3 is out 🥳
pub.dev/packages/mas...

Today is Flame's 8th birthday!! 🥳

Since our graphical media master Renan was busy today I (Lukas) very nicely fixed up last years media. 😅

This year's contest is to create a Flame splash screen.🔥
The winner gets a Flame Care Package!
Deadline: 2025-10-26 23:59 CET (Sunday)