|
|
|
|
|
by dman
2596 days ago
|
|
I respectfully disagree. A contrary viewpoint which I happen to share is the following - As a software developer you build productivity multipliers for your users. Users spend non trivial amounts of time, money and energy building skills to master a tool you build. Users use these skills to earn a livelihood and sometimes due to a change in employer / life situation find themselves in a position where they do not have control over the OS that they need to be productive in. I think empathy with your user dictates that you try to maximize the combinations in which they can put their skills to productive use. Taking ideological positions on fit/finish/aesthetics is questionable if your user has to spend time relearning some other tool because you refused to port your software. The port might not be as pixel perfect but if it helps a user carry over their skills into a new job / earn more money then I will sleep well at night knowing I stood by users. |
|
There's a long-running subculture in MacOS (and once Nextstep and now iOS) software development that I'll call 'app craftsmanship'. At its best it produces high-quality, slick apps that usefully leverage the platform's strengths and build dedicated (and typically paying) user bases. So when someone puts out a new Mac or iOS and makes a fuss about how it's fully native and supports the Face Bar™, they're signaling to potential users 'Hey! I'm about to do some App Craftsmanship here, people' and hoping deciated users will flock to them, credit cards in hand. They're not selling to the people who are going to be irritated the app doesn't run on Ubuntu Maimed Mastodon. And that's not a moral failing, it's just market targeting.