5 ms·
It's an interesting space, it strikes me immediately as the video version of Minut[1] I got one their first-gen units and was pretty disappointed, but the princ
by blacksmith_tb 7y ago
It's an interesting space, it strikes me immediately as the video version of Minut[1] I got one their first-gen units and was pretty disappointed, but the principle has a lot of potential. What I have really wanted to see from any of these IoT devices is a workflow that goes - tell app you are going to teach it to look for something (or listen), stage an occurrence, confirm the device registered, then stage it again, and expect a notification. So for example, "this is what its sounds like when the clothes dryer is done" - dryer plays a little song - app says 'got it' - dryer plays its little song - notification is delivered saying "your dryer says it's done". I don't think that's beyond the capability of the hw and sw, yet I haven't seen a good implementation yet...
1: https://www.minut.com/product/features/ https://www.minut.com/product/features/
- mrafiee 7y agoThat was actually my vision initially when I started working on the problem. I wanted to allow users to train their cameras for things they care about. But later decided to start with events that we can detect without requiring a lot of input from the users initially...
- blacksmith_tb 7y agoI can see advantages to both, I am sure plenty of users want plug-and-play and would be annoyed by the idea of having to work through manually training. Maybe there can be an "advanced" or "developer" mode... Even just having a feed of events that I could go into and add tags or other info to might work.
- mrafiee 7y agoI like the idea of having a different tier for people who are more tech savvy/patient. We currently allow users to provide feedback on alerts (thumbs up/down) which we use to make the models more accurate over time but training from scratch would require a lot more input from users...