My ‘premise’ is actually based on fact.
Go and find a decent developer who understands the architecture involved and the challenges and ask them to explain to you.
Even if MS wanted to, it can’t. But hey, I don’t disagree with their appetite to develop for an Apple environment, why should they? In the same way Adobe don’t develop fully fledged all singing and all dancing versions of their apps for iPadOS..
The current iPadOS version of Excel is not actually Excel, it’s a completely different programme built for a Darwin based platform and restricted ARM64 environment. Not to mention a restricted filesystem (sandboxed environment), prohibited automation, etc etc.
The foundations (building blocks) and fundamental way that Excel works and functions is not something that can be ported. It would have to be rebuilt from scratch and even then, many of the Excel functions would still not be possible, architecturally impossible in fact.
If you understand, then you’ll understand. If you don’t that’s fine but don’t call me out if you don’t.
I know several “decent developers”, and they disagree with you…
The fact of the matter is, Microsoft doesn’t deliver better Office apps because they don’t want to. I demonstrated several basic features they absolutely could implement if they actually cared about full support, or as close to full support as possible. But they clearly and obviously don’t. And when asked why they don’t deliver a fully functional Office suite for a platforms like iPadOS and Android, they are even fairly open about their strategy of keeping these apps a restricted and “light” experience primarily as a companion to a Windows PC… They don’t ever claim they can’t provide either the full suite, or much closer to it due to iPadOS.
Also, the “it’s iPadOS’s fault” claim doesn’t hold up, because the Android versions are also essentially the same, and just as kneecapped… If this were truly just due to a limitation in the OS, and not Microsoft’s very obvious and intentional strategy to prevent other tablets from having the “full Office experience” (which would pose a big threat to the Surface Pro if other tablets were closer), then we would expect to see Office on Android far closer to desktop level than the iPad version, because it isn’t as “sandboxed” or “restricted”, right? WRONG… Exact same artificial limitations… So no, it is not due to iPadOS limitations…
Also, the web versions are similarly hobbled, with nearly all the same exact limitations/restrictions. Hugh, what a coincidence… 🤔.
It is immediately obvious that Microsoft is artificially limiting and restricting these apps in order to try to secure Windows and Surface Pro lock-in…
And again, assuming your premise, there is absolutely zero reason they couldn’t push them FAR closer than they are currently. Even basics I’ve already talked about like inserting images from OneDrive or Files. Precisely positioning page elements. Custom document templates. These are just a few incredibly basic features that competing Word processors already possess on the iPad, so don’t give me that “this is iPadOS’s fault” nonsense... These are basics…
Also, this weak-sauce “it’s iPad’s fault” argument doesn’t do anything to address the very obvious and very anti-customer issue of charging people the EXACT SAME PRICE for these gimped versions vs the Windows versions… Even assuming that they were running into legitimate technical barriers (they aren’t, that’s a complete load of rubbish), if they actually cared about customers on other platforms, they would not be charging us the same price to access these apps. At least make it cheaper. Give us a discount if we’re not using your lousy Windows platform, and instead are forced to use your lousy, gimped apps… Or, give it to us for free, since you already do that on phones. Don’t charge us the exact same rates for these neutered apps…
The fact of the matter is, this is ENTIRELY Microsoft’s fault, because even if there were supposed “technical barriers” (there really aren’t, at least not for 99.99% of Office features), then they could always choose to, I don’t know, give us a discount… 🙄🤦🏼♂️.
And there is zero reason the web versions have to be as limited as they are either. Even if you were arguing that there’s “OS limitations” involved here, that doesn’t really apply to the web versions. The web versions could be Windows feature level if they wanted to, since they’re running on servers and such…