Jay
I just updated all my devices to your new version as of today (8/20/23) and rebooted all devices.
Logging out/in is no longer loading old documents/MyFirstDocument. I’ll perform logout/logins more over the next several days and keep watch for it, but the newest version seems like it fixed that issue.
Regarding remote changes……yes, this is tough to determine what the best way to keep the user updated…..Here’s my biggest concern, which is common to any thing that relies on synchronization (as opposed to live data manipulation):
1-Device 1, create a new item, and that syncs with the server.
2-Device 2, that Item appears as it syncs.
3-On device 1, you update the item (Call this change A)
4-On device 2, a sync hasn’t happened for some reason or is delayed, but you don’t know that, and you update that item with Change B without seeing Change A.
Now what happens?
At some time later, does Device 2 finally sync, then overwrite Change B with the old Change A?
Or, does Change A, because it happened later, overwrite the Change A, preventing you from ever knowing it happened on Device 2.
Obviously this is a ‘dangerous’ scenario.
Regarding what you said about Legend not using ‘push notifications’ and only ‘syncing when the app comes into the foreground’……it cannot be only syncing when the app comes into the foreground, otherwise while the app is left in the foreground I would not see changes being made from another device. Is the client (Legend App) running some type of loop that says “any changes on the server” every few seconds? What is the ‘event’ that causes a Legend App app to refresh with changes? Perhaps knowing this will help me better understand why some syncs are not happening.
