Posted on 06-16-2014
After speaking at API Craft SF on Thursday, I kept the API talk going with two days of API car talk at API Days San Francisco. While there is a lot of focus specifically on the car itself, there was also a lot of talk beyond the auto at API Days San Francisco, which was dubbed "Disrupting the Car Industry and Driver Experience with APIs".
In 2014, you just can’t talk about disrupting the car industry, without including public transportation. With smart phones in our pockets, we need to get "smarter" about when and how we drive our cars, but also when should not drive our cars. Public transportation has to be part of the conversation when developers are looking to “disrupt the car industry”.
I was pleased to also hear bicycles mentioned during several of the talks, and that developers should think about bicycle culture when developing apps. Many automobile owners are also bicyclists, and merging car and bike culture, expanding the opportunities to ride to work, large public events, or just for recreation, should be part of the consideration when developers are looking to “disrupt the car industry”.
Self-Driving Car Skepticism
It is easy to be captivated by the work coming out of Google around the self-driving car, but I was also so surprised to hear several folks express skepticism around whether or not the self-driving car will live up to the hype, and whether or not we even need the self-driving car at all—with investment around public transportation being a preferred alternative.
When preparing for API Days, I expected the usual API crowd, educating people generally on the API opportunity, with a handful of high level car talks from people who have worked for the major car companies, or those working for aftermarket startups. This existed, but I was pleasantly surprised to see so much "out of the box" conversation as well.
Seeing that the conversation wasn't just focused on automobiles, but also the wider world of transportation at API Days San Francisco, made me very hopeful for the future of APIs, and how they will be applied within the automobile industry.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- The New StrongLoop API Server Provides A Look At Future Of API Deployment
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs
- Applying APIs.json To API Discovery In The Federal Government
- The Power In API Discovery For APIs.json Will Be In The API URL Type
- Fixing The Machine Readability in API Commons
- Evolving How We Approach The API Lifecycle With APIMatic
- APIs Can Open Up Your Company To Outside Ideas
- APIs Are Often Just A Facade That Is Covering Up The Legacy View Of World
- A Mobile Developer Toolkit With The University Of Michigan APIs