Minimal mobile apps for Android and iOS

expo go not working for me sadly

Good news, TestFlight let me submit my build despite not having the app on my OS. It’s only available for Internal Testing currently, so anyone interested in testing on TestFlight please DM whatever info you’d like me to add to these fields. They’re looking for an email, a first, and a last name.


Screen Shot 2022-02-17 at 11.20.47 PM



Update: Apple rejected our first submission because we need to implement App Tracking Transparency (apparently just having the user choose to allow or disallow cookies the way we have it set up does not meet their requirements in and of itself). Luckily, Expo has a module specifically for this. I will implement this module so we have this covered and resubmit ASAP!

Once our review has been accepted, we will be allowed to do public TestFlight builds (instead of just internal testing), as well as eventually have the app available for free download on the Apple App Store.

App Store Connect Rejection #1.pdf (47.4 KB)


Shouldn’t we remove the in app credits topup system first?

@auggod, can you elaborate on this? What is the relation between the topup system and a mobile app? I know there was a UI bug with it or two that was fixed in the past month or two, but outside of that I don’t know too much about it. Thanks!

This pull request enables requesting tracking permissions in a way that should appease Apple and is in line with their guidelines. I am creating a new build and will be submitting the new build to Apple for review when that finishes. Essentially, if the user declines permissions, we simply show them this screen and inform them that if they want to use the app they’ll have to allow them, which should be enough to satisfy Apple’s requirements (I’m hoping):

I’m not sure we should publish this app now.

Isn’t it just a test version to check bugs and everything?


Yeah, this is a test version. We’re still in the proposal phase here, but Peter has taken initiative to give us something tangible to look at and discuss. Appreciated!

@auggod, with your knowledge of our platform we’d all benefit from hearing more about your hesitations, what the roadblocks are, or what a better time for this would be. I know this is a tricky time for new things to arrive, since we are focused on the complicated transition off our wordpress infrastructure.

There could possibly be some complications with publishing this before we are off wordpress.

The main change Augustin is referencing is that the current player has a built-in page for purchasing credits. Once we finish QA testing (help needed!) and move off wordpress, we’ll have a more robust system for purchasing credits, paying for a membership, etc, but checkout will happen on a separate Stripe portal the user will be transferred to.

There could also be some complications involving the relationship between the player and the ID server where users manage and update their accounts.

It would take someone more knowledgable about apps, stripe, etc to get into these questions. @Nick_M could possibly help as well.

1 Like

You’re right @LLK, this is merely to prepare for approval and allow for public testing - which just means anyone with the TestFlight app can take it for a test drive. Don’t worry @auggod, I am not submitting this to the App Store for public download! It seems that the same review process that allows us conduct external testing via TestFlight (e.g you can test on TestFlight without privately sending me your full name and email) also allows for submission to the App Store, so this is pretty intrinsic to the preparation process of checking all the boxes and ensuring the app meets everyone’s requirements and is ready to go.

Again, this is just a quick little thing I got together just to tide us over (since it seems people keep asking for it). It’s very limited. However, it may (once we have other things together) be enough to satisfy an alpha stage (referring to this as even a beta would be far too generous in my opinion) and show we mean business, and allow us more time to provide full built-out native apps for both Android and iOS. Bugs users experience using this app should, in theory, be limited to bugs a user would experience when using in the default browser on their phone.

I completely understand (and agree) that the difference between creating a browser shortcut to our webpage and this app are, from a tech standpoint, basically indiscernible. However, given the current tech culture and the majority of folks’ knowledge/thought regarding these concepts, this tech does exist to easily bridge this gap.

Again, I have a lot of trust in @auggod’s knowledge and knowhow regarding Resonate’s ecosystem/infrastructure. I wouldn’t want to release this publicly if it wasn’t the right time or wouldn’t help Resonate grow and thrive. It may be that this is not an advisable route to take, and if that’s the case I assure you I fully accept that potentiality.

In the time of writing this, our amended build 1.0.1, was accepted by Apple, and should now be available for External Testing on TestFlight here: Join the Resonate Co-op beta - TestFlight - Apple (if that’s okay with everyone that is). For now, fear not, the Availability is currently set to Remove from sale so it won’t be showing up in the App Store.

Testing it now - tracks sometimes load slow and sometimes load fast. Tracks do naturally continue to the next track on the album and even while the app is in the background. One current limitation is the status bar: it’s a white bar at the top (my phone is in dark mode so presumably the time and the other information presented is also white so it’s just white text on a white bar. Could disable it completely by setting this prop to true, but newer iPhone users with the status bar surrounding their camera would probably still have a white bar by their camera (at least that’s how it tests in the simulator, I don’t have one of those new phones to test that on actual hardware).


Great - I’m on the testflight.

First feedback, the flow on create account would probably need to be adjusted before actual submission.

From the testflight app:

  • press log in
  • press join
  • am taken to this page

There’s a join on the top, some boxes with listener, artist, and label, and join now way at the bottom.

It’s not really clear to me how to join.

  • Tapping the largest join button and the one at the very top (the black one) refreshes the screen, not sure what these are for

Have login on the streaming app go to the listener login.

Offer an other option at the bottom like - “Are you an artist or label? Click here”


how does this work? I got access since you sent me the email.

is there a public link people can click to get the invite?

1 Like

Here is the public link: TestFlight - Apple

I realized I had to download the TestFlight app to my phone to enable the public link. The latest build 1.0.2 is still in ‘Waiting for Beta App Review’ though. I’m not sure why 1.0.1 isn’t there but my guess/hope is that this should be finally open to the public once the review is complete, now that the public link has been toggled on.

Do we have a test version for Android or is it just apple only right now?

@piper is working on the android @LLK

1 Like

Just as the #1 feedback, being able to use this widget on iOS is a game-changer. The browser shortcut doesn’t work this way. With the browser shortcut, when the screen goes to sleep (like it’s supposed to) the music turns off. With the browser shortcut I can’t listen to a playlist on my phone and do something else with my hands, since I have to keep on coming back to touch the screen to keep it awake.

With the expo wrapper it functions more like a music app.

Obviously it would be nice to have some tweaks (like show what artist), but since the point is to listen when the screen is black not being able to see it is not an issue.


If the iOS PWA doesn’t allow for screen-off listening, it is rather useless!

Android PWA has always had this. IME, it is functionally indistinguishable from an app, although a recent update by Google seems to have removed most audio control buttons from the widget :thinking:

On Android:

This makes even a “minimal” app indeed a game-changer for iOS. Any ideas why screen-off listening doesn’t work on iOS PWA?

1 Like

it says " This beta isn’t accepting any new testers right now. "

Apple approved the latest build, 1.0.2, shortly after you posted this, so hopefully the link should now finally be open for public testing now.


It looks like I’ll be able to publish apps on Google Play (for both testing and eventually publicly) once they verify my Google Play Console account:

Screen Shot 2022-02-20 at 11.00.36 AM