| ▲ | bob1029 3 hours ago | |||||||
WebView2 can be a fantastic experience when the application is designed around it with intent. It can't be a technological afterthought. Taking an application that was designed for web and throwing it in a desktop shell is how you wind up with bad experiences. A hybrid of WebView2 and native elements seems to be the best approach. You can completely hide the browser startup delay with these techniques. The Discord engineers decided to just throw a splash screen in front and call it a day. You could do that too. It seems to fly. | ||||||||
| ▲ | gigel82 2 hours ago | parent [-] | |||||||
Until you look at memory consumption in Task Manager or Process Explorer. WebView2 spawns ~400Mb worth of various browser processes. Your main app process by itself might look nice and slim, but all that (somewhat hidden) cost is atrocious. | ||||||||
| ||||||||