While that may be just some paperwork and a small expense, the next requirement is more insidious: “a phone number and email address for Google Play users to contact you”. I’m fine showing an email address, but I absolutely do not want my phone number to be available to anyone on the internet. (Even for phone calls. But remember that a phone number is used for much more than phone calls these days.) And that’s just me, a privileged hetero white cis dude who is unlikely to be the target of harassment or doxxing.

Yup. For small developers (FOSS or not) that don't make money which can insulate them from this kind of stuff, it's a no-no.

Fuck them for these games. It's an abuse of their market position.

Does Google offer a phone number for me to contact them about problems with their half-assed products? I've tried lots of times to reach a human being, but never raised a response as a private citizen.

A phone number? Hard fucking pass.

Fuck google. I just want to be able to play minit on my phone, but no, Google says it's not good enough for me because they haven't updated the app in a while. You know, like most games. Of course they haven't updated the app, the game is finished, they've moved on from it.

It would be much more customer and developer friendly to allow linking a service portal instead of providing a phone number. I would go insane if a user called me directly every time one of my projects had a bug or some perceived (non)issue. No, that's not how this works.

They removed the requirement for a DUNS for individual developers, so I switched my account to individual from my previous LLC. My LLC has been inactive for a long time and I didn't feel like changing my address with the IRS and all that. But all of my apps are free.

But the real issue is they keep making it more difficult to keep the app active. There are so many documentation requirements that I just didn't have time for, so my apps which are really old got removed over one of those new requirements a while back. I fixed a few like making it an adults only app because it has a recipe for mulled wine. But it just wasn't worth all the other stuff and I haven't wanted to recompile in the newer SDK. If I could do it without making any changes to the code it would be fine, but there's been too many changes. One of these days I'll update it, but I'm one of the few people who even use my apps, so it's not a big deal.

This paperwork is required by EU regulation (Digital Services Act - DSA).

It is theoretically possible to be excepted but I doubt OP has any chance there.

As a developer myself, I'm not really sure where I feel on this. I can definitely see where this would hinder people's want a posting on the store and suppress their creativity, but I can also see why they're requiring it.

I couldn't imagine publishing an app without some form of ability to reach out to report bugs or reach out for support, cuz at that point what's the point of making the app if you're not planning on having people use the app.

That being said, the entire publishing a DUNS number I struggle to feel bad for, they went down the same route that I've done in the past where I've registered as an organization because organizations have less information that's had to be obtained, but because of that you're expected that you're doing it on a more commercial scale, which also means a more complicated and sometimes pricey system. This requirement would not have been the case if they hadn't set it up as an organization in the first place and just put it in as a one person development project, that would have required putting more personal information.

All in all, the information that is required from developers doesn't seem unreasonable, it's basic things that as a user you would want, and as a developer you should want to telling your users anyway.

As for the API requirements, I understand why they want to push the newer API levels, and nothing's more aggravating from a user's point of view then downloading an app only to find out that it has barely been upgraded since Kit Kat and still requires every permission under the moon to operate because it doesn't integrate with the newer permission systems, but I can understand that if you're relying on features that the API versions required that finding the new way of doing things isn't always an easy task, even when there's a super simple and easy to read article that says the changes between API levels like Google provides.

Nonetheless I don't think the API requirements are there as a way to cause a hindrance to the developer, I believe they're there to force developers to use the newer standards and it also acts as a way of knowing which apps are still being actively maintained, because really apps that are no longer being maintained don't really have a place on the Play Store. They already have a huge issue of abandonware apps, which gives Google play a trashy/unmaintained feel that their competitors (i.e Apple store) doesn't have, I can understand why they are finally putting a stop to it

Hopefully more devs switch to f-droid.org or start their own repositories ;)