Apple Maps on the web launches in beta

Original Article ↗ Hacker News Discussion ↗

Browser and platform support

  • Major controversy: site blocks Firefox entirely and also Chrome/other browsers on Linux and Android via UA sniffing, showing “browser unsupported” instead of a warning or “continue anyway.”
  • Even some Apple products (Safari on iPhone and early iOS 18 betas) are blocked; iPad and macOS Safari generally work.
  • Several users bypass the block with user‑agent switching or by visiting a subpath (e.g. /abc), revealing that it mostly works on blocked browsers.
  • Apple’s support page says it’s beta, English‑only, and will expand to more browsers, platforms, and languages later; some argue that using UA blocks in a beta undermines that goal.

Feature set and beta quality

  • Missing or incomplete features: no transit or cycling directions in the web UI, no obvious reverse geocoding by click, miles‑only for some users, limited routing options, inability to click arbitrary map points for directions.
  • Some report poor behavior (misplaced POIs, wrong current location, bizarre routing, dropped pins that are hard to remove, non‑obvious clickable elements).
  • Others praise smooth, fast rendering and visually appealing maps; some say it’s better than the native macOS app.

Comparison with Google Maps

  • Opinions diverge strongly by region:
    • In some places (e.g., SF Bay Area, parts of Turkey, Sydney transit), Apple’s data and/or imagery are said to beat Google’s.
    • In others (rural US, Canada, mountains near Google HQ, parts of South Africa), Apple routes are described as inaccurate or absurd, with stale or wrong business data.
  • Google is still seen as far ahead for: rich business data and reviews, transit and bike routing, integrations (e.g., bikeshare), “how busy” signals, and discovery.
  • Apple wins for: cleaner UI, fewer/no ads, lane guidance and voice directions, privacy posture, and being “nicer” to use for turn‑by‑turn.

Strategic rationale and ecosystem

  • Many view Maps as defensive “core tech” so Apple isn’t dependent on Google, especially for iPhone, CarPlay, and potential future auto efforts.
  • Web version is seen as:
    • Lowering switching costs for people on mixed OS setups (e.g., Linux desktop + iPhone).
    • A data and business‑onboarding funnel (“Have a Business on Maps?”) and potential ad surface.
    • Consistent with Apple’s slow, persistent build‑out of services.

Data sources and OpenStreetMap

  • Apple relies heavily on OSM and other sources; some OSM contributors complain Apple edits can misinterpret local details from imagery.
  • Others note Apple also contributes significantly to OSM and likely bears high infrastructure costs (tiles, satellite, routing, traffic, reviews) that now get reused on the web.