WorkbenchPREVIEW

PHOTO HANDOFF · IMPLEMENTATION PREVIEW

A photo now.
Ready on your Mac later.

Take a picture of the real reception, office or place you’re presenting. Send that picture from Workbench. When you next open the Mac app, it checks for your selected photos.

Implementation status

A real photo milestone is now observed: the installed Mac Preview downloaded an existing iPhone photo after a transient timeout and retry. This does not establish every deferred-delivery or account-recovery path. The notarized Mac Preview 4 includes the provisioned photo and scene capabilities. The new Mac scene Preview is installed with that photo and existing scenes intact. Editable scene sync has its own evidence and acceptance checks; its paired runtime remains unverified. Default development and Simulator builds keep cloud access disabled. iOS 2.1.0 (3) is available for internal maintainer testing through TestFlight. Public App Store review remains pending.

ONE PICTURE, THREE MOMENTS

The useful connection is the whole experience.

  1. 01

    Choose on iPhone

    Use the native camera or select one photo. Check the picture, optionally name it, then keep it locally or deliberately send it.

  2. 02

    Find it on Mac

    Open Workbench or refresh Saved resources → From iPhone. A downloaded copy stays available even when iCloud is turned off.

  3. 03

    Put it to work

    Use as backdrop chooses an existing scene and opens its replacement preview. Adjust the crop and Apply. The device, logo, persona and other layers stay where you put them.

A presentation and your everyday wallpaper keep separate settings. Photo arrival changes neither. You can also save an independent JPEG copy for another app. The newer Scenes journey puts camera and photo selection inside mobile preparation for a Mac presentation.

DESIGN EXPLORATION

Make arrival clear. Keep setup out of the way.

Generated concept showing the same fictional reception photo selected on iPhone and available beside a Mac scene preview.
Experiment A — the complete journey. Retained the optional name, the same recognisable photo on both devices and an explicit backdrop action. This is generated artwork, not a working-cloud screenshot.
Generated state study comparing a prepared photo, a queued upload, an iCloud copy and a downloaded Mac copy.
Experiment B — truthful states. Retained “Queued for iCloud” and “Downloaded” as different facts. Rejected the invented Projects navigation. Workbench keeps its existing Tools/Saved tabs on mobile and Saved resources on Mac.

Generation briefs and critical decisions →

RANKED BY THE USER’S JOB

Two small additions. One useful idea parked.

RankOpportunityDecision
1Take it now; find it later.
Reliable selected-photo transfer while the Mac is away or closed.
A real existing iPhone photo has downloaded on Mac after a retry. Repeat deferred delivery, restart and account recovery before calling the whole journey verified.
2Make the arrival useful.
One action into the scene’s existing backdrop preview.
Implemented using the existing scene transaction. Explicit Apply preserves the rest of the composition.
3Take a nearby photo from the Mac.
Apple Continuity Camera inside the same arrival surface.
Parked. Valuable later, but different from deferred arrival and already available in supported Mac apps.

What we borrowed—and what we declined

Apple’s native inputs

The camera, selected-photo picker and Apple Account do familiar jobs. Continuity Camera suits nearby, Mac-initiated capture. It is not a cloud inbox for a closed Mac.

Yoink and Anybox

Yoink makes temporary gathering and transfer approachable; Anybox makes saved content useful across Apple devices. Workbench borrows a clear destination and retained copies, without becoming a general collection manager.

Dropover and LocalSend

Dropover’s cloud links solve sharing with somebody else. LocalSend solves nearby transfer across platforms. Neither is a reason to add public links or a second transfer network to this first job.

Research reviewed on 13 September 2026. Primary documentation, architecture alternatives and testing limits are recorded in the canonical specification. Yoink’s official trial was installed after signature verification, but native automation did not obtain an operable app window; its behavior here is documentation evidence, not a completed hands-on transfer test.

FINE DETAILS THAT EARN TRUST

“Sent” is not the same as “on your Mac.”

StateWhat is trueWhat happens next
Only on this deviceThe local save succeeded. Nothing was uploaded.Keep it here, or enable handoff and choose Send.
Queued for iCloudSend intent is saved for a previously verified Apple Account. Delivery is not yet confirmed.Retry on a later foreground refresh with that same account.
In iCloudApple acknowledged the cloud record.The Mac checks when Workbench opens, becomes active or you refresh.
Downloaded on this deviceThe image was validated and saved locally.Preview it in a scene, or save another copy.

No guaranteed background delivery, no silent account switching and no automatic scene edits. An error stays visible alongside the local photo.

A SMALL COMMODITY LAYER

Keep photo ownership separate from the transport.

Native inputsCamera · Photos picker
PhotoHandoffKitLocal original · queue · validation
Private CloudKitSelected JPEG · same account
Mac arrivalOwned copy · deliberate reuse

Why this backend

CloudKit supplies private Apple-account storage without a Workbench login or an operated web service. We accepted developer signing/schema setup to avoid making every person choose and repair a sync folder.

An app-owned iCloud Drive container remains a credible alternative if visible files become the product. A separate service only earns its place when a concrete cross-platform or team-sharing job needs it.

Where change can happen

A narrow transport protocol serves a versioned, account-bound photo store. Native camera and Mac scene interfaces remain separate. Better image processing or a replacement service must preserve original files, explicit send intent and honest status.

We have not built a universal sync framework. A backend migration would need explicit account consent, stable identifiers and a tested import path.

Architecture decision, rejection reasons and upgrade triggers →

ONLY THE PHOTO YOU CHOOSE

A considered default for real workplaces.

Workbench keeps the selected original locally and transfers a new JPEG, up to 3,840 pixels on the long edge. It does not copy the source’s GPS or camera metadata into that JPEG. Your optional title and image contents still travel with it.

Private iCloud uses the same Apple Account on both devices. Turning handoff off stops cloud work and keeps local copies. Removing the cloud record is separate from deleting local pictures or already composed scenes. There is no public photo link, full-library scan or automatic wallpaper change.

Read the app privacy details →

EVIDENCE AND NEXT CONTRIBUTION

Read the contract. Check the real journey.

Validation record

The installed Mac downloaded an existing real iPhone photo after the CloudKit owner-alias correction, following a transient timeout and retry. The newer signed Mac Preview retains that photo and existing scenes. No private photo is published here. This establishes one real download, not every deferred-delivery or recovery path. The current evidence table keeps this photo milestone separate from unverified editable-scene transfer. The captures below are earlier synthetic UI checks. Historical tests and engineering record · Earlier installed Mac account check.

Actual iPhone Simulator photo preview with a synthetic whiteboard, optional name and separate Send and Keep actions. Cloud access is disabled.
Actual iPhone UI. A synthetic photo stays local. Full-width actions avoid wrapped, uneven buttons. Reopened saved photo.
Actual Mac photo handoff view showing a downloaded synthetic image, with a visible Simulated arrival, no iCloud banner.
Actual Mac view, simulated transport. The production model validates and stores an injected JPEG. This proves local arrival UI, not CloudKit delivery. Offline failure with the image retained. The fixture’s backdrop callback is simulated; scene preservation is tested separately.
  1. Start with local tools.

    The normal Xcode/Simulator build keeps iCloud off. Test a selected synthetic photo, a local save and reopening Saved without an account.

  2. Prepare the paired Preview.

    Use the same Apple developer team, shared private container and CloudKit environment for both apps. The profile and signed-app preflight checks this configuration. A passing build alone does not.

  3. Prove deferred delivery.

    Send a synthetic photo while the Mac is closed. Reopen Workbench, verify the downloaded image, then preview and apply it to a disposable scene. Repeat offline, after restart, after account change and after cloud removal.

Canonical product and engineering specification → · Real-device acceptance gate · Parked Continuity Camera idea · Source Preview and review →