Cross-device edit handoff for Lightroom and Photoshop workflows

A designer starts a complex composite on their desktop — multiple layers, masks, adjustment layers, the works. They leave the office and want to continue on their iPad or phone. What they find is that the mobile app either can't open the file properly, silently flattens layers, or strips out features that don't exist on mobile. 'All features aren't the same across platforms' and 'the mobile app does not allow for some of the same features offered on the Mac software' — these aren't complaints about missing buttons, they're complaints about broken trust in a workflow.

The gap exists because cross-device state synchronization is genuinely hard, and the incumbent vendors have different engineering teams for desktop and mobile products that don't share a unified layer model. The incentive to fix it is also weak on their side: desktop users with complex workflows are their highest-retention customers, and those users have already accepted staying at their desk. The person who suffers is the one who switches contexts — the designer who travels, the art director who reviews on a tablet, the retoucher who wants to show a client a live edit on a phone.

What's actually missing isn't more features crammed into mobile — it's a smart handoff layer that understands which edits are mobile-safe and queues the rest. Something that knows a healing brush stroke can be previewed but not re-edited on mobile, and surfaces that honestly rather than just breaking. Existing sync tools move the file but not the edit state context.

This recurs every time someone changes devices mid-project. For agencies and studios where multiple people touch the same file on different machines, it happens daily. The cost is time lost to re-doing work, or delivering something unfinished because the mobile app couldn't continue what the desktop started.

What to build

Build a file-state proxy layer that sits between Adobe Creative Cloud sync and mobile apps, parses PSD and XMP metadata on the fly, identifies which layers and adjustments are mobile-renderable, and presents a mobile-safe edit session that queues desktop-only operations as pending rather than silently dropping them.

Where to start

Target retouchers who use iPads specifically for client review sessions — they need to show work in progress on the iPad without returning to desktop, and the use case is narrow enough (view-plus-light-touch-edit) that the proxy layer doesn't need to support every desktop feature to be immediately useful.

The hard part

Parsing PSD internals reliably across every version of Photoshop's file format is notoriously fragile — edge cases in layer effects, smart objects, and third-party plugins will break the proxy layer in ways that are hard to reproduce and harder to debug without a large beta corpus of real-world files.

How it makes money

Per-seat monthly subscription sold to studios, with a solo tier for freelancers at a lower price point — the stickiness comes from the proxy layer becoming the standard handoff step in the team's workflow.