Not important enough: 1Password abandons its native Mac app
1–10 of 91 posts
Re: Not important enough: 1Password abandons its native Mac app
#2Funny. Because by that definition Mac OS's preference app is an Electron app. Go to Keyboard -> Modifier keys. Opens a dialog window that cannot be moved.
Re: Not important enough: 1Password abandons its native Mac app
#3> If you can’t move the preferences window because it’s fake, you might be running an Electron app Funny. Because by that definition Mac OS's preference app is an Electron app. Go to Keyboard -> Modifier keys. Opens a dialog window that cannot be moved.
Re: Not important enough: 1Password abandons its native Mac app
#4Re: Not important enough: 1Password abandons its native Mac app
#5The developer productivity and consistency gains of working on one codebase rather than 2 or 3 cannot be argued with, and I’m confident more and more software will be moving in this direction regardless of the opinion of (what is probably) a fairly small number of hardcore users.
However, I do agree that Electron can give a sub-optimal experience compared to a native app in many cases. React Native could potentially provide a good compromise - write your app in JS but it renders using native UI widgets, resource usage is lower because it’s just using a JS engine rather than a full browser.
It would probably be more work than Electon because each platform will have differences in how it renders, but much less work than building separate native apps.
Last time I checked on RN on MacOS (well over a year ago) it was quite immature, but with Microsoft pushing it on both Windows and Mac, it could become a realistic option soon (if it’s not already).
Not sure if there’s anything on Linux? You could maybe fall back to Electron, with the the UI rendered via react-native-web to turn it back to HTML.
Re: Not important enough: 1Password abandons its native Mac app
#6Re: Not important enough: 1Password abandons its native Mac app
#7> If you can’t move the preferences window because it’s fake, you might be running an Electron app Funny. Because by that definition Mac OS's preference app is an Electron app. Go to Keyboard -> Modifier keys. Opens a dialog window that cannot be moved.
(And of course, modal dialog boxes of all kinds are used far more often than they should be. They're not always the wrong choice, but more often than not they're a symptom of poorly thought-out UI design.)
Re: Not important enough: 1Password abandons its native Mac app
#8I’ll be interested to see how React Native on desktop progresses. The developer productivity and consistency gains of working on one codebase rather than 2 or 3 cannot be argued with, and I’m confident more and more software will be moving in this direction regardless of the opinion of (what is probably) a fairly small number of hardcore users. However, I do agree that Electron can give a sub-optimal experience compa…
That said, most applications are really windows onto server-based algorithms, so the need for a “pure native” UX is a lot less, these days, than it used to be.
The one big skunk at the hybrid picnic is that we are “dancing with a gorilla.” That means that we don’t get to change the step, or stop, until the gorilla says so.
If we are dependent on any external framework (not just ones like Electron or RN), then we are at their mercy, wrt to adapting to platform and environmental changes.
I know folks that have written code that won’t run on current versions of the OS, because an SDK they use, has not been updated.
Re: Not important enough: 1Password abandons its native Mac app
#9I’ll be interested to see how React Native on desktop progresses. The developer productivity and consistency gains of working on one codebase rather than 2 or 3 cannot be argued with, and I’m confident more and more software will be moving in this direction regardless of the opinion of (what is probably) a fairly small number of hardcore users. However, I do agree that Electron can give a sub-optimal experience compa…
Native will always give the richest user experience, and deliver the most up-to-date tech. That said, most applications are really windows onto server-based algorithms, so the need for a “pure native” UX is a lot less, these days, than it used to be. The one big skunk at the hybrid picnic is that we are “dancing with a gorilla.” That means that we don’t get to change the step, or stop, until the gorilla says so. If w…
Oh yeah, not arguing with that at all. But I think the commercial reality is a lot of companies will think the trade off of using a cross platform framework like Electron is worthwhile, the UX is “good enough” for most users and the development process is much more efficient.
Of course, users might vote with their feet and go to other apps which are native, but I suspect this trend is here to stay and so it’s good to consider what the “least bad” hybrid option is.