Identify the main differences between Android Open Source Project (AOSP), Android Automotive OS (AAOS), and Google Automotive Services (GAS.)
Understand the minimal requirements (e.g., CDD compliance), benefits, and drawbacks in the adoption of AAOS and GAS.
Comprehend how AAOS and GAS affect companies in different parts of the automotive value chain.
Use the strategic recommendations to adapt and reposition in response to Google’s entry into the automotive industry.
Critical Questions Answered
How AAOS affects the automotive industry?
How GAS affects the automotive industry?
Who are the main winners and losers of Google’s entry into the automotive industry?
How can the most affected companies respond to Google?
Research Highlights
Thorough examination on how AAOS and GAS affect the automotive value chain.
Comprehensive analysis of the benefits and drawbacks of AAOS and GAS.
Strategic recommendations for players affected by Google automotive solutions.
Forecasts of shipments of vehicles by automotive OS, GAS, and digital cockpit controller.
Who Should Read This?
Planners at automotive OEMs, Tier 1, and Tier 2 suppliers looking to comprehend better the impact of AAOS and GAS on the industry.
Strategists in automotive OEMs looking to adopt AAOS or GAS.
Product managers at Tier 1suppliers, semiconductor companies, and software providers developing solutions to optimize Android to the automotive use case or rival AAOs and GAS.
Table of Contents
1. EXECUTIVE SUMMARY
1.1. Main Findings
1.2. Definitions of Key Concepts
2. AAOS
2.1. AAOS Adoption
2.2. AAOS Advantages
2.3. AAOS Disadvantages
2.4. Not Quite There Yet
3. GAS
3.1. GAS Adoption
3.2. GAS Advantages
3.3. GAS Disadvantages
4. INDUSTRY IMPACT AND STRATEGIC RECOMMENDATIONS
4.1. Tier One Suppliers
4.2. Infotainment Middleware and Software Development Suppliers
