Without a first-party backend service, the smart screens would need to store configuration data (e.g. which app is currently active, where to reach the render e

Without a first-party backend service, the smart screens would need to store configuration data (e.g. which app is currently active, where to reach the render endpoint) directly on the device. Every time you wanted to change that data, for example to change which app is active on the device, you would need to pair to it with bluetooth or some other means. Now that I think about it, I actually like the idea of offering this as a fallback option. Hmm... but I don't want to over-promise anything. But as long as the backend is available, handling configuration changes on the backend is simply a much better user experience. This is why I chose this option as the initial way to go. I hope this makes some sense, I am happy to answer further questions.