>IoT device doesn't have a web interface or a standard

>this kills the embedded engineer

>you are expected to whip up your phone to take a piss
I hate this stupid fucking timeline.

God as soon as my Niggerberry falls apart I'm getting a dumbphone.

I would just piss on the floor if I ever saw this shit.

Smartphones are comfy, but the whole "you need an app for this" is retarded

>>61405870 Esp8266 is too slow for a proper web GUI. No SSL, no ajax, no images, no usage statistics.
B-but muh bare HTML is good enough. No it doest. You won't sell anything that way.
>standard API
Same thing as games on Linux. 1% of sales 50% of support tickets.

>>61405870
I think this would be cooler it was like an arcade machine that just displayed per urinal (or maybe per bathroom) highscores.

>tfw your bladder bursts because you held your piss in for 3 days in order to get the new high score

File: IMG_20170716_192052.jpg (33KB, 699x325px) Image search: [Google]

33KB, 699x325px

>

>>61406417
I agree.

Also you should enter your initial by repeatedly pressing the flush button.

>>61407019
That would be hilarious and fantastic.

>No SSL
This is not a problem on LAN, and most devices webUI (routers and shit) doesn't have it anyway, or with a broken cert.
>no ajax
JavaScript is client side, and just do HTTP requests to an API when needed, it's not heavier that any page loading.
>no images
Optional, you can make good looking pages with fancy CSS
>no usage statistics
lol
>B-but muh bare HTML is good enough. No it doest.
Yes it is. JavaScript and CSS can make a nice WebUI in few ko if the dev isn't retarded.
>You won't sell anything that way.
You can still make a dumb app and market the device for the app, but a web UI should be present in case of phone failure, and the device should be usable without a phone.