This isn’t a unique idea, but thanks anyway to Zenarus for being the first to dare to share this idea.
Many people in these industries thought of this when QR verification first appeared. However, as the many people mentioned, this isn’t a simple matter. It only makes sense if you can do it at a low cost.
The direction is absolutely right. Google accounts are essential for the industry. The solution will indeed come through this path, but not in such a superficial way!
With this approach, you can only create a few long lasting accounts, and the cost would be very high.
You could create a new emulator for each Gmail with a unique fingerprint and proxy, but in that case, why create Gmail elsewhere and then verify in emulator? We might as well create it directly inside emulator.
I have my own antidetect browser and automation software, which I can confidently call industry-leading class. Currently, using my own mobile proxies, I’m achieving around a 40% rate of avoiding QR codes. That’s acceptable for now, because once a Gmail account is successfully opened, now it’s much easier to work with that account afterward.
It seems Google moved the security barrier to the beginning (QR verification) to reduce costs and loosen the checks in later stages. So if you successfully create a Gmail account, it’s now easier to activate services like Cloud or Ads.
In short, 40% is acceptable for now, but this won’t last. At this point, we need to solve this issue through the approach being discussed here, but in a deeper, more comprehensive way.
Instead of trying to complete QR verification inside emulators, may be we can create Gmail accounts directly in emulator, automation there is also possible!
I plan to start working on this topic soon. If I make any progress, I’ll be happy to share updates with you all.