1Password developed a SwiftUI version in parallel to Electron and chose Electron

There&#x27;s a very vocal subset of (mostly Apple) users that demand native apps for everything. Meanwhile I suspect that for most people, this matters very little. Yes, if performance is too bad, it might be an issue, but VSCode, for example, is extremely popular.<p>There are certainly issues with Electron bundling an entire browser runtime, and JavaScript is not really a language I like doing development in. On the other hand, I find it absurd how many developers seem to think that it&#x27;s totally normal that you have to have 3 or 4 different code bases if you want to write an application that runs on every major platform (including Windows).<p>I&#x27;m also amazed that even small startups immediately go down the &quot;multiple apps&quot; road instead of iterating first on a cross-platform solution (and then maybe later switching if there really are prohibitive issues). That makes me think that maybe part of the reason is that app developers don&#x27;t want to see themselves become obsolete.

Not surprised in the least, SwiftUI is unfortunately nowhere near production ready on macOS, and arguably iOS depending on the use case.<p>Electron is essentially the only <i>reasonable</i> way to develop non trivial macOS applications at the moment.<p>It’s also v debatable whether the UX is much worse with electron as well, are text only List components still failing to scroll at 60fps? Can I rotate the utterly bog standard example Landmarks app’s detail scene without breaking the NavigationView?<p>And at least in ~2017-2018, the vast, vast majority of competent AppKit developers appeared to either be in China, or Cupertino, unlike UIKit.