From the phone in your hand to the car around you — APEXDOT engineers the hardware, the operating system and the interaction language that make them behave like one product.
Most suppliers treat a phone team and a car team as two companies that happen to share a logo. We do not. A cockpit is a large, thermally-generous, safety-certified device — and a phone is a small, thermally-hostile, battery-bound one. The industrial design, the sensor stack and the certification regime differ. The software layer underneath does not have to.
AMobile
Mobile Devices
Full-stack smartphone engineering, from ID lock to mass production.
DOT OS is a shared device runtime. The same application framework, design system, update pipeline and telemetry schema build for a handset SoC and for a cockpit domain controller. Below the framework the two diverge — above it, they are the same product.
An AOSP-derived handset build and an Android Automotive OS cockpit build produced from one source tree. One design system, one update pipeline, one telemetry schema.
Handset base
AOSP 15
Cockpit base
AAOS 15
Shared code
Framework and above
Update model
A/B seamless, signed
AC-1
02
Cockpit reference platform
A three-display cockpit reference: driver cluster, centre stack and passenger display driven from a single domain controller, with the safety-relevant cluster isolated behind a hypervisor.
Displays
3 (cluster / centre / passenger)
Isolation
Type-1 hypervisor
Cluster target
Safety-isolated partition
Cold start target
First frame under 2 s
DOT Link
03
Phone-to-car continuity
The handset is the identity. Approach the car and your seat, mirrors, climate, audio and navigation state are already there. Walk away and the car forgets you.
Key
UWB + BLE digital key
Handover
Navigation, media, calls
Profile
Seat, mirror, HVAC, audio
Fallback
NFC card, offline
DOT Signal
04
Ambient interaction language
A light-and-haptic vocabulary shared between the phone and the cabin. Information you can read without looking at a screen, and without taking your eyes off the road.
Channels
Light, haptic, spatial audio
Surfaces
Handset, door line, dash line
Grammar
Composable patterns
Eyes-off
Designed for glance-free use
Where we are
Small, deliberately.
2
Product lines
Mobile and cockpit
1
Shared runtime
DOT OS
48
Engineers by Q4 2026
Target
3
Cockpit programmes
Target, 2027
Figures below are the 2026 operating plan. Forward-looking items are labelled as targets — we would rather be held to a number we published than to one we implied.
Singapore engineering team stood up. DOT OS source tree established with a handset build and a cockpit build produced from one branch. Design system published internally.
2026 H2Planned
AC-1 reference cockpit
First three-display cockpit reference platform running on a domain controller, with the cluster isolated behind a hypervisor and DOT Signal driving the ambient line.
2027 H1Planned
DOT Link in a vehicle
Phone-to-car continuity demonstrated in a real vehicle: digital key, profile restore and navigation handover, on a partner mule rather than a bench.
2027 H2Planned
Process certification
ISO 26262 and ISO/SAE 21434 process assessments completed for the cockpit practice, and the OTA chain producing UN R155 / R156 evidence as a by-product of normal releases.
2028Ambition
Programme delivery
Cockpit software delivered into a customer vehicle programme, and a handset programme in mass production on the same runtime. One layer, two industries, shipping.
The company
Singapore, since April 2025.
The company was incorporated in Singapore on 8 April 2025 as an exempt private company limited by shares. Singapore was not a tax decision — it is where the supply chain, the automotive programmes and the engineering talent we need actually intersect. Shenzhen is a four-hour flight; Bangkok, Jakarta and Chennai are closer still.