I think I get the idea and it seems reasonable. I'm curious about the use cases. It's basically a remote interface for a spreadsheet or, more abstractly, an array of key:value pairs.
The thing is, that's kind of a constrained interface. It's rare to track only one value at a time. Normally you want to track either sets of values (EX: how many grams protein, fat, carbs) or at least multiple individual values (EX: calories, weight, sleep).
So if there's nothing new about the data store (IE: just a spreadsheet on a server) and there's nothing new about the data (IE: just calories or mood or whatever) then the new part is the interface. Instead of firing up an entire application you do the exact opposite; ping one or two simple codes.
But, like, what do YOU add? Is there no other service that accepts brief messages from any registered phone/email and tracks the values over time? Is that filling a hole? Maybe if there is a hole you could build a platform that performs that function for anything. Individuals could use it for data like weight, businesses could use it for logging business things.
For example, I currently use google docs to track this kind of information. I just open a spreadsheet, plug in my values, and they're automatically saved "to the cloud." Normally I don't even close the sheet; I just leave it open for weeks at a stretch. I doubt it takes fewer clicks to enter a single value into an already-open sheet than to send a text message. However, it does mean if I want to review the data, or rearrange it, or add another column, or backdate something, I've already got the appropriate interface open.
IoQS would work for people who don't have a smartphone...but is there a lot of overlap between people who have an old phone and people who want to track quantified self data?
Sorry for the slow reply, thought I was so far down the list people wouldn't be seeing it.
First - thanks for the feedback and discussion. Really useful insights.
You are correct in that the interface is the 'new' - and also that single codes are a poor way of input. The original reason for SMS was to interupt the user to actually get them to make a measurement. I've since changed that the interupt still comes as a message, but the input/logging is done through a full application. It also means that the application is more accessable for reviewing data, making changes, processing, etc - as you mention is an advantage for simple spreadsheets.
The advantage over a spreadsheet is trading some 'freedom' for easier analytics. I'm wanting to make quantified self more accessible for people without the skills (or maybe interest) to do data processing themselves.
Agreed that having a smartphone is probably a good assumption for the market.
Comments
I think I get the idea and it seems reasonable. I'm curious about the use cases. It's basically a remote interface for a spreadsheet or, more abstractly, an array of key:value pairs.
The thing is, that's kind of a constrained interface. It's rare to track only one value at a time. Normally you want to track either sets of values (EX: how many grams protein, fat, carbs) or at least multiple individual values (EX: calories, weight, sleep).
So if there's nothing new about the data store (IE: just a spreadsheet on a server) and there's nothing new about the data (IE: just calories or mood or whatever) then the new part is the interface. Instead of firing up an entire application you do the exact opposite; ping one or two simple codes.
But, like, what do YOU add? Is there no other service that accepts brief messages from any registered phone/email and tracks the values over time? Is that filling a hole? Maybe if there is a hole you could build a platform that performs that function for anything. Individuals could use it for data like weight, businesses could use it for logging business things.
For example, I currently use google docs to track this kind of information. I just open a spreadsheet, plug in my values, and they're automatically saved "to the cloud." Normally I don't even close the sheet; I just leave it open for weeks at a stretch. I doubt it takes fewer clicks to enter a single value into an already-open sheet than to send a text message. However, it does mean if I want to review the data, or rearrange it, or add another column, or backdate something, I've already got the appropriate interface open.
IoQS would work for people who don't have a smartphone...but is there a lot of overlap between people who have an old phone and people who want to track quantified self data?
Sorry for the slow reply, thought I was so far down the list people wouldn't be seeing it.
First - thanks for the feedback and discussion. Really useful insights.
You are correct in that the interface is the 'new' - and also that single codes are a poor way of input. The original reason for SMS was to interupt the user to actually get them to make a measurement. I've since changed that the interupt still comes as a message, but the input/logging is done through a full application. It also means that the application is more accessable for reviewing data, making changes, processing, etc - as you mention is an advantage for simple spreadsheets.
The advantage over a spreadsheet is trading some 'freedom' for easier analytics. I'm wanting to make quantified self more accessible for people without the skills (or maybe interest) to do data processing themselves.
Agreed that having a smartphone is probably a good assumption for the market.