Camera AX and ROID API provided by Google are ready for third-party camera applications

Google already has CameraX and roid API, but knows very little about it. This was first heard at the Android Q AMA conference last year. Initially, the new mobile operating system of Android 10 introduced the CameraX Jetpack library and CameraX vendor extensions. CameraX was a highlight of the Android team last year. The API has great potential to help improve mobile photography, which is why Google decided to allow third-party applications to use it.

The camera on the Pixel phone may not be impressive, but CameraX API can help other OEM or mobile apps take advantage of new features and improvements developed by Google. With CameraX API, you can use super-resolution zoom, HDR, night view, and portrait modes. Pixel 4 phones have these features, and even other OEMs are copying them. Samsung, Yijia, Vivo, Xiaomi and OPPO all put forward their own photo functions.

For mobile app developers, they know that third-party camera applications can still be improved. Today's phones have built-in camera applications that use different sensors, especially when there are multiple cameras.

Not only are they useful, but unfortunately, third-party applications do not take advantage of their capabilities. These applications used to be unable to use other camera sensors, but recent updates have changed all that. Different OEMs can use different API on different phones, but the implementation is always for each device.

Camera application developers can now consider using CameraX API during development or update. In this way, mobile applications are compatible with most mobile devices. Hopefully CameraX API will solve the problems that need to be fixed and bring some of the best CameraX features that Android can provide through Jetpack support libraries (especially the CameraX library). This makes camera development more efficient and easier than ever, especially when using Camera2 API.