Skip to content
Browse

For automakers and Tier-1 suppliers

A production web browser for your head unit

Browse brings the full web to Android Automotive OS through Mozilla's GeckoView engine, with driver-distraction handling built on the platform's own signals. We work with vehicle makers and their suppliers to bring it to in-vehicle app stores.

Contact usPress kit

Integration

Fits the platform you already ship

Browse runs as a standard app on Android Automotive OS. No custom system image or platform changes are required.

  • A standard Android app

    Browse is delivered as a signed Android app package (APK) for your in-vehicle app store. It installs as a regular third-party app and needs no platform signature or privileged permissions.

  • Driver-distraction handling

    Browse listens to the platform's CarUxRestrictions signal and the vehicle's gear and parking-brake state. When restrictions apply on the driver's display, it pauses playback and covers the screen with a driving notice, then resumes normal browsing when they end. It fails closed: until the vehicle's driving state is confirmed, the driver's display stays restricted.

  • Multi-display aware

    Browse resolves the display and seat it runs on through CarOccupantZoneManager. The driving notice applies to the driver's display and to any display it can't identify. Front-passenger and rear-seat displays that the vehicle reports keep browsing while the car moves.

  • Built for in-car input

    Touch, rotary controllers and D-pad keys, with a visible focus ring on web content. Steering-wheel media keys work through Android's media session, and audio continues in the background while parked.

Security and privacy

Locked down by default

A summary of the posture of the in-vehicle store build.

  • No account, no saved passwords

    There is nothing to sign up for, and Browse doesn't store website passwords.

  • Least-privilege web permissions

    Website requests for location, notifications and similar permissions are declined automatically. Media can autoplay only silently; sound needs a tap.

  • No microphone, camera or location access

    Browse never asks for microphone, camera or location permissions. Voice search arrives as text from the vehicle's own assistant, and vehicle signals (driving restrictions, gear, parking brake and, where granted, speed) are used on the head unit only.

  • No phone pairing in the store build

    Phone pairing and local-network sync are not part of the in-vehicle store build.

  • Privacy-first telemetry

    Analytics carry only the site's scheme and host, never full addresses, page titles or typed text. Crash reports carry no screenshots or screen recordings. Details are in the privacy policy.

  • Coordinated disclosure

    Researchers can reach us through our vulnerability disclosure policy and security.txt.

  • Open-source notices

    Every open-source component in the build, its version and its licence are listed on our open-source page, with source links for MPL and LGPL code.

Technical facts

The current store build

Package name
art.dart.browse
Version
1.36.62
Platform
Android Automotive OS, Android 9 (API level 28) or later
Engine
Mozilla GeckoView 150
Input
Touch, rotary, D-pad, steering-wheel media keys
Display awareness
Occupant zones via CarOccupantZoneManager
Distribution
In-vehicle app stores. Availability depends on the vehicle maker and region.

Talk to us

Tell us about your vehicle program, display layout and target markets, and we'll follow up with integration details.

Email support@dart.artSecurity researchers: security@dart.art