A portrait photographer finishes a session, imports 800 RAW files, culls them in Lightroom, does basic tone corrections, then needs to open a dozen selects in Photoshop for skin retouching and compositing. What sounds like a two-step process is actually six: export from Lightroom, open in Camera Raw, flatten adjustments, retouch in Photoshop, save back, re-import, re-sync metadata. Users describe this as 'clumsy' and note that you need 'Bridge, Camera Raw, and Photoshop to mimic' what should be one fluid path. Adobe has no incentive to collapse this workflow cleanly because selling Photoshop and Lightroom as separate subscriptions — or bundling both in Creative Cloud — is the business model. Fixing the handoff too elegantly would reduce the perceived value of owning both.
What photographers actually lose is time they bill against: a working portrait photographer who does 40 sessions a year and spends 45 minutes per session on this switching overhead is losing roughly 30 hours annually to file shuffling, not editing. The complaints about missing layers in Lightroom and limited per-photo custom editing aren't asking for Lightroom to become Photoshop — they're asking for the retouching step to happen without breaking their organizational context.
A focused desktop app that sits between Lightroom and Photoshop — reading Lightroom catalog metadata natively, preserving develop settings as a live reference panel, and letting the photographer open any select directly into a layered retouching environment without flattening or round-tripping — would eliminate the handoff entirely. The output writes back to the Lightroom-compatible folder structure with a PSD or TIFF that Lightroom re-ingests automatically. No Bridge, no re-import dialog, no lost star ratings.
What to build
Build a macOS desktop app that reads Lightroom catalog files directly, displays develop settings and metadata as a reference sidebar, and opens RAW selects into a layered retouching canvas — then writes finished PSDs back into the catalog's folder structure with sidecar metadata intact, so Lightroom re-ingests them without a manual import step.
Where to start
Wedding photographers are the ideal first customer: they have the highest per-session file volume, the most predictable retouching workflow (skin, exposure, color grading), and they talk to each other constantly in tight online communities — a referral loop that's fast to activate if the core handoff works.
The hard part
Lightroom's catalog format (.lrcat) is an undocumented SQLite schema that Adobe changes without notice, meaning catalog-reading logic needs to be reverse-engineered and maintained version by version — one Lightroom update can break the integration and immediately generate support tickets.
How it makes money
One-time purchase around $99, with a paid upgrade for each major version — the same model photographers already trust from other desktop tools in their stack.
See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Photo Editing.
More ideas in Photo Editing