The Programmable Car - Apps, APIs, Data and Ecosystems
Download as PPTX, PDF16 likes21,946 views
The document discusses the rising significance of software in vehicles, noting that modern cars can contain over 100 million lines of code due to advanced, cloud-connected infotainment systems. It outlines three scenarios for programmable cars involving smartphone applications and emphasizes the need for safety and security in automotive software development. Additionally, it highlights the challenges and opportunities in creating a developer-friendly ecosystem within the automotive industry.
![public void onOnButtonPress(OnButtonPress notification) {
if(notification.getButtonName() == OK) {
_audioDetails.startAudioPlayer();
}
}
Android
Ford AppLink SDK Examples
- (void) onOnButtonPress:(FMOnButtonPress*) notification {
if (notification.buttonName == [FMButtonName OK]) {
[audioController startMusic];
}
}
iOS](https://image.slidesharecdn.com/theprogrammablecar-appsapisdataandecosystems-130521122233-phpapp02/85/The-Programmable-Car-Apps-APIs-Data-and-Ecosystems-29-320.jpg)
The Programmable Car - Apps, APIs, Data and Ecosystems
- 1. The Programmable Car Brian Mulloy @landlessness Apigee @apigee Apps, APIs, Data and Ecosystems
- 13. The amount of software in the average vehicle has grown exponentially — a typical new car has about 100 million lines of code — with the advent of sophisticated, cloud-connected infotainment systems. Software has become a competitive advantage as vital to General Motors or Toyota as it is to Apple or Google. “ Doug Newcomb “The Next Big OS War Is in Your Dashboard” Wired, December 3rd, 2012
- 15. For developers who have been making apps for smartphones…
- 17. …and open source hardware…
- 18. http://scoolbell.wordpress.com/2012/10/30/how-arduino-is-open-sourcing-imagination/
- 19. …the car is a dream platform.
- 21. Three programmable car scenarios:
- 22. 1. Smartphone App within the Car 2. Smartphone App without the Car 3. Head Unit App
- 23. Smartphone App within the Car
- 24. Example: using the car’s display and controls to play music on the developer’s smartphone app.
- 26. Ford AppLink provides Android and iOS SDKs for developers.
- 27. For Android, the developer adds Ford’s .jar files to the app project.
- 28. For iOS, the developer imports Ford’s XCode project files and links them to the app’s project.
- 29. public void onOnButtonPress(OnButtonPress notification) { if(notification.getButtonName() == OK) { _audioDetails.startAudioPlayer(); } } Android Ford AppLink SDK Examples - (void) onOnButtonPress:(FMOnButtonPress*) notification { if (notification.buttonName == [FMButtonName OK]) { [audioController startMusic]; } } iOS
- 30. Smartphone App without the Car
- 31. Example: start the car parked at the airport parking lot while the user is at baggage claim.
- 32. Car Company Data Center Smartphone App WebWeb Car HTTP API Proprietary SMS MQTT
- 33. GM provides a simple web API for developers.
- 34. The developer registers at GM’s developer portal and requests an access token.
- 35. HTTP & OAuth 2.0 GM Remote API POST /api/v1/account/vehicles/{vin}/commands/start Authorization: Bearer 490699ea3c903790c600f82042f27947
- 36. Head Unit App
- 37. Head Unit App App Developer’s Mobile Backend Web HTTP API
- 38. GM provides an HTML5 and JavaScript internet apps framework and emulator for developers.
- 39. The developer submits a developer agreement, downloads the SDK, builds the app and submits it to the GM AppShop.
- 40. gm.system.getSpeed(); gm.info.getRadioInfo(success, failure); gm.comm.webServiceRequest(success, failure, options); JavaScript GM In-Vehicle JavaScript API
- 41. The progress is tangible.
- 42. What are the risks?
- 44. Traditional software platforms must account for two key vectors:
- 45. Features
- 46. Security
- 47. Three-legged auth helped us a bunch.
- 48. The car as platform must add an important third vector:
- 49. Physical safety
- 51. There’s another inherent issue.
- 52. Car: $30,303 Washing Machine: $1,012 Smartphone: $200
- 53. Car: 10 years Washing machine: 10 years Smartphone: 21 months
- 54. There is a frequency mismatch between consumer electronics and automobiles.
- 55. And then there’s culture.
- 62. APIs make cars a software platform, not just a hardware platform. That is where the high velocity innovation is going to happen. Running a platform is like running a small town. A lot of it is about governance and policies -- very little is about the tech. The most valuable platforms provide a large audience + user acquisition or unique data. Cars have the potential to offer both. Ryan Sarver @rsarver Director, Twi er API & Pla orm Cranbrook ’98 “ Ryan Sarver Product/BD, Platform Team Twitter
- 63. Running a developer platform is difficult.
- 64. It’s about winning the hearts and minds of app developers.
- 66. Minds: Vehicles Sold in Q1 2013 Tesla GM 4,900 2,360,000
- 67. Hearts: ZOMG Tesla has an API!
- 69. A developer reverse-engineered the API used by Tesla’s apps.
- 70. Which is exactly what happens when you when the heart of a developer.
- 71. What is Apigee’s role in the programmable world?
- 72. OEM Data Center Web Smartphone within the Car Smartphone without the CarHead Unit Developer Channel App Developer MAx MAx MAx API Gateway App ServicesAPI Analytics Bluetooth
- 75. The car is a compelling component of the internet of things.
- 76. Questions?
- 77. THANK YOU Subscribe to API webinars at: youtube.com/apigee
- 78. THANK YOU Questions and ideas to: groups.google.com/group/api-craft
- 79. THANK YOU Contact me at: Brian Mulloy @landlessness brian@apigee.com @apigee
Editor's Notes
- #2: Creative Commons Attribution-Share Alike 3.0 United States License
- #10: Designed with virtual reality software
- #11: Designed with virtual reality software
- #12: Manufactured by Roboticists
- #13: electric powertrains
- #14: Paraphrase auto engineer who said, “we stopped driving our cars years ago. Today we make gestures with our hands and feet and the software determines the appropriate action”
- #16: Anecdote: conversation between a military roboticist and a vehicle manufacturer: blown away by lower costs and higher quality
- #18: Anecdote: conversation between a military roboticist and a vehicle manufacturer: blown away by lower costs and higher quality
- #20: Anecdote: conversation between a military roboticist and a vehicle manufacturer: blown away by lower costs and higher quality
- #22: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #23: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #24: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #25: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #27: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #28: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #29: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #30: Handles as part of query string parameters in the header
- #31: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #32: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #34: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #35: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #36: Handles as part of query string parameters in the header
- #37: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #39: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #40: We follow the “pragmatic REST” philosophy .Currently most of our internal services are all SOAP based and we sometimes do spend cycles RESTifying them and externalize.There is a push to ensure that internal services are designed with REST principles so they can be exposed externally with minimal effort, unlocking their value faster.
- #41: Handles as part of query string parameters in the header
- #42: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #43: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #44: The CNN moment
- #45: If metadata is requested, we can return it as part of the response header or modify the response body as needed by the client.
- #46: If metadata is requested, we can return it as part of the response header or modify the response body as needed by the client.
- #47: If metadata is requested, we can return it as part of the response header or modify the response body as needed by the client.
- #48: If metadata is requested, we can return it as part of the response header or modify the response body as needed by the client.
- #49: If metadata is requested, we can return it as part of the response header or modify the response body as needed by the client.
- #50: If metadata is requested, we can return it as part of the response header or modify the response body as needed by the client.
- #52: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #53: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #54: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #55: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #56: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #57: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #58: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #59: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #60: harman / kardon - http://www2.mercedes-benz.co.uk/content/unitedkingdom/mpc/mpc_unitedkingdom_website/en/home_mpc/passengercars/home/new_cars/models/s-class/_w221/facts_/overview/telematics.0006.htmlbose - http://blog.donwheaton.com/2013/04/15/2013-buick-encore-premium-awd-review/bang & olufsen - http://www.seriouswheels.com/2009/a/2009-Audi-Q7-Bang-Olufsen-4-1280x960.htm
- #61: Opportunity: Monetize Dell services, solutions, capabilities through API Tool for Dell to open our portfolio of solutions to our customersBuild on success and expand API services to generate revenueEnable high ROI programsStarted as an innovation center incubation project to explore the best possible options to connect partners and customers with valuable Dell internal services.
- #63: The ones that have generated the most discussion are those around defining service levels and throttling limits. We have found that it is an ever changing definition, getting refined with over time with new API and associated clients. We need to adapt the service levels to the needs of our clients and the constraints of our internal services, which has been a challenging, but a nice intellectual exercise.The other is around versioning and how do we manage communication around internal service version changes and how it affects clients usign our API’s