Skip to main content

Hardware Access Policy

Pleos Connect apps must access hardware only through platform APIs, and mobile-only APIs may be restricted in the in-vehicle environment. You must also design for potential network instability while driving.

Hardware Access Policy (Use of Platform APIs)​

Within the Pleos Connect/Playground ecosystem, direct access to vehicle hardware is strictly prohibited to ensure security and system stability.

  • No direct control: Do not attempt to directly access the vehicle’s physical controls or sensors.
  • Platform API first principle: Information about the vehicle state must be obtained via the standard APIs provided by Pleos Playground.
Caution when using mobile-only APIs
  • Restricted items: Telephony (calls), SMS, some sensors (gyro, proximity, etc.), calendar/contacts, etc.
  • Mitigation strategy: Boldly remove functionality that is not essential in the in-vehicle environment, or design an “optional” structure that checks for feature availability before operation.

Network Environment Mitigation Strategy (Network Resilience)​

While driving, it is common for cellular or Wi‑Fi connections to drop or for the available bandwidth to decrease sharply. To address this, we recommend designing offline/low-bandwidth modes.

  • Caching strategy: Store recently used content locally so that it can be displayed even when offline.
  • Communication optimization: Implement request retry logic and appropriate timeout handling.
  • User feedback: Provide an “offline mode” guidance UI so that users are aware when the network is disconnected.