Managing iOS web restrictions – the web problem and the Chrome problem

[Special thanks to one of my Explorers for teaching me about this.]

After quite a bit of experimentation I’m sort of satisfied with a fairly simple approach to managing iOS Screen Time for everything except the web.

I start by defining all the apps that always available: email, iMessage, Calendar, Find Friends, Music and so on. It’s a list of useful but kind of boring apps that Explorers can have available anytime.

Next I set an overall daily limit for use of all apps. Lastly I set Downtime for work on day breaks. It’s not a perfect solution [1] but it covers the bases for all but the web.

The web is another story. Apple isn’t much help here and I’m not sure anything works that well. I am coming around to the idea of blocking all web access for younger or more vulnerable Explorers. To do this you have to do two things:

  1. Toggle Safari off in Content & Privacy Restrictions:Allowed Apps
  2. Set Web Content to Allowed Websites Only and delete the items on the Allowed Site list.

The second measure blocks Chrome use and I believe it will block many embedded browsers as well. 

Blocking all web access has less impact now than it would have had five years ago. A lot of functionality has moved from the web to apps.

If you want to allow web access things get complicated. Apple’s iOS 12 Web Content restrictions work for both Safari and Chrome [2], but the “Limit Adult Websites” doesn’t work very well [3], and there’s no longer a way for an Explorer to request adding a blocked site to the “Allowed Websites” list. (In prior versions of iOS an Explorer could remotely request additions. I miss that feature.)

The best I’ve been able to do with Apple’s iOS 12.2 tech is to:

  1. Set Web Content to Allowed Websites Only.
  2. If Chrome or other browser is installed set App Limit on Chrome to 1 min (we want a 0 min limit, but that’s not available). Alternatively, if you have limitations on app installation, remove Chrome and don’t authorize reinstallation.
  3. Set App Limit on problem websites to 1 min.

How do you set App Limits on individual apps or websites?

Well, thanks to Apple’s famous focus on user experience and intuitive user interfaces that’s really easy …

Hah, hah. Just kidding. It’s insanely obscure.

From a Guide’s iPhone go to the Explorer’s Screen Time settings. Enable “include website data”.  Now tap on the Report of time used. Yeah, tap on the Report of hours and minutes.

You’ll now see the Secret Power User Screen Time Controls (SPUSCTC). Look at Most Used. You can toggle between Apps & Websites and Categories. From Apps & Websites you can see individual sites visited in Safari, not in Chrome or other browsers, just Safari.  You can tap on an App like Chrome.app, or an individual web site, and set a limit. You can’t set a limit of 0 minutes (that would be nice), but you can choose 1 minute.

If you do this regularly for a few weeks you may be able to manage high risk web activities for a vulnerable Explore. Or you may find you just need to turn the web off.

You have to block Chrome by preventing installation or limiting use to “1 minute” because these site specific restrictions only work for Safari [4]. An Explorer who installs Chrome can bypass them all. 

PS. Dear Apple, I’d be willing to redesign your Screen Time app for very modest fee. I swear you don’t need to add a lot of new features or do anything hard.

– fn –

[1] We’d be better off if Apple added an Apple Limit Category of “All but always allowed”. That would significantly improve Screen Time use. Define always allowed, then set a time cap for everything else. I’d rather listening to music didn’t count against the time cap.

[2] You may need to toggle airplane mode on a Guide’s iPhone to see the effect of changes. Otherwise they take a while to show up.

[3] Pornhub and other well known sites are blocked, but it’s not hard to find a universe of unblocked adult sites.

NYT on Apple’s Screen Time failures and the assault on third party alternatives

The New York Times has a pretty good article on the existential crisis facing vendors who have tried to provide parental control (parenting support) services for iOS devices:

Apple Cracks Down on Apps That Fight iPhone Addiction – The New York Times, Jack Nicas, April 27, 2019
 
… Over the past year, Apple has removed or restricted at least 11 of the 17 most downloaded screen-time and parental-control apps, according to an analysis by The New York Times and Sensor Tower, an app-data firm. Apple has also clamped down on a number of lesser-known apps.

In some cases, Apple forced companies to remove features that allowed parents to control their children’s devices or that blocked children’s access to certain apps and adult content. In other cases, it simply pulled the apps from its App Store…. 

…. On Thursday, two of the most popular parental-control apps, Kidslox and Qustodio, filed a complaint with the European Union’s competition office. Kidslox said business had plummeted since Apple forced changes to its app that made it less useful than Apple’s tool.

Apple also faces an antitrust complaint in Russia from Kaspersky Lab …  which said Apple had forced it to remove key features from its parental-control app. The company is exploring a similar complaint in Europe, a Kaspersky spokeswoman said.

… In early 2018, two prominent Wall Street investors urged Apple to address concerns that people were becoming addicted to their smartphones. In June, the company announced plans for tools to help iPhone owners track and limit their and their children’s phone use. It began offering the tools in September, tucked into the phone’s settings menu.

Shortly after announcing its new tools, Apple began purging apps that offered similar services.

Apple told the companies that their apps violated App Store rules, like enabling one iPhone to control another, although it had allowed such practices for years and had approved hundreds of versions of their apps.

Apple allows corporations to use such software to control employees’ phones. But last year, the company stopped apps from using the software to enable parents to control their children’s devices. The Apple spokeswoman said Apple had blocked the practice because app makers could gain access to too much information on the children’s devices. [jf: I think this means ability to access protected data that can be misused by vendors, such as Contacts.]

Unlike apps such as OurPact, Apple’s tools don’t allow parents to schedule different times throughout a day when an app is blocked — for school or family dinner. And Apple’s tool blocks adult content only on its Safari web browser and some apps, not on other browsers or many popular apps, like Twitter, YouTube and Instagram…

Apple’s tool has another shortcoming: It requires the whole family to own iPhones. Many apps removed by Apple allowed parents with iPhones to control their children’s Android devices.

Apple has also limited the options for adults who want to fight their own phone addiction. In August, it abruptly pulled down the Freedom app, which allowed users to temporarily disable certain apps and websites. Mr. Stutzman, Freedom’s chief executive, said that to return to iPhones, he was forced to stop blocking apps and to block sites only on Apple’s Safari browser.

Apple’s tool now appears to be one of the few ways to disable apps, if not the only one. Yet when a user hits an app’s time limit on Apple’s tool, it provides a single option: “Ignore Limit.” [jf: This is not quite correct, but I understand why they got his wrong.]

The app makers said they were most frustrated by the process of meeting Apple’s sudden demands. In many cases, Apple alerted them that their apps would be removed — and their businesses crippled — via a short note, according to correspondence viewed by The Times.

When app makers asked for more information, responses were often perfunctory and slow in coming…

I give the NY Times a lot of credit for tackling this topic. Mr Nicas probably needed a stiff drink after finishing this. It’s a complex problem.

On the one hand, Apple is right. I spent quite a bit of time testing Qustodio and it’s competitors prior to the release of enhanced Screen Time. None of them were acceptable. They all had business model issues or were easy to bypass, or didn’t quite work, or had weird side effects. I can believe they all broke App Store rules and that good devs would have known that.

On the other hand … Apple tolerated these apps. Then Apple both abruptly enforced rules and added new ones (allegedly blocking use of corporate MDM). Apple also shipped a half-built solution that has big bugs (if you enroll a device in remote Screen Time you can never truly remove it), almost non-existent documentation (especially for remote Screen Time), works only within the iOS ecosystem (no web interface), is both very complex and also insufficient, requires complex side-effect rich family sharing that ends abruptly at age 18, and is understood by almost nobody. Did I mention the #$! bugs?

Oh, yeah, and Apple’s new Screen Time is really lousy at managing web sites and the Safari app. It’s a significant regression from iOS 11 Restrictions. (My guess is that Apple figures the web is dead, so not worth worrying about.)

So there are sins on both sides, but as the best outside judge anyone is going to get I rule against Apple. They made a good initial effort on Screen Time but then they stopped work. They aren’t fixing their bugs. They haven’t provided a toolkit outside vendors can use to provide features Apple doesn’t provide. They have been as brutal to these vendors as they’ve been to all but the big and powerful. The one thing Apple has succeeded at is ending the external pressure they were getting.

I’d love to see Congress put some pressure on Apple. They need to finish the work they started, then they need to refine it and provide an API vendors can use to support unique needs, such as extended support for special needs adult. I’m available to testify!

Enabling remote Screen Time for an Adult Explorer

In a previous post I covered setting up local Screen Time in iOS 12. Remote Screen Time, where a Guide can manage an Explorer’s screen time from the Guide’s iPhone works similarly, but it requires setting up Family Sharing and possibly changing an Explorer’s birthdate. Here’s the draft version of that setup:

———

It’s great to be able to manage an Explorer’s Screen Time settings from a Guide’s iPhone. There’s some setup required however — with an extra step for an adult Explorer.

There are two things that have to happen to enable remote Screen Time management of an Explorer’s iPhone from a Guide’s iPhone. First, the Explorer has to be part of a Family Sharing group for which the Guide is an Organizer. Second, if you want to be able to Block rather than just Remind, Apple must think the Explorer is under 18 years old.

Apple’s describes setting up “Family Sharing” in the User Guide and a support article[1]. I describe it further in Buying apps and media for an Explorer’s iPhone. Briefly, start by searching iPhone Settings for “Family”, tap on Family Sharing, and add people by their Apple ID email. You can add up to five people (Apple IDs).

Then, for the entire Family, you choose which “Shared Features” to enable. One of them is “Screen Time”. For each Family Member tap on Screen Time, then enable it. Your family member will receive an invitation to join which they can then accept. Typically a Guide would do this for their Explorer with the Explorer’s iPhone at hand.

If a Family Member is not set up as a Parent/Guardian they can have Screen Time settings. If Apple thinks a family member is more than 18 years old they will be able to override any Screen Time limits. If Apple thinks a Family Member is under 18 then limits can be created that only an Organizer or Parent/Guardian can override. Apple calls these “Blocks”

For some adult Explorers a true Block may be the best choice. To enable this you need to change the Explorer’s birthday in their Apple ID setup. This is easy to do. From the Explorer’s iPhone tap on their name at the top of Settings (Apple ID). Tap “Name, Phone Numbers, Email”. Scroll down to Birthday, tap on the Birthdate, then change it. For my Explorers I have set the birthdate so that they are “14” at the time of the change. I have not found any side-effects with changing birth dates but I suggest writing down what date you chose. That might be important if an Explorer ever needs to establish their identity to Apple.

Although this setup is not hard it’s not ideal. There’s more Apple could do to support Adult Explorers. They could separate Screen Time from Family Sharing, and they could eliminate the need to give an adult Explorer a child’s birthdate. These are topics I’d hope advocacy groups will help with. I’ll address them again in the last chapter of this book.

[1] https://support.apple.com/en-us/HT20108

Screen Time – the quick setup guide

I’m still rewriting Screen Time advice. Decided to put together the simplest possible setup for “Local” Screen Time (not using family sharing screen time). This give 90% of the value of more complex use.

———-

Using the Explorer’s iPhone open Settings:Screen Time. Tap “Turn On Screen Time”. When asked “Is This iPhone for Yourself or Your Child” be sure to tap “This is My Child’s iPhone”.

The next screens ask about Downtime and App Limits. Tap “Not Now” for both.

Set a Parent Passcode. Don’t use the Explorer’s phone passcode! This has to be a 4 digit number and the Explorer would not normally know it. Don’t lose the passcode, you can’t reset it.

That’s It! You’ve enabled Local Screen Time. You haven’t set up any restrictions though, so your Explorer won’t notice any difference in their iPhone.

Go back to Screen Time:Settings and do these three things:

  1. Always Allowed: Tap on “Always Allowed” and add apps that every Explorer should always have access to. Basically everying that’s useful but boring[1].
  2. App Limits: Tap on “App Limits”, then “Add Limit”, choose “All Apps & Categories” and set a daily limit of, say, 3 hours. Be sure to enable “Block at End of Limit”[2].
  3. Downtime: Tap on “Downtime” and enter time that Explorer is at work or school.

———-

That’s it. You’re done! With this setup the “Always Allowed” apps are never disabled. So your Explorer can alway use their Calendar, Reminders and so on. During work or school hours (Downtime) games, social media and the like won’t work. For the rest of the day “fun” apps can be used for a maximum of 3 hours. (Productivity apps count against this limit too, but most people use these less than 10 minutes a day.)

If an Explorer runs into a limit the non-permitted app will stop working and the Home Screen icon will show a small timer icon. They can bring the device to a Guide who can enter the security code and override the block for a few minutes or for the day.

– fn –

[1] Example: Messages, FaceTime, Maps, Books, Calculator, Calendar, Camera, Compass, Contacts, Find Friends, Health, Mail, Notes, Photos, Reminders, Voice Memos, Weather. For many add Books and Music and consider Podcasts. If your Explorer uses Googe Maps then add that too.

[2] This is easy to miss. If you don’t do this then your Explorer just gets a notice they can override. In some cases this is what you want, but that’s more advanced use. “Block at End of Limit” is the default.

Screen Time for supported iPhone use — the best reviews

The more I look at (remote) Screen Time the more impressed I am by the power and complexity of this project. Today, for example, I realized there is an option to include or exclude “Website Data”. I also discovered that after you’ve set an app limit time, a magic “Customize Days” option appears! I can’t “unsee” “Customize Days” now, but for weeks I didn’t notice that it suddenly appears once you set a time value.

It’s not perfect by any means. Screen Time reports don’t always update promptly.  I have a device that refuses to enroll in Screen Time. The need to change an Explorers Apple ID age to be under 18 is more than frustrating — this should be an Accessibility setting. We need Apple to offer an API that devs can build solutions around, so the burden of making this work doesn’t fall only on parents. Note least — we need better documentation!

I’ve been trying to write that documentation and I now understand why it doesn’t exist. This is really complicated. I’ve rewritten my chapter work several times, and now I’m stepping back to collect the best documentation I can find by searching on some keyword phrases:

  • Screen Time
  • Family Sharing
  • Include Website Data
  • Customize Days

As of 1/5/2019 if I ask for all of these I get one result! Relaxing the search a bit here are the best docs I’ve found (most of ‘em don’t get the difference between remote and local Screen Time controls):

And from Apple support (there’s not much in the iOS 12 User Guide):

That’s the current set. Next step is to finish my own take, then go through each of the above and add in what I’ve missed.

Remote Screen Time in iOS 12 – a breakthrough in Explorer support

With iOS 12 Apple made big changes to what it used to call “restrictions” or “parental controls” and is now called “Screen Time”. It took me a while to appreciate the power of Apple’s approach. It’s not everything Explorer need, but it’s a big step forward. I’m seeing encouraging tweaks and improvements with minor revisions to iOS 12; I think Apple has decided to get this right.

The really big change is that, with the right setup and configuration, it’s possible for a Guide to use an iOS 12 iPhone or iPad[1] to remotely manage app use on an Explorer’s iOS 12 iPhone. I call this Remote Screen Time. I’ll review what it can do here, in the next chapter I’ll discuss local Screen Time and how to make Remote Screen Time work.

Using Screen Time a Guide can define a core set of apps that are always available and then set time limits on individual apps or categories of apps. For example, a Explorer’s iPhone could be set allow only productivity apps during work hours but enable full use after work is done. How important is this? It can make the difference between employment and unemployment.

This is a big improvement over what we’ve had for the past 8 years. There is still room for improvement though. Apple, at the time I write this, has wounded (broken, really) its web access content controls. It would be nice to be able to manage devices from iCloud as well as a Guide’s iPhone. You can’t mix local (on device) and remote Screen Time. There are many small bugs. There can be odd delays in Screen Time enrollment and updating. Most of all there’s an age problem — in order for restrictions to work optimally an Explorer’s age needs to be set in their Apple ID to be under 18 (more on that later) and they have to be configured as part of a Guide’s “family”.

That’s the bad news. I’ll go over the setup and workarounds in the next chapter, but here I’ll review what we do and why it’s worth the struggle. The Screen TIme image below is taken from my (Guide) personal iPhone. I got to it through Settings:Screen Time.

The image shows my personal Screen Time settings[2] first, then in a section labeled “FAMILY” it shows 3 members of our family (names hidden) who are, as far as Apple knows, “under 18”. I can tap on those names to see a screen that is identical to my personal, locally managed, screen.

ScreenTimeFamily 20181124
For each FAMILY member you can see reports like this for a day or a week or a day, for one device or for multiple devices (such as an iPad and an iPhone).

Jf screentimeSummary 20181208

The key features of Screen Time are briefly described in the iPhone User Guide. Please take a look at those, but there’s quite a bit that’s left out. Screen Time has 4 parts: Downtime, App Limits, Always Allowed, and Content & Privacy Restrictions. I’ll talk about the Content & Privacy Restrictions in a later chapter[3], along with some other iOS settings that are important for safe iPhone use.

Downtime, App Limits, Always Allowed are the main ways to setup Screen Time. There’s another hidden and undocumented control that extends App Limits, I’ll discuss it together with App Limits.

Assuming remote Screen Time is working (see next section on setup), the first thing to do is define the apps that are Always Allowed. These will be available regardless of time related blocks. For most Explorers this will be the safety and productivity apps like Health[4], Contacts, Notes, Calendar, Find Friends, Maps and so on. Other standard items I enable include Calculator, Camera, Compass, Files, Find Friends, Mail, Music, Photos, Weather, and Voice Memos. I also enable Messages though it can be a distraction for some Explorers.

Once the Always Allowed apps are defined there’s an opportunity to set limits. You can do the following:

1. Schedule a time interval during which all non-Allowed apps will be blocked. A family user can request more time from a family manager. There’s just one time interval, you can’t schedule different intervals on weekday vs. weekend for example. This is most useful during an Explorer’s work or school hours.
2. Schedule a time interval when the entire device will be blocked. We don’t use this.
3. Set a daily Time Limit for collections of apps like “Social Networking”, Games, and so on. This is total time, not a time interval. These collections are based on how apps are classified in Apple’s App Store. Sometimes they are a bit odd; on one Explorer’s iPhone “Police Scanner Radio” is classified as “Reading & Reference”. We have made use of limits for “Social Networking” and Games, but I actually find the next, undocumented, method more useful.
4. Set a daily limit for a specific app. This undocumented feature is only available for apps that have already been used by an Explorer. It doesn’t show up under “App Limits” where you’d expect to see it[5]!

To set a daily limit for a specific app you have to first tap on the summary of screen time use. This shows a screen where you can see use for “Today” or for “Last 7 Days” and, for Explorers with both an iPad and iPhone you can choose which device to see. Here’s where the secret is found. It may not be obvious, but you can scroll down to see a list of either most used Apps & Websites or Categories for either the current day or the past 7 days. This the real power in Screen Time. You can set daily usage limits for a specific app or even a specific web site. This is where we do most of our adjustments.

There’s a lot of power hidden in remote Screen Time once you have it working. Some of it is more obscure than it should be, but it’s great stuff. To summarize first step is to specify which apps are always allowed, then block all non-Allowed apps during work or school hours, then, if desired, set usage limits on individual apps like Instagram, Snapchat, Safari and the like.

– fn-

[1] I think the almost forgotten iPod Touch would also work. Even an old iPhone 5s can do remote control as long as it’s running iOS 12.
[2] We are all, fundamentally, Explorers. Advanced Explorers, including Guides, may find it helpful to set personal, locally managed, Screen Time limits. Assuming we known our own Screen Time passcodes we can override them, but I find it helpful to set a limit on my compulsive reading habits.
[3] “Content & Privacy Restrictions” aren’t related to time at all, so it’s awkward to have them bundled under “Screen Time”. A more accurate, but less engaging, name for all these things would be “Restrictions”.
[4] See discussion of Health.app. This provides critical health information even when an iPhone is locked. You need this to work.
[5] I hope this gets fixed in iOS 13. It really should show up under App Limits.

Managing an Explorer iPhone with Apple’s two factor authentication

One of my Explorers is very particular about phone hygiene.

He force quits all his apps — immediately. He deletes all instant messages and emails after reading them. He has the makings of a master spy.

In the same vein he clears all nags and notifications cleared — always. When Apple nags him to update iOS he updates immediately — ready or not. When Apple nags him to enable two-factor authentication he enables it. Whether I want it or not.

Two-factor authentication is a problem for Guides. It’s designed to protect a user’s phone and data from outsiders. Unfortunately, that includes well intentioned outsiders like Guides. This makes it hard to support an Explorer by editing their Notes and Contacts for example.

Guide work is a easier, and an Explorer’s iPhone is quite secure, with a strong iCloud password that the Explorer doesn’t know. (You can’t reveal what you don’t know and iPhone use requires the phone passcode, not the iCloud password). It’s hard to avoid Apple’s two-factor authentication [1] though. Even if an Explorer doesn’t enable it Apple requires two-factor authentication for several useful services.

Fortunately there is a workaround — at least for now. From Apple’s ID management site or iPhone Settings:Apple ID:Password & Security you can add a Guide’s mobile phone number [2] to an Explorer’s Apple ID account information:

Two-factor authentication for Apple ID – Apple Support

… A trusted phone number is a number that can be used to receive verification codes by text message or automated phone call. You must verify at least one trusted phone number to enroll in two-factor authentication.

You should also consider verifying an additional phone number you can access, such as a home phone, or a number used by a family member or close friend. You can use this number if you temporarily can’t access your primary number or your own devices

Once you’ve followed the directions at that site this you can access an Explorer’s iCloud account:

  1. Let your Explorer known you’re updating their iCloud data. They will receive a notification on their iPhone that you are visiting their account. If they choose “Don’t Allow” you’ll be blocked. 
  2. Go to iCloud.com and enter the Explorer’s Apple ID and password. At the next screen your Explorer will get the Notification to grant access, but you don’t need it. Instead click “Didn’t get a verification code?”
    Icloud no code
  3. At the next prompt choose “Use Phone Number”.
  4. Choose the number of your phone (Guide phone):
    Choose phone
  5. Enter the number you receive.

You will be given an option to trust the browser you are using so you don’t have to do this again. Accept that offer! In my experience this doesn’t always “stick” but it means you will often avoid this procedure.

I’d rather not have to deal with Apple 2FA but with this workaround it’s manageable.

– fn –

[1] Not to be confused with Apple’s obsolete “two-step verification” — which still shows up in Google searches on this topic.

[2] A number that accepts SMS, including Google Voice numbers.

iPhone safety for Explorers – a chapter section on setting Apple age

When I started my book project I though iPhone setup would be a quick chapter. It didn’t turn out that way. iPhone configuration is probably a third of the book, including initial setup, simplifications, and safety measures.

Most recently iOS 12 forced a complete rewrite of all these chapters and, in the absence of documentation, a good amount of experimentation (my Explorers have been justly annoyed by that)  I’ve discovered, for example, that there are significant remote control options for users whose “Apple age” is less than 18. I’ve also found that when one enables remote control all local Screen Time settings are erased without warning.

With the changes made in iOS 12 safety support now requires setting an Explorer’s Apple age to be under 18 by changing their Apple ID associated birth date. Here’s what I wrote about this today …

The key to safe iPhone use is to decide what birth date Apple should use for the Explorer you are supporting. Apple only provides effective safety support for users for users under 18 years old. The user age, which I think of as the “Apple age”, is based on the birthdate associated with a user’s Apple ID.

If an Explorer’s Apple age is well under 18 this isn’t a concern. If Apple believes an Explorer is near or above age 18 then safety support requires changing the birthday Apple uses.

A user’s birth date can be changed using a web browser at Apple’s ID management site⁠ [1] or through the iPhone’s user account settings [screenshot] under “Name, Phone Numbers, Email”. In my own testing I think it works better to change birth date on the Explorer’s iPhone⁠ [2].

My current practice is to initially set a birth date so that Apple software considers the Explorer to be 14 years old. This doesn’t seem to have many side-effects beyond enabling the iPhone’s safety features⁠ [3]. I can, for example, set my Explorers’ age to 14 but “Allow All Movies” and “Explicit” books.

An initial “Apple age” of 14 means every 3 years a Guide and Explorer must decide whether to revert to the true age or dial back to 14 again. That seems a reasonable interval for reconsideration. The goal of both Explorer and Guide is for the Explorer to no longer require this kind of supported use⁠ [4].

Of course an Explorer can also change their Apple Age using a web browser or their iPhone or any Apple device (including a Mac). Teens discovered this within seconds of Screen Time being available in iOS 12 beta. If this is a concern there are two measures to take.

One measure is to use the Screen Time “Content & Privacy Restrictions” to restrict Account Changes. That will prevent changing Apple Age on the Explorer’s iPhone.

The second measure was discussed in the chapter on initial setup and is also discussed later in this safety chapter. Most Explorer’s don’t need to know their iCloud password and there are safety advantages to keeping that secret. Without knowledge of that password it’s difficult to change Apple Age using web browser [⁠5].

I don’t like changing an Explorer’s Apple age. It’s demeaning. I would like Apple to provide an Accessibility setting called “supported use” that would enable support without changing an Explorer’s birth date. Until Apple does that however, this is the only way I know to support iPhone use for a vulnerable adult. Whether to bring this Apple age change up with an Explorer is something a Guide must decide.

– fn -
1 https://appleid.apple.com/account/manage
2 At the time I write this Screen Flow is new and has many undocumented behaviors and a few bugs.
3 I think this age may also affect what kind of marketing Apple does to its customers.
4 On my own iPhone I have enabled Screen Time blocks to restrict my own use of social media. As an adult I can lift the blocks, but it requires an extra step.
5 I discuss password resets and the effects of two factor authentication later in this chapter.

Netflix accounts can be purchased with a gift card

We learned today that it’s not hard to create an individual Netflix account for an Explorer without the risks of automated credit card or debit car withdrawals (overdrafts, lack of expense control, tracking of spend, etc).

A Netflix account can be funded by a Netflix gift card. Our Explorer paid me cash from his job, I bought him a Netflix gift card on Amazon. When I set up his account I used the Gift card option. It worked. It will be interesting to see what happens when he exhausts the Gift Card fund. I’ll update this post when I learn that.

There is a bug in the process to beware of. Even after entering the Gift card Netflix tries to get a debit or credit card. You can continue without this, but if you click the credit/debit option there’s no control to continue without entering the data. I had to close the window. When I reopened Netflix asked me to finish my Explorer’s signup. I did that and chose the “Continue” option.

iOS 12.0.1 bug: can’t enable blocked site by entering restriction code

In iOS 11 when Web Content was set to “Allowed websites only” and a user tried to access a non-allowed site there was an option to allow the page. Tap on that, enter the restriction code, and the page was added to the permitted list.

This option is missing in iOS 12.0.1. Instead the “allowed websites only” list but be manually edited. Which is almost useless.