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.
Google Console closed testing requirements are awful
11–20 of 52 posts
Re: Google Console closed testing requirements are awful
#12Re: Google Console closed testing requirements are awful
#13Earlier 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.
Re: Google Console closed testing requirements are awful
#14Is 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.
Re: Google Console closed testing requirements are awful
#15Re: Google Console closed testing requirements are awful
#16Earlier 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.
Re: Google Console closed testing requirements are awful
#17Re: Google Console closed testing requirements are awful
#18Earlier 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.
Re: Google Console closed testing requirements are awful
#19It'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.
Re: Google Console closed testing requirements are awful
#20It'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.
It's hard to understate how little sense everything related to appstoreconnect and the dev account makes.