by vkuruthers on 10/4/2017, 2:48:25 PM
Looks pretty good. However, how are you going to differentiate your offering from other more established players out there? (e.g. ThingWorkx, AWS IoT etc.)?
Also usually these types of "no embedded code needed" offerings are OK for demo applications, but what happens when a lot of custom features are needed? E.g. how can one add custom biz. logic to the auto-generated code? If this is not clearly spelled out, then customers are going to be hesitant to get locked into your platform I think.
You can msg. me direct if more info needed, I've worked in the industrial monitoring space for over 15 years now.
by subrat_rout on 10/5/2017, 6:25:30 AM
This looks very promising. As a healthcare professional I am interested to know if it can be used to monitor various healthcare related devices such as medical devices or hospital hardwares. Would love to know more on this.
by dev360 on 10/4/2017, 10:03:30 PM
Isn't it a bit of a stretch to run something like this on rails when you need cheap concurrency? Go, Rust, erlang would come to mind.
We've built/are building a service to help web developers (starting with Rails devs) build end-to-end IoT applications with custom connected devices. The idea is to let web developers do this using their web dev skills. We have a video showing how this is done here: https://www.apiotics.com/videos/1 We're looking for feedback on this, and if anyone wants to try and build an IoT on Rails app with us, please let me know: info - at - apiotics.com.