Now I have a major feature to release and I want to see the impact of it on a specific app store. The question is, if I submitted the app to the store and approved it.
Would it kill all other instances on all stores and my app would be available on that one specific AppStore?
It's not possible to "soft launch" an update by itself via iTunes Connect (only new apps by choosing the available territories for sale).
If you change the availability of your app to one country, users would not be able to download/purchase/update your app anywhere else, which I guess is something you don't want.
But it's definitely something you can hard-code. (Question is, if you really want this/it makes sense)
I don't think so , since when releasing a new version it automatically remove the previous ones from the store , so the new and only version is valid for the territories you select.
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.
I'll clear myself, is it possible to add my app to iTunes Connect and add my binary and if all is good then put it on hold (mean, wait with the publishing, but the app will get accepted and publish in 1-2 weeks)?
You can control the your app release,
because in nearest past i have updated my app and in app control version it will ask me for releasing automatic or i will release after approved,
Yes, you can decide the date of publishing on iStore, and change it whenever you want.
Whenever you add a new app or want to upload the new version on the app store. You are asked for the two options
Automatically release - That you want to publish the app as soon as apple reviews the app. (this means app will be immediately become live if apple reviewed your app and don't find any issue)
I will release - that you want to make your app live on a specific date. (this means once apple reviewed your app still app will not be live until the user doesn't want)
Hope this will help you. Happy coding :)
I have an app on the iOS app store at the moment, and I've been asked to make it available on more stores. I can't see how I can change this (or even see what stores it is on). I tried adding a new version to see if the option becomes available but I still can't see where I can put it on more stores.
Thanks!
Log into iTunes Connect. Manage your apps. Choose your app. Click on "Rights and Pricing". There's a link for choosing the countries.
My client is planning to release an iOS app (call it A) on the App Store which only has value for a limited time (say, a few weeks). After that time, they want to release another, basically completely different app (call it B), with functionality that is related to app A, but much more general. B will be built from scratch and will reuse no code at all from A.
They want to release B as an update to A, so as to retain their user base. Technically this should be no problem: we can change name/icon/metadata, as long as we keep the Bundle ID the same. But will this be a problem with the review process? Could Apple decide that it would be confusing for the user to release a completely different app as an update to an existing one?
So a different way of putting my question would be: can we freely reuse a Bundle ID for a different app within the same account?
Does anyone have experience with this?
What you want to do is absolutely acceptable. I don't see any reason why Apple would reject your app.
I personally recently updated an app with a new icon and a new name.
Granted, I kept most of the features from the previous version, but I really don't see Apple rejecting an update based on "it's too different from the previous version". Also, you often see notes in updates saying "rewritten from scratch", so this is also perfectly valid.
Technically you can do this, and lack of code re-use is irrelevant.
I have written and submitted apps that have have had their codebase completely replaced over their lifetime.
I've also changed an app's icons and name, so all the component parts are definitely OK to do.
You cannot reuse a bundle ID. Your best option is to just update the app. The review process accounts for major changes like this, so it will most likely be a longer review time.
I haven't been able to find relevant answer to this problem. Please redirect if you know it's a duplicate question.
Background:
I have this version 1.0 of an app on the App Store. It's basically a wrapper around a WebApp and the updated 2.0 version I am working on is a native implementation for iPhone.
Now the current version 1.0 of the app is Universal. So trying to submit our finished 2.0-native iPhone only app is refused by AppStore since it's considered a downgrade to no longer support iPad.
The roadmap ahead includes a future release of an iPad-version as well, and this needs to be taken into account. I believe there are good reasons for this iPad-app to be Universal. We need to keep the current AppName in some way.
Now I need advice on how to best handle the situation. These are the steps I consider:
Release v2.0 under new appName i.e. "MyApp 2"
Remove v1.0 app from sales, but keep it in iTunesConnect to save the name
Change WebAppContent of v1.0 to notify the current userbase of the native app (2.0)
When we are ready to release a Universal App we update the current 1.0 instead of 2.0 to reclaim the original name
Questions:
Is there a better way?
If we remove v1.0 from sales and release v2.0 under the name "MyApp 2", is there a way to change the later name back to "MyApp" when v1.0 is of the stores?
If we consider deleting v1.0 completely from iTunesConnect, can we, as the same company, then reclaim the name when it becomes publicly available again (or are we blacklisted for that name)?
Can you have different display names for an App on AppStore and on the devices home screen (how is this done)?
Warning: If you delete an app in iTunes Connect, that app's name is no longer available for use by that same Developer account ever again.
Bundle display names are independent of App store names. Many apps have shortened or abbreviated Bundle display names to fit under the icon, and a much longer app store name.