Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Comment Re: My Favorite part (Score 4, Informative) 32

I understand the concerns. I've tried to disclose appropriately and focused on two things: 1. This is a legitimately new approach. Pretty much everyone I know in the IoT and connected device world is still building a backend infrastructure and coding their own APIs, even for pure analytics apps. 2. A detailed tutorial seemed appropriate so people can see some of the ins and outs of doing this, and to show that now non-experts can do this kind of thing as a weekend project. Obviously, this doesn't eliminate code or servers. But the big win is that I don't have to deal with any of that. It's like saying Rails wasn't a big deal because all the code is on the framework, or AWS isn't a big deal because there are still servers. So look, I'm not a PR flack or something, I've been working on wireless sensors professionally for over a decade and I'm just excited to see the work get a easier, because I've spent a lot of the past 6 years building out and maintaining a scaled sensor backend before. It sucked, and I don't want to do it again if I can avoid it!

Submission + - Ellipto: a DIY fitness tracker and dashboard in 70 lines (medium.com)

InternetOfJim writes: This is one of the most fun weekend projects I've done in a while — a fitness tracker for my elliptical trainer. But the real agenda was to figure out how lazy I could be via web services (Keen IO and Brace IO) and development platforms (Electric Imp). Quite lazy, as it turns out. I wound up with a working device and a nice realtime dashboard with no soldering, no backend to manage, and surprisingly little original code needed beyond the sensing and power conserving parts of the firmware and a little javascript to customize the dashboard.

Slashdot Top Deals

New York... when civilization falls apart, remember, we were way ahead of you. - David Letterman

Working...