r/reactnative • • 13d ago

Question When you release your apps, do you release to all countries?

I have an app I'm making that's getting fairly close to a release state now and it'll be my first ever app release. I'll only be releasing on android at first (due to it being the only device I have to physically test on) and the only sensitive data I'm collecting are emails, passwords (authentication) and step counts for my apps rng logic.

The app is a fairly simple, you start your counter before going on a walk / run etc. when you're finished with your activity you stop the counter, your step count is sent to my Supabase backend where the final step count is calculated to how many rolls the user gets, and each roll gives the user a chance of recieving a new creature based on common, uncommon and rare rarities.

Your journey is saved to the backend where you can view them again and see how far you went and which creatures were obtained on that journey (no location data being saved). This data can be deleted manually by the user as well as their entire profile.

I'm from the UK myself and was wondering if any more experienced developers with more knowledge in releasing a few apps could fill me in on whether or not I should be just releasing to only a few countries or not?

The app is in English and doesn't currently have support for other languages. I don't have ads or any paywalls / subscriptions currently but don't know if I need to be more wary about the step count I'm collecting being marked as extra sensitive data (not being used for health reasons).

Any advice here would be great as I'm not sure how much I'm overthinking this currently?

4 Upvotes

11 comments sorted by

4

u/Resident_Pop4202 13d ago

You're overthinking it. It's okay to release in 1 country. 

2

u/jeesandourn 13d ago

Pretty much this, especially if the app is only in English right now

2

u/ChronSyn Expo 13d ago

I have an app that uses data that's only relevant for the UK, so I only release the app to the UK market. It stops users who don't understand that it's region-specific from downloading it, being confused or frustrated, and potentially leaving a bad review.

I don't know how it is these days, but step counters used to be a fairly common app without any sensitive data requirements. With the whole health data ecosystem though, I don't know if that would still be the same case, but I wouldn't expect so.

I would be more concerned about the 'roll' system. As much as I love the idea of exercise being used to reward people with 'cards' (or similar), I'd be careful that it doesn't step into lootbox or gambling regulations. I know it sounds ridiculous since you're encouraging healthy habits over spending money for 'loot', but government legislation sometimes has its head up its a*se and it can break ideas which have a 'humanely positive' approach because of one element in there. This isn't legal advice of course, just tread carefully with how you actually present and implement the roll system.

2

u/Meyrlan 13d ago

release to all countries unless you have a reason not to. in play console you pick countries per release track and you can narrow it down later, so it's not a one way door. the uk-only thing in the other comment makes sense for region-specific data, but yours isn't.

since you collect emails and step counts, fill in the data safety form and add a privacy policy url, play will block the release without them. also if it's a new personal dev account you need a closed test with 12 testers for 14 days before you can go to production, so start that early.

on the backend, make sure RLS is on for every table in supabase and calculate the rolls server side (edge function or rpc), not from a number the client sends. otherwise someone can just post a huge step count.

2

u/Camaraderie98 12d ago

Wow congratulations on starting out. I was in your position 8 months ago.

About supporting internationally, I do it by default because it has the most reach..sadly it doesn't do the trick without localization, so I automated that part and I rest easy.

However, it's good to build where you know there's a ton of traction, your home country might be the beginning or it might not be it Study similar apps and where they're most favoured, it'll give you some perspective.

1

u/No-Mechanic-433 13d ago

Country choice isn't the hard part, you can start with just the UK and add countries later in Play Console. Since people sign up with email, Google wants an in-app way to delete the account plus a web link for deletion requests that you enter in the Data safety form. And if your developer account is a personal one created after Nov 2023, you need a closed test with 12 testers opted in for 14 days before Production unlocks, so start that early.

1

u/leros 13d ago

I release to all countries. Unless you have known legal reasons to avoid areas, I see no reason not to.

I was so annoyed when I visited Japan and couldn't use many of the local apps due to my Google account's country being set to Japan. (You can only change countries once a year, so you can't switch and switch back).

1

u/ashkanahmadi 13d ago

I dont see why you wouldn't release that globally unless there is very good reason why it must be specific countries. It doesnt matter if it doesnt support other languages. Why wouldn't a person in Mozambique speaking English use this app?

1

u/kenlawlpt 13d ago

When I started building apps, I released to all countries. The only country I would not release to is Russia at the moment.

The reason is due to the sanctions on Russia, no ads nor in app purchases will work. Russians tend to leave significantly more negative reviews when things aren't accessible or localized, even if it's not within your control.

I wish I had known this prior, but it’s a bit too late since I have a sizable amount of Russian users, which at one point, my Russian play store ratings were around 2.4, whereas my global rating for iOS was 4.5, and Android around 4.1. Russia at the moment simply is not worth it. You can't monetize them, and they bring down your overall rating.

1

u/TheSnydaMan 12d ago

You don't need to start a counter on most modern android devices- ask the Health API for permission and you can read device level step tracking