The schematics are basically "here's a black-box SoC and here are the data lines connecting it to a black-box camera module". The magic of the iPhone are the black-box chips and their firmware, not the traces on the PCB.
About the most useful thing you're getting out of this are capacitor values, which are easy to measure either way.
Things used to be different 2-3 decades ago, but nowadays, most commodity PCBs are exceptionally boring - it's mostly just digital signal routing and some power-related stuff.
The repair process for a modern phone involves swapping salvaged parts on to salvaged PCBs.
Most of the parts on the PCB are custom and not available for purchase separately. The passives aren't likely to be points of failure, but even when they are they're usually swapped from some other donor board rather than purchased new.
I don't think right-to-repair folks would have much use for anything more than that hardware-wise. You can give a technician the HDL or lithography masks to Apple's A17 chip, but it's not like he has an EUV lithography machine in the back of his repair shop.
But a technician won't care about those magic. All they care is whether they can get those FW and chips, and there is mechanism to flash/replace them.
A trace on PCB is much more important. Boardview is a must to do board repair.
In modern phones the key part numbers for ICs aren't going to correspond to anything you can buy.
At best, you can see the part numbers for the passives and their alternate suppliers. The part numbers for most of the actives aren't going to be useful to anyone outside of the manufacturing chain for these parts. A repair tech would simply source the donor parts from an identical phone model.
It still saves competitors on R&D. As in "ah they routed it this way, nice!" or "They have this capacitor here, we don't. I wonder why it is there" etc.
Schematics are extremely valuable!
Sure thing if you copy the schematic, routing, you don't suddenly get a working iPhone, but you might use it to design your own device that will have robustness of a phone designed by multi trillion corporation.
However having high quality documentation that is easily accessible is always the first step, and if there are information there that are important it is _much_ more likely it will be known.
It is not "a much less of a deal" as you say, it is a pretty big deal for a global product that billions of people touch.
But a technician won't care about those magic. All they care is whether they can get those FW and chips, and there is mechanism to flash/replace them.
If anyone is curious
Very nice to see these out in the open though. Saves some work. Even if it is the 16e.
I doubt Apple could demonstrably prove damages before the civil statute of limitations expires. This is a nonstarter in court, and furthermore this is not negligence by the FCC. You do not have a right to keep your FCC filings from leaking under all circumstances, and the FCC has not assumed a civil obligation externally to your rights to do so. Government agencies do not sign NDAs when corporations submit technical documents to them. The Federal government has no obligation in statute to keep them secret, you asking them to is a polite suggestion to the FCC and holds no bearing in law. Even if you could prove damages, trying to bring a case under the Federal Tort Claims Act against the government for this would be a nightmare in any administration, and there's no way that the Supreme Court would cede the idea that the government has an absolute obligation your filings secret forever under pain of civil penalties. It's an embarrassing clerical error, but it isn't a tort.
Examples of this happening in the past?
Apple fears the tariffs.
> The parties acknowledge that monetary damages may not be a sufficient remedy for unauthorized disclosure or use of Confidential Information [...list ways Apple is allowed to nail disclosing partner...]
For competitors they're useless anyway - the big guns (think Samsung, Apple, Motorola, ...) all know how to design a smartphone and none of them will want to get caught copying a competitor. Chinese cloners and repair shop suppliers somehow manage to reverse engineer even highly complex PCBs in a matter of weeks, to the tune you can walk around in Shenzen and have a multitude of deepest level repair options, including upgrades by reballing and replacing storage options that Apple doesn't even offer.
But actual repair shops and repair cafes here? They would greatly benefit from having quality documentation and access to tools.
However, some schematics are for products only used internally - like Google TPU’s or some cellular radio access network equipment. I think that there exist FCC-approved devices for which the public does not have any interest in the schematics and can remain private.
The schematics aren’t really “secret” in the sense of a recipe. There’s not really a way to precisely determine the recipe for a particular food product, it’s more of a process than just a list of ingredients.
Schematics are right there inside the physical circuit board for anyone to inspect. You already give them away with every product. It’s just expensive to reverse engineer.
Personally I also think most material compositions should also be made public by similar logic. I think consumers should be able to know what’s in their blankets, dishware, and alcoholic beverages as well. Apparently beer/liquor isn’t required to list ingredients either, which is mind-blowing to me in 2025.
Schematics for high-density boards like this are not as informative as you might expect. It's mostly connections between balls of ICs and the values of passives here and there. The values of those passives can be measured from parts salvaged from boards if necessary. More likely, the technician would simply steal the part from another PCB that has been scrapped.
It doesn't even matter if the Chinese companies get it. That will only accelerate innovation because nobody would buy an unrepairable clone if repairability is the norm. The Chinese companies will have to publish their schematics too.
Two, take a look at the system specification and block diagram also.
I guess an argument can also be made for security. Publishing schematics makes it easier bad actors.
Tim has made some terrible choices – I'm sad this is so accurate.