zlacker

>>headal+(OP)
We're building a neuromodulation sleep headband, and we've always had the aim of getting to the point where the user puts it on, it does it's thing (slow-wave enhancement) the person takes it off in the morning and goes about their day.

I don't even want to put IO into the device at all. Not only because it increases cost and size, but because I don't what the user having to interact. We have to find better ways to fit the device in your life, so you don't even think about it.

>>pedalp+Q61
I was working on a similar IO problem with wearables a while ago (though by the sounds of things, far less seriously than you are), and I had the idea that maybe that band/strap could function as an on-off switch, so when you undo the band (which you do when taking it off), it turns the device off, and vice versa. Could be something you could try too

>>bodge5+ad1
Polar H10 basically works like that. It's great until you are suddenly unable to connect to it via bluetooth, and have to blindly debug the reason. Is the device even on? Battery low? Broken? App issues? Who the fuck knows.

>>_Alger+us2
Yeah, you hit on a very important point. There are ways to handle this via lighting on the device (as far as, connected, battery, etc), and I think the app being clear about the state, beyond just "connected/not connected" is important.

We've had very few issues with BLE, but it is one of the things I'm most worried about as it absolutely kills the experience.