Posted on 09-17-2012
I’m immersing myself into the fascinating new world of the Quantified Self (QS). If you are not familiar with what QS is, according to Wikipedia:
Quantified Self is a movement to incorporate technology into data acquisition on aspects of a person's daily life in terms of inputs (e.g. food consumed, quality of surrounding air), states (e.g. mood, arousal, blood oxygen levels), and performance (mental and physical).
As I do with other areas, I start my research by doing a roundup of companies who offer QS products and services--which helps me define the space. Within an hour I easily found 50+ QS device manufacturers, some of which were complete with API driven integration platforms-- way too many to list in a single roundup, but here are a couple of better known companies:
- Fitbit - Fitbit is a health and fitness tracking device
- RunKeeper - Runkeeper is a device for tracking, measuring, and improving your fitness
- Withings - Withings provides connected body scales, blood pressure and baby monitors
- Zeo - Zeo has sleep tracking and management devices and apps
These QS platforms represent a whole new opportunity for the API industry, one that will drive the next generation of healthcare innovation. Self-quantification starts with data collection, followed by visualization, then cross-referencing and the discovery of correlations--all three opportunites for APIs.
Devices can use APIs via cell and wifi to transmit data for collection and storage, while also allowing app developers to use the same APIs to help end-users manage and visualize their data. Then, when appropriate, use the same APIs providing access to other systems and providers who can then cross-reference and discover correlations within individual or groups of users.
It is exciting to think about the possibilities around QS. New ways to gather data about our health and the environment around us in real-time, but also be able to understand this data in the most meaningful way possible, in a way that impacts the most important thing to us--our health!
Devices + APIs + Cloud = Exciting Opportunities!
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