Instrument Manufacturers: Build a Riding APP or Integrate an APP and SDK?

Decide whether the phone APP is your core product

If your team needs direct control over the phone interface, feature roadmap and platform maintenance, evaluate building a riding APP. If your focus is instrument hardware, vehicle interfaces and the instrument UI, evaluate integrating an existing APP and terminal SDK. Both approaches require hardware adaptation and device acceptance tests; successful pairing is only a starting point.

Infinite Ride provides an Android/iOS riding APP and a C99 hardware SDK for FreeRTOS, for connected motorcycle and electric two-wheeler instruments. Manufacturers retain their boards, display interfaces and vehicle connections. Infinite Ride does not supply complete vehicles or universal plug-and-play instrument hardware.

Where does the work sit in each approach?

Evaluation area	Building your own phone solution	Integrating Infinite Ride APP and SDK
Phone maintenance	Your team owns the APP, connection flows, business protocol and OS adaptation	Reuse existing APP and SDK flows after checking required feature coverage
Instrument firmware	Design or choose a communication protocol and connect board drivers	Use a platform-matched SDK library and connect Wi-Fi, storage, clock and display drivers; add Bluetooth notifications and pairing assistance as needed
Instrument interface	Your team designs and implements it	The manufacturer still controls the UI and updates it from SDK events
Vehicle interfaces	Implement actual state reading, command execution and results	The manufacturer still adapts CAN, serial or other vehicle interfaces
Delivery assessment	Scope phone software, protocol, firmware and ongoing operations	Confirm feature coverage, platform compatibility, licensing and hardware adaptation

Bluetooth notifications require a separate Core BLE companion; Managed Wi-Fi does not create that connection. Use the architecture and lifecycle overview to choose an interface for your target features.

Budget and schedule depend on existing software, team resources and hardware readiness. Compare both approaches against the same feature list and acceptance criteria instead of assuming a fixed percentage saving.

What does Infinite Ride deliver, and what does the manufacturer implement?

The SDK core is delivered as closed-source binaries, with target-platform static libraries, public headers, examples and integration documentation. Libraries must match the CPU architecture, FreeRTOS configuration and compiler ABI. Reconfirm the package when changing the chip or toolchain.

The manufacturer implements board connectivity, persistence, display, decoding and vehicle interfaces. The SDK passes phone-device events to firmware; it does not automatically implement vehicle unlocking, video decoding or drivers for arbitrary boards. Firmware features must also match the device model configuration in the management platform.

Start with the SDK overview, platform and licensing guide and first connection steps to identify what your project can reuse.

Common questions before choosing an approach

Can we keep our instrument UI?

Yes. Manufacturers handle SDK events with their own display drivers and interfaces. Large-screen navigation integrates both video and HUD; compact displays that cannot show video can use HUD alone. Manufacturers decide the layout. See the navigation integration guide.

Does the ESP32-P4 example run on every board?

No. The public ESP32-P4 reference project provides application and board integration examples; the SDK core remains binary. Other boards need compatible libraries, drivers and a resource assessment.

Does successful device pairing mean integration is complete?

No. Validate real vehicle state, command results, reconnection, navigation display and permission withdrawal for the required features. Use the testing and delivery guide to define acceptance criteria.

How are cost, scope and delivery timing confirmed?

Share the chip and toolchain, FreeRTOS version, display and decoding capabilities, BLE/Wi-Fi setup, vehicle interfaces, target features and prototype readiness. These inputs support confirmation of platform support, device licensing, delivery scope and a quotation. Public documentation does not replace a project delivery agreement.

Begin with one prototype

Start with discovery, authenticated pairing, capability exchange and one real state update. Then add vehicle controls, navigation and notifications as required. For multiple instrument models, read about sharing one riding APP.

Share your hardware details to discuss APP and SDK integration.