For instance, an ecommerce app that offers return functionality may need some proof of damage to the products. They don’t necessarily need to build a camera feature. So they rely on any other camera app of your choosing. Now, users of Android version 11 and above will be forced to use the default camera app for that. Or use any other camera app, and upload photos from the gallery. The new behavior, spotted by Android Police, is documented in the Google Issue Tracker. A Google engineer said this move is to protect the privacy and security of users: In addition to this, Google will also prevent these apps from using its own camera interface. So, if you’re an app developer, you have to rely on the default camera app. While this makes the handling of the not very common case mentioned here more complicated, we believe it’s the right trade-off to protect the privacy and security of our users. A lot of users use third-party camera apps to take photos with filters or effects. While you might not encounter camera pickers ever so much, it’s a bit of a bummer for Google not to provide this option. Moreover, it also goes against the open Android values that Google takes very often pride in. Did you know we have an online event about digital art coming up? Join the Form Track at TNW2020 to explore how technology is changing how we create, experience, and share art.
