The validation process has several steps.

First, a compatibility test is performed on Faurecia Aptoide standard automotive platform aiming to identify potential compatibility and functional issues on the app associated with our automotive environment. These tests focus on main functionalities, which may vary depending on the type of app under test, such as opening the app, login and account creation, purchases, video and/or audio streaming, controller compatibility, etc. All the info gathered during the initial compatibility tests, including screenshots and logs, will be shared with the app developers.

Once the app is deemed ready to be distributed with the partners it is uploaded to our platform. Each version uploaded will be the subject of a series of manual and automated tests to ensure that our initial assessment is still valid and that it doesn’t contain any type of malware by running it on our antivirus platform.

At this point, the app is ready to be shared with the OEMs but before it is made available on the platforms it will be put through a final batch of tests on the OEM device. Besides running the same tests that were run on the standard platform, specific tests might apply depending on the app. Gaming apps might need low latency and external hardware compatibility tests to be executed to guarantee a good user experience, VoD apps can be subjected to a series of network performance tests while driving the car to ensure that a smooth streaming capability is achieved. Also, for IVI implementations, applications are tested to ensure that they follow the Driver Distraction Guidelines.

After the app passes all the testing stages and is made available on one of the OEMs platforms it will continue to be monitored at each new version uploaded, any issue that might arise will be shared with the app developers to help guarantee a fast and smooth solution. Our commitment is to ensure both OEMs and Developers satisfaction.

Besides Faurecia Aptoide validation procedures, app developers might want to replicate Faurecia Aptoide compatibility tests. Unfortunately given the lack of devices available, it might be difficult to replicate.

Even though this is not a perfect testing scenario, an emulator can help replicate most of the issues identified on Faurecia Aptoide reports.

Android Studio installed (https://developer.android.com/studio/install)

• SDK 29
• SDK 30
• Snapp Automotive

ADB installed on your macOS/Windows/Linux

1. Open your SDK Manager

2. Navigate to “SDK Update Sites“ separator located on the top right.

To integrate Snapp Automotive into Android Studio:

1. Click add button located on bottom left (+)
2. Fill information in the form:
   1. Name: Snapp Automotive
   2. URL: https://downloads.snappautomotive.com/emulator/snapp-automotive-sys-img2-1.xml
3. Click “Ok”
4. Restart Android Studio

Android Studio SDK Platform configuration:

1. Open SDK Manager
2. To install original Android AOSP emulator images and Snapp Automotive images perform follow steps:
   1. Activate “Show package Details“
   2. Activate “Snapp Automotive Intel x86 Atom System“ for Android 11.0 (R)
   3. Activate “Intel x86 Atom_64 System Image“ for Android 11.0 (R)
   4. Click “Ok”
   5. Restart Android Studio (after download and installation finish)

Note: (For Android 10.0 (Q) version, activate “Intel x86 Atom_64 System Image“ on Android 10 item)

Android Virtual Device creation

1. Open SDK Manager
2. Click on “+ Create Virtual Device…”

3. Click on “Import Hardware Profiles“ and import all the necessary profiles.

After importing all necessary hardware profiles, you can create emulator from list of available profiles.
It is possible to search for the names that were set for each hardware profile.

Then,

1. Select hardware profile needed
2. Select Operating System associated to that specific hardware profile consulting table above
3. Finish hardware profile setup

1. Start the emulator.
2. Once the emulator is running and the system has booted, the app can be installed with drag-n-drop.

If the app is installed successfully, you can scroll up to open the app drawer and you’ll find the app there available for testing.

If the app hasn’t been installed, an error message will be displayed. The most probable cause for unsuccessful installation is the lack of support for x86 or incompatible screen density. It’s possible to get a more detailed failure message by using adbs’ install command (https://developer.android.com/studio/command-line/adb).