As OEMs adopt Android Open Source Operating System (AOSP) for Automotive, the ecosystem for third party applications is critical to provide end-consumers with access to their favorite digital content. For ecosystems to thrive, platform, interface and tool fragmentation must be avoided such that apps can be written once and deployed and run without modification on IVI systems developed by different OEMs. AOSP provides a solid base to start, but there are gaps. It does not specify or provide key services, such as app store, voice assistant, or maps. An Expert Group is being proposed to identify and address these gaps through standardization such that an automotive app ecosystem may thrive.