How “Write-Once/Deploy Everywhere” is Becoming a Reality
summary
Claims a path to write-once/deploy-everywhere by standardizing APIs and delivery: a Kovesa SDK (ADL interface + Kotlin/Flow wrapper) plus an ADL-based mock service for emulator testing, a funded reference implementation of unified push (built on UnifiedPush, Apache license) and examples like a lights service POC. More than 80 companies engage, ~30 on calls; code and samples live on GitHub, Maven artifacts planned, development is active with proofs of concept and OEM-compatible reference servers.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:07Automotive app ecosystems
- 2:09Android apps to cars
- 3:13Joint automotive ecosystem
- 4:39OEM approaches failed developers
- 5:45Covesa mission
- 7:30What is Covesa
- 9:17Covesa work streams
- 10:19Push notifications in automotive
- 12:30Push notifications importance
- 13:58Push notification architecture
- 15:48Covesa push notification solution
- 17:38Push notification status
- 17:58Get involved in Covesa
- 19:23Covesa successes
- 21:09Covesa SDK
- 22:56SDK demo light control
- 24:44SDK technical details
- 27:57SDK future plans
- 29:44Contribute to SDK
- 30:48Trust in automotive apps
- 31:52Closing
related talks
37mWrite once, ship multiple times
41mWrite once, ship multiple times
26mContinuous Everything in Mobile
13mLightning Talk: Beyond Good Enough: Why We Want a Kotlin API and SDK
41mApollo-Android: a Journey to Kotlin Multiplatform
41mMobile DevOps
41mIt Just Works
54mXfinity Connected Living: building really, really big android apps