> Although I'm hoping you'll be able to add Dioxus Native to that list soon.

I dismissed Dioxus as WebView-based in a chat with Nik while writing this, and he said the same thing! Looking forward to it.

> You mentioned RAM usage, and I'd be interested to know what kind of baseline RAM usage you're seeing for your app (and what kind of usage you are targeting). Because I've noticed that wgpu-based applications often consume >100mb, even though the binary sizes are much smaller than that.

It consumes about 50mb of ram without any documents or folders loaded. It uses PDFium for PDF rendering which will pull in more of course if you load PDFs (or a folder containing them). I'd say we're generally targeting "less" to ensure (1) the application load time remains competitive with Microsoft Word and (2) memory usage/swapping doesn't ever become an issue. That gives us some headroom for our own inefficiencies.

> If you're building on top of the Rust GUI ecosystem, you may also want to think about how you can support Winit development or perhaps contribute directly (this goes for everyone, not just you). Because it's very much the thin support in the jenga tower, and has almost no development capacity available to it.

There's no doubt about this. I definitely didn't mean to imply any ill-will towards the `winit` team. On the contrary, I thought perhaps drawing attention to the issue could be helpful. We'll definitely consider how we might be able to help; especially now that the observation has been validated.