dsharpdiabetes

Sounds like you are talking about self-diagnosis. I think the "health + mobile" market is really well suited to chronic care / ongoing issues, rather than one off or acute care issues.

If you know you have high blood pressure and your doctor has asked you to track your BP over time, an app to assist you makes a lot of sense.

We built http://dsharpdiabetes.com for similar reasons. It's not realistic to ask the modern smartphone user to carry around a pad of paper all day long for months at a time to track their stats.

I had a similar experience with Erlang. Node has totally taken over the erlang shaped hole in my life ;)

If you want any more case studies, I'd love to hear your thoughts on http://dsharpdiabetes.com

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.

Would love some feedback! Thanks everyone.

From a tech perspective, D Sharp is built using Express, Node-Canvas for rendering Flot graphs, MongoDB via Mongoose and JQuery Mobile.

It's hard to tell what type of app you are building.. but the home page for our mobile web app ( http://dsharpdiabetes.com launching September) is a dashboard that contains all recent activity at a glance along with small sparkline graphs.