BMW turned the nav screen into an ad slot. This is where cars are going.

What happened

BMW is running full-screen ads for *Spider-Man: Brand New Day* on the central infotainment display of its cars. The campaign was documented on the community-maintained [consumerrights.wiki](https://consumerrights.wiki/w/BMW_Spider-Man_in-car_advertising) and hit the top of Hacker News with 177 points, where owners across the iDrive 8 and iDrive 9 generations chimed in with photos: a Spider-Man splash card sitting on top of the map, dismissible with a tap, but present.

BMW's official framing is that the notifications are part of the ConnectedDrive services layer — the same channel used for recall notices, over-the-air update prompts, and dealer service reminders. In practice, users are describing it as an ad. The distinction matters legally (a "service notification" is not regulated the same way a paid promotion is) but not experientially. If a full-screen Spider-Man promotion appears on top of your navigation and you have to tap it away, it is an ad, regardless of which internal Jira ticket shipped it.

This is not BMW's first rodeo. The company has previously trialed a monthly subscription for heated seats (walked back after backlash), gated Apple CarPlay behind a subscription in some markets (also walked back), and rolled out an in-car app store built on Android Automotive. The Spider-Man promo is the logical next step of a strategy that has been publicly telegraphed for years: the car is a screen, the screen has inventory, and inventory gets sold.

Why it matters

The outrage is predictable and, honestly, deserved — but the outrage is not the interesting part. The interesting part is what had to be true, technically and organizationally, for this to ship.

For a Spider-Man card to render on an iDrive display, someone at BMW built (or bought) a server-side content management system that targets vehicles by market, model year, and probably VIN cohort. The head unit runs a client that polls that CMS, downloads creative, and renders it inside a UI layer that has priority over the map. That client has to be reliable enough that Sony Pictures — or whichever media buyer sits in the middle — will pay for guaranteed impressions. None of that infrastructure gets built for a single Spider-Man deal. It gets built because the OEM has decided vehicles are a permanent advertising surface, and this campaign is the pilot that proves the pipe works.

Compare this to how Tesla, Rivian, and the Chinese OEMs are approaching the same real estate. Tesla runs its own promos (referral bonuses, Supercharger network expansions, FSD upsells) but has so far avoided third-party ad inventory on the center screen. Rivian pushes adventure content and OTA release notes. NIO and XPeng have gone further in the other direction — full in-car app ecosystems, karaoke, streaming — but keep the ad layer inside those apps, not on the primary driving UI. BMW is the first legacy premium OEM to cross the line into interstitials that appear regardless of what app you were using.

The HN thread splits along a predictable axis. One camp argues this is a Rubicon moment and that the correct response is to never buy another BMW. The other camp points out that every modern car with a cellular connection is already a data-collection endpoint and that the ad is just the visible tip of a telemetry iceberg most owners never think about. Both camps are right. The car has been a networked device with a remote content channel for close to a decade — the Spider-Man ad just made the business model legible.

There is also a regulatory dimension that isn't getting enough attention. UN Regulation No. 79 and various NHTSA guidelines govern driver distraction, and there is a reasonable argument that a full-screen interstitial covering the navigation map while the vehicle is in motion crosses a line. BMW's defense will presumably be that the ads only render when the vehicle is stationary — a claim that will be very testable once someone with a dashcam and a Twitter account decides to stress-test it.

What this means for your stack

If you build software, the practical takeaway is not "don't buy a BMW." It is that the automotive SDK surface is now large enough, and the OEM business incentives aligned enough, that in-car ad tech is a real vertical. Android Automotive OS (the full stack, not Android Auto the projection layer) already supports third-party apps with monetization hooks. Harman, LG, and Bosch all sell head-unit reference designs that ship with content-delivery clients out of the box. If you have shipped an ad server before, you can ship one for vehicles now.

For developers working on automotive integrations — CarPlay, Android Auto, or native head-unit apps — this changes the priority list. Your app is competing for screen time against an OEM that now has a direct financial reason to keep users on the native UI rather than a projected phone interface. Expect CarPlay and Android Auto to get progressively less prominent placement over the next three years. Expect the OEM's own app store to start charging rent. If your business model depends on drivers casting from their phone, you are building on borrowed real estate.

For everyone else: the mental model to update is that a car with an internet connection is a consumer device with the same enshittification curve as a smart TV, a Kindle, or a Roku. The hardware is sold at a margin that assumes ongoing service revenue. The service revenue increasingly includes ads. The hardware lifecycle is 10-15 years, which means the ads compound.

Looking ahead

BMW will probably walk this specific campaign back after a week of bad press, the same way it walked back heated-seat subscriptions and CarPlay paywalls. But the CMS stays. The content client stays. The commercial team that negotiated the Sony deal stays. The next campaign will be quieter — a smaller card, a longer dwell time before the interstitial fires, better targeting so it only appears when the media buyer's model thinks you're most likely to convert. The Spider-Man ad is loud enough to become a story. The next one won't be.