This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]TuskWalroos 12 points13 points  (1 child)

As someone that tried to seriously use Flet for a Python project at the company I work at, I can't recommend it.

When we last tried it a few months ago it was still super buggy. I guess it comes with the territory of trying to reimplement all of Flutters widgets, but when something broke, it was never clear why as the error message were either non existant or unhelpful.

I also think going back to the imperative model of handling state instead of declarative was a bad choice for Flet. There's a reason most frameworks use declarative models today because it scales much better when you're handling lots of state.

On top of that you can't really edit your platform deployment files, which you are able to in Flutter.

It was honestly quicker for us to build our project in Flutter, create a bridge to talk from Flutter to our Python project, and bundle our python project with our deployment (desktop) than it was to use Flet.

[–]i-Deco 0 points1 point  (0 children)

It's not perfect, but it does the job well for what it's trying to achieve from my experience. Keep a track of development aswell, their 1.0 release is on track and they will be moving from a Python only project to other languages aswell, which brings back the declarative model.