From Newsgroup: comp.sys.mac.advocacy

Everybody knows about ApplerCOs infamous rCLWalled GardenrCY. Its products
fit together into an ecosystem which is comfortable ... as long as you
donrCOt try to leave it.

Now it turns out there are walls *within* that garden, as well. Here <https://www.theverge.com/tech/875919/halide-mark-iii-process-zero-hands-on>
is an account of a user trying to take photos on one Apple device (an
Iphone) and do professional-quality processing of same on another
Apple device (a MacBook):

Something happens every time I try to use an iPhone camera like a
real camera.

HererCOs how it goes: I shoot RAW in addition to the default HEIC
output, and since I have the RAW file I might as well edit it to
my taste. And if IrCOm going to do that, I want to use Lightroom on
my MacBook. You know, real software. Then I remember: iPhone
photos hate real software. Moving image files between devices is
mysterious. If I Airdrop them to my MacBook will the HDR gain map
tag along? Why do my photos always come out of Lightroom looking
different than my edit? Where did that gain map go? I lack the
patience to find out, so I just live with what my phone camera
produces on its own and leave the heavy lifting to my rCLrealrCY
camera.

This has its pros and cons. On the plus side, itrCOs way easier to
deal with iPhone photos if they never leave the native camera app.
But it also means leaving processing up to the iPhone, which tends
to run amok with sharpening and raising shadows.

And it goes on to describe a third-party product which doesnrCOt
actually pierce that wall, but tries to bring over some more
functionality from the rCLreal computerrCY side over to the Iphone side.

More of a workaround than a solution, in other words.
--- Synchronet 3.21b-Linux NewsLink 1.2