Since Kloudless’ API has been available, it’s clear that our developers are awesome! Dev Logs are the stories of developers who have created some sweet hacks using Kloudless and other technologies. Know of a hack or smart dev who should be featured in Dev Logs? Email email@example.com for next steps!
Quincy Larson and Noah Kaplan are featured in today’s Dev Logs —
check it out!
This week, Dev Logs catches up with not one, but two cool developers — Quincy Larson and Noah Kaplan. They created a pretty sweet mashup using Kloudless, Twitter and Readability. Check out this a little demo video of Twitter Explorer, which gets readable articles delivered straight to your cloud:
[vimeo 96378174 w=500 h=281]
Quincy Larson, co-founder and CEO of Course Forward, is getting ready to go into open beta. Course Forward asks people one question: What job do you want to do next? It then parses their LinkedIn profile to recommend a personalized sequence of online courses to help them get the skills they need to get that kind of job.
Noah Kaplan is a software engineer, working in full stack web development as his main gig, with side projects in hardware such as an interactive animation with sensors and a wearable device prototype. You can learn more about Noah from noahkap.com, GitHub, or LinkedIn profile.
When asked why they created this hack, Noah shared:
Quincy had the idea to take the articles relating to a hashtag and take them offline to give you relevant reading for when you’re riding a subway or airplane. The Kloudless API offered a perfect way to use synced cloud storage systems.
Because Kloudless integration was easy and of obvious merit. I plan on using it in the future, and this was a nice opportunity to get familiar with it.
They each shared challenges they faced and worked through, with regard to the Kloudless API. Quincy hit a small roadblock when he tried to successfully post through the Ruby SDK. Ultimately, he just resorted to using a curl command, which worked. Noah’s perspective on the most challenging part was just getting configured with the API. For such a quick hackathon, he thought they took too much time getting their curl post statement to work, but that was due to a missing curly bracket in their metadata JSON. Overall, the Kloudless API was simple to use and had great documentation, and it was nice not having to worry at all about which cloud storage system users wanted to send their files to.
Both were free with their feedback, with Quincy pointing out that an example ruby app that developers could quickly plug into would be helpful for a quick start while Noah would like to see parts of the documentation explanations more explicit, with examples given. For example, they thought “@filename” was using an instance variable (as they were working in Ruby), when it really meant that they had to put an @ sign before the path to the file. But overall, Noah thought it a solid idea and very helpful for using cloud storage systems.
It was very easy to use and had some of the best documentation for an API I’ve seen. – Noah Kaplan
Thanks for sharing your story, Quincy and Noah! Come back next week for more Dev Logs, or sign up for your own Kloudless developer account. Swap tips and ideas in the comments below or ping us at firstname.lastname@example.org!