Android has long struggled with the differences we find between native camera apps and external apps. Each manufacturer adds different functions to the native application, external engineers will not take advantage.
Although the solution for this depends not only on the manufacturers, but on the aspects we will describe a few lines later, Google wants to reduce the difference in the user experience of the stock camera compared to the application camera. Camera X is her best project to accomplish, A few tools can be easily translated for they are not the “salvation” we might think. We'll explain what the Camera X is, what the difference is with the current software and what it will allow.
What is CameraX
Google defines CameraX as the compiler library was created to facilitate the development of the camera application. This description is not very perfect, but we go through the parts. In other words, CameraX allows developers Include camera features already provided by manufacturers in your applications. In other words, put effects like HDR, night mode or traditional beauty mode on the phone's camera in a third-party application.
The summary is simple: CameraX is a library that allows manufacturers to use the camera functions of manufacturers in their applications.
From Google they confirm that it is "difficult to maintain and consistent camera behavior between applications". To do this, they have developed this series of tools that allow developers access the same functions available for a traditional camera app using a few lines of code.
Which brings it against the Camera2 API
Although CameraX sounds like something new, there are similar tools, such as the Camera2 API. This is is another interface designed for developers, developed from Android 5 and directed in this case to provide developers with advanced camera functions, such as hand focus, shooting images in RAW, exposure settings, white balance, etc.
The Camera2 API allows to use different functions on the camera. CameraX is focused on acquiring third-party apps with features that are already native
The Camera2 API has four levels (Legacy, limited, Full and Level 3). More level, most functions the app can run. In short, Google introduced the Camera 2 API to facilitate the development of camera functions Also, depending on the phone we use, we can enjoy more or less activities, depending on the level that it has.
The unique point of CameraX is that focuses on worshiping traditional cameras and third-party cameras, in addition to providing itself with a range of activities.
Why won't solve a quality issue in third-party apps
Once we've explained what CameraX is, it's worth a little analysis of what it offers and what it doesn't. Camera's first problem is that it's a library, not a built-in Android application. Translation? Developers will have the choice to work with it or not.
On the off chance that all the programs include CameraX (we want to assume that Instagram, WhatsApp and others will) we should make that clear this will not be the only quality issue in third-party applications. Google has already moved on with Visual Core, a chip that allows Google Pixel to process HDR + on Instagram, WhatsApp and other applications. Does this solve the quality problem? No. Adding jobs is always a plus, but it's something other than quality.
The biggest problem with Android apps compression and algorithms used to load images, much lower than iOS. In short, CameraX will arrive so that third-party apps are complete at work level, but quality will remain a pending issue.
