The UK will legislate the nudity block Apple and Google were asked to volunteer

The duty lands in the second between the camera button and the share sheet. A child raises a phone inside whatever app is open, and the planned law covers the taking as much as the sending ^[1], so something on the handset has to judge the image before it becomes a file anyone can forward, and it has to know whether the person holding the phone is under 18 ^[15].

There are two layers in the plan, and the seam between them is where the interesting reading sits. Nandy credited Apple and Google with meaningful changes at the core of their systems ^[7] in the same statement that called their proposals short of the scale of the crisis ^[3]. Apple's reply points at Communication Safety, launched in 2021 and expanded since, plus future plans shared with UK officials ^[8]; Google's says it has made progress and describes itself as an industry leader on non-consensual intimate imagery ^[9]. On the record, then, the government's complaint is about reach rather than feasibility, which is why the draft bill picks up providers of apps used by children as well ^[5].

Reach matters because of where capture happens. The NSPCC says content filmed on a child's own device can be the starting point for grooming and sexual extortion ^[10], and UK police chiefs have said restricting a child's device from taking or sharing nude images would be a key step against sextortion ^[11]. Ofcom data suggests smartphone ownership is growing among younger children ^[18], though the report puts no figure on it ^[2].

Count the calendar: three months from June ran out in September, so the move to legislate follows a lapsed voluntary deadline rather than a live one ^[1]. The NSPCC's Chris Sherwood called the plans a necessary move after firms missed that deadline ^[12]; Andy Burrows of the Molly Rose Foundation called the route to them needlessly long and torturous ^[13]. What the report does not carry is an introduction date, a penalty regime, or any definition of an app used by children ^[2].

For anyone who has to size this before the bill text exists, two questions do most of the work. First, does your product have a path that creates or forwards an image, including a camera, an upload field, or a share sheet? Second, do you hold an age signal you would defend to a regulator? If both answers are yes, you are building classification for a defined subset of accounts. Have an image path with no age signal, though, and the choice is between classifying everyone's pictures and gating everyone at the door -- precisely the outcome Open Rights Group warned about when it said adults would be pushed through a digital ID checkpoint and private images scanned by default ^[16]. Hold an age signal without an image path, and you are a spectator until scope is written down. Lack both, and the bill text is your only homework.

The pitch is a block on children's devices, and the government is clear that adults' access to naked imagery is not the target ^[14] and denies this amounts to surveillance ^[17]. The build is an age-assurance dependency inside products that never had one, because the child and adult distinction has to be drawn somewhere on the device ^[15]. Teams with a camera and no defensible age signal will spend their money on the second problem, not the first.