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.
Related
We've an Application which is already live and used by many users. Now that we've came up with newer Programming language and new backend. We have created a new version of the App with completely different programming language as the older one.
We have some users who are still using the older(Legacy services).
Is it possible to create a new App with different bundleId than the older App but the same Display name and also the same Screenshots in App store as the older App?
According to App Store Review Guidelines,
Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase.
The problem is, we also require the older App for some of our customers, who have not migrated to the newer services.
Does Apple allows to have exactly same looking apps with different bundleIds and same display name in App Store?
Any help would be greatly appreciated.
It is possible to set this new version up as a new app, you can even use the same screenshots. What you cannot re-use is the app name displayed to your customers on the App Store (Entered in App Store Connect). That is unique and you will get an error if you try to use the same name. You can of course use the same on device name (entered in Xcode).
As long as you do not spam the App Store with "copies" of the app, there should be no problem, I've seen this countless times and there are also some prominent examples of companies "phasing" out their old apps. It would probably appropriate to remove the "old" app from sale on the store in the mid- to long-term though.
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.
I have a situation where the app functionality required is identical for a number of clients. The clients, for marketing purposes, wish to have the app completely rebranded in their own respective company colors - which means different launch icon, display name, skins etc.
From a code perspective, this is fairly easy to handle, but from an App Store perspective, I am a little uncertain about whether each version needs to be submitted to Apple as a separate app or is there a way to submit a single version to the App store which embodies the different UI variations
Thanks
The only thing that's not doable is the icon. Apps on the App Store are not allowed to change their icon.
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.
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