Looks interesting at first glance. Would you use Gmail aliases?
The main place where I see this working is people who want to use aliases with services that block aliases. Its harder to filter for @ gmail addresses compared to something like Proton or SL or Tuta, since mass blocks would be foolish.
Yes, if I would ever use Gmail, but I never will.
Hopefully mainstream providers introducing alias addresses will discourage companies from blocking alias addresses even from smaller providers like simplelogin and addy.io.
Hopefully. Although what is more likely to happen is whitelisting Gmail 
I never faced this issue with Proton Pass aliases nor with SimpleLogin.
Hopefully it’ll make alias usage a norm. Among the top help needed post on most privacy/security commmunity I’ve been part of was for recovering from leaked address and/or curbing spam. Turns out using just 1 address for everything might be as bad as using just 1 password everywhere.
Disregard how privacy invasiva gmail is, its the most widely used email service in the world. Apple did the same with the introduction of their hide-my-email alias but their userbase is far less than gmail.
Please read the original source. It appears this will be integrated on Android “Auto-fill with Google”. While there will certainly an integration with Gmail, it might also works with other providers.
From the “original source” (emphasis mine):
The APK on the menu this afternoon is the new 24.45.33 release of Google Play Services, and upon cracking it open, we find a whole boatload of strings referencing and in support of something called “Shielded Email.”
We were able to spot the Shielded Email feature in the Autofill settings menu. Unfortunately, tapping this option currently redirects us to an empty page on myaccount.google.com. Check out the screenshot below.
Seems fairly straight forward:
Also seems in line with ghacks coverage. Not sure what the original coverage also adds.
Other parties can already use the framework.