The thing I hate about this trend is that we seem to love to forego a vital part of interfaces in the process: visibility. I don't know why designers seem to hate buttons, but it's really annoying.
Can you write C? Do with it what you like. I'll make a javascript framework that runs on a smartphone too. (Nordic Bluetooth LE chip, microphone, speaker, 12 RGB LEDs, gyro/accelerometer, battery that should last weeks). Internet connected walkie-talkie, translator, study languages (like this: https://forum.language-learners.org/viewtopic.php?t=8699).
I'll make more devices soon, and will sell them for $25. Send me an email, and I'll message when they are ready (mail in profile).
Love it! Sadly, my self-insight has reached the level where I know I would buy it then never use it after tinkering for a few hours, so I'm afraid I have to pass on ordering one.. but I really like the concept!
It has to be more than that. A touch sensor might be cheaper than a button, but even Software UI distances itself from the button visual of the 90s and 00s, instead opting for icons with no discernible background or button association. Software UI design is very much imitating how a physical touch sensor interface looks. It seems to be the current trend, chasing a "clean" design above all else.
I miss switches. Big metal toggle switches with labeled positions. These tiny hall effect buttons that barely give any feedback are the worst of both worlds. They have no visible status. The tactile element isn't much better than a touchscreen, and they break. Toggles!
Buttons aren't visible if they're on the side of your head. I have headphones with about 5 buttons. I can often successfully use the volume and power ones if I locate them correctly, but there are another two next to those that I sometimes end up pressing instead.
I should have been more clear: those buttons are still "visible" in that they have a haptic interface. I have a headphone with "tap to play/pause, swipe to change songs or volume" - it's impossible to know without reading the manual or triggering one of these actions by accident. Which incidentally also happens a lot.
That's bad interface design IMO. I guess the headphones look "cleaner" but it's really annoying in practice and not worth it.
Those are crappy buttons. Good buttons are ones that you don't need your eyes. Take an xbox controller. Every button on the device is labelled and there is a schematic detailing every aspect of their function in every game, however you never look down at the controller because you can discern every single button on the controller by feel alone.
EDIT: where "visibility" also includes haptic feedback and all of that other good stuff. See http://worrydream.com/ABriefRantOnTheFutureOfInteractionDesi...