Thank you! I didn’t take it as criticism at all - I was only joking about the rewrite.
I wonder if this is a Mac/Windows difference. I’ve never seen a cross-platform app that looks entirely at home on the Mac. There are some cross-platform apps that look and work great on the Mac, don’t get me wrong, but they’re still obviously built with non-native tools. They have the traffic light buttons in the toolbar and a lot of the general look, but their toolbars use different colours or aren’t quite the same height as other toolbars and things like that. All of which is absolutely fine for apps that want their own custom UI standardised across platforms with only minimal differences in where the “close/minimise” buttons are. But I like to work with a more platform-standard UI, which on the Mac means a UI that looks like Apple apps - and the Apple tools.
That said, you could prove me wrong and show me an app that I had assumed was native but turns out not to be, and it wouldn’t make an awful lot of difference. 
The truth is that for as long as I’m leading the design and development, I’m going to be using a Mac because I love the tools and programming languages (Objective-C and Swift) and work well with them. To move to a fully cross-platform toolkit for all operating systems, I would either have to retrain in tools and languages I’m not entirely enthusiastic about, or step back and oversee other developers take over. Right now, I’d honestly hate that. I love thinking about were to go next, coding up ideas and prototyping, throwing out ideas and refining them - and implementing them in the Mac toolkits. (One of my absolute favourite comments from last year’s survey was, “I don’t think Keith is fit to be the lead developer because of his personality.” 
Maybe they’re right, as it is to some extent my love of working with Mac tools that prevents us from moving to a fully cross-platform solution. It’s a conundrum, though, because if I gave that up I’d have less enthusiasm, and someone else would have to take over driving Scrivener forward. And I’d just end up writing my own new version anyway and launching a competitor product!)
With regard to other Windows tools (other than Qt), as I understand it - and you will know more than me on this, as I haven’t spoken to our Windows developers to check this so am going from hazy memory - one of the problems with Windows development has been the number of tools and languages available, with Microsoft introducing different ones and partly abandoning older ones. When I first had the idea for Scrivener, a few years before moving for Mac, I looked at developing it on Windows using C++ (and M… something? I can’t remember, but you’ll probably know). I didn’t get along with C++, so abandoned the idea until I moved to a Mac, but at the time MS seemed to be transitioning to C# and .Net, and since that there have been, what, two or three others? I know of other developers who have banged their heads trying to work out the best Windows dev approach. That’s why it seemed best to us to use a cross-platform tool like Qt for Windows (and hopefully one day Android) development, but to stick to the Mac native tools for macOS and iOS.
As for Android, I hope that won’t stay a missed opportunity forever. Our research certainly suggests that Android is far less profitable than other platforms - despite more people in the world having Android, iOS developers make more. But we’ve never been driven entirely by profit (which is actually an advantage of being profitable). We want to get Scrivener onto Android too, but we have a lot more ahead of us before that (things that will have a direct influence on the Android version).
I feel sorry for the grief the 1Password guys are getting. I understand their reasons and things must be very frustrating for them right now. I understand the concerns of users, though - I tried out out an app the other day that markets itself as a competitor to Scrivener and which is built on Electron, and its Chrome renderer background process was eating up anywhere between 10% and 40% of my M1 MacBook’s CPU after it had been left open in the background for a couple of hours. Ouch.
Anyway, I wrote far more than I intended there - back to the code!
All the best,
Keith