When we launched Flet Studio back in May, it was a place to write a Flet app in the browser, run it and share it as a link. In July it got an AI agent, and in September the agent got eyes and ears to see the app it builds.

That first post ended with a promise: "Further down the road we'd love to take you the rest of the way: packaging and publishing your app straight from the browser. That part's still cooking."

It's cooked! Today we are releasing Flet Studio 2.0. It takes your app from the browser to your users: build it for Android, iOS, Windows, macOS, Linux and the web, sign it, and publish it to Google Play, the App Store and the Microsoft Store. No Xcode, no Android Studio, no Flutter SDK, and no Mac required to ship an iPhone app.

Flet 1.1.0 is here, the first feature release since Flet 1.0!

When we shipped 1.0, the roadmap promised "more UI choices such as shadcn" and newer Flutter versions. 1.1 delivers the first of both: a full set of shadcn/ui-styled controls, local notifications on every platform, a cleaner neutral default theme, and Flutter 3.47 with the Impeller renderer on desktop. There's also a long list of flet build improvements and bug fixes, many of them from the community.

Highlights in this release:

• shadcn/ui controls - 33 new controls styled after shadcn/ui, with color schemes and the Lucide icon set.
• Local notifications - show, schedule and cancel notifications on Android, iOS, macOS, Windows, Linux and web.
• Neutral theme surfaces - white and near-black backgrounds by default, plus new themes for text fields, dropdowns and Markdown.
• Min and max sizes on every control - min_width, max_width, min_height and max_height for responsive layouts without resize handlers.
• Flutter 3.47.9 with Impeller as the default desktop renderer.
• More flet build options - Android intent filters and App Links, package visibility queries, iOS entitlements, per-platform permissions and more.
• New APIs - RefreshIndicator, Page.get_package_info(), keyboard actions for text fields and an awaitable page.run_task().
• Faster web loading - Flet serves web app files gzip-compressed, about 3x smaller.

Building an AI agent is exciting. Seeing people actually use it and get the results they wanted is even more exciting. And seeing early adopters go beyond the free plan and subscribe to the Creator plan is the best part! Thank you for your support! :)

Today's release of Flet Studio gives the agent eyes and ears: it can now run your app, take a screenshot of it and read its console while it's working. You can also attach pictures, PDFs and code files to your messages, or just paste a screenshot.

Today, we're releasing Flet 1.0! 🎉

More than four years ago, we introduced Flet with a simple idea: building a cross-platform app should be within reach of anyone who knows Python.

Since then, that idea has grown through the apps you've built, the feedback you've shared, and the contributions you've made.

Today, Flet has more than 16,700 stars on GitHub, 100 contributors and has been downloaded from PyPI more than 9,000,000 times! We've merged over 1,000 pull requests, closed 2,800 issues and our Discord community has grown to more than 6,000 members.

Getting started is easier, too: Flet Studio lets you build, explore, and share apps in your browser with help from its AI agent. If you prefer your own editor, the Flet MCP server gives your AI coding assistant up-to-date knowledge of Flet's API.

What 1.0 means​

Flet 1.0 means it's ready for building production apps.

When we announced the alpha, we promised to make Flet more reliable, improve the docs, and add more tests. We've been working on those promises ever since, so you can build your app with confidence and keep it running as Flet grows.

In case you missed it, we have Flet Studio - an online tool for building Flet apps and sharing them with other users. What started as a quick "FletPad" experiment has already grown into a solid app - an online Flet IDE, if you will - with user accounts, a forkable gallery of examples, multiple apps per account, and version history. You can play with Flet and learn the framework before ever running pip install flet on your machine. Flet Studio itself is written in Flet, with a custom FastAPI backend, and it's a fantastic opportunity for us to dogfood Flet ourselves.

Our vision is to shape Flet Studio into a hub of online services that help you build better Flet apps. The first such service was an online editor with the ability to share your apps with other users.

Today we are introducing a new member of the family - the AI agent!

Go to studio.flet.dev and ask something like:

...and in a few moments you get code you can start working with: