3 ms·
Unless the use cases are very simple or there's a special reason not to for most embedded devices I think I'd rather communicate largely with an app (e.g. by bl
by pydry 5y ago
Unless the use cases are very simple or there's a special reason not to for most embedded devices I think I'd rather communicate largely with an app (e.g. by bluetooth).
I'm thinking for washing machines, dishwashers, aircon, things like that.
Unless simple, embedded UIs are usually bad and usually make complex interactions (e.g. setting timers) especially horrible. Whereas android/apple/the web have been optimized for UX.
It's oddly not as common as I'd have expected, though.
- malfist 5y agoPersonally I'd rather avoid apps. I already have like seven dozen apps from all the smarthome devices my partner buys. It clutters up my phone, I have no idea how much they're spying on me, and it's a pain to pull out my phone to change some hardware right in front of me. Let me configure it physically, or do it over a web browser, but preferably the later. Especially for when the servers are shutdown because the product is no longer profitable (looking at you sonos) Another thing, has anyone seen a well designed software made by a hardware company? They seem very rare. Just look at any printers.
- pydry 5y agoThis is true. If embedded device makers do make an app they seemingly can't resist doing it without vacuuming up your personal data / device telemetry or proxying device connections via their servers.
- HeyLaughingBoy 5y agoIt's not even that. I'm one of those people who never has their phone nearby so it would be a chore to have to get my phone out of the bedroom every time I wanted to use an appliance.
- CamperBob2 5y agoIt's oddly not as common as I'd have expected, though. If you put Apple on your hardware product's critical path, they may capriciously change their app store rules at some point to invalidate your whole product or business model. If you put Google on your hardware product's critical path, they may just get bored of supporting whatever Google product(s) you are using, and kill your whole product or business model without even realizing they're doing it. These companies should be treated as forces to be reckoned with, not (just) as friends to partner with.
- djmips 5y agoNot to mention they may ask for money, if not now then perhaps later.
- jacknews 5y agoWe definitely don't want an app, but a standard API of some kind. 3rd parties can then write apps, or web apps, etc, spawning a 3rd party market to create great UIs. Manufacturers can focus on what they should be good at, manufacturing ergonomic, efficient, reliable, long-lasting and repairable devices and appliances.