I was curious, and at the same time it provides RK with feedback from the consumer base. So if you own a Bot, thinking about getting one, or in the market for a tester. Select your top 3 choices and leave a comment on any "Must have" features for you to consider, or what would sway you from one tester to another.
Reffbot Features/Changes Poll
- Thread starter Inamo
- Start date
- Tagged users None
Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)
- Joined
- Jul 16, 2009
- Messages
- 5,071
- Reaction score
- 8,108
LoL
- API - I purchased the from the first batch on the promise that the API was already done and that I could pull test results into my 3rd party dashboard.... After months of asking and badgering I was told that the API was not a priority and due low demand and use case, would not likely ever happen.
- Cloud Dependency - the entire product is built around the model that all processing is done in the cloud. The local device is just a slave device that follows instructions and then sends the results to the cloud for interpretation and display. What you ask for will never happen, the device would need to be redesigned from the ground up. So think about this. For every device that they sell, they need to accommodate the bandwidth and storage at their data host FOR AS LONG AS YOU OWN THE DEVICE. Without their hosted services, your device is a useless brick. These costs mount for them over time and scale based on the number of devices out there. This eats into their profit with each passing day. Without perpetually increasing device sales (it is a small market with limited lifetime potential sales) or other RMR they begin to loose an increasing amount of margin over time. Eventually, they will start to lose money hosting these devices. This does not even account for support. The business model is unsustainable and your device is doomed to be a brick unless they start charging a monthly subscription to use your device. This goes for any vendor in any IoT space that does not have a subscription model or other RMR to offset the IoT hosting costs.
- API - I purchased the from the first batch on the promise that the API was already done and that I could pull test results into my 3rd party dashboard.... After months of asking and badgering I was told that the API was not a priority and due low demand and use case, would not likely ever happen.
- Cloud Dependency - the entire product is built around the model that all processing is done in the cloud. The local device is just a slave device that follows instructions and then sends the results to the cloud for interpretation and display. What you ask for will never happen, the device would need to be redesigned from the ground up. So think about this. For every device that they sell, they need to accommodate the bandwidth and storage at their data host FOR AS LONG AS YOU OWN THE DEVICE. Without their hosted services, your device is a useless brick. These costs mount for them over time and scale based on the number of devices out there. This eats into their profit with each passing day. Without perpetually increasing device sales (it is a small market with limited lifetime potential sales) or other RMR they begin to loose an increasing amount of margin over time. Eventually, they will start to lose money hosting these devices. This does not even account for support. The business model is unsustainable and your device is doomed to be a brick unless they start charging a monthly subscription to use your device. This goes for any vendor in any IoT space that does not have a subscription model or other RMR to offset the IoT hosting costs.
