I have an iOS app in the App Store and I want to use my app in different countries. So I wonder if it's possible to upload a different version for each country.
For example, I want to update Turkey's app but I want to hold the old version of an app on the UK market.
There are essentially two options to consider:
Using localized models/controllers in order to display a different content to users with different locales. Here's the Apple Developer guide about localizing your app.
Creating different configurations with different Bundle ID suffixes and treating the them as separate apps. You can read more about configuration handling here.
I'd recommend the first one for most projects, since it's easier to handle one app than several ones. However, it's up to you and the project which one you'll choose.
You cannot hold a version in different countries say for example If your app is published in 2 countries then next version will be automatically available in that 2 the countries because does not allow it.
If you want can add or remove the countries but if we talk about version holding on some countries that is not possible
Related
Current issue: How do we efficiently deploy different versions of the same App to different customers?
Example:
App version 1.1 needs to be installed for customer A.
App version 1.2 needs to be installed for customer B.
App version 1.3 needs to be installed for customer C.
App versions 1.1, 1.2 and 1.3 are basically the same application with small differences between them (probably different backend versions required). Some features might be missing or might be extra on some versions depending on customers explicitly wanting them or not, or the branding might be different: different logo, different theme etc. It is basically the same codebase but with variations specifically asked by the clients.
We need a way to publish the app and indicate to our customers which app version they need to install. What options do we have?
I would really appreciate an answer from someone who dealt with this kind of situation before.
If you are planning to give application with slightly changes by features to different users. Firstly you can only submit 1 final build on the App Store. There is no such option for uploading separate versions on the store while keeping the old version.
But if you have fixed set of users than you should have some of the options like :
First option is you can upload 3 different distribution builds on TestFlight & invite the users on the specific build where you wants them to access the features
Another option is you can create the links on the online link services from where you can generate the links for the app & you can distribute that links to the specific users
Last option is you can create a single build only but you can control the features hide & show on basis of APIs & by that way you can give the access of specific features to the relevant users only
I hope this will help everyone.
After referring already discussed references -
https://developer.apple.com/internationalization/
https://www.raywenderlich.com/64401/internationalization-tutorial-for-ios-2014
https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/AppStoreTerritories.html#//apple_ref/doc/uid/TP40011225-CH18-SW1
https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPInternational/Introduction/Introduction.html
https://forums.developer.apple.com/community/app-frameworks/localization
Multilingual app in App Store; use two versions - or use apple localisation? (special case)
I understand below possibilities, but no solution! -
Have one universal/generic app, and add internationalization and localization as per user language and manage features accordingly.
(This is based on language of user, not country or store so would not serve my purpose)
Have different apps with almost same features but having country specific changes (due to some country protocols/requirements), and release each for specific countries/store only.
(Possible solution, but will it carry a risk of app store spamming
with similar apps even if those are in different store? and certain
risk is to maintain separate code base)
What could be the best way to serve different countries with their slightly different requirement in the main app?
I would recommend to have one application and in which based first you fetch the location of user and based on that location you can load the assets or code based upon the country.
I have a mobile app developed for number of different companies on AppStroe. Each company is using different endpoint to server/icon/logo. I have managed to add this in custom plist file and according to companies endpoint, I switched to different build setting.
Now these companies are going to different ways of authentication. One is using another app to authenticate and one is using server calls. Also for one company I am receiving datas one from server call and other one from local files.
I have to handle different login behaviour for different projects. It is mostly display/disable some extra views. I don't want to have two repositories or branches. Because almost %85 of functionalities are same. I want to add functionalities same time to both and some times to only one of them and run my tests and all.
I am looking for some way way to manage this app to maintain most functionalities and keep it only one app. How can I do that? Any suggestion?
This is a very old problem. Basically you have two options: build time and run-time; from your description it may be that you need a both (I would not trust configuration to drive my authentication code).
Build time means using conditional compile (e.g. Which conditional compile to use to switch between Mac and iPhone specific code?) and a different build profile for each customer. I assume that Xcode Targets (see How to manage the code of multiple, very similar Xcode projects) allows you to define different build profiles.
Run-time checks maps to Feature Toggling.
I suggest not using version control to manage nuances of the same application because it quickly becomes a merge nightmare, even with Git.
Initially I had a single app registered with Flurry.. we used this app pre-launch for testing etc.. and flurry captured all the data from my testers etc. We have recently launched the app and basically made flurry only capture the data from live users (ie so that it doesn't get polluted by our testers actions).. is there a way to instruct flurry to erase or hide all the data it captured prelaunch and just show us the post launch data?
One of way of doing this is to select which version u're interested in looking at
the problem with this approach is that it only gives you stats for a single version..
another approach is to simply delete the versions that contains the polluted data.. this way you can go over the results of all the versions that have accurate data
Flurry recommends that you create two or more projects for each app. You can use one project for development and testing and another for the published version of your app. Just don't forget to swap the api key when you publish the app.
This also has the benefit of splitting your versions up so you do not approach the limit of 1000 versions per project.
Alternatively you can use the timeframe filter to remove data that precedes the publication date of your app.
I am trying to use google in app billing to make my application sell able . In my app I have wallpapers some of which are free others have different prices I am really confused how to set different prices to different wallpapers because my whole application is one apk and I am not finding way to set different prices using the same apk. Is there a way out or am I missing any information
Strange why i was unanswered but simply adding new products at in-apps menu solved my problem using different produid as SKU i could set differnt prices of different wall pappers