We currently have an English app on the AppStore and have decided to support another language. But I'm not sure where to start.
How should the app content be created to be able to support this? Should I just create two separate applications in their respective language and submit them both to the AppStore? Or do I have to create one app with some kind of mechanism that translates on the fly??
I somehow don't think that flooding the AppStore with multiple versions of my app would be the way to go (at least in the eyes of the Apple Review team).
Any ideas?
The usual way is to use the localization of iOS. You should not upload different apps!
See this link for a tutorial: How to localize an iPhone app
Related
We have an iOS app that we are currently looking forward to distributing to various clients in the live environment. We have several versions of the same app (version 4, version 5 and etc). Each client wants a different version. We need to handle multiple versioning of the app. We were searching the distribution options.
Ad-Hoc Distribution
App Store
In-House Distribution
Custom Apps
Searched various options that we need to follow in order to achieve the multiple versioning requirement but didn't find a clear answer. We were checking the Custom Apps options and had a few doubts.
Will it be a problem with multiple versioning?
If we need to submit an app with a different version do we need to submit it as a new app?
We would be grateful if someone give a clear thought about how do we need to handle this multiple versioning thing in the same app.
Please note that the app name and logo will be the same in every version.
I am planning on using DeviceCheckor indentifierForVendor to ensure that the same device is not being used to redeem multiple times the same gift (free money for example sake) offered to new users. I am wondering however, if it is possible to trick this system on a jailbroken device? Or using a custom simulator or a botnet (do iOS botnets exist?)?
I haven't tried it myself, but I think it is possible to change the bundle identifier, resign the app and side load it to your device.
This will change the change the identifier for both DeviceCheck and indentifierForVendor.
Now, for this to really affect you, the user needs to get a hold of the ipa. Which is getting increasingly difficult with the newer versions of iOS.
If you are interested in trying what I've discussed, refer to this link.
https://coderwall.com/p/qwqpnw/resign-ipa-with-new-cfbundleidentifier-and-certificate
And probably AirSign (much easier). Its a paid app for the Mac. https://www.macupdate.com/app/mac/51845/airsign
I'm currently working on my first iOS app (phonegap/cordova). I'm wondering if I need to take certain steps in order to make it available not only to the german app store (which is my language), but also international?
No you don't. By default it's distributed to all countries.
From the Dropbox API doc:
Use a single app key for each distinct app
If you build multiple apps, use one and exactly one key for each app
you make. This makes it much easier for us to debug issues when they
arise. That said, if you're just building the same app for different
platforms (for example, iOS and Android), you can use the same key.
It sounds like multiple-apps-single-key only makes it harder to debug. Does anyone successfully deploy multiple iOS apps with a single app key?
There are a few different scenarios mentioned in the Dropbox Platform developer guide you're quoting from, and it's a bit unclear which really applies to your question. To enumerate everything:
"multiple different apps (on the same platform)" e.g.:
MyCoolTaskApp for iOS
MyCoolTimerApp for iOS
In this case, you need to register different apps with the Dropbox API, which means using a different key in each (since they are different logical apps). Also, this way, users will see the different app names when they look at their linked apps list in their account.
"same app for different platforms" e.g.:
MyCoolTaskApp for iOS
MyCoolTaskApp for Android
In this case, you shouldn't register multiple apps with the Dropbox API, and you should use the same key in each (since it is the same logical app.)
"multiple versions of the same app (on the same platform)" e.g.:
MyCoolTaskApp for iOS Lite
MyCoolTaskApp for iOS Pro
In this case, you shouldn't register multiple apps with the Dropbox API, but due to a technical detail there would be a problem with trying to use a single app key in both, as noted under Can multiple versions of my app (e.g., free and paid) use the same app folder on iOS or Android? in the Dropbox Developer support FAQ. In this case, you should contact Dropbox Developer support for help with getting this set up correctly.
To answer your question overall though, each of these scenarios above have been successfully deployed by various developers, but you shouldn't deploy multiple different apps with the same key.
here is my question, i made an app and put on appstore, but i wish to charge the version without any iAd for 69p ...and the version WITH iad built in for free...
so, should I make two separte projects for each version?
and how do i make the free version with iAd should a pop up alert recommend user to go to appstore buy the ad free version?
is it just a normal UIAlertView with delegate method to call the App Store or open it as UIWeb in browser? how do i implement that?
any suggestions ?thank you very much
You can use compiler flags to wrap around your code so that you can have one source, and create multiple targets from the same project and build multiple apps (with different app identifiers and everything).
However, this causes you do have to manage two different apps in the app store (entering the same meta data twice), and deal with the review process on two different apps.
Also, people might skip over your paid version, whereas they would have installed your free version, and upgraded later.
I recommend that you have one source, one project, one target, and one app in the app store and use in app purchases (IAP) to turn off advertisements.