This demo's PC-side scripts were run on macOS.  It uses
app-specific storage for both zips and content on the phone.
This example changes only pathnames in config files.

Note that zips and content need not both use app-specific
storage the way this demo does.  In practice, you might use
app-specific for zipfiles to optimize sync speed, and shared 
storage for content to boost accessibility and longevity.

NONPORTABLE FILENAMES 
  Don't need to be fixed here, because they are allowed in 
  Android app-specific storage when unzipped, and are silently
  munged to work on the exFAT proxy by macOS.

SYMLINKS 
  Are forged on the exFAT proxy by macOS, so they don't 
  generate perpetual diffs the way they do on Linux (though 
  they also won't register as symlinks elsewhere).  On phones,
  symlinks in the initial-copy unzip leave stub files in Android
  app-specific storage, which are largely harmless unless
  backsynced to PCs (and avoid perpetual failures for Linux).

For more info on filenames and symlinks, see the main doc's:
  _README.html#Nonportable Filenames
  _README.html#storagemetadata