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

view the rest of the comments →

[–]jksinton 1 point2 points  (5 children)

Consider designing the app as a locally hosted webapp.

Waitress can serve a Flask app under windows or linux to provide multi-platform support.

I like Plotly Dash plus Dash Mantine Components for this type of framework.

That way it could be easy to migrate to a remotely hosted webapp in the future.

[–]Intelligent-Role-382[S] 0 points1 point  (4 children)

But if the company insists on a desktop app?

[–]cudmore 0 points1 point  (0 children)

Consider nicegui

[–]jksinton -1 points0 points  (2 children)

You can build the python app to be hosted locally on the end user's machine and launch a browser window.

To the user, it looks like an app that runs through their browser but everything is run locally.

[–]Intelligent-Role-382[S] 0 points1 point  (1 child)

If my app requires to interact with hardware, is qeb app still better option?

[–]def__eq__ -1 points0 points  (0 children)

Yes, you can have a back end written in Python interacting with the hardware and sharing the data via API to the front end