Dual-Version Camera
After every shot, compare the sensor original with the system-rendered photo, then keep or remove HDR, noise reduction, and color processing one setting at a time.
After taking a portrait or night photo on a phone, people may look back and find that the system has rendered skin tones, the sky, or saturation unlike the scene. Each time the user presses the shutter, the app saves the sensor original and the system-processed image as two versions of the same photo, ready for side-by-side comparison immediately after capture.
The comparison screen offers more than a choice of which version to keep. Users can retain the system’s HDR to control highlights, turn off excessive sharpening, or roll back only the color styling and skin-tone adjustments; every processing option has a toggle and before-and-after preview. The selected combination becomes a preference for the next shot without overwriting the original file.
In the photo library, both versions live under one item, with the thumbnail showing the version the user ultimately chose. On export, users can select the sensor original, the full system-rendered image, or their own mixed version. The edit record stays with the photo, so users can revisit the trade-offs later without recovering an old backup.
The first release supports common portrait, daytime, and night-scene processing, without claiming to replace a professional RAW workflow. Its purpose is to make every step of phone computational photography visible and reversible, rather than letting automatic beautification become an irreversible result.
Why now
On July 28, an iPhone 15 user posted that the system makes colors more muted immediately after the shutter is pressed, with no way to undo it. S1 As of July 29, the post had accumulated 661 likes, 4 reposts, and 16,068 views, making the problem of noticing a changed image immediately after capture more visible. S1
Target user
iPhone users who care about skin tones, sky detail, and the atmosphere of the original scene. They are usually not professional photo editors, but immediately notice when a review image looks grayer, oversharpened, or has reshaped highlights. While the scene is still in front of them, they are best able to judge which version feels more faithful. By the time they edit at home, their memory has faded and an adjustable original may not have been kept.
Minimal entry point
Use AVFoundation’s AVCapturePhotoOutput to make a RAW-plus-processed-photo request and obtain two outputs from the same capture on supported devices. S2 An in-app library uses a local database to link the DNG, processed image, preview, and edit recipe. Rebuild the RAW version with Core Image’s CIRAWFilter, exposing controls for highlight recovery, local tone, noise reduction, sharpening, and white balance. S3 The interface can still present HDR, sharpening, and color toggles, while the underlying RAW pipeline reconstructs approximate effects. Keep the system-rendered image intact as a reference, without claiming to extract every intermediate step of Apple’s processing. Prioritize daytime scenes and static portraits in the first release; enable night scenes only where device and format support permits.
Punching above its weight
The most persuasive asset is a swipe comparison from the same shutter press. Create short videos around grayed-out skin tones, abrupt sky changes, and oversharpened night scenes, with original files available for photography users to inspect. Recruit early testers from iPhone photography communities, Halide user groups, and comments on posts discussing computational photography. Shared photo pages can retain a summary of the device and processing toggles, so posting a photo naturally surfaces the product entry point.
Competitors & gaps
- Halide Process ZeroGoogle
- Halide has already made resistance to overprocessing into a mature camera experience. Process Zero creates a lightly processed image from sensor RAW and saves the RAW alongside a JPG or HEIC. Image Lab can also reprocess RAW, leaving room to adjust exposure again. It lets users switch between Apple processing and Halide’s processing, already covering the demand for more natural-looking images. S4 Its primary choice, however, is between processing modes. Image Lab is closer to a streamlined RAW development tool than an explanation of each computational step applied to a given shot. The opening for Dual-Version Camera is to put the system version and a lightly processed version from the same shutter press into one comparison workflow. Users can also retain processing combinations by subject, without first needing to understand a RAW workflow. The real challenge is making that separation credible: its own reconstructed result cannot be presented as an intermediate layer of Apple’s pipeline.
- Apple ProRAW and Photos editingGoogle
- Apple ProRAW already combines RAW information with iPhone image processing in one file, preserving more room to adjust exposure, color, and white balance. AVFoundation also supports returning RAW or ProRAW and its corresponding processed image in a single request. S2 That provides a system-level foundation for dual-version capture. But ProRAW still requires users to enter an editing interface and understand a set of conventional parameters. It does not turn the scene seen before capture, the system-rendered result, and a lightly processed version into an immediate swipe comparison. Public APIs also do not expose separate outputs for Apple’s HDR, sharpening, or skin-tone processing. Dual-Version Camera can place the professional format behind a more intuitive choice flow. Its distinction is not having RAW, but showing ordinary users what the system changed and carrying their preferences into the next shot.
How it makes money
Use a one-time purchase model. The free version supports dual-version capture and basic comparison; the paid version unlocks the full set of processing controls, batch export, preference presets, and a persistent edit history.
The case against
Saving both a RAW file and a processed image with every shutter press quickly increases storage, write, and backup demands. Continuous shooting also brings processing delays, heat, and dropped frames, with a higher cost for night scenes. More importantly, public APIs do not expose Apple’s HDR, sharpening, and skin-tone processing as separate intermediate outputs. S2 The app can only preserve the complete system version and reconstruct a controllable version from RAW. If that approximation is described as undoing a specific Apple processing step, users will quickly lose trust in the comparison. Different devices and lenses also require separate color calibration; otherwise, preferences will not transfer reliably.