Google Photos tests locking Color Pop behind a Google One paywall
Throughout the year, we’ve seen evidence Google might introduce premium editing features to Google Photos that would be locked behind a paywall. Now, it looks like Google is slowly starting to implement those changes.
Shortly after we published this article, a reader in the comments section informed us that Google Photos’ Color Pop feature is locked behind a Google One membership. We’ve attached the two screenshots shared by the user, and we’ve also added two screenshots showing off the Color Pop feature in action (this was from a Google account that doesn’t have a Google One subscription).
Google first introduced the Color Pop feature to the Google Photos app in May of 2018, shortly after the company’s I/O developer conference. The feature essentially keeps the subject in color while turning the background black and white (or vice versa), allowing the subject to “pop.” It’s a fun feature, and seemingly one Google thinks is advanced enough to convince people to pay for.
It’s unclear what other premium editing features will be put behind a paywall. However, we recently uncovered strings of code in Google Photos 5.18 that suggest Google will introduce preprocessing suggestions and a Skypalette feature, which will include new filters to help users edit the sky.
The changes come on the heels of a major redesign to the Google Photos editor. The company also recently added a print service that will send subscribers 10 high-quality photo prints each month for $6.99. Google Photos has been one of Google’s best services since its introduction in 2015, offering free, unlimited storage for photos up to 16 MP. These new features might be Google’s way of trying to better monetize the service.
We reached out to Google PR for confirmation about the changes, but we haven’t heard back yet.
Google Photos (Free, Google Play) →
The post Google Photos tests locking Color Pop behind a Google One paywall appeared first on xda-developers.
from xda-developers https://ift.tt/36eLe0i
via IFTTT
No comments: