Our goal was to make it work for anyone with diabetes. Most apps target Type 2 diabetics who use diet primarily and really don't work well for insulin users (and even worse for insulin pump users).
You can configure D Sharp to handle oral medications, insulin via pump or pen needle/syringe, etc plus the general logbook functions for blood glucose, blood pressure, weight, diet, etc.
I think the most unique feature is that if you are taking insulin, D Sharp can calculate the insulin dose required to cover the carbs in a meal. It will even track your active insulin and adjust to avoid "stacking" multiple administrations, etc. In this way it provides a lot of the features of an insulin pump and makes them available to someone who is just using a pen needle.
Been on the Subjot BETA for a couple of months and have only been totally impressed. May have a few scaling issues around topic tags but from what I have seen so far no reason why this team couldn't tackle it. Great work!
:) Above and and beyond my friend. Thanks to everyone for all your help, feel free to keep adding to the discussion I'm checking out each and everyone.
There were 4 features that are necessary for the app to do anything:
1. Create a poll
2. Pick a number
3. Process SMS msgs
4. Show results
For this first release, I didn't do anything outside of those 4 features. Soon I'll be adding the ability to open and close the poll by SMS, get results by SMS, and many more things, but for now it is "done".
For cueyoutube - there's no backend! It's just a static page with some JavaScript on it (mostly jQuery but totally hacked together because I can't stand JavaScript :)
I actually copied and pasted most of it from other sources (which I've listed on the page).
The playlists are "saved" by sharing them - each playlist exists only as a URL containing a comma separated list of video IDs.
I've been sharing on Twitter using the #cueyoutube hashtag.
Unfortunately, however, my primary webserver is down due to a drive failure - I'm waiting for the VPS image to copy to a new host now. Bummer :( Should be back up in about an hour with any luck.
I really want to only work on the site in response to user demand, you know? Like I want to keep it as an MVP always. If people like it, then they will use it and make suggestions and I'll react to that.
I'm really enjoying the "throwaway" nature of the playlists themselves (ie. you don't login, you don't give them a name, you don't "save" them, you just create, share and move on with your life), but also the "throwaway" nature of the project - it's good to have something that's useful but that I'm not so heavily invested in (unlike Decal, which I'm like, totally invested in to the point of insanity).
Why code a back-end if you don't need one? You can get away with a lot more than you think you can just with a static page and the browser. With hn-books the book list exists as a static JSON file. I can put my entire site on any kind of web server -- even run it easily offline.
Hey no problem with sharing your own as far as I'm concerened. Looks like a great MVP and I'll be interested to see how your own feedback leads the direction of any future features you have planned.
The front end tool is built in JavaScript with jQuery (but it's safe to use with other JS frameworks). The website and processing side was built in PHP/CodeIgniter, running on a linode VPS.
I think that's one of the most important things about MVP - don't bother automating processes until they are actually taking up your time.
As a consultant I see a lot of people put way too much effort into developing bespoke software to automate or "improve" workflows that don't even really exist in their business yet, only to find out that the real bottlenecks exist in places they never even knew (and that they've wasted a bunch of money building something they'll never really use).
It's like a "real life" analogue of the adage "premature optimisation is the devil".
