3 ms·

I love it when someone's example makes it clear that they have no idea what they're talking about. OS Widgets don't implement undo. Undo is inherently tied to

I love it when someone's example makes it clear that they have no idea what they're talking about. OS Widgets don't implement undo. Undo is inherently tied to app state and the developer is responsible for managing it. At most, the OS will give you an undo button/icon and you can use it to fit in visually. Frankly, building a separate version of my app per platform to conform to your nativist standards is a huge waste of time. My UI will work across all target platforms. If you can't figure out interfaces that aren't straight out of an Apple/Microsoft design document, that's on you.

wat10000 2y ago
Bullshit. Undo in a macOS text entry box is part of the widget’s implementation and you get it for free. It doesn’t need to be tied to the app’s state, since it’s just working on the text you put into the box. Have you actually built any native macOS apps? I have.
- johnecheck 2y ago
  Ah, my apologies. I thought you were talking about something like an undo button, rather than cmd+z within a particular text box. Sure, point taken. Native widgets might work differently than cross-platform ones. That said, there's no reason a cross-platform widget couldn't work identically to the native one. Indeed, a platform's native widgets an effective way to give users a consistent style and functionality across apps from many developers. Yet, as a one-man dev team, the cost of building a separate version for each platform is prohibitive. The choice is to disregard most platforms or disregard a small corner of the expectations each user has for apps on a given platform. The choice was pretty obvious to me.
  - wat10000 2y ago
    Sure, I won’t dispute that it saves time to build apps this way, and that may be the right choice. But the results still suck and I still don’t like them. Ironically, out of the apps I use regularly, the ugly, misbehaving apps built with cross-platform frameworks are from big companies that could easily afford to do it right, like Slack. The apps I use that come from small indie developers are all native. I suppose this is down to competition. I tend to have a choice for those apps, so I can choose ones that work the way I like. For Slack, my choices are to use the app, use it on the web (same as using the app, more or less), or find a new job at a company that uses something else.

wat10000 2y ago

Bullshit. Undo in a macOS text entry box is part of the widget’s implementation and you get it for free. It doesn’t need to be tied to the app’s state, since it’s just working on the text you put into the box. Have you actually built any native macOS apps? I have.

johnecheck 2y ago
Ah, my apologies. I thought you were talking about something like an undo button, rather than cmd+z within a particular text box. Sure, point taken. Native widgets might work differently than cross-platform ones. That said, there's no reason a cross-platform widget couldn't work identically to the native one. Indeed, a platform's native widgets an effective way to give users a consistent style and functionality across apps from many developers. Yet, as a one-man dev team, the cost of building a separate version for each platform is prohibitive. The choice is to disregard most platforms or disregard a small corner of the expectations each user has for apps on a given platform. The choice was pretty obvious to me.
- wat10000 2y ago
  Sure, I won’t dispute that it saves time to build apps this way, and that may be the right choice. But the results still suck and I still don’t like them. Ironically, out of the apps I use regularly, the ugly, misbehaving apps built with cross-platform frameworks are from big companies that could easily afford to do it right, like Slack. The apps I use that come from small indie developers are all native. I suppose this is down to competition. I tend to have a choice for those apps, so I can choose ones that work the way I like. For Slack, my choices are to use the app, use it on the web (same as using the app, more or less), or find a new job at a company that uses something else.