Live data from Hacker News

Google Console closed testing requirements are awful

news.ycombinator.com

11–20 of 52 posts

Re: Google Console closed testing requirements are awful

#11
post #7
post #5

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

Beware of spammers providing these services, it's an easy way to lose it all.

Definitely not worth the risk. I think all this policy is going to do is reinforce the already strong incentive to launch first on iOS and only consider an Android port once you've validated your idea. And the Android ports are going to be outsourced and often not very high quality.

Re: Google Console closed testing requirements are awful

#13
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.

Do you have an example of this workflow? Are you developing outside of XCode on a non-macOS platform in Swift and then essentially compiling and packaging using GitHub Actions?

Re: Google Console closed testing requirements are awful

#14

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.

Yes it began afaik for any new developers joining after November 2023 for any type of application. If you have an account registered as a Play Store developer before Nov 2023, it's not required...

Re: Google Console closed testing requirements are awful

#15
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.

Re: Google Console closed testing requirements are awful

#16
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.

Distribution and retention still vastly better on the app stores. Haven’t seen a successful web app match polish on mobile either - react native etc. do though but only when distributed as a native bundle.

Re: Google Console closed testing requirements are awful

#18
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.

I'm more hopeful about Apple porting a proper version of Xcode to the iPadOS, and I'm not particularly hopeful about that either.

Re: Google Console closed testing requirements are awful

#20
post #2

It's a dumb & very counter-productive policy and will choke off the supply of new Android devs. Ironically it's now much easier to launch a new app on the Apple App Store than it is on Android.

I've done both and I'd say Apple is still lagging behind even with this stupid move from Google.

It's hard to understate how little sense everything related to appstoreconnect and the dev account makes.

Post reply on HN