Last Week

Well, last week didn’t go quite as planned. My main goal was to integrate RevenueCat’s functionalities into my app’s view models. This would allow the app to display paywalls and handle subscriptions. Unfortunately, that task got pushed back. I had friends visiting, and they’re actually still here as I’m writing this – seeing them off tomorrow!

The good news is that the RevenueCat SDK is already in the project, and the data layer for it is complete. It’s just a matter of connecting it to the view models so the user interface can interact with it. That’s now top of the list for next week.

What I did manage to accomplish was setting up a Google Group for the first batch of alpha testers. This is a crucial step because, as Google Play Store requires, any new app needs to be thoroughly tested before it can be published. They stipulate that you need at least 12 testers to give it a good run-through. I’ve started recruiting, managing to get about six or seven friends and family on board. The slight challenge is that most of them are iPhone users, so finding Android testers will be an ongoing focus in the coming weeks.

While setting this up, I ran into a bit of a snag with Google Play Console. It turns out you can’t use Google Groups that are created from within a Google Workspace account (like the ones tied to a custom domain for a business). You have to use what I learned are essentially “public” Google Groups – the standard kind you create at groups.google.com. That was a bit annoying to figure out, but it’s sorted now.

My app is getting there; it’s mostly feature-complete. The main things left are some user experience polishing and, of course, getting that RevenueCat paywall fully operational. I’m still aiming for a first alpha release to testers on Android within the first half of this year. Looking at the calendar, time is definitely ticking. I have about four full weeks left to work on this before I’m away for a bit, all before that H1 deadline. So, the pressure is on!

What does it mean in English?

Last week, instead of working on the part of my app that will handle payments, I focused on getting ready for people to test the app. I created a special email group for these first testers. This is important because Google, who runs the app store for Android phones, wants to make sure apps are well-tested before they’re available to everyone.

I also hit a small roadblock: the type of email group I usually use for my business doesn’t work with Google’s app testing system. I had to create a different kind of group, a more standard one, to manage my testers. It’s like needing a specific type of key for a specific lock – the first one I tried didn’t fit!

Nerdy Details

Setting up alpha testers for your Android app via the Google Play Console is a common step, and using Google Groups can simplify tester management. Here’s a breakdown, including the Google Workspace group issue I encountered:

Why Use Google Groups for Play Console Testing?

Google Play Console allows you to manage testers for your closed testing tracks (like alpha or beta tests) by specifying their email addresses. Instead of manually entering dozens of emails or uploading CSVs every time, you can link a Google Group. Any member added to that Google Group automatically gets access to the test build (after opting in).

The Google Workspace vs. Standard Google Groups Issue

This was the hurdle I mentioned.

  • Google Workspace Groups: If you have Google Workspace (formerly G Suite) for your domain (e.g., [email protected]), you can create groups within your Workspace Admin console (e.g., [email protected]). These groups are often designed for internal organization communication.
  • Standard Google Groups: These are created at groups.google.com and typically have an @googlegroups.com email address (e.g., [email protected]).

The Google Play Console specifically requires that for tester lists managed by Google Groups, you must use a standard Google Group (with an @googlegroups.com address). Groups created and managed solely within the Google Workspace Admin console for your custom domain are generally not compatible for this purpose with Play Console. The Play Console needs to be able to reliably resolve the list of members, and Workspace group permissions or structure can interfere with this.

Steps to Set Up a Google Group for Play Console Alpha Testers:

  1. Create a Standard Google Group:

    • Go to https://groups.google.com/.
    • Click on “Create group”.
    • Group name: Something descriptive, e.g., “MyApp Alpha Testers”.
    • Group email: This will be auto-suggested or you can customize it (e.g., [email protected]). This is the email address you’ll use in Play Console.
    • Group description: Briefly explain the purpose.
    • Privacy Settings:
      • Who can search for group: For a closed test, you likely don’t need this to be public on the web. “Only group members” or unchecking discoverability might be fine. The key is Play Console’s access.
      • Who can view members: “Group managers” or “All members” is typical.
      • Who can join group: For an alpha test, “Only invited users” is most common. You’ll add testers manually.
      • Who can post: Decide if testers can email the group or only managers.
    • Click “Create group”.

  2. Add Members to Your Google Group:

    • Once the group is created, go to the “Members” section.
    • Click “Add members.”
    • Enter the Google Account email addresses (Gmail or Google-linked emails) of your alpha testers. You can also add a welcome message.

  3. Link the Google Group to Your Play Console Test Track:

    • Log in to your Google Play Console.
    • Select your app.
    • In the left navigation menu, go to Release > Testing > Closed testing.
    • Either create a new closed test track (e.g., “Alpha”) or select an existing one to manage.
    • Click on the “Testers” tab for that track.
    • Scroll down to the “Manage testers” section. You’ll see options to add testers by email lists or Google Groups.
    • Select “Google Groups”.
    • In the field that appears, enter the email address of the Google Group you created (e.g., [email protected]).
    • Click “Save changes” at the bottom of the page.

  4. Tester Opt-In:

    • Once you’ve added the Google Group and uploaded a build to this track, Play Console will provide an opt-in link.
    • Share this link with your testers. Members of the Google Group (and any individual emails you might have added) will need to click this link to confirm they want to be testers for your app.
    • After opting in, they can download the test version of your app from the Google Play Store.

This setup ensures that you can easily manage your list of alpha testers directly within Google Groups, and Play Console will automatically sync with it.

Next Week

Alright, with the tester group foundation laid, next week the absolute priority is to get back to RevenueCat. As I mentioned, the SDK is in, the data layer is done. The mission now is to hook up RevenueCat’s functions within the app’s view models. This means making the actual calls to display paywalls, initiate purchases, and check subscription statuses, all triggered from the user interface.

The goal is to have the paywall fully functional within the app. This is a big piece of the puzzle, and I’m keen to get it checked off the list.