We heard that the man behind Google's computational Pixel photography magic, Marc Levoy, was going to work at Adobe and help build a single universal camera app for every phone. We all loved hearing it because, no matter how well the native camera app on your phone is, you'll usually find more features, better features, or at least that one single feature you can't live without in a third-party app.
I'm sorry for doing this, but I'm about to crush our dreams a little bit by explaining why Adobe's app is going to be no better than any other good camera app in the Google Play Store. It's all about access to software and hardware that Adobe isn't going to get.
This is not anything new, but it did float into our consciousness when Moment decided to abandon its Android camera app and gave us a plain-language reason why — Android phone makers don't use the "regular" Google camera APIs. Instead, all seem to have a mishmash of proprietary software and hardware that's used to make a good photo.
A third-party app doesn't have this sort of access and instead relies on the basic Android camera APIs to take control of the minimal amount of hardware needed to capture a photo. That means a third-party app, like Adobe's planned universal camera app, isn't going to be able to use features like pixel doubling or mechanical aperture settings or special AI-powered chips that many phones use. Nope, it gets to control the basics and use the lens. That's it.
And those extras are what make a phone camera great. You would not get the amazing shots from a Google Pixel 4 without using Google's proprietary Neural Engine and the silicon that drives it. You can't use the incredible "regular" zoom on a Galaxy S20 without access to Samsung's software and hardware. The same applies to every good Android camera, no matter if it's from Huawei, Sony, or LG.
Google has taken a small step to fix this by releasing the CameraX Jetpack Library in April 2020. What that could do is allow Android phone makers to open up all of their secret sauce to third-party apps in a way that would still protect their intellectual property rights. But participation is optional, and Android phone makers don't have to share anything. So they haven't, and they won't. We see the same thing year after year whenever something is optional.
We've already had a preview of what is likely going to happen here in the unofficial Gcam ports for various phones. Getting Google's Pixel phone camera app installed on other phones with better camera hardware doesn't mean better photos. Google's camera app is designed to take advantage of the special silicon inside Pixel phones that is used to build a finished picture.
Samsung, Huawei, and every other Android manufacturer that makes a good camera also has its own special software or hardware or both. But the Google camera app can't use any of it. It leverages the standard Android Camera2 API, and the photos aren't anything special.
What makes all of this even worse is how well a Marc Levoy-designed Adobe camera app will probably be on iOS. The APIs in iOS are standard for every app, including Apple's own, and the result is some very good third-party camera apps like Halide (opens in new tab). Using the standard camera and machine learning APIs in iOS means Levoy can work out something very much like the Pixel phone camera on a modern iPhone.
The only company that can do anything about this whole situation is Google. What it could do, unfortunately, is also something that nobody really wants — force Android phone makers to toe the line using access to the Google Play Store as leverage. That is also something that probably wouldn't fly too well in an EU court, so it's unlikely that Google has a simple solution it can roll out.
What we can do is sit and twiddle our fingers waiting for a solution, and in the meantime, learn to live with the camera app that came with our phone instead of enjoying great photos and videos from apps like Instagram or a new app from Adobe. We don't have to be happy about it, though, and I'm not.
The paragraph mentioning getting googles camera app and it not leading to better photos isn't true. I know plenty of Motorola and Oneplus phones that take photos miles better once GCam gets installed. Since that is the case this could mean people could see slight improvements with their photos using this adobe camera app but since it's universal by design that will prove to be a hinderance.
I guess it depends on the phone then. I loaded GCam on the U12+, and photos were worse, mostly due to noise. I think the stock camera app has some AI going for it though, as it recognizes when things are moving and makes adjustments.
Yup. I've mostly given up on third-party cameras, precisely because of what Jerry mentions. Nothing beats the stock OEM software for output quality and app versatility; nothing. I still use Filmic Pro and Firstlight, but mainly for their desqueeze function; otherwise, the output quality blows compared to the stock Samsung app.
The main question I have is, if Apple's API is so open, how come 3rd parties can't have control over shutter speed? They are forced to use a 5 second exposure, and if they need more, they have to stack images. I have a rack of iPhones and would love to have the 1/8000 to 32 second control range like on my HTC, but I can't. I'm working with the dev for Slow Shutter, but it seems like there is no solution.
The issue with this premise is that many phones get better pictures out of using ported versions of the iPixel GCam than using their stock cameras. HMD's pseudo-Nokia phones are a perfect example. So if Abode releases a camera that outperforms the GCam (and it's not that hard. Add a manual mode to it and it's automatically better) that'll be enough for a lot of people. And of course, with Abode making a camera app, the door is always open to partnerships with OEMs.
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.