Honestly, it seems kind of moot if it already works in the browser. It’s a negligible amount of work to make an app use a browser engine to run offline to run their stack, but some heavy lifting to do a direct port to any specific OS without an adjoining framework to help in the cosmetics of everything.
That being said, they could also use a unified framework to do one release for every OS, which again is pretty much the same as making offline work for anywhere.
My fear is they do something stupid like build in GTK, and then QT users have UI problems, or vice versa. Seems easier to just go with a unified (non-electron) kit that runs everywhere the same way.
Honestly, it seems kind of moot if it already works in the browser. It’s a negligible amount of work to make an app use a browser engine to run offline to run their stack, but some heavy lifting to do a direct port to any specific OS without an adjoining framework to help in the cosmetics of everything.
That being said, they could also use a unified framework to do one release for every OS, which again is pretty much the same as making offline work for anywhere.
My fear is they do something stupid like build in GTK, and then QT users have UI problems, or vice versa. Seems easier to just go with a unified (non-electron) kit that runs everywhere the same way.