Flet 1.0 is about more than a facelift. Our goal is to help Python developers build production-grade apps that scale from a handful of screens to hundreds of pages, views, and dialogs.

Dogfooding Flet — building our own products like the Flet mobile app and the Control Gallery — made it clear that the imperative approach becomes hard to manage as apps grow.

That’s why Flet 1.0 introduces a declarative approach alongside the existing imperative API, drawing inspiration from frameworks such as React, SwiftUI, and Jetpack Compose.

Here's a quick look at a counter app written declaratively:

import flet as ft

@ft.component
def App():
    count, set_count = ft.use_state(0)

    return ft.Row(
        controls=[
            ft.Text(value=f"{count}"),
            ft.Button("Add", on_click=lambda: set_count(count + 1)),
        ],
    )

ft.run(lambda page: page.render(App))

Keep reading to see how it works and how you can start using it today.

Flet has been in the making for over three years, steadily gaining traction and building a vibrant user community. As more developers adopt Flet for real-world projects, one thing has become clear: people are ready to commit — but they also want to see the same commitment from us.

Releasing Flet 1.0 isn’t just about a version number. It’s about signaling stability, maturity, and long-term vision. A stable API, comprehensive documentation, better testing and clearly communicated roadmap — these are the foundational pieces developers need to confidently build serious apps on Flet.

But Flet 1.0 isn’t just the next incremental release. It’s a complete re-architecture.

The first versions of Flet inherited design decisions from Pglet — a web-based framework with a focus on multi-language support. While that served as a useful starting point, Flet has since evolved into a Python-centric framework for building cross-platform apps — web, desktop, and mobile.

With that evolution came technical debt, architectural misfits, and increasing complexity. Rather than patch over the cracks, we made a bold decision: to rewrite Flet from the ground up. It’s always risky to rewrite, but there’s no better time than now — before 1.0 — while the user base is still manageable and we can afford to break things in the name of long-term simplicity and maintainability.

After nearly five months of work, today we’re releasing the Flet 1.0 Alpha — a technical preview of what’s coming.

When building mobile apps with Flet, you may need to interact directly with platform-specific APIs. Whether it’s accessing system information, managing Bluetooth devices, or working with user preferences, Pyjnius and Pyobjus by Kivy provide a seamless way to bridge Python with Java (for Android) and Objective-C (for iOS).

You can now integrate both Pyjnius and Pyobjus into your Flet apps! 🚀

Flet 0.27.0 is now released with exciting new features and improvements!

• iOS packaging & signing updates – ensures compliance with App Store Connect verification requirements.
• Reduced startup delay – faster initial launch for desktop applications.
• Faster incremental re-builds – enhances development efficiency with quicker iteration times.
• Enhanced Dropdown control – improved functionality and user experience.
• Bug fixes & stability improvements – various fixes to enhance overall performance and reliability.

The Flet 0.26.0 release is here, featuring a significant update to the extensibility approach!

In summary, a Flet extension is now a single Python package that bundles both Python and Flutter code. This package can be part of your Flet project or hosted in a public Git repository or PyPI.

Built-in Flet extensions, such as Audio, Video, and Map, have been moved to their own repositories. You’re welcome to fork these extensions to create your own or contribute to Flet! These extensions have been published to PyPI, making them easy to include in your Flet app. To use them, simply add the desired extensions to the dependencies section of your pyproject.toml file.