​​​​Building a Parking or Charging A​​pp

For application which supports the new Google's androidx.car.app APKs, we offer easy migration to Ignite Store using Ignite host component.

Adding Temp​​late Support To Your App (AndroidAuto androidx.car.app libraries)

For compliance as a driving safe automotive app, you need to display your content through the templates. The good news is that the interfaces are the same as is used in Android Auto projection mode.

Requireme​ntResource​
Build navigatio n, parkin​g and charging apps for Android Auto
https://developer.andro​id.com/training/cars/navigation
Android for Cars App Libraryhttps://developer.android.com/reference/androidx/car/app/package-summary
Design Guidelineshttps://developer.android.com/training/cars/Android%20for%20Cars%20Jetpack%20Library%20design%20guidelines.pdf
Code Sampleshttps://github.com/android/car-samples/tree/main/car_app_library
Build a navigation apphttps://developer.android.com/training/cars/navigation#build-navigation-app
Build a parking or charging apphttps://developer.android.com/training/cars/navigation#build-parking-charging-app
Test android app for carshttps://developer.android.com/training/cars/testing
https://developer.android.com/reference/androidx/car/app/testing/package-summary
Display notificationshttps://developer.android.com/training/cars/notifications

 

Migrate your app to Android Automotive OS and Ignite ​​Store

Once your application supports display through the androidx.car.app template interfaces,  there's a few other requirements to get your app ready for Android Automotive OS with Ignite Store.


RequirementResource​​​Comments​
Removing 3rd party dependencies
https://developer.android.com/training/cars/google-services



​Google and Fir ebase services are restricted from being used in android instances not certified by Google. The article lists the available GMS services which should be removed for the Ignite Store integration.
Minimum API level
https://developer.android.com/training/cars/navigation#set-minsdkversion


​Android Auto requires your app to target Android 6.0 (API level 23) or higher, we recommend using min API level 27 to include the support for FCA R1 platform.
Signing and whitelisting Harman Host
https://developer.android.com/training/cars/media/automotive-os#configure-service

<!-- Android Automotive OS Harman Ignite Core Template Host - Release -->​
<item>55f45fd489cf7cfae76cdcbfedf49a783de5fc534641645d82a9937e0d355190,
    com.harman.ignite.core</item>
<!-- Android Automotive OS Harman Ignite Core Template Host - Debug -->
<item>8a5e57e998757cfc3b42ce1945b54e0cc14d79b525b7d9b6905a691053564e33,
    com.harman.ignite.core</item>
<!-- Android Automotive OS Harman Ignite Template Host - Release -->
<item>55f45fd489cf7cfae76cdcbfedf49a783de5fc534641645d82a9937e0d355190,
    com.harman.ignite.car.app.host</item>
<!-- Android Automotive OS Harman Ignite Template Host - Debug -->
<item>8a5e57e998757cfc3b42ce1945b54e0cc14d79b525b7d9b6905a691053564e33,
    com.harman.ignite.car.app.host</item>
Sign in process (optional)
https://developer.android.com/training/cars/media/automotive-os#settings-sign-in (similar to media)
​At this stage we allow the 3rd party developers to use their own login flow. In later stage, we will consider to implement a templatized login flow.
App settings (optional)
https://developer.android.com/training/cars/media/automotive-os#settings-sign-in (similar to media)
​At this stage we allow the 3rd party developers to use their own settings implementation. In later stage, we will consider to implement a templatized settings view.
Voice 
TBD​

​Voice is a key modality for accessing EV and parking services. Harman, is working with a leading voice provider to launch apps via voice that are registered to the Parking or EV intent filter categories of CarAppService. The user can utter phrases such as “find parking at my destination” or “find a charging point nearby” and the app will receive the intent.
Subscriptions
TBD

​We are currently in discussions to standardize payment integration requirements across OEMs.
In App Payments
TBD

​We are currently in discussions to standardize payment integration requirements across OEMs. ​​