> We should build networked applications that cache content and make network fetches asynchronously to remote APIs so that humans aren’t waiting for data to com

> We should build networked applications that cache content and make network fetches asynchronously to remote APIs so that humans aren’t waiting for data to come back over the wire while they’re working. I built something like that a year ago and thought that I wouldn't have to bother the user with the sync state. I was wrong. Due to the nature of the mobile connections it happens quite often that for short periods multiple devices aren't synced. Yes I could certainly improve the logic to let this happen less often but in the end the user requires some indication about the sync state (e.g. last successful sync). So when you build something similar don't hide everything from the user just give him as much freedom as possible to allow him to keep working while the sync happens in the background.