Download Flet desktop client binaries from GitHub Releases on demand

[FeodorFitsner]

We are getting stuck with failed builds more often. The limit of a single "project" on PyPI is 10 GB and I remember I asked PyPI once for increase and they did it for flet project, but told me "please do not do that". Now it's flet-desktop.

We need to get back to downloading binaries from GitHub releases. Now, when we have strict built-in version stamp inside version.py it should be a breeze, for both release and pre-release builds.

[ndonkoHenri]

• Project Limit Request: Flet - 20 GB pypi/support#3865
• https://docs.pypi.org/project-management/storage-limits/

Let's attempt to request more storage for Flet-desktop?

[HappyCoder256]

The problem is u guys u're releasing more versions with more bugs. Atleast take a beautiful moment and suppress all Current issues and bugs and release one bug free version not introducing more versions, more features and appending more bugs to the Current ones. Please take that into consideration 🙏

[FeodorFitsner]

Thanks for sharing your concerns. I hear you!
We are releasing often, true, but most of the work today is done around stabilization and bug fixing. We done a great job in Flet 1.0 by adding auto-generated docs, integration tests and pulling everything into a mono-repo - all to make sure the project is scalable and ready to grow.

We check/triage issues every day and most pressing of them are fixed (will be fixed). Sadly, many issues is just a noise, more like "how do I" questions or platform/configuration specific issues - this adds some churn.

This specific issue with binaries stored in wheels - what worked before in 0.28.x does not work now in 1.0. With releases size (platform matrix) and volume it's ridiculous to put artifacts into wheels. I cannot request for PyPI storage extension every week!

Flet is definitely getting better as we "dogfood" it on internal projects and many requirements come from that.

Hey, having a lot of issues does not necessary mean the project is bad! 😏 Look, Flutter scores 5K+ issues and yet it's a wonderful product! ☺️ And we are not doing things like that!

Cheers!

[FeodorFitsner]

...and it's impossible to fix all bugs with the current "agile" model of software development. In 90-s we had "waterfall" model :) with clear end-product features and the product was thoroughly tested before reaching RTM (release to manufacturing) state and burned to CDs. The cost of releasing and distributing on CDs was high hence the flow. Dealing with GitHub issues sometimes feels like tilting at windmills. :)

[HappyCoder256]

I get where you’re coming from, and I appreciate the effort going into improving Flet it’s clear a lot of work has been done around testing, docs, and structure.

That said, I think many of us would really benefit from a strong focus on a fully stable, reliable release. Right now, it sometimes feels like new features are coming in faster than existing issues are being fully resolved, and that can make it harder to build production-ready apps with confidence.

Having a long-term stable version where the priority is stability, consistency, and minimal regression would go a long way. Even if development continues quickly in parallel, a dependable version would help developers who need something solid to rely on. And flet 0.82.2 is not that reliable production ready compound to lean on.

In short, it’s not about slowing progress, but about balancing innovation with stability so the framework can be trusted in real-world use.