Grounding to reality is key. There’s often a tendency to trust the map over the terrain. This architecture seems to promote relying on the database always have a perfect representation of state. But consider a scenario where a company restores a 12-hour-old backup, losing hours of state. States that can’t be externally revalidated in such cases are a serious concern.
It's an excellent point. In such a scenario, if you're bound to a rigid workflow system, you will probably have a hard time recreating all the intermediary steps required to get the system back into a consistent state with the external world.
Idempotency is key and the choice of the idempotency key as well ;)
After my Pebble I tried an e-ink "Watchy" from SQFMI (https://watchy.sqfmi.com/) thinking that the battery life would be great but the battery only lasted a few days.
I've been wearing a Bangle 2 (https://www.espruino.com/Bangle.js2) which feels closest to recreating my Pebble. It has super long battery life and feels a lot like my Pebble did, but doesn't have the polish of the pebble UI and animations.
Can't wait to get a new Pebble!
I've written my own watchface and a couple of other apps and made changes to a number of existing apps, it's really simple because you can always test your code changes live on the watch while keeping it on your wrist. There's an IDE that connects to it using Bluetooth and the code can be modified during runtime
Lthere's also a great community of hackers and tinkerers that steadily improve the watch.
It might not have the same polish as the pebble had, but it makes it up in hackability. I can only recommend getting a banglejs2 (battery life is also pretty great, I get about 10 days with regular use)