From the experiment

Do coding agents recommend Apple Maps (MapKit)?

Apple Maps (MapKit) was chosen in 14% of 759 judged maps sessions, ranking third. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.

Published September 28, 2026 Updated September 29, 2026 Read as Markdown

Apple Maps (MapKit) was chosen in 14% of 759 judged maps sessions, ranking third. It was also raised as a candidate in 1 further sessions without being chosen.

This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in maps inside a realistic codebase. Not what a chat assistant says about Apple Maps (MapKit). What an agent actually installed.

The numbers

CategoryMaps
Sessions in the category759
Sessions where Apple Maps (MapKit) was chosen104
Install share14%
Rank in category3 of 49
Codebases it won in2
Raised as a candidate, not chosen1
Chosen when considered99%
Sitedeveloper.apple.com

By agent

Claude Code, Codex, Cursor, Grok Build CLI and Muse Code agree closely on Apple Maps (MapKit), choosing it at rates within 4 points of each other.

AgentSessionsChose Apple Maps (MapKit)Share
Claude Code1642314%
Codex2272812%
Cursor1542416%
Grok Build CLI37616%
Muse Code1772313%

By who was asking

Apple Maps (MapKit) does much better with one kind of buyer than another. It won 34% of sessions asked as senior engineer and 0% of those asked as enterprise team.

Who is askingSessionsChose Apple Maps (MapKit)Share
Vibe coder1634930%
Junior developer24700%
Senior engineer1625534%
Enterprise team18700%

What Apple Maps (MapKit) was up against

The full ranking in maps, from the same sessions:

#ProductRuns wonShare
1Google Maps13318%
2Leaflet12516%
3Apple Maps (MapKit) (this page)10414%
4MapLibre618%
5Mapbox527%
6Built in-house (no product adopted)436%
7react-native-maps375%
8OpenStreetMap375%

What this means

Agents almost never raise Apple Maps (MapKit) without choosing it: 1 sessions raised against 104 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.

Where these numbers come from

The 759 sessions in maps are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.

Every maps run can be replayed on the board.

If you work on Apple Maps (MapKit): the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.

<!-- generated by scripts/write-data-pages.mjs -->

Common questions

Do coding agents recommend Apple Maps (MapKit)?

Yes. Apple Maps (MapKit) was chosen in 104 of the 759 judged sessions in maps, a 14% install share, ranking third in its category.

Does Claude Code recommend Apple Maps (MapKit)?

In 23 of the 164 sessions in maps run with Claude Code, which is 14%.

Do different coding agents treat Apple Maps (MapKit) differently?

Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 12% and 16% of their runs.

How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 92 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.

How often is Apple Maps (MapKit) considered but not chosen?

It was raised as a candidate in 1 sessions without being chosen, and chosen in 104. That is a 99% conversion from considered to chosen.

Where this comes from

Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages