714
Replies
I just registered to express my gratitude and support to the team. I’ve been using Indigo since release and while it's understandably still maturing, it shows a lot of promise. They are clearly aiming for something that isn't just a repeat of what Marc's team started at Google. I own iPhones and a variety of Android phones to experiment with computational photography, and it's clear Indigo is forging its own path.
Having said that, I would like to share my view as a developer (albeit of the web kind) on the behavior in this thread. It seems to have turned into both: a wishlist (probably fine) and a list of demands for the team to replicate what other camera apps do, which is particularly appalling when specific solutions are prescribed. The team has repeatedly mentioned they are small, so their budget (time, resources, etc.) is limited. Their time is (probably) best spent improving stability (their stated top priority) and executing on their vision, not reproducing the Google camera or emulating the iPhone's ISP.
I bet the best way to get what we want is by helping the team with feedback about specific, reproducible issues. Indigo appears to be an experiment, and its future isn't guaranteed. It needs to be stable and have an identity of its own, which it won’t achieve by copying what came before. This is just my perspective as a lurker who's genuinely excited to see this project succeed.
By @red0ne
Thank you @red0ne - most of what you have written is true. Having said that, we really don't mind a variety of feedback from users. This is after all one of the main reasons we published what is clearly and experimental app: it's to hear both the good, the bad, the ugly, and the demanding. 😉 One of the aspects of our effort is to help educate the general public about mobile photography where we think it matters. Many things that need to happen to get a nice looking image are very difficult to do, and most of us are not really aware of them until we start building a camera app. Here is where working on an iPhone is both a blessing and a curse: on one side it is a very stable (and shareable platform) where we can immediately address many generations of devices, but on the other hand it is quite closed and not very amenable to mods. Things like dual conversion gain are simply not exposed in any way, shape, or form to 3rd party apps, and if we were to find some secret API which allows control over it, our app would not pass the App Store review as, per guidelines, one cannot use such APIs.
Bottom line is, myself and the team are at this point quite versed in not getting upset at any criticism, asks, demands, or any other feedback. We are working as best as we can, and we will be releasing improvements asked by the users when we can.
Indigo was a very promising camera app until a few days ago when it stopped writing DNG files.
I tried erasing / downloading Indigo again, tried quitting Indigo then shooting RAW with the native Apple app then back to Indigo. Always wait for the little progress circle over the preview to complete before doing anything else. No quick clicks of the shutter. No overheating.
Nothing has restored DNG functionality (while Indigo is obviously set to DNG+JPG).
Indigo 1.0.2 on iPhone 16 pro / iOS 18.6.2 / available 81 GB / no previous photos saved in Photos / iCloud not used for Photos.
It should be obvious that not having access to DNG files has made Indigo rather useless.
By @Antonis R
Hi Antonis, this is indeed concerning, but it also sounds very weird - I can honestly say this is the first time I am hearing of this problem. To debug this further, can you answer a couple of additional questions:
- If you capture JPEG-only, is it always saved correctly?
- If you capture JPEG+DNG, is the JPEG always saved correctly?
- How are you verifying that the DNG is or isn't written to disk?
- Have you tried rebooting the device to see if that helps?
Thank you for helping to triage this.
I have been using Indigo from the start and it became my main camera app (mapped it to camera button)
the main differentiator from stock camera app is color rendition wchi feels much more natural, film-like, less flat and processed. The image has much more plasticity!
Attached few recent pictures (all are straight unprocessed jpegs)
p.s. still waiting for pure astophotography mode
By @karen_5438
Thank you for sharing your images - these all look wonderful! Regarding improvements to long exposure functionality, including the astrophotography mode, these are in progress. It will take a few cycles for us to progressively add more, as astrophotography requires custom processing which differs from regular captures. Stay tuned!
I’m using a Japanese-model iPhone and a shutter / notification sound is required when taking photos in Japan (or when the device is in Airplane Mode). However, in Project Indigo the shutter sound plays continuously—even when I’m not pressing the shutter button. This constant sound makes it very hard to take photos in public without disturbing others.
By @liyuu_8951
Thank you for reaching out. This is a known issue, due to the fact that Indigo's viewfinder always streams raw frames which are used both for our custom auto-exposure algorithm and for our Zero Shutter Lag (ZSL) functionality. We are working with Apple on trying to enable shutter sound disabling world wide. Please stay tuned.
I love the images from the app, they're amazing. I notice that ewhen i view the images on iphone there is a slight pause then it seems like the lights turn on. What's happening? Can i print the lights on image?
By @carromdc
Hello - I am not sure I understand what you are experiencing with the lights turning on. Would you mind explaining a bit more?
@BorisTheBlade What happened with the app updates? You said it is coming in the upcoming weeks? Also i hope app performance is greatly improved and heat since this update took almost 3 months.
By @powerful_Elixir5E29
A new build is imminent. Having said that, there are a few things to be aware of here:
- Indigo is experimental, and there is no commitment (yet) from Adobe on productizing it. So all effort that goes in it is due to a passionate, but rather small team working on it.
- As menioned above, we are a small team. Depending on what an app does one doesn't necessarily need a big team, but Indigo is complex so things take time.
- Did I mention that Indigo is complex? Indeed, since we own the full image capture and processing pipeline, making changes is oftentimes a lot more involved than if we were to "just" reuse Apple's capture pipeline. For many 3rd party camera apps adding certain features is really just a bit of UI/UX work. For us it may require that plus a decent amount of messing about with the core capture and processing functionality.
- Furthermore, building on the 'experimental' label from above, as we are building Indigo, we often find that the way we did some things initially is suboptimal and may make things slower for the user, or it may make building extensions harder. So we are changing quite a few things under-the-hood which you may not notice any gains from, but which will allow us to do things better or faster later.
The team really appreciates the support we are getting from the community, especially here on the forum. We are accutely aware that Indigo has some sore spots that need fixing or improving, and the main one are stability and performance. These will be coming out to our users over time, and the next update already includes some such improvements - for example, I can tease that we managed to improve the super-resolution speed without impacting image quality. Stay tuned for more.
AdChoices
