Syncing mobile device offline actions with remote servers

A non-transitory computer-readable medium with instructions stored thereon that, when executed by one or more computers, cause the one or more computers to perform operations, the operations comprising:

• while a mobile device is not connected to a network:
• creating a plurality of commits, the plurality of commits including a first commit that describes first changes to be made to first entities;
• determining the first entities from first identifiers;
• and
• transforming the first entities based on a latest unresolved state by applying the first changes described in the first commit;
• in response to the mobile device establishing a network connection, selecting the first commit for acceptance at a server before other commits from the plurality of commits based on the first commit being a next oldest commit without read dependency on the other commits;
• transmitting the first commit to the server for acceptance;
• responsive to receiving a notification that the server successfully applied the first commit, recording an expired version of the first commit;
• and
• responsive to determining that the server failed to apply the first commit, discarding the first commit.

A system comprising:

• a processor;
• and
• a memory coupled to the processor, with instructions stored thereon that, when executed by the processor, cause the processor to perform operations comprising:
• while a mobile device is not connected to a network:
• creating a plurality of commits, the plurality of commits including a first commit that describes first changes to be made to first entities;
• determining the first entities from first identifiers;
• and
• transforming the first entities based on a latest unresolved state by applying the first changes described in the first commit;
• in response to the mobile device establishing a network connection, selecting the first commit for acceptance at a server before other commits from the plurality of commits based on the first commit being a next oldest commit without read dependency on the other commits;
• transmitting the first commit to the server for acceptance;
• responsive to receiving a notification that the server successfully applied the first commit, recording an expired version of the first commit;
• and
• responsive to determining that the server failed to apply the first commit, discarding the first commit.