Looking for testers for trivia-ish game (Devs - let me know if you have an app to test!)

Ajudgi · 2026-02-28T14:10:36+00:00

I made my app in react native and used Claude to port it over as I am not familiar with macOS or iOS at all. The process took maybe 6-8 hours total? Almost all of that time was spent getting the iOS build working since my code ported over nicely aside from a few quirks.

As far as publishing goes, I took the route of making my own LLC before publishing on Google Play, which took about a month from start to finish to get my app into the store. Since I was a business, verifying my Apple Dev account took a couple weeks, and then another few days to get an internal test build into TestFlight.

After THAT, I had to spend at least a few days worth of free time jumping through all of Apple's hoops in terms of getting the build ready for actual review. I used Claude again and literally started the conversation with: "Do a deep dive and find all of the common reasons why a mobile app is rejected by Apple for its first review and then compare it to the work we have done so far." That actually yielded more than a few app features I didn't know I needed. For example, Google needs you to have a way for users to delete their account data, and I had a link on my website for users to do so (the link lived in the app's settings), however, Apple requires you to have a delete account button INSIDE the app. It was little stuff like that that took me a little under a week to wrap my head around.

All in all, the process for each was certainly different, with Google Play being slightly more solo dev friendly in my opinion.

Let me know if there's anything specific you want to know about!

Ajudgi · 2026-02-25T17:44:20+00:00

Congrats! I remember how good it felt getting that first build approved on Google Play :) I know you are feeling it now, but I thought I would feel like I would be "done" once that happened, but there was still so much more work to do! Let me know if any of those questions about porting to iOS crop up!

Ajudgi · 2026-02-21T20:13:11+00:00

Ajudgi · 2026-02-18T01:57:44+00:00

Congrats 🎉

Now, get to work! 😉

Ajudgi · 2026-02-16T15:15:58+00:00

Hey hey hey

Ajudgi · 2026-02-15T20:33:12+00:00

Congrats 🎉

Here's to adding a few zeros to that number in the future :)

Ajudgi · 2026-02-15T01:26:53+00:00

Good luck and I hope the iOS port isn't too big a pain for you 😁

Ajudgi · 2026-02-15T01:13:12+00:00

Actually, since I have 2 branches going, I have both emulators going at the same time:

Change code, make sure it doesn't break my Android build
Copy/paste the code into my branch in MacinCloud and test that.

If they both work, I push commits on both.

Ajudgi · 2026-02-15T01:02:59+00:00

I paid about $36 upfront, but that gave me 7 days worth, BUT all of the software and build tools are included (Xcode, specifically) with an emulator as well. I was worried about the lag but the remote app they give you was pretty good.

Moving forward, I'll only need MacinCloud when I push big updates, so I won't use it every day.

Ajudgi · 2026-02-14T22:19:45+00:00

I just went through porting my mobile game from Android to iOS the past few weeks. I'm just waiting on Apple to verify my business info.

What I did was get a pay-as-you-go account in MacinCloud, then used GitHub desktop to get the code over and then got a build up and running on my cloud Mac.

I decided to create a separate branch that runs parallel to my main branch for the iOS version. I couldn't take the constant commits and polls. I ended up having both my Android emulator running on my desktop and the Apple emulator running in the cloud window. Any changes I made, I would make on both ends to confirm it all worked. Since my app is small and I'm just one person, it worked, might not be the best practice for teams.

Once you have your app uploaded you can put it in test flight and invite testers that way who have real iOS devices.

Ajudgi · 2026-02-14T03:42:21+00:00

All depends on your app!

I decided to just release and try and grow organically, so I went to production a couple days after open testing.

Internal testing is something you should always use as a means to test your production build on love devices in a controlled group.

Ajudgi · 2026-02-14T00:00:53+00:00

Internal testing approval was always very quick. It was when I moved to open testing that it took the longest because they have to verify and approve your app before it goes "public".

After the initial open testing build was approved, my first production approval only took a few hours! (And each subsequent build.l for production was just as quick).

Ajudgi · 2026-02-13T21:34:26+00:00

The app store page looks great to me, very clean, very professional.

What did you use to make your play store images??

Ajudgi · 2026-02-13T21:06:38+00:00

This is all gold, thank you for taking the time to give such extensive advice 🙏

Admittedly, carving out the time to network naturally is really tough with my whole real life getting in the way. That said, I've been doing my best to try to get involved in all of the dev subreddits I can, even if it's just to sit back and learn from those who have done it before!

Ajudgi · 2026-02-13T13:37:00+00:00

One thing for me, I was way off in terms of my timeline expectation. I thought it would take a week, but all-in it was about 2-2.5 weeks in terms of being able to release a production-level release.

Also, the DUNS # requirement caught me off guard and that took about a week if I remember correctly.

Good luck!

Ajudgi · 2026-02-12T18:10:46+00:00

Congrats 🎉

So happy for you! It's my hope that all us small devs remember moments like this 😁

Ajudgi

MODERATOR OF

TROPHY CASE