4 ms·

One cross platform Python framework I found interesting is flet https://flet.dev/ https://flet.dev/ It's powered by Flutter behind the scenes and familiar enou

One cross platform Python framework I found interesting is flet https://flet.dev/ https://flet.dev/ It's powered by Flutter behind the scenes and familiar enough so that you can translate most things from Flutter/Dart tutorials to Flet. I haven't used it and I'll most likely never will (Flutter developer trying to pivot to real native development), but it seems to have an active community, and in theory, it enables developers to write relatively nice looking apps with a very popular language.

heavyset_go 2y ago
Last time I looked at Flet, it gave the impression that you had to use the wrapped Flutter widgets, making it hard to use widgets and packages from pub.dev in a Flet application.
- skeledrew 2y ago
  If something isn't supported you can open an issue, or add that support yourself. The latter is relatively easy to do nowadays.
- serial_dev 2y ago
  That seems to be the case even today: https://flet.dev/roadmap https://flet.dev/roadmap. As I see, you can use pure python packages, but not Flutter packages or Python packages with some other languages in the mix.
BaculumMeumEst 2y ago
Why do people keep doing things like investing in a framework, written by one set of developers, built on another framework, written by another set of developers, and acting like that is not insane? Unless both stacks are written by huge software companies that have an extreme vested interest in keeping them running, there is a huge risk of abandonment. Maybe Google just decides maintaining flutter is a pain in the ass and React Native is just good enough. Maybe the flet devs don't turn enough profit. Maybe flutter changes too radically and makes it difficult for flet to catch up. Such situations have happened again and again and again, and they will continue to into the future. What are we gaining here that is worth such an enormous risk?
- Operyl 2y ago
  Why do people write frameworks on top of programming languages that other developers wrote? Feels like a similar kind of energy, but your scenario is easier: if it goes away they could find new maintainers or take it up themselves.
- cle 2y ago
  > What are we gaining here that is worth such an enormous risk? Well, Flet's landing page has a bunch of features and benefits. What is an "enormous risk" anyway? Depends on what you're doing. There are endless cases I can imagine where I just don't care at all about such a risk.
- serial_dev 2y ago
  While the risks you mentioned are indeed valid risks, it doesn't automatically mean that these risks (however small or huge they be) outweigh the benefits the Flet project offers. It's somewhat of a niche project, and certainly not for everyone, or for every project, but it's an active project with some real users.
BiteCode_dev 2y ago
What do you mean by "Flutter developer trying to pivot to real native development" ?
insane_dreamer 2y ago
Interesting. Looking for something like this to use instead of Flask, which is great on the server side but need something that’s easy to work with on the client side that provides a feature complete and nice looking set on controls for the client side.

heavyset_go 2y ago

Last time I looked at Flet, it gave the impression that you had to use the wrapped Flutter widgets, making it hard to use widgets and packages from pub.dev in a Flet application.

skeledrew 2y ago
If something isn't supported you can open an issue, or add that support yourself. The latter is relatively easy to do nowadays.
serial_dev 2y ago
That seems to be the case even today: https://flet.dev/roadmap https://flet.dev/roadmap. As I see, you can use pure python packages, but not Flutter packages or Python packages with some other languages in the mix.

BaculumMeumEst 2y ago

Why do people keep doing things like investing in a framework, written by one set of developers, built on another framework, written by another set of developers, and acting like that is not insane? Unless both stacks are written by huge software companies that have an extreme vested interest in keeping them running, there is a huge risk of abandonment. Maybe Google just decides maintaining flutter is a pain in the ass and React Native is just good enough. Maybe the flet devs don't turn enough profit. Maybe flutter changes too radically and makes it difficult for flet to catch up. Such situations have happened again and again and again, and they will continue to into the future. What are we gaining here that is worth such an enormous risk?

Operyl 2y ago
Why do people write frameworks on top of programming languages that other developers wrote? Feels like a similar kind of energy, but your scenario is easier: if it goes away they could find new maintainers or take it up themselves.
cle 2y ago
> What are we gaining here that is worth such an enormous risk? Well, Flet's landing page has a bunch of features and benefits. What is an "enormous risk" anyway? Depends on what you're doing. There are endless cases I can imagine where I just don't care at all about such a risk.
serial_dev 2y ago
While the risks you mentioned are indeed valid risks, it doesn't automatically mean that these risks (however small or huge they be) outweigh the benefits the Flet project offers. It's somewhat of a niche project, and certainly not for everyone, or for every project, but it's an active project with some real users.

BiteCode_dev 2y ago

What do you mean by "Flutter developer trying to pivot to real native development" ?

insane_dreamer 2y ago

Interesting. Looking for something like this to use instead of Flask, which is great on the server side but need something that’s easy to work with on the client side that provides a feature complete and nice looking set on controls for the client side.