Posted on 03-06-2014
I had the pleasure of doing Carvoyant Connected Car Cast today with Bret Tobey and Matt Galvin, hosted by the infamous Mike Maney (@the_spinmd) today. The session was nothing formal, just a conversation about cars and APIs.
The conversation triggered several potential stories for me, but after the talk I couldn’t stop thinking about how they talked about the Carvoyant API being a research & development (R&D) lab, and conversation starter about whats next for the automobile industry.
Auto companies are on board with APIs playing a significant role in the future of the auto industry, but their window for change is in not just years, but multiple years. Tech giants like Google and Apple are turning their attention to the opportunities surrounding the connected car, but their runway is pretty lengthy as well—highly dependent on the car manufacturers.
Carvoyant has options for connecting cars right now, providing a device you can plug in cars that are 1996 and newer, and an API for developers to build apps that integrate with user’s vehicles. Carvoyant isn’t about delivering content to your vehicle like Apple and Google are working on, it is about getting data from your vehicle, about its location, engine, tires, fuel and other vehicle data points and automobile centric events.
Like other Internet connected devices in our lives its going to take some experimentation before we find the right formula that works for people and their beloved cars, the sort of R&D that APIs are well suited for. I think vehicles play a pretty clear role in our lives, we understand the value they deliver, but I think its going to take some time to understand how to safely, and sensibly connect our cars to the Internet, and we need to jumpstart this conversation—not let it just be between car manufacturers and tech giants, but include auto enthusiasts, mechanics, developers and most importantly car owners.
As with other industries API are moving into, I’m extremely excited about the opportunities, but also very concerned with the potential for exploitation of end-users. As we move towards a world of connected cars, we need to have some serious conversations appropriate uses of technology, access to data, privacy, security and numerous other challenges we face with the API connected automobile.
I’m excited that Carvoyant is available to connect cars now, and not having waiting for each year of new vehicles from manufacturers, allowing us to jumpstart not just the research & development, but also the conversation about what a connected car in our world actually means.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Swagger Visualization Layer Using D3.js
- Establishing Common Dictionaries That Industries Can Use In Their API Design
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API