Hardware Access Policy
Apps running on vehicles equipped with Pleos Connect must access hardware through the standard platform APIs provided by the Pleos Connect SDK. Apps developed for a mobile environment may not run as-is in a vehicle because mobile-only APIs may not be available or may be restricted in the in-vehicle environment. Apps running on vehicles equipped with Pleos Connect must also be designed to handle network instability while driving.
Vehicle Hardware Access Policy
Apps running on vehicles equipped with Pleos Connect cannot directly access vehicle hardware to ensure security and system stability.
- No direct access: Do not directly access the vehicle’s physical controls or sensors.
- Platform API first principle: Use the standard platform APIs provided by the Pleos Connect SDK to obtain vehicle state information and control the vehicle.
APIs used to develop mobile apps may not be available or may have limited functionality on an in-vehicle platform. When converting a mobile app into a vehicle app, always verify that the APIs it uses are supported in the vehicle environment.
- Functions that may be restricted: Telephony (calls), SMS, some sensors (gyro, proximity, etc.), calendar, contacts, and so on.
- Mitigation strategy: Remove functionality that is not essential in the vehicle environment, or design an optional structure that checks API support before operation.
Network Environment Response While Driving
Apps running on vehicles equipped with Pleos Connect must be prepared for cellular or Wi‑Fi connections to drop or for the available bandwidth to decrease sharply while driving. We recommend designing apps so that core functions remain available in offline or low-bandwidth environments.
- 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 settings.
- User feedback: Provide an offline mode guidance UI so that users are aware when the network is disconnected.