Preference and settings backup for Adobe Creative Cloud apps

The moment someone feels this problem most acutely: they've spent months building a precise Photoshop workspace — custom keyboard shortcuts, tool presets, workspace layouts, color settings — and a major update silently wipes it. They file it under 'annoying' until the third time it happens mid-deadline, at which point they'd pay immediately for something that simply saved and restored their setup.

This gap is structural. Adobe's own Creative Cloud sync for preferences is notoriously unreliable and has been for years — users in these complaints describe preferences being 'wiped with each successive upgrade,' which is not a new bug but a recurring architectural weakness in how the apps handle version migrations. Adobe's incentive is to ship new features, not to fix invisible infrastructure that only hurts users when something breaks. The sync mechanism also doesn't version-control preferences, meaning if a bad update wipes your settings, there's no restore point even if sync was on.

What's missing is versioned, timestamped snapshots of the full preference state — not just workspace layouts, but color profiles, export presets, plugin configurations, keyboard shortcuts, and scratch disk settings — stored outside the app's update path so they survive upgrades. The complaints specifically name preferences being wiped and the inability to easily identify what changed after an update. Right now, the manual workaround is to copy preference folders before every update, which requires knowing where they live on each OS, varies by app version, and is error-prone enough that most users don't bother until they've already been burned.

This is a business because the need recurs every update cycle and because the restoration workflow — figuring out which files to copy back, in what order, without breaking the new version — is genuinely complex enough that automation saves real time. A studio with five retouchers could lose a combined day of work to a single bad update cycle.

What to build

Build a Mac/Windows desktop app that automatically snapshots the full preference state of Photoshop and Lightroom Classic before each update, stores versioned backups locally and optionally to a user-specified cloud location, and provides a one-click restore that correctly maps old preference files to the paths expected by the new app version.

Where to start

Sell to e-commerce photo studios first — they run multiple identical Lightroom Classic workstations with standardized export presets and catalog structures, so a single sale covers 5-15 seats and the value is immediately obvious because one broken update affects the whole team on the same day.

The hard part

Adobe changes preference file locations and formats across major versions, so the mapping logic between 'what you backed up' and 'where to restore it' in the new version requires ongoing maintenance for every major app release — it's not a build-once problem, it's a build-and-maintain-forever problem that requires someone tracking Adobe's internal file structure changes.

How it makes money

Per-seat annual subscription at $30/year per machine, with a studio tier at $20/seat for five or more seats; free 30-day trial triggered at first detected update event.