Skip to content
Concept visualization of a woman driving with a personalized NOAH cockpit

NOAH / Evolving cockpit experiences

Let drivers define their personalized experiences.

A cockpit platform that lets drivers design their own HMI appearance and behavior—and apply changes immediately without updating the vehicle’s system software. Keep the cockpit experience evolving after delivery through an OEM-owned service model.

Driving scene: concept visualization.

01 / Driver Experiences

Let drivers design their own HMI and UX.

With a cellphone app, drivers design both the GUI they see and the behavior they want. NOAH brings their design into the cockpit immediately, without changing vehicle hardware or the system binary, and without restart or reboot.

NOAH cluster with a purple three-dimensional landscape
Her chosen design

A colourful landscape.

She chooses a playful 3D world around her driving information.

NOAH cluster with cyan circular instruments
His chosen design

A focused instrument view.

He chooses luminous gauges and a different information layout.

Illustrative individual design preferences. Both interface designs were built with NOAH; these screenshots illustrate appearance, not the cellphone design tool.

UI / What you see

Design your own interface.

Use the cellphone app to personalize colours, graphics, layouts and displayed information. Drivers shape their own GUI, then apply it to the cockpit through NOAH.

UX / How it responds

Define the HMI behavior you want.

Use the cellphone app to define responses to context. For example: “When it rains after dark, use my low-glare layout and bring navigation into focus.” Behavior can respond to time, weather, sensor inputs and driver state within the integrated vehicle scope.

Design on your phone. Apply in your vehicle.

Driver creates

Cellphone app

Design your GUI and define context-based behavior

NOAH brings it to life

NOAH Runtime

Apply the driver’s design immediately

Driver experiences

Personalized cockpit

Your appearance. Your defined responses.

Vehicle hardware and system binary remain unchanged. No restart or reboot.

02 / Display Coordination

Multiple displays. One connected visual experience.

Carry graphics and animation across cockpit displays with perspective aligned to the driver’s viewing position. Give your brand a visual experience that belongs to the whole cockpit.

Conceptual NOAH cockpit showing a coordinated three-dimensional scene across displays
Concept illustration / A shared scene rendered across separate display surfaces.

Consistent perspective

Display views are composed around a shared scene and viewing position, so the geometry reads as one connected view.

Continuous motion

Move visual elements between screens as part of a coordinated animation.

A recognisable brand experience

Use depth, motion and display composition to create a cockpit identity beyond a flat instrument layout.

03 / Functions On Demand

Describe the response you want.

An advanced path to designing your own experience: describe your preferred behavior in a prompt, and let FOD interpret it into personalized functions. It extends the cellphone app’s GUI and behavior design with prompt-based creation.

“When I look tired at night, simplify my display and suggest a rest stop.”

VibeMachine interprets the request and can coordinate HMI functions and vehicle systems to create a personalized UX. Available responses depend on the integrated vehicle functions.

LLM-assisted personalization is at proof-of-concept stage.

Explore VibeMachine / FOD →

04 / Embedded Demonstrations

Built with NOAH. Demonstrated in hardware.

NOAH has been implemented on Renesas, Qualcomm and MediaTek platforms. Embedded performance has been measured; evaluation results can be reviewed against your target hardware and display workload.

Renesas Qualcomm MediaTek
NOAH cross-display proof of concept on physical display hardware
Hardware proof of concept / Cross-display rendering and animation.

These examples show implemented graphics and display capabilities. The UX Apps Store below describes a proposed OEM business model.

05 / Oem Benefits

Keep creating value after vehicle delivery.

Use NOAH as the platform for an evolving cockpit experience business: give customers reasons to return, and give your brand room to introduce something new.

Differentiate your brand

Create a recognisable cockpit identity—and extend it with new designs and behaviors over the vehicle’s life.

Offer new experiences

Let customers create their own GUI and behavior through a cellphone app. Extend the offering with manufacturer-created experiences and advanced prompt-based personalization.

Create recurring revenue opportunities

Build paid experience collections or services around a platform customers can also use to create their own UX. An OEM-controlled store can distribute additional content; commercial results depend on the offering and demand.

Reuse across vehicle programs

Build on a common experience platform, with integration and validation defined for each vehicle and hardware configuration.

06 / Ux Apps Store

Add a UX Apps Store to a platform for user-created experiences.

Drivers can design their own GUI and behavior with the cellphone app. A UX Apps Store adds another path: discover and download OEM or partner experiences, then personalize them. NOAH is the common platform that brings user-created and downloaded experiences into the cockpit.

OEM experiences MAI experience development Selected content partners
Discover & choose

OEM UX Apps Store

Catalogue, pricing and customer relationship

Experience deployment

NOAH Runtime

Bring the selected UX package into the cockpit

Use & personalize

Driver’s cockpit

New appearance and supported behavior

Vehicle hardware and system binary remain unchanged.

Design packages

New visual worlds, layouts and display compositions.

Behavior packages

Context-based HMI responses for supported vehicle functions.

Complete UX packages

Appearance and behavior designed to work together.

Additional commercial channel / The store distributes experiences; the cellphone app lets drivers create their own. Catalogue operations, package validation, distribution and commercial responsibilities are agreed with the OEM.

07 / NOAH Runtime Ota

Seamless OTA deployment on the fly.

Runtime-OTA updates HMI content and behavior immediately without a reboot. The change can come from a manufacturer’s OTA release or a user’s personalization request.

Manufacturer OTA

Deliver a new HMI after production.

Release a revised interface, add a display experience, or update interaction behavior through the OEM’s secure telematics channel. NOAH applies the HMI update immediately without a reboot.

HMI package OEM secure telematics NOAH Live update
User personalization

Make the same vehicle feel different.

A driver designs a preferred GUI and behavior through the cellphone app. NOAH applies the resulting configuration immediately on the same vehicle, without rebuilding its system software or rebooting.

User design Cellphone app NOAH Live update
Experience-package deployment compared with binary and firmware updates
What changes? Traditional FOTA / SOTA NOAH Runtime-OTA
Update payload Firmware or software binaries Supported HMI content and behavior packages
Taking effect Binary updates commonly require a restart or reboot UX behaviors change immediately without restart or reboot
Driver personalization Often limited to manufacturer-provided presets and options Drivers design their own GUI and behavior after delivery; OEM and store experiences can also be deployed
Update boundary Changes to executable system software require system-level validation and protection Experience updates retain the existing binary; package validation and security remain necessary

Runtime-OTA complements firmware and system updates. It applies to supported experience changes; new underlying system capabilities may still require conventional software updates.

08 / Work With Mai

A clear path to NOAH adoption

Choose the delivery model that fits your cockpit program. Start with a concrete driver experience, then assess it on the hardware you plan to use.

MAI delivers the cockpit

Engage MAI to build a NOAH-based dashboard and integrate the agreed driver experiences into your vehicle program.

Tier-1 works for dashboard/IVI

MAI works with your nominated Tier-1 to integrate NOAH Runtime in their hardware platform.

OEM

Own the brand direction, customer offering, catalogue strategy and commercial decisions.

MAI

Provide NOAH, integration expertise, agreed experience development and lifecycle support.

Tier-1 / partners

Deliver agreed hardware, vehicle integration, experience content and program validation.

  1. Define Target hardware and one desired driver experience
  2. Demonstrate Review UI, behavior and deployment scope
  3. Measure Memory, rendering performance and integration effort
  4. Agree Delivery model, licensing and lifecycle responsibilities
  5. Integrate Validate within your vehicle program

09 / Why Adopt Noah

Start with an implemented platform. Build your business on it.

What NOAH can demonstrate and deliver:

Implemented graphics and integration

Start with existing UI examples, cross-display demonstrations and experience on several embedded platforms.

Memory-optimized execution

Evaluate NOAH’s memory use on your target workload, alongside frame rate, visual quality and display configuration.

A platform for user-created UX

Connect cellphone-based GUI and behavior design with immediate cockpit deployment. The same NOAH platform can support OEM-distributed experiences and an advanced FOD path—giving you a basis for more than a download catalogue.

A delivery and support partner

Combine the platform with MAI’s integration work, experience development and agreed lifecycle services.

Compare on the same workload.

Evaluate NOAH alongside your current HMI framework using the same hardware, resolution, scene complexity, assets and animation. Review peak and steady-state memory, frame rate, startup and experience activation time.

Discuss an embedded benchmark →

Evaluate NOAH

Bring one experience you want to deliver.

Tell us your target platform, display configuration and the GUI or behavior you want drivers to design. We can demonstrate the cellphone-to-cockpit path, define measurements and agree a delivery scope.

Discuss your cockpit program →