CODEWITHSUNDEEP
android
Andy A
Andy A

Reputation: 4301

How to publish an almost identical version of my android app in a different location

I have released an android app downloadable in the UK, but I wish to release a (very slightly different) version of the app for the U.S. Currently I believe I need to do the following for the new version of the app ...

1. Change the 'package' attribute in the manifest file to something different.

2. Ensure that on Google Play only the US can download the app.

Is there anything else I am yet to discover I need to do, or any other problems I am yet to consider?

Edit 19th July 13:19 GMT - I am currently warming towards using TelephonyManager.getNetworkCountryIso() as an initial country guess, and falling back on the locale if this fails (because of no SIM card). What do people think? Using GPS is also an option though, but is that overkill?

Upvotes: 1

Views: 186

Answers (3)

Andy A
Andy A

Reputation: 4301

I eventually decided that the best policy was to use TelephonyManager to check the country of the Network.

TelephonyManager tm = (TelephonyManager)context.getSystemService(Context.TELEPHONY_SERVICE);
String networkCountryCode = tm.getNetworkCountryIso();

If that failed, I got the locale. 

String locale = context.getResources().getConfiguration().locale.getCountry();

This would happen once at the start of the app. The results of this would then be saved and be configurable in the settings screen.

Upvotes: 0

Kevin Coppock
Kevin Coppock

Reputation: 134714

Since you say you're just changing a couple of strings (we'll think of the URL as just a string, too), I would suggest the following:

  1. Create the resource directories res/values and res/values-en-rUS.

  2. In each of these, create a strings.xml resource file

  3. Define your default (UK specific) string values in the res/values directory, and your US specific string values in the res/values-en-rUS folder.

Then, to refer to these strings, simply use @string/my_string_name when referring to them from an XML document, or getResources().getString(R.string.my_string_name) when referring to them from code.

For more details on the types of resource qualifiers, check out this page, also for the list of qualified country codes you can use, see this page.

I'm sure anyone determined enough could change their region to US -- I'm honestly not sure offhand how the region is determined -- but for all intents and purposes this should do the trick without having to maintain two separate applications. I would just evaluate how critical it is that UK users be unable to access the US specific functions of the application, and with that in mind determine whether it is worth the maintenance of two applications.

EDIT Some more additional searching leads me to believe the region is locked into the build.prop file, which is not editable outside of rooting your device (i.e. it is not going to happen accidentally). That said, if it's still imperative that they have the correct option, I might suggest a popup dialog only on the first run of the application that confirms the locale with the user, saves it as a SharedPreference, and then choose your Strings programmatically based on that preference. That way you're still only maintaining one application, but you still have the flexibility of handling the two regions.

Upvotes: 1

Daniel Lockard
Daniel Lockard

Reputation: 615

This is correct. The Play Store goes off of two things for who can download and if they can update. The first is the packagename com.andya.myukapp -> com.andya.myusapp should work, as long as none of your existing customers are expecting to switch freely between the two (assuming it's a paid app)

Upvotes: 0

Related Questions