Monetization for Automotive AOSP Apps
summary
Foria’s platform ships an OEM-embedded module plus a developer SDK that enable in‑app purchases across 23 car brands and ~200 apps now, with a worldwide rollout to 38 countries on six continents by end of 2024. It supports consumable and non‑consumable purchases today, subscriptions and paid apps soon; developers define products in a portal, get a public key for signature verification, and integrate a Google‑style billing client. Two UI modes exist: delegated variant (OEM controls UX and user data) and self‑delegated UI; testing uses AOSP generic images, upcoming emulator and remote device access, and private SDK/docs by request.
AI-written summary · about
chapters (11)
- 0:00Monetization introduction
- 1:30Last year’s gaps
- 2:36New in-app payment system
- 6:27Products and portal setup
- 7:54SDK integration with Gradle
- 9:47Querying products and purchases
- 11:34Billing flow and UI variants
- 12:59Purchase verification
- 14:00Testing strategies
- 15:46Standardizing payments with COVESA
- 16:06Open automotive app challenge
related talks
19mWhat’s Appning on AAOS?
32mIt's time to develop apps for Android cars
17mAndroid for Cars third party ecosystem
35mBuilding Automotive-Grade Experience
48mAn Introduction to Android Automotive OS
31mHow to build Android apps for cars
23mMy car - my ecosystem? A close view on emerging automotive app stores
16mGet more mileage out of your app with Android for Cars