Ruby fans, meet the Health Graph
This week we are featuring one of the developers building libraries and wrappers on top of the Health Graph (@healthgraphapi), Kenny Ma (@kennyma). Kenny has made his Health Graph Ruby gem available via GitHub for anyone and everyone to use. Click here to give it a try yourself and read on for more on why and how he built it.
Bill Day: Please tell us about yourself and your interest in the Health Graph API.
Kenny Ma: I’m an entrepreneur and software engineer in San Francisco. Prior to my venture in a new health startup, I was a lead engineer at IGN Entertainment where I worked on IGN’s social network for gamers and IGN’s mobile apps. My cofounder and I are working on improving workplace wellness by creating fitness challenges for groups within companies. The Health Graph API provides a great way to track each individual’s progress.
BD: Why did you develop your own Ruby gem for accessing the Health Graph API?
KM: There are quite a few good Ruby gems for the Health Graph API now but there weren’t any when we started.
BD: Which portions of the Health Graph API does your gem support? Do you use all of them in your own application?
KM: The gem currently supports authentication, fitness activities, sleep, weight, profile, and users. We are currently using all of these in our application and will also be adding more API support soon.
BD: Which additional portions of the Health Graph API do you plan to add in the future?
BD: What do you like about the Health Graph? What would you like to see changed?
KM: I love the idea of making this data available so that developers like myself can quickly build health applications on top of it. I think end users will benefit tremendously from the innovations that will come out of this. I don’t see a need to change anything at this time. Keep up the good work.
BD: If you could request any new feature from the Health Graph, what would it be? How would you use it?
KM: None. The Health Graph works very well for us and we haven’t had any problems with it for our application.
BD: Can you share any future plans for your gem? What’s coming next that Health Graph developers may be excited about?
KM: There will definitely be more API support and more test coverage. We will be releasing more updates very soon so make sure you watch the repository if you are using the gem.
BD: Is there anything else we should know about you or your gem?
KM: I’m excited to be able to share the gem with the community and any suggestions for improvment are always welcome.
Cross-posted from the Health Graph blog.