That's the key problem, the conflict of interest as separate native apps are much better for users but a single cross-platform app (often web/Electron based) is much better for the developer due to cost, compatibility and maintenance issues.
So the endgame is probably resigning to having lousy non-native software until/unless there once more comes a time with a single dominant/monopoly platform where people just make a single native app for everyone.
That's the problem from your point of view. For me, a lousy cross-platform app is a direct upgrade from "no app at all", so I don't anticipate that very many software engineers are going to spend their time designing a bespoke version of their app for >20% of their target audience, even if the experience on that one platform is better. If we lived in a perfect world, every app would have a Qt, GTK3, GTK4, SwiftUI, Winforms and Fluent Xaml version that makes everyone happy. Somewhere you've got to draw the line though.
Linux has native GUI toolkits. If those lazy developers didn't just sit around all day developing Electron clients that worked, we could have a SwiftUI, Catalyst, WinForms, GTK and Qt version that everyone can hate! What a waste of developer resources, amirite?
I've had a totally different experience as a Linux 1password user.
I went from a shitty cli and a laggy browser extension to an excellent native feeling 1password app that is fully integrated into my desktop environment. I don't notice any lag, in fact it feels snappier than the native windows version on my handful of years older laptop.
Unlike many other apps I use (Spotify, vscode, intellij, Firefox) I don't notice any difference in system load when it's running too.
So the endgame is probably resigning to having lousy non-native software until/unless there once more comes a time with a single dominant/monopoly platform where people just make a single native app for everyone.