Today, we're releasing Flet 1.0! 🎉
\nMore 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.
\nSince then, that idea has grown through the apps you've built, the feedback you've shared, and the contributions you've made.
\nToday, 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.
\nGetting 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.
\nFlet 1.0 means it's ready for building production apps.
\nWhen 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.
\nWhy do we think it's ready? A big part of the answer is testing, from individual Python functions all the way to packaged apps running on devices:
\nflet build integration tests build apps with Python 3.12, 3.13, and 3.14 for Windows, macOS, Linux, iOS, Android, and web. Android and web builds are also checked from multiple host operating systems.flet test integration tests go further: they launch a packaged app and interact with it on all five native platforms, across all three bundled Python versions, including Linux ARM64.These checks are automated in CI, with unit tests running on relevant pushes and pull requests, and build and device integration suites running on relevant pull requests. You can inspect the framework CI, control tests, build matrix, and on-device tests.
\nYou can also write integration tests for your own apps using pytest. Run them with flet test against your packaged app on desktop or mobile: tap buttons, enter text, and verify complete user flows. On Android and iOS, screenshot comparisons help catch visual regressions too.
If that doesn't give you confidence that the framework is stable, I don't know what will! 😅
\nOur API documentation is generated from Python sources, so the descriptions you see in your editor and on the website come from the same place. Example screenshots and GIFs come from integration tests, with CI checking the rendered UI against reference images.
\nWe even built our own tooling, CrocoDocs, to bring Python API documentation into Docusaurus. It connects docstrings, cross-references, runnable examples, and generated media, making it easier to keep documentation aligned with the framework. Read how we built the documentation pipeline.
\nSince the alpha, we've improved the parts of Flet that affect how responsive your app feels and how easily it reaches users:
\nFlet can bundle Python 3.12, 3.13, or 3.14 with your app. Choose the version that works for your dependencies and move to a newer runtime when you're ready. Web builds use the corresponding Pyodide release. See how to choose a Python version.
\nAnd Python should still feel like Python when your app runs on a phone. That means being able to use the libraries you already rely on.
\nOur package index now contains more than 100 packages, including NumPy, pandas, Matplotlib, Pillow, SciPy, scikit-learn, cryptography, and pydantic-core, along with supporting native libraries. Our mobile-forge pipeline automates building wheels for iOS and Android across supported Python versions, with integration tests to exercise packages on mobile. Availability depends on the package and target, but you no longer have to start by figuring out how to cross-compile a native dependency yourself.
\nFlet Declarative lets you describe the UI as a function of application state and organize it into reusable components. As an app grows, that makes it easier to reason about changes than manually keeping controls synchronized across many event handlers.
\nWe use it ourselves: both Flet Studio and the Flet mobile app are declarative Flet apps. Building our own products with Flet helps us find and fix the same problems you encounter in yours.
\nThe imperative style remains supported. See our comparison of declarative and imperative apps to choose the approach that fits your project.
\nWe promise not to break everything so often. :)
\nMore seriously, we know that every API change can mean work for someone maintaining an app. With 1.0, our goal is to make upgrades more predictable, give you time to adapt, and explain what needs changing.
\nOur compatibility policy describes how this works: when possible, APIs are deprecated before removal, with warnings and documentation pointing you toward their replacements. The default deprecation period is three minor releases, with exceptions explained in release notes or migration guidance. Changes that require action are collected in breaking changes and deprecations.
\nThe Flet MCP server gives your AI coding assistant access to version-specific Flet API information, with additional tools for finding examples, icons, and CLI options. It helps the assistant work with the API you're actually using.
\nFlet Studio gives you a place to explore Flet in your browser: try examples, fork an app, edit it, and share it with someone else. Its built-in AI agent can help you get a first version running, and you can download the project to continue developing locally. It's an easy way to go from "I wonder if I could build this" to something you can try.
\nWe believe Flet 1.0 is ready for production apps. At the same time, 1.0 is just a milestone, and Flet will continue to evolve.
\nThere will be bugs to fix, APIs to improve, and workflows that could be easier. We will keep working on performance, platform support, documentation, and the everyday details that make a framework pleasant to use.
\nOur next chapter is about improving the Flet framework and making the whole experience of building, shipping, and using Flet apps better. The roadmap for 2026 and 2027 covers three areas:
\nThe goal is to let you spend more time building your app while the tools help with the work around it, from the first experiment to publishing and maintaining it. These are our plans for the coming releases; follow the roadmap as they take shape.
\nIf you use pip:
\npip install 'flet[all]' --upgradeIf you use uv with pyproject.toml and want to upgrade all dependencies:
uv sync --upgradeTo upgrade only the core Flet packages:
\nuv sync --upgrade-package flet \\\n --upgrade-package flet-cli \\\n --upgrade-package flet-desktop \\\n --upgrade-package flet-webIf your project pins an older Flet version, update the version constraints in pyproject.toml or requirements.txt first. Update any Flet extension packages you use, such as flet-audio or flet-video, to their matching 1.0 release as well.
Before upgrading an existing app, review the 1.0 migration notes, including removed deprecated APIs and changes to InputBorder.
If you're moving from 0.28.x, this is a larger migration - Flet 1.0 is not a drop-in replacement. The new Migrating from Flet 0.28 to 1.0 guide walks through it step by step, starting with dependencies and the renamed APIs. Pay particular attention to the single-threaded model: in 0.28 every sync event handler ran on its own thread, so blocking code never froze the UI. In 1.0 handlers run on the app's event loop, and code that was fine before will make a migrated app feel unresponsive until it's moved off the loop.
\nNew to Flet? Follow the getting started guide or open Flet Studio and try it right in your browser.
\nTo everyone who contributed code, reported a bug, improved an example, answered a question, or trusted Flet with an app: thank you 🙏🏻. You helped us get here.
\nReaching 1.0 is a moment we're proud of, and we're excited to see what you build with it. If you've been waiting for 1.0 to give Flet a try, today is the day.
\nGo get Flet 1.0, build something you've been dreaming about, and share it with the community! 🎉
","headings":[{"level":1,"text":"Flet 1.0","id":"flet-1-0"},{"level":2,"text":"What 1.0 means","id":"what-1-0-means"},{"level":3,"text":"Tests, tests, and tests","id":"tests-tests-and-tests"},{"level":3,"text":"Documentation that grows with the code","id":"documentation-that-grows-with-the-code"},{"level":3,"text":"Faster updates, faster startup, better packaging","id":"faster-updates-faster-startup-better-packaging"},{"level":3,"text":"Your Python version, your Python libraries","id":"your-python-version-your-python-libraries"},{"level":3,"text":"Declarative UI for larger apps","id":"declarative-ui-for-larger-apps"},{"level":3,"text":"A commitment to smoother upgrades","id":"a-commitment-to-smoother-upgrades"},{"level":3,"text":"Better tools for getting started","id":"better-tools-for-getting-started"},{"level":3,"text":"Ready doesn't mean finished","id":"ready-doesn-t-mean-finished"},{"level":2,"text":"What's coming","id":"what-s-coming"},{"level":2,"text":"How to upgrade","id":"how-to-upgrade"},{"level":2,"text":"Thank you! ❤️","id":"thank-you"}]}}