Live data from Hacker News

Google Console closed testing requirements are awful

news.ycombinator.com

21–30 of 52 posts

Re: Google Console closed testing requirements are awful

#21

> I wanted to publish it to the play store, get exposure and share what I have made. It's not clear what you mean exactly with "exposure". But if you only care about sharing your work, it may be better to publish it on f-droid.

Play store is the de facto marketplace for Android apps, someone looking for a new game or application will often search the Play store...

Re: Google Console closed testing requirements are awful

#22
post #3

Earlier quoted context omitted.

Apple has its own unnecessary hurdles. Mostly around requiring xcode, which requires a mac. But yeah, both stores need to be forcefully opened. They're sitting on their laurels inside their moats.

I've just been using the MacOS runner in Github Actions. Still requires the $99/year fee but not the $2000 laptop.

I actually use codemagic.io which is free at my usage level. And amazing. Codemagic has repeatedly provided painless tools to work around Apple's artificial pain points.

Re: Google Console closed testing requirements are awful

#24

If you're using Flutter, you can start with just the web app. Flutter for Web is definitely not as good as Flutter for iOS/Android, but it's decent, and the web itself is far easier platform to publish on. Then, if people like the app, you can bother jumping through all those bureaucratic hoops and get it on iOS/Android natively.

This is probably the path I will go down, should be easier to get the testers if it's already got some users on the web. Still feels a little unfair that as a new dev, I have to jump through these hoops that existing devs and businesses aren't subjected to.

Re: Google Console closed testing requirements are awful

#27

Is this a new requirement? I launched a flutter app about 8 months ago and didn't need any testers. It's a free app though. Not sure if that makes a difference.

I hadn't come across this, but found https://support.google.com/googleplay/android-developer/answ...

It seems this only applies to personal accounts that were created recently (which would explain why I've not had any issues with recently created business accounts, nor my own personal account which is probably old enough to be in school)

Re: Google Console closed testing requirements are awful

#28

> I wanted to publish it to the play store, get exposure and share what I have made. It's not clear what you mean exactly with "exposure". But if you only care about sharing your work, it may be better to publish it on f-droid.

Publishing on F-Droid is good, but that presumably depends on releasing your app as open source/FOSS, which is not something every app creator will want to do.

Re: Google Console closed testing requirements are awful

#29
post #6
post #3

Earlier quoted context omitted.

Apple has its own unnecessary hurdles. Mostly around requiring xcode, which requires a mac. But yeah, both stores need to be forcefully opened. They're sitting on their laurels inside their moats.

The XCode requirement makes some sense because it would take Apple a lot of extra work to port and support their tools on other platforms. Work that they have no incentive to do. But I think the native app market in general has peaked. Most things can be done in a web app now.

The underlying assumption is that Apple is expected to port XCode to some other platform, rather than just using a third party tool on that platform like gcc or VSCode to make iOS apps.

Publish a spec and people who want to will make their own tools.

Re: Google Console closed testing requirements are awful

#30
post #8
post #5

What are the price quotes for getting the required testers part fulfilled?

I've seen anywhere between $5 - $50 for a <50mb application.

What sort of testing will you get for $50 paying 14 people? Seems rather pointless because no one will take that task seriously
Post reply on HN