iOS Developer Mode, explained

Developer Mode is a switch Apple added in iOS 16 that lets developer tooling talk to your phone. It is not a jailbreak, it removes no protection from iOS, and turning it back off is one toggle and a restart.

If you have ever enabled this, you have seen the screen: a warning, a required restart, and language stern enough that plenty of people back out. So it is worth saying plainly what this setting is, because the reputation it has acquired is not the thing Apple built.

What it actually is

Developer Mode arrived in iOS 16. It is a switch in Settings that allows developer tooling to talk to your phone: installing a build you compiled yourself, attaching a debugger, running instruments, and simulating conditions like a location.

Before it existed, any iPhone connected to a trusted computer could be targeted by that tooling without a separate opt-in on the phone. Developer Mode makes it a deliberate decision, taken on the device, with a restart in the way.

It exists on iOS 16 and later. On iOS 15 and earlier there is no such row, because there was nothing to switch on: the tooling simply worked against any phone that had already trusted the computer. If you are hunting for the setting on an older phone, that is why it is not there.

On a phone that does have it, the row still does not appear until a computer running developer tooling has tried to reach the phone at least once. This catches people out constantly. They go looking for the toggle before anything has asked for it, do not find it, and conclude their phone is not supported. Plug in, let the tool make its attempt and fail, then look again.

It is not a jailbreak

These get conflated constantly and they are close to opposites in intent.

The distinction that matters: a jailbreak removes the rule that code must be signed. Developer Mode leaves that rule exactly where it was. Everything installed while it is on is still signed, still sandboxed, still subject to the same permissions any App Store app faces.

What the warning screen is actually about

The screen tells you the phone has to restart, and that Developer Mode reduces the security of the device. That second half is where the fear comes from, and it is narrower than it sounds.

The threat Apple is describing is not your phone in your pocket. It is your phone in somebody else’s hands. Before iOS 16, a phone that had once trusted a computer could have developer tooling pointed at it with nothing on the phone objecting. That is a convenient property if you are running extraction gear against a device you have taken off someone. The fix was to make the phone ask out loud, with a reboot in the way and a passcode afterwards.

So the honest reading is this: leaving Developer Mode on removes one obstacle in front of somebody who already has your phone and a laptop. That is a real cost and worth weighing. It is a completely different cost from the one most people imagine, which is that apps somehow get a free run of the device.

What changes on the phone

• Developer tooling on a trusted computer can install and debug builds.
• Location simulation becomes available, which is the part relevant here.
• A new row appears under Settings, Privacy and Security.

What does not change: App Store apps behave identically, your data is not exposed to anything it was not exposed to before, the sandbox holds, and no security prompt disappears.

What it does not unlock

The list of things it does not do is longer than the list of things it does, and it is the more useful list.

• No root, no filesystem. You do not get to browse the phone’s storage.
• No reading other apps’ data. The sandbox is untouched, so nothing you install can look at what Messages or your banking app keeps.
• No unsigned code. Everything still has to be signed, which is precisely the rule a jailbreak exists to break.
• No permission changes. Location, camera, contacts and the rest still prompt, and you can still revoke any of them from Settings.

Where it sits in the chain

On its own, Developer Mode does nothing you can see. It is one of three things that all have to be true before a computer can simulate a location on your phone, and it is the least interesting of them.

• The phone has trusted the computer, which is the Trust This Computer prompt and your passcode.
• Developer Mode is on, which is this article.
• Something is actually driving it: a tool on that computer, connected, sending coordinates.

Switch Developer Mode on and walk away and your location does not move a metre. It is a permission, not a feature.

Location simulation, specifically

This is the capability relevant to what we build, so here is the whole of it. Location simulation is the mechanism Apple gives developers to test an app in a city they are not standing in. While it is running, iOS hands apps a coordinate through the ordinary location API instead of the one the GPS chip produced.

That is Apple’s own pathway rather than a way around Apple, and it is why a modern iPhone spoofer works on a completely stock phone. The capability was always there for developers. iOS 16 moved the gate for it into Settings, where you can see it.

What it does not do is make anything invisible. The simulated coordinate reaches an app in the same shape a real one would, but the pattern of your movement is still yours to get wrong, and the pattern is what gets noticed. We wrote a longer piece on that. The short version is that nobody should be promising you anything here, us included.

Can an app tell it is on?

We do not know of a public API that reports Developer Mode’s state to a third-party app, and we went looking. That is not the same as saying nothing can tell, and we have not tested this against every app that might care, so treat it as what it is: an absence we could not fill rather than a result.

Two things we can say with more confidence. A phone enrolled in an employer’s or a school’s device management can have Developer Mode withheld by policy, so on a managed handset that is the first thing to rule out when the row is missing or refuses to switch on. And whatever an app can work out about the setting, it can always see the location you report, which is the part actually worth thinking about.

Turning it on

Connect the phone to the computer running whichever tool you intend to use and let it try. Then, on the phone: Settings, Privacy and Security, Developer Mode, on. The phone offers to restart. When it comes back, unlock it and it asks a second time, and you confirm with your passcode.

Turning it off

Settings, Privacy and Security, Developer Mode, off. The phone restarts and the row disappears. Anything that depended on it stops working, which is the expected outcome rather than a fault.

Expect anything installed with a development certificate to refuse to launch until it is back on. App Store apps are unaffected, because they never needed it in the first place.

There is no cleanup afterwards and no residue we are aware of. The row leaves Settings, the capability goes, and the phone is back in the state it shipped in. Switching it off once you are done costs a restart, and is a reasonable habit.