Former manager here - you'd be very surprised at how much effort it takes to act as a human shield for your developers to keep the interruptions to a minimum and keep their roadmap stable. It's work, and it can be delicate. Try running interference with a company president who wants to bother your developers when they're trying to get something out the door, or trying to make sure stupid ideas die before they become your team's problem.
In a perfect world you would be right, but spend some time with a bunch of clueless executives who don't know how clueless they are (or are trying to pretend they do have a clue) and you'll realize there's no amount of context that will help them realize why there's bad news.
Not necessarily. macOS and iOS have multiple accommodations for users with accessibility needs, from dynamic type to UI element voiceover plus pretty decent speech-to-text recognition and haptic feedback. Developers that want to take the time can build apps that can be effectively used by users with visual and/or auditory deficits.
This line of argument sounds like a petition-gatherer trying to get signatures for a niche local issue and getting frustrated that they can't get enough people to see things their way.
"I'm spread too thin" isn't an actual lie as much as it's a reframing. Working with difficult people can take a lot of mental energy, which ought to be considered part of the work effort. It's the polite way of saying "I don't have the bandwidth to do the work and manage my way around your issues, so best of luck finding someone who does have that bandwidth" the same way that "Thank you for your input" is a polite way (in the business world) of saying "That was the dumbest thing I have heard all day".
"Technologies like objective C, C sharp, Azure or swift are designed so you can not escape the company platform. So easy to get in, so hard to move your code to other platforms once you have been programming for years on them."
FYI, Swift is available on Linux and Windows along with a significant chunk of its core libraries (e.g. https://github.com/apple/swift-corelibs-foundation) and app frameworks such as Vapor (used for writing web apps and APIs).
You do not have a "duty to your job". Employers love it when they can get their workers to think that way because it raises the threshold amount they can overwork and over-stress you before you've had enough and quit. You have to protect your personal time and your mental and emotional health. (I have had to learn this lesson a couple of times in 40+ years as a software dev.)
It helps a lot to think your management knows what it's doing. If you're stressing out on the latest likely "swing and a miss" feature that you think they picked using a dart board and ransom-note cutouts from magazines, you can end up burnt out for a good long time.
I think you're right, and I think it will motivate those of us who want to work remotely to quit and find companies that have that as their culture and let the "back to the office" folks become more homogenized.
Already you sound adversarial, like this is a battle of work cultures and you want your side to win. You say things like "return to work", as if the people who are working from home aren't already working. Did you mean your comment to come across this way?
FWIW, the styling system mainly talks to the parameterized native components that the build system pulls down from GitHub. You can do the same kind of thing in SwiftUI using View Modifiers.
You make it sound like users are switching among Windows, Linux, macOS, Android and iOS all the time so the app UI has to have the lowest common denominator. By and large they're not and as such the native UI is the consistent UI: the apps launch the same way, you know how to get to settings or the trash can and the gestures all do pretty much the same thing to get the same result.