[EvanAnderson]

This thing looks like a lot of fun, however it looks like the device is "tethered" to some kind of back-end service you provide, rather than just being a standalone device on the network. Can you explain how communication with the device works?

[konschubert]

Yes, it needs a backend service. It is just a dumb screen that pools from a backend URL.

The upside of this is that you can easily configure it remotely, because all settings after the initial setup are stored server-side...

... and it makes the whole development flow easier when you can build, iterate and deploy on a server.

[EvanAnderson]

Is there any option to self-host that backend service? I'm not comfortable, from a mental health perspective, with integrating a device into my life routines that could suddenly stop working through loss of a hosted service.

What's the actual communication technology? Is it Wi-Fi? Cellular?

Edit: I see elsewhere you state it's Bluetooth and Wi-Fi. From a Wi-Fi perspective and workplace deployment does it support 802.1x?

[konschubert]

> Is there any option to self-host that backend service?

Not yet, I want to support that in future but it's not possible yet. I have personally decided that I will keep the backend running even if I decide the project isn't worth it for me any more... but of course, I understand the this is no 100% guarantee.

> From a Wi-Fi perspective and workplace deployment does it support 802.1x? Uhhh, I don't know.. how would I check that?

[SanderNL]

You don’t support changing an URL? Why..?