I was unaware that this was still in an early stage of development and am glad to hear of plans to move forward on a native app. > Hopefully that roadmap and e

I was unaware that this was still in an early stage of development and am glad to hear of plans to move forward on a native app. > Hopefully that roadmap and explanation of the architectural decisions clears up any worries about the short and long term state of our GUI. Yes. To expound on my original complaint about web apps in general, my main problems with them are: * responsiveness -- specifically latency when using the gui, as well as the long staggering pauses when I don't know if I am waiting for the server to respond or if there is an app hiccup or if the thing is frozen (the random long unresponsive breaks is what made me unable to use Roboflow, for instance) * file management -- having to do everything in the browser is frustrating because of the way the browser is separate from the OS and makes everything an 'app'. Having to import files to some server to work on them is annoying when they are right here in my system. I also like to manage the files in a specific way and have access to program and preference files and know where everything is stored (if it crashes I can find the temp files, for instance). Sandboxing the app from the OS is the opposite of how I want a desktop application to behave * portability / offline use -- I don't want to login to use an application. I don't want my files on a cloud and I want to be able to use the application forever, even if the original company is defunct I hope this sheds light on where I am coming from. It seems you thought of at least a few of these issues and are mitigating them.