> 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.
Google Console closed testing requirements are awful
21–30 of 52 posts
Re: Google Console closed testing requirements are awful
#22Earlier 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
#23[flagged]
Re: Google Console closed testing requirements are awful
#24If 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
#25Re: Google Console closed testing requirements are awful
#26Re: Google Console closed testing requirements are awful
#27Is 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.
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.
Re: Google Console closed testing requirements are awful
#29Earlier 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.
Publish a spec and people who want to will make their own tools.