badgolferman wrote:

> Samsung has rejected seamless updates. Does Apple use this method? I know
> it downloads updates in the background while I continue to use the phone
> but I don�t know if that�s the same thing.
>
> https://www.androidpolice.com/samsung-galaxy-s23-seamless-updates/

Hi badgolferman,

Andy Burns, who knows Android even better than I do, has Pixels where he
responded to a similar (but different) question I had asked about the
_size_ of these updates (layered Android versus the monolithic iOS).

He knows more about A/B updates than anyone on the iOS newsgroups will (as
it's clear none of the iKooks have used an Android phone) so I asked him to
let us know on the _true_ impact of these supposedly seamless A/B updates.

My free bottom-of-the-barrel Samsung Galaxy gets plenty of updates, almost
all of which are seamless, but while it "can" do A/B updates, it doesn't.

While _every_ iOS monolithic update causes turmoil on my iPads, almost none
of the Android layered updates do - simply because they're invisible.

As a simple example, if Google needs to update any of two dozen core
components of Android, they just update them - without even telling us.

We'd never know unless we keep track specifically of the subversions of
those more than two dozen core components of Android.

By way of stark contrast, Apple can't even update a single line of code in
all of iOS, which includes things like Safari, without impacting users.

The difference is _huge_ but most iOS owners won't realize how horrible the
primitive monolithic update mechanism is in terms of having huge seams.

Anyway, the thread with this information from Andy Burns, whom I told to
not sugarcoat the answer as I only care for the God's honest truth, is
*What is the SIZE difference between iOS & Android updates?*
<https://groups.google.com/g/comp.mobile.android/c/fpIACZI6RCc>
--
This is posted because I have two goals on this newsgroup, one of which is
to learn and disseminate useful information which is important to users.