I just ran through the Losant Walkthrough and I have some first impressions and improvements.
- In adding a device, we set device attributes. These should autofill in other parts of the process that can use this data. I also wish there were a better way to enter these than typing them all out. Perhaps a way to send a JSON request to the service we want and then chose from the response what we want to turn into a attribute.
- What’s the point of a device ID? Can’t the website just remember the devices and refer to them by name?
- I love the idea of the flow chart-esqe workflow designer. The only issue I had with it is that the Debug & Error Stream is only shown when you click outside of any nodes. It took me too long to find this. Perhaps a console-style window along the bottom would be better? There’s actually a pretty good log function in the device window too. Maybe these can be combined?
- I also ran into the issue with Twitter rejecting tweets and the Debug node didn’t give me any information when hooked up to the Tweet node, although there was information in the Debug & Error Stream.
- It took me forever to understand why we want to add the “optional” response path, but it actually seems very important for viewing received data in other parts of the application. I feel that section should be changed to refer to that as a variable, or something, so that the user can access that data in other places.
- The Virtual Device State fields are where I believe there should be some sort of autofill (as described in #1) that automatically relates device attributes to device states. Also we should be able to pick the device by name here and not by ID.
- Again, creating a dashboard should be as easy as selecting sources that are already there. No need to type in ID’s and remember specific variables.
- Once the data is there, the dashboard is fantastic for re-sizing and rearranging data. Amazing for a web app.
Not being to sound like a jerk with all of the complaints. I think it’s just useful to find out how a new user feels on the first time. Also, no reason to change things just because I don’t like them. Just voicing my opinion.
Looking forward to seeing how this service evolves!