I understand where you're coming from with this comment. I'm also generally frustrated when I see people commenting on sensationalized headlines without taking the time to learn more.

I, however, have read their published plans for developer ID's.

Think back, and be objective about how Google has managed Android since AOSP launched. Time and time again, Google has borrowed and adapted code which was submitted to the project by talented, passionate developers who expected no compensation. At each milestone, Google has taken steps to apply additional restrictions on developers- Siding instead with hardware manufacturers to limit the public's ability to use their purchased hardware as they see fit.

I am aware that there is a balance that must be struck to limit expense, exploitation, and to prevent widespread security incidents and piracy, but how many times in the past have end users and developers been in this precise situation over the years? How long until Google decides that they don't need the AOSP project at all and fork the entire project? They've already taken large parts of the framework private.

Maybe I'm a little jaded, but I can't see a benefit here for anyone but Google and hardware manufacturers. This is just another step towards locking us out.

You do need to submit an ID if your app gets a larger audience. Plus, the account requirement stays. With the way google bans developer accounts I wouldn't be surprised if your hobby developer gets an axe once a while.

It's not hard to imagine them abusing/being compelled to limit apps based on regional restrictions or perhaps other apps terms of service. Like newpipe could be nuked out of nowhere assuming it even gets a say since it breaks YouTube's Terms of service.

Or manga, book reading apps getting the axe due to copyright strike. Plus, the devs could get doxxed again due to copyright strike.

No sane developer should risk submitting this personal information to google for a side or hobby or even a community project.