I agree than the basic functionality should require so little work that multiple threads should be useless. Some features like bots or game analysis could benef

I agree than the basic functionality should require so little work that multiple threads should be useless. Some features like bots or game analysis could benefit from multiple threads, and should at the very least run outside the main UI thread. However these are only nice-to-have, and I'd be happy with a web-client that either doesn't support these at all, or only uses a single worker thread. And I see no reason to support this on desktop, while redirecting to an app on mobile. Moving those features a webworker so the UI stays responsive should be easy, however I'm not sure how synchronizing multiple webworkers to take advantage of multiple cores compares to synchronizing multiple threads in a native app.