Adobe’s experimental camera app, Project Indigo, quietly walked into a classic modern problem: new phone hardware changed shape faster than the software could catch up. After a month of being essentially incompatible with Apple’s latest handsets, Indigo has been updated to run on the iPhone 17 — but only if you’re willing to give up selfies for now. Adobe’s short-term fix was to disable access to the front-facing camera entirely so the app can work with the rear cameras while the company and Apple finish ironing out the selfie-sensor issues.

Project Indigo isn’t a simple filter app. It’s a computational-photography project led by imaging veterans (Marc Levoy is one of the names attached), and it relies on carefully tuned processing pipelines that expect certain sensor geometries, noise characteristics, and metadata. When Apple redesigned the iPhone 17’s front camera — moving to a higher-resolution, square-format sensor — those expectations broke. Because Indigo does a lot of its processing “under the hood,” the app needs per-camera calibration to match its algorithms to the new sensor’s behavior; without that calibration, results can be poor or the app can’t initialize the camera at all.

This is less a bug in the user-facing sense and more a mismatch between two complex systems. Adobe’s engineers reported the incompatibility in forum threads and release notes, and Apple has indicated the needed system-level fixes are headed to iOS 26.1 — the update Adobe is waiting on before it can safely re-enable the front camera.

Instead of holding the entire iPhone 17 user base hostage until a perfect solution landed, Adobe chose a pragmatic path: ship an App Store update that restores Project Indigo’s core experience on iPhone 17 devices, but with one caveat — no front-camera support yet. That means iPhone 17 owners can use Indigo’s signature rear-camera processing and manual controls, but anyone who lives on their front camera (portrait selfies, video calls using the app, etc.) will have to wait until Apple’s iOS patch and Adobe’s follow-up update arrive.

For users, this feels a little jarring — an app that launched in June and quickly developed a small but enthusiastic following is now partially limited on Apple’s newest phones. But from a product team’s perspective, it’s defensible: the core value of Indigo (its rear-camera computational engine and the “softer,” more natural rendering people liked) is back in users’ hands without introducing more subtle image-quality regressions.

The incident is a neat microcosm of a larger trend: computational photography is increasingly dependent on tight coordination between hardware makers (Apple, Samsung, etc.) and software vendors (Adobe, Google, third-party app makers). Tiny changes in sensor layout, bit-depth, or driver behavior can cascade into big compatibility headaches because modern camera apps don’t just take a single JPEG — they capture bursts, merge exposures, denoise, and apply models that expect very specific inputs. The result is a brittle ecosystem where OS-level camera APIs and timely driver fixes become as important as the app’s own code.

It’s also a reminder that experimental, lab-style projects that ship to consumers — as Adobe has framed Indigo — come with operational risk. When you push advanced processing into the wild, you’re signing up for the long tail of device variety: differing sensors, different firmwares, different quirks. Adobe’s choice to disable just one camera instead of delaying the whole release is a practical trade-off that preserves user access to most of the app while buying engineering time to properly calibrate the front-facing pipeline.

What should iPhone 17 owners do now?

If you use Project Indigo and just picked up an iPhone 17, here are the practical takeaways:

• You can install the latest Indigo and shoot with the rear cameras as usual. Indigo’s rear-camera processing and manual controls are available again on iPhone 17 devices.
• Don’t expect front-camera (selfie) support until iOS 26.1 and a subsequent Adobe update that re-enables and calibrates the front-facing pipeline. Adobe’s App Store release notes explicitly mention front-camera support arriving after Apple’s system fix.
• If selfie functionality is crucial to your workflow, you’ll need to use Apple’s native Camera app or another third-party camera that supports the iPhone 17 front sensor until Adobe finishes its work.

The soft landing — and the hard lesson

This feels like a soft landing. Adobe didn’t pretend the front camera was fine; it told users what it was doing and shipped the largest chunk of the app that would work reliably. For enthusiasts who liked Indigo’s “softer touch” on images, that’s welcome. For everyone else, it exposes the fragility of the camera-app ecosystem: cutting-edge photo features increasingly depend on timely OS updates and close hardware cooperation.

If you’re following computational photography as a field, this is worth watching. The iOS 26.1 release will be the little patch that determines whether Adobe can flip the selfie switch back on quickly or if there will be more tweaks to get the front-camera pipeline behaving the way the Indigo team wants. Either way, Adobe’s approach — ship what’s stable, be transparent about the limitations, and finish the calibration work in public forums — is a useful template for how experimental apps can stay usable without overpromising.