And there are also many third party apps that never made Mac versions.
So the amount of data we are talking about exposing is significantly higher.
And the issue is that the DMA is ambiguous about what competition and interoperability specifically means and so it would just take one company to complain about your solution for Apple to be fined 10% of global revenue.
This is again a misinformed take. Your Mac can already get all your iPhone's data from the cloud where it is synced without viable opt-out or compartmentalization.
Only if the data is available in iCloud and it is stored in files and it is not encrypted.
Otherwise data from apps like Instagram will be exposed exclusively via screen sharing.
We do not live in this universe. Consider getting a Chromebook instead if you want to be in that universe. (But then you have a tradeoff: Apple itself seems pretty good about not using your data inappropriately. Google, not so much.)
Health data is available in there, just to go after your example. iPhone backups are also available in there.
At no point am I being asked anything else beyond my Apple ID, password, and two-step approval on another device (such as the Mac) to set up a new iPhone and download all my data.
Thus the outcome is that the Mac indeed has everything it needs to get access to all your iCloud data. In fact, reverse-engineering how to get it directly is unnecessary work - instead, just reverse-engineer enough to capture the Apple ID password (or prompt to it - given there's still no way for the user to tell a real system dialog from one drawn by malware) and approve the 2FA prompt, get an actual, real iPhone and sign into the person's account and then extract all the data from there (via screenshots if necessary).
> You would be allowing third parties the ability to continuously record your iPhone's screen. Which includes websites you browse, apps you open, health information, text messages etc.
> And the Mac is so much open that you could do this, have a local model to transcribe it and ship it to a remote server without the user noticing.
MacOS is not secure in the way you would like to think it's secure. This is already risk. And Apple really could do this right: make screen mirroring use the DRM playback paths, and open up the API to trigger it to competitors (who would get precisely the same DRM-playback-pathed result of a screen mirror showing up in a window from which they cannot read). I don't really know why a competitor would want to compete here, but they could.