This is the first time my iPhone 14 Pro felt inadequate.
The app is so heavy that the phone is overheating after the first photo. it consumes so much resources that’s the music was playing in the background stopped because my AirPods connection dropped. For the very first time on this phone I felt like I need an upgrade, it felt like the last days of my iPhone 6s. I didn’t know you can do that to an iPhone.
The photo quality is supperb though, obviously not DSLR replacement but it really gives you that feel. Apple’s own processing has become too boring, sometimes I use Halide just to have unprocessed raws.
Aurornis 8 hours ago [-]
> The app is so heavy that the phone is overheating after the first photo.
I have the same phone and no overheating errors here.
Do you mean the phone got slightly warm? That’s not overheating, it’s just what happens when you use an app that leverage the CPU for anything non-trivial. It’s not overheating.
EDIT: The screenshot below clarifies that the heat warning is a message in the app, not the actual iOS overheating protection as ( https://support.apple.com/en-us/118431 ). Regardless, I still can’t trigger the in-app temperature warning on my phone.
It will dim the screen soon, so much that it's unusable outdoors. I wasn't able to capture a photo outdoors yesterday using this app because of this. The first photo slowly finished processing but the app crashed, lost the photo. Then the device was overheating, the screen dimmed to unusable and the FPS dropped, the app become unresponsive and the music went away, the AirPods re-connected. Couldn't even try to capture a second one.
It wasn't even that hot, just 28C.
josephg 6 hours ago [-]
I’d be shocked if this is an actual limitation of the hardware. Modern iPhones have plenty of horsepower for computational photography.
I bet this a software bug of some sort - like they’re using the cpu where it should be using Metal or something. Hopefully they can sort it out.
khurs 4 hours ago [-]
iPhone have less ram though, compared to Pixels and androids in general.
Depends where it's being used. The phone can easily get that hot if you're shooting in sunlight.
Aurornis 6 hours ago [-]
Interesting. I can get the app to crash if I spam the photo button and queue up the maximum number (8) of background processing tasks. Feels like an OOM error if I had to guess. Can’t get any of the other things you experienced to occur, though I haven’t tried Bluetooth audio.
qwopmaster 6 hours ago [-]
Same experience on 14 pro - it got noticeably hot after 2nd photo, and after 3rd the app crashed and OS was choppy for a few minutes. And that was indoors, in 22C and screen fairly dim. Never seen anything like it; as-is I’d avoid the app lest it actually damages something.
The photos themselves do look better than apple’s default cam, but not by a huge amount. Most noticeable is better range, like a photo of a blue sky with a few clouds seen through your window that takes up a third of the photo, which by default is either very dim inside or mostly indistinct blue-gray or blown out if focusing inside. Super-resolution however, especially at 6x (double 14 pro’s 3x optical zoom) is actual wizardry.
On the other hand night photos seem like garbage - there’s a bit more stuff visible than on default 3sec night mode but the colors are nonsensical and details nonexistent, certainly nothing even remotely close to what adobe promises on their webpage.
All in all I’m not sure what use it is with the terrible performance, outside of long-range photos that you really want to shoot at 6x zoom and keep as much detail as possible.
pantulis 4 hours ago [-]
Another datapoint with an 15 Pro Max. I shot a couple of pics indoors in my own room and got the message. Seems the app is continuosly processing what's coming from the sensor.
vachina 1 hours ago [-]
Par for the course for an Adobe app. Bloated, slow and meh output.
leptons 7 hours ago [-]
>For the very first time on this phone I felt like I need an upgrade, it felt like the last days of my iPhone 6s. I didn’t know you can do that to an iPhone.
Apple got caught purposely slowing down older model iPhones.
Because of how aged batteries work, if you don't purposely slow down the phone sometimes it'll shut off, which is worse.
throwaway14452 6 hours ago [-]
Maybe Apple should use their proverbial ingenuity and inventiveness to invent a smartphone design that lets you open its back shell without screws to allow the user to replace their own battery, though I'm not sure if the technology for it is quite there yet.
xp84 4 hours ago [-]
Sure, 100%, though that's a separate topic to the ridiculous urban legend that came out of that story. Something still must be done when a user has a degraded battery that can't handle the full draw of the CPU.
vbezhenar 4 hours ago [-]
It was literally court decision that led to the Apple implementing switch allowing users to switch their smartphones to unsafe mode.
I still think that Apple was right there by not implementing this switch, and judge was an idiot. But that's just me.
astrange 5 hours ago [-]
Batteries last years and are already easily replaceable.
They're not even the only consumable part anyway.
throwaway14452 5 hours ago [-]
Last as in "works" is a very low bar, they are going to have severely reduced capacity, which also affects performance.
> Last as in "works" is a very low bar, they are going to have severely reduced capacity, which also affects performance.
Batteries tend to degrade to about 85% quickly and then spend a long time at that capacity. Couldn't tell you why.
A USB battery is a more useful thing to have, for instance because you don't have to turn off the phone to use it.
> Is this[1] what easy looks like?
For something you'd do every 2-3 years, sure. He's put in some extra steps in that video I think.
greenpresident 5 hours ago [-]
Ifixit score of 7 plus best parts availability of any phone makes for a great combination in my mind.
xp84 4 hours ago [-]
On the other hand, before the iPhone, literally every phone had a back cover that could be removed with bare hands and batteries held in by friction. After iPhone, all phones are sealed and require tiny screws to be removed, special adhesives to be defeated (god help you if you break off the stretchy adhesive strips), and of course seals to be replaced. And all this was done from the 2007 iPhone, over a decade before Apple did any IP67 rating of any kind, so none of it was done for waterproofing.
So, "Apple killed battery swappability" is a fair thing to say.
mrtksn 5 hours ago [-]
It's pretty easy for something you do every 2 years and you can get it done by someone else at reasonable price.
iPhones being hard to repair, let alone change the battery is such a ridiculous meme.
leptons 3 hours ago [-]
Instead of offering to replace the batteries, or making a phone with an easy to replace battery, Apple chose the shady move and hid their "solution" from the public and just slowed down older phones.
>"In March, Apple agreed to pay up to $500 million to settle claims of intentionally slowing down older phones."
They got slapped on the wrist. This resulted in them making the batteries slightly easier to replace, but their batteries are still impossible to replace by the average iPhone owner.
sixothree 6 hours ago [-]
I don’t buy this excuse. I experienced it first hand with my iPhone 4. When moving from iOS 6 to 7 my phone became unusable. As did everyone’s. And there was no going back to
iOS 6. It wasn’t the battery in any way. The upgrade basically made the phone unusable.
astrange 6 hours ago [-]
Those are called performance bugs. That was a long time and a lot of software development cycle changes ago.
If it helps I believe the EU just made it illegal two days ago to release updates that make battery life worse. But I could've confused some of the details there.
vbezhenar 4 hours ago [-]
It was not a bug. I have similar story with my iPhone 4S became unusable with iOS 7. It was never fixed. One day I managed to jailbreak it, rolling back to iOS 6 and was astonished how fast and smooth it is.
They just implemented iOS 7 with much more compute requirements, so only newer phones were able to run it smoothly. The progress of mobile CPUs these old days was crazy, so I don't really complain about it, it was inevitable.
astrange 4 hours ago [-]
> They just implemented iOS 7 with much more compute requirements, so only newer phones were able to run it smoothly.
Yeah, that's a bug. Any regression on any supported device is a bug.
That was a very, very rushed release.
xp84 4 hours ago [-]
Those are separate issues. No one ever proved Apple set out to do that. Sure, they do care as little as the next company how their older hardware runs a new OS, but it's silly to believe it's a conspiracy. Tell me, do you believe Apple (A) adds in a bunch of conditional code to trigger just older phones to infinitely loop to kill your performance? Or (B) that they deliberately add a bunch of poorly-performing code, but it's code that everyone has to run and only the newest phones can manage?
It seems like A would have been whistleblown by now, and B would be idiotic for them to do on purpose since it would make their new devices unnecessarily slow too.
My opinion is basically B but without malice, it's just that they're obsessed with tons of animation and other eye candy, and added a lot of bloat in those years in general, rushing code out the door out of a desire to hit iOS release dates and the synchronized iPhone release dates they used to have.
Brajeshwar 10 hours ago [-]
For those interested in this, Leica LUX is the alternative iOS Camera. It also works for those who cannot afford to own a Leica.
I really love this app, but I'm not a fan of the subscription model. While I understand the business reasoning, I'd much prefer having the option to purchase individual presets instead of committing to a full subscription.
I recently used the B/W preset by Greg Williams during my trip to Iceland, and the results were fantastic. The grainy texture it added to my photos was exactly what I was looking for and really enhanced the dramatic Icelandic landscapes.
mrtksn 7 hours ago [-]
Wow I love that. The processing looks like a Leica indeed, the UI has a Leica feel and put me in a mood for candid Leica style photos haha :)
When using a DSLR I almost always shoot in (A)perture mode, it helps you control how much you separate the subject from the background and it's the thing I miss the most on phone. The portrait mode isn't quite the same.
It's the first app that I came across to have an aperture mode, cool.
PS: Apparently it lets you capture in all modes, but to edit the parameters after taking the picture it requires the pro mode.
raylad 8 hours ago [-]
I just tried it and the Leica Chrome setting looked better to me than anything the normal camera app or Project Indigo produced.
But I hate subscription apps. And the rest of the UI seems quite clumsy.
throwaway314155 7 hours ago [-]
Cheaper than a Leica, but still really damn expensive for a camera app.
al_borland 57 minutes ago [-]
And if you want the shutter button accessory they advertise, that’s $395 (but sold out currently). That’s a lot of money for a MagSafe button. A person could get an entry level DSLR from Canon for about the same price.
jrgaston 8 hours ago [-]
It's not a dslr replacement, what a weird claim. My Nikons and Fujis are so much nicer to hold, to adjust, to shoot. But for a phone camera the s.w is ok. More adjustable than the iPhone app. I like the controls, the current settings text, and built in help text.
Only knock so far is it runs hot: never seen an overheating warning ever on my iPhone 14pro. Now i get one every ten or fifteen minutes when using Indigo.
stlava 10 hours ago [-]
I’m impressed they managed to make an app that makes me not want to use it or my phone to take photos! After I used it for about 5 mins I resolved to dust off my older DSLR and use it instead.
modeless 8 hours ago [-]
Marc Levoy is an "engineer"? Sure, but maybe more relevant is the fact that he's a well-known computer graphics researcher and professor emeritus at Stanford.
dwayne_dibley 1 hours ago [-]
I know this is ranty, but I really miss internet sites that aren't 60% adverts, 30% padding and 10% actual thing. This isn't anything more than an announcement page.
jeroenhd 3 hours ago [-]
Runs on my iPhone 15, but not well. Phone heats up like crazy and processing photos takes a while.
The end result is almost the same as the pictures the normal camera app takes. I think I must be missing something because this looks like a worse re-implementation of the normal camera app to me. Maybe I need to take the app out at dusk to take some pictures in more challenging conditions?
I still prefer the photos from my Pixel over the photos from my work iPhone.
thedougd 9 hours ago [-]
This is the first app I’ve ever downloaded for it to tell me my phone isn’t supported.
jeroenhd 3 hours ago [-]
I'm surprised they did a hardware check within the app rather than just restrict the app on the iOS app store side. Surely they should've marked your phone incompatible before you wasted your time downloading the app?
I do wonder what makes older phones incompatible, though. Others are complaining about the performance, so it could be that the low amounts of RAM Apple puts in their phones is starting to catch up, or it could be as simple as them not having trained their AI models for some older phones yet.
yumraj 8 hours ago [-]
Same experience on SE3.
neya 4 hours ago [-]
Who cares, it's Adobe. They'll eventually steal your work under some under-the-hood TOS update and even charge you for it. Don't believe me? Ask the existing CS customers. Fuck Adobe. They should be boycotted to oblivion.
preek 5 hours ago [-]
After the first shot on my iPhone 13 Pro in default settings, it immediately told me my phone was overheating and going to be unstable. Then it crashed. I tried once more, turned off raw mode, waited _minutes_ for one image to process and now my screen turns off and on again randomly while I type this comment.
coolandsmartrr 6 hours ago [-]
Strange, they don't let you download this app from the App Store in Japan.
Springtime 10 hours ago [-]
The article's wording suggests this supports computational RAW which would be useful. That is, auto stacking multiple captures into a single RAW (a la Google Camera for Pixel phones), rather than the traditional single capture. Allowing for reduced noise and higher dynamic range.
It's interesting as when I last looked a couple years ago only Fujifilm had a mirrorless digital camera (with cropped sensor) that supported this on-device.
DidYaWipe 8 hours ago [-]
It's just "raw."
Springtime 7 hours ago [-]
Every instance I've seen it referred to has used the RAW capitalization, including Google's PR, as it's an image format.
meatmanek 6 hours ago [-]
.RAW is an image format, but it's rarely used. Raw photos are usually stored in a manufacturer-defined format like .NEF (Nikon) or .CR3 (Canon), or occasionally in .DNG files. Nevertheless, it's fairly common to see the word capitalized as RAW.
strogonoff 5 hours ago [-]
You are certainly free to write in any fashion you want, but any time you turn “raw” (as in raw photography, raw image data, raw image formats) into “RAW”, or Wasm into “WASM”, etc., you will[0] be knowingly wrong—like non-dyslexic people who choose to spell “u” instead of “you”, except unlike them you will not be saving keystrokes and you will be perceived as shouting, which I presume is almost never the intended vibe in the context.
Obviously, it’s not the end of the world. Employees of famous companies, occasionally even reputable and knowledgeable people are not immune to using wrong or mistaken spelling. This is explained by a simple fact that there are plenty of professionals who are dyslexic and/or careless about spelling, while still being experts in their subject areas. There is nothing wrong about that, but evidence of their misuse of written language is not grounds for an argument that the wrong spelling is correct. Researching what the word actually stands for takes less than a minute, and it should clear any doubt and avoid unnecessary arguments.
[0] Now that you know…
DidYaWipe 6 hours ago [-]
R, A, and W don't stand for anything. It's raw data off the sensor, not an acronym. Therefore not capitalized.
You can find millions of instances of any given literacy-impaired error. "Would of" and "your not going to find this" are wrong... but they're out there by the boatload. No need to propagate them further.
Springtime 5 hours ago [-]
My impression has been that the capitalization is to identify the word as an image format (a stand-in for whatever actual format is used), rather than being an initialism. Canon, Nikon and Sony among other hardware and software companies use it in this way.
ZIP similarly doesn't stand for anything but is styled as such. So I suppose the pushback is more against being used as a stand-in for generic raw image formats.
Edit: just noticed your comment was greyed but I didn't downvote it fwiw.
bix6 9 hours ago [-]
Is this an actual SLR replacement / anyone know the RAW size and print size at 300dpi?
Last time I sent iPhone photos into my print shop they kicked them back.
tlhunter 9 hours ago [-]
> Is this an actual SLR replacement
There's just no way to replace the massive 35mm sensor of a larger DSLR / mirrorless camera. The amount of light gathered can only be simulated by capturing many frames. True depth of field can only be emulated by imperfectly blurring estimated background area via software, leading to goofy blurred hairs. Even the reported megapixels of a smartphone contain a quarter or less the equivalent DSLR resolution detail (a 24MP smartphone photo is roughly equivalent to the detail of a 6MP DSLR photo).
josephg 6 hours ago [-]
Yep this. I’ve been getting into photography over the last 9 months or so. I got a Sony a7iv and an increasing pile of lenses for it. It’s making me a huge camera snob. The truth is that nothing a phone can do can come close to the image quality of a proper modern camera. You can spot the difference a mile off. Photos from phones look like they’ve been passed through stable diffusion or something. They just look wrong in comparison to a real camera with real lenses and real lights.
It shouldn’t be surprising. Real depth of field is physically impossible with a small lens. And cameras have teeny tiny lenses and sensors. It’s impressive how good the photos are given the hardware, but the hardware is very very bad in comparison to a dedicated camera with replaceable lenses.
astrange 6 hours ago [-]
Nobody cares about image quality, that's not a goal in itself.
(There's an old camera influencer named Ken Rockwell who constantly pushes this; he has every possible opinion at once and is trolling most of the time, but he's right about this.)
The smallness of a phone means it can take pictures larger cameras can't because you have it with you when the picture is happening. And that's what really matters.
> They just look wrong in comparison to a real camera with real lenses and real lights.
You can use real lights with a phone camera all you want!
josephg 3 hours ago [-]
> Nobody cares about image quality
Hi! I'm right here! I care about image quality!
Image quality helps me feel proud of my photos. If I don't feel proud of my photos, its way less fun to wander around taking them - and I just don't bother. Image quality actively makes or breaks some of the joy of the medium for me.
I went to a nature photography exhibit / competition today. The exhibition was full of incredible photos of nature taken from all over the world. But some of the images were lower quality. There weren't enough pixels for the printer to do a good job, or you could see digital noise in them. I wanted to like them just as much, but I didn't. The photos weren't as good.
> The smallness of a phone means [...] you have it with you when the picture is happening. And that's what really matters.
What a weird statement. "What really matters" is completely contextual. What matters when you're entering a photography competition is completely different from what matters at your friends' birthday party. Or at a wedding, or on a photo walk, or a live show.
Use the right camera for the job. I personally hate the look of the photos my phone takes. My phone is almost never the right camera for me.
6 hours ago [-]
DidYaWipe 8 hours ago [-]
Software can't turn a phone into an SLR. It's an asinine claim.
It's not that the application can't bring value to the platform, but they need to better convey what it is. "Making images that look like they're from an SLR" smacks of fakery.
vr46 9 hours ago [-]
Indigo is excellent so far, a little bit buggy, but I am seriously impressed. (iPhone 12 Pro)
And I have a Q2, a 5D4 and a 645Z, this little app is really great, and colour me surprised.
The app is so heavy that the phone is overheating after the first photo. it consumes so much resources that’s the music was playing in the background stopped because my AirPods connection dropped. For the very first time on this phone I felt like I need an upgrade, it felt like the last days of my iPhone 6s. I didn’t know you can do that to an iPhone.
The photo quality is supperb though, obviously not DSLR replacement but it really gives you that feel. Apple’s own processing has become too boring, sometimes I use Halide just to have unprocessed raws.
I have the same phone and no overheating errors here.
Do you mean the phone got slightly warm? That’s not overheating, it’s just what happens when you use an app that leverage the CPU for anything non-trivial. It’s not overheating.
EDIT: The screenshot below clarifies that the heat warning is a message in the app, not the actual iOS overheating protection as ( https://support.apple.com/en-us/118431 ). Regardless, I still can’t trigger the in-app temperature warning on my phone.
It will dim the screen soon, so much that it's unusable outdoors. I wasn't able to capture a photo outdoors yesterday using this app because of this. The first photo slowly finished processing but the app crashed, lost the photo. Then the device was overheating, the screen dimmed to unusable and the FPS dropped, the app become unresponsive and the music went away, the AirPods re-connected. Couldn't even try to capture a second one.
It wasn't even that hot, just 28C.
I bet this a software bug of some sort - like they’re using the cpu where it should be using Metal or something. Hopefully they can sort it out.
https://iosref.com/ram-processor
On the other hand night photos seem like garbage - there’s a bit more stuff visible than on default 3sec night mode but the colors are nonsensical and details nonexistent, certainly nothing even remotely close to what adobe promises on their webpage.
All in all I’m not sure what use it is with the terrible performance, outside of long-range photos that you really want to shoot at 6x zoom and keep as much detail as possible.
Apple got caught purposely slowing down older model iPhones.
https://www.npr.org/2020/11/18/936268845/apple-agrees-to-pay...
I still think that Apple was right there by not implementing this switch, and judge was an idiot. But that's just me.
They're not even the only consumable part anyway.
>Batteries ... are already easily replaceable
Is this[1] what easy looks like?
[1] https://www.youtube.com/watch?v=T0fUmW-2swg
Batteries tend to degrade to about 85% quickly and then spend a long time at that capacity. Couldn't tell you why.
A USB battery is a more useful thing to have, for instance because you don't have to turn off the phone to use it.
> Is this[1] what easy looks like?
For something you'd do every 2-3 years, sure. He's put in some extra steps in that video I think.
So, "Apple killed battery swappability" is a fair thing to say.
iPhones being hard to repair, let alone change the battery is such a ridiculous meme.
>"In March, Apple agreed to pay up to $500 million to settle claims of intentionally slowing down older phones."
They got slapped on the wrist. This resulted in them making the batteries slightly easier to replace, but their batteries are still impossible to replace by the average iPhone owner.
If it helps I believe the EU just made it illegal two days ago to release updates that make battery life worse. But I could've confused some of the details there.
They just implemented iOS 7 with much more compute requirements, so only newer phones were able to run it smoothly. The progress of mobile CPUs these old days was crazy, so I don't really complain about it, it was inevitable.
Yeah, that's a bug. Any regression on any supported device is a bug.
That was a very, very rushed release.
It seems like A would have been whistleblown by now, and B would be idiotic for them to do on purpose since it would make their new devices unnecessarily slow too.
My opinion is basically B but without malice, it's just that they're obsessed with tons of animation and other eye candy, and added a lot of bloat in those years in general, rushing code out the door out of a desire to hit iOS release dates and the synchronized iPhone release dates they used to have.
https://leica-camera.com/en-SG/photography/leica-apps/leica-...
I recently used the B/W preset by Greg Williams during my trip to Iceland, and the results were fantastic. The grainy texture it added to my photos was exactly what I was looking for and really enhanced the dramatic Icelandic landscapes.
When using a DSLR I almost always shoot in (A)perture mode, it helps you control how much you separate the subject from the background and it's the thing I miss the most on phone. The portrait mode isn't quite the same.
It's the first app that I came across to have an aperture mode, cool.
PS: Apparently it lets you capture in all modes, but to edit the parameters after taking the picture it requires the pro mode.
But I hate subscription apps. And the rest of the UI seems quite clumsy.
Only knock so far is it runs hot: never seen an overheating warning ever on my iPhone 14pro. Now i get one every ten or fifteen minutes when using Indigo.
The end result is almost the same as the pictures the normal camera app takes. I think I must be missing something because this looks like a worse re-implementation of the normal camera app to me. Maybe I need to take the app out at dusk to take some pictures in more challenging conditions?
I still prefer the photos from my Pixel over the photos from my work iPhone.
I do wonder what makes older phones incompatible, though. Others are complaining about the performance, so it could be that the low amounts of RAM Apple puts in their phones is starting to catch up, or it could be as simple as them not having trained their AI models for some older phones yet.
It's interesting as when I last looked a couple years ago only Fujifilm had a mirrorless digital camera (with cropped sensor) that supported this on-device.
Obviously, it’s not the end of the world. Employees of famous companies, occasionally even reputable and knowledgeable people are not immune to using wrong or mistaken spelling. This is explained by a simple fact that there are plenty of professionals who are dyslexic and/or careless about spelling, while still being experts in their subject areas. There is nothing wrong about that, but evidence of their misuse of written language is not grounds for an argument that the wrong spelling is correct. Researching what the word actually stands for takes less than a minute, and it should clear any doubt and avoid unnecessary arguments.
[0] Now that you know…
You can find millions of instances of any given literacy-impaired error. "Would of" and "your not going to find this" are wrong... but they're out there by the boatload. No need to propagate them further.
ZIP similarly doesn't stand for anything but is styled as such. So I suppose the pushback is more against being used as a stand-in for generic raw image formats.
Edit: just noticed your comment was greyed but I didn't downvote it fwiw.
Last time I sent iPhone photos into my print shop they kicked them back.
There's just no way to replace the massive 35mm sensor of a larger DSLR / mirrorless camera. The amount of light gathered can only be simulated by capturing many frames. True depth of field can only be emulated by imperfectly blurring estimated background area via software, leading to goofy blurred hairs. Even the reported megapixels of a smartphone contain a quarter or less the equivalent DSLR resolution detail (a 24MP smartphone photo is roughly equivalent to the detail of a 6MP DSLR photo).
It shouldn’t be surprising. Real depth of field is physically impossible with a small lens. And cameras have teeny tiny lenses and sensors. It’s impressive how good the photos are given the hardware, but the hardware is very very bad in comparison to a dedicated camera with replaceable lenses.
(There's an old camera influencer named Ken Rockwell who constantly pushes this; he has every possible opinion at once and is trolling most of the time, but he's right about this.)
The smallness of a phone means it can take pictures larger cameras can't because you have it with you when the picture is happening. And that's what really matters.
> They just look wrong in comparison to a real camera with real lenses and real lights.
You can use real lights with a phone camera all you want!
Hi! I'm right here! I care about image quality!
Image quality helps me feel proud of my photos. If I don't feel proud of my photos, its way less fun to wander around taking them - and I just don't bother. Image quality actively makes or breaks some of the joy of the medium for me.
I went to a nature photography exhibit / competition today. The exhibition was full of incredible photos of nature taken from all over the world. But some of the images were lower quality. There weren't enough pixels for the printer to do a good job, or you could see digital noise in them. I wanted to like them just as much, but I didn't. The photos weren't as good.
> The smallness of a phone means [...] you have it with you when the picture is happening. And that's what really matters.
What a weird statement. "What really matters" is completely contextual. What matters when you're entering a photography competition is completely different from what matters at your friends' birthday party. Or at a wedding, or on a photo walk, or a live show.
Use the right camera for the job. I personally hate the look of the photos my phone takes. My phone is almost never the right camera for me.
It's not that the application can't bring value to the platform, but they need to better convey what it is. "Making images that look like they're from an SLR" smacks of fakery.
And I have a Q2, a 5D4 and a 645Z, this little app is really great, and colour me surprised.