Monday, April 6, 2026

Notes From Setting Up New Apple Devices

This weekend, I helped my non-techie father migrate to a new iPhone 17e and MacBook Air:

Previously:

12 Comments RSS · Twitter · Mastodon


If I were an Apple employee working in HR, I would ask candidates applying for a job in UX or something to share their thoughts on this fascinating list. I laughed at the Weather widget part.


I should add that he was totally happy to keep using the Intel MacBook Air except that the SSD was full (and not upgradeable).


What is this "new age verification question" you speak of?


@bob Maybe “age verification” isn’t the right term, since it didn’t actually ask for any documents to verify and I’m not in the UK, but I don’t know what else to call it. It was a new screen at setup that had two or three choices for the age, basically to see whether you’re a minor or not. Maybe it’s for the declared age range API?


Paul McGrane

Despite Michael claiming his dad isn't a techie, I think he almost is. Wouldn't bluetooth be re-enabled per restart or system update? He must have been constantly disabling it! Plus the dad is glad to have 2 available USB ports!


Dan Shockley

I recently upgraded from an iPhone 13 to an iPhone 17. It was a huge pain in the neck. So many apps required fresh login. Re-authorizing things took forever. I can’t even remember all the confusing hoops I had to jump through, some of which had to be tried several times to work, without doing anything different. Basically wasted almost a full day of wrangling.
A week later I still run into a random app either on my Watch or my iPhone that isn’t set up properly.


@Paul Yeah, I would have thought Bluetooth would get re-enabled, though he doesn’t remember doing it recently. Only using two USB devices: Time Machine and printer. I don’t remember why he didn’t want to use a hub.


The iDevice migration process is so error-prone and tedious, it's actually one the main factors in me not upgrading my phone frequently. Every time I go through it I'm terrified it's going to just fail in any of a billion possible inscrutable ways, and I'll be permanently stuck with no working phone or no access to any accounts (imagine not having any of your authenticator apps nor access to SMS - not just for a few hours as is sadly normal during the process, but indefinitely).

And that's for *me*, someone with (at this point *too many*) decades of experience using, developing for, and *developing* Apple products (I worked at Apple for a few years, circa the iPhone release). Every time I see a non-techie family member or friend go through the process, I wonder how on earth anyone ever manages to succeed at it.

There's so many things about iDevices (and Macs) these days which genuinely make me wonder if anyone at Apple ever uses these products. And of course what's *really* depressing about that line of thinking is that of *course* they use them, which means that they *know* how bad it is and they *choose* not to do anything about it.


I'll also note that every time i set up a new device, it creates an insane number of emails in my inbox.

Verification Codes
New Login Detected
New Machine added
Do you recognize this login?

etc etc


@Wade Needless to say, the Symantec authenticator app did not preserve its ID after migration so we had to go into various sites to update the credential.


> New Machine added

I have some older machines I don't use all that often, but when I do, they cause a popup on every other machine claiming a new device was added to my account.

The older machine is still signed in when this happens.


I'm in the process of setting up a new phone from scratch instead of restoring it from backup, as I usually do. The amount of work needed to make everything work the way I like/need it is insane.

> Basically wasted almost a full day of wrangling.

Sadly this is not an exaggeration. I'm still not finished after working on this for the third consecutive evening.

Leave a Comment