Persistent shortcut config sync for Photoshop across machines and updates

Photographers and retouchers who work across multiple machines — a desktop in studio, a laptop on location — hit a specific version of this problem that is worse than the single-machine case. Not only do updates change their shortcuts, but Creative Cloud's built-in settings sync doesn't reliably preserve custom keyboard shortcuts across machines or update events. Users end up with different shortcut configurations on different machines without knowing it, and they only discover the mismatch mid-job when a key does the wrong thing.

Adobe offers a 'sync settings' feature, but it has a documented, long-standing history of silently failing or overwriting custom configs with cloud defaults rather than preserving local customizations. Adobe has structural reasons to deprioritize fixing this: sync edge cases are expensive to debug, and the failure mode is quiet (users blame themselves or assume they forgot to remap something) rather than loud and attributable. The buyer — a working photographer paying for Creative Cloud — just accepts it as one of those Adobe things.

What's missing is a lightweight background process that treats your Photoshop shortcut file as a versioned, synced artifact — like a dotfile in a git repo — separate from Adobe's own sync. It watches the file, commits changes with timestamps, and pushes them to a private store. When you open Photoshop on a second machine, it checks whether that machine's shortcut config matches your latest snapshot and prompts you to sync before you start working. It can also detect post-update drift — when an Adobe update silently overwrites your custom config with new defaults — and restore your version automatically.

This is a business rather than a feature because the multi-machine workflow recurs constantly for the audience it targets, the cost of getting it wrong is tangible (a retoucher on a client shoot with wrong shortcuts), and Adobe has explicitly not solved it despite years of user complaints — not because it's technically impossible but because their sync architecture treats preferences as a lower priority than document files.

What to build

Build a background menu-bar app for macOS that version-controls the Photoshop keyboard shortcut config file using a private encrypted store, syncs it across up to five machines on a user's account, detects when an Adobe update has overwritten the config, and restores the last user-confirmed version automatically with a notification.

Where to start

Distribute exclusively through photographer gear and workflow newsletters where the multi-machine use case is assumed and common — the wedge is that your first customers already have the exact two-machine setup the product is designed for, so the value is immediately obvious without explanation.

The hard part

The hardest early trade-off is deciding whether to build your own sync infrastructure or piggyback on something like iCloud Drive or Dropbox — building your own is more reliable and defensible but dramatically increases the scope and cost of the first version, while piggybacking creates dependency and trust issues with users storing preference files in third-party clouds.

How it makes money

Subscription at $5/month or $45/year per individual, with a studio plan at $12/month covering up to 8 seats sharing a team shortcut config baseline.