Skip to content

Automotive · EV

Battle Motors

A unified digital layer for configuring, tracking and managing next-gen electric trucks.

  • AOSP
  • .NET
  • Angular
  • Flutter
  • GPS tracking
  • Vehicle management
Battle Motors project visual
Industry
Automotive · EV
Services
Web, Mobile, Embedded
Platforms
In-cab, iOS, Android, Web
Engagement
Long-term partner
  • 4platforms, one backend

The challenge

Battle Motors builds next-generation electric and vocational trucks. Managing how those vehicles are configured, tracked and serviced spanned the cab, the field and the back office — each with its own tools and its own copy of the truth. The brief was a single digital layer that every surface could share.

Our approach

We built across four surfaces against one backend: an in-cab Android (AOSP) experience, iOS and Android companion apps in Flutter, and an Angular web console, all served by a .NET services layer with GPS tracking and vehicle-management data flowing through a single source of truth.

Battle Motors fleet console and trip-management view

The build

  • AOSP
  • .NET
  • Angular
  • Flutter
  • GPS tracking
  • Vehicle management

How it's built

  • In-cab Android (AOSP)
  • iOS & Android (Flutter)
  • Web console (Angular)
One backend One .NET backend · GPS + vehicle-management data
Next case study CallHippo →