Same app name for iPhone and iPad,but different release dates - ios

We are about the release app to the iPad store under the name appName. We don't want to add anything to that name (e.g. HD ) . the app is now only for iPad(not universal) .
Later we would like to release it to the iPhone under the same name .
But, for this to work we will have to later make that same app to be universal , and release an update to it.
Problem: On the release date to iPhone , we will not get the right attention , because its only an update, not a new app. (e.g. get to be in the first places/promption by Apple ,etc ).
How you usually solve this problem ,to get a full attention as a new release, when you only submit an update to include another iDevices ?

This is more of opinion question rather than a programming one. Still I will let you know my thoughts.
This statement is not entirely true.
"Problem: On the release date to iPhone , we will not get the right attention , because its only an update, not a new app. (e.g. get to be in the first places/promption by Apple ,etc )."
what exactly are you plans for advertising your release or update? If you hope that website that monitor new app releases automatically to advertise your app then yes, you get a shot at the new release and updates not so much.
You can release an iPad version and then with an update make the app universal as long as you advertise your app update like mad all over the social media and such. Hopefully your update will be received with just as interest as your initial app release.
The only other option, which you already know, is to create two different apps with different names "HD" and have two sets of code to maintain which I can tell from experience is a pain in the butt.
If I were you I would hold off on releasing an iPad version till I made it universal. Trust me Apple customers now expect all apps to work on every apple devices and not to buy the same app twice for iPhone vs iPad.
Just my two cents.

You can use the app same name, but launch the universal version of the app with a different bundle ID. No problem from the Apple side.

Related

New requirements for iOS app - keep them accessible to users/customers

I got an email from Apple that apps now require iOS13 + storyboard for app launch screen for existing apps. (I do not use storyboard for main app functionality)
I have developed a couple swift1/swift2 based for schools a long time ago. (Still works well)
Can I somehow ditch the app store and then provide direct access or download for school pupils?
i.e. is there any way forward to simple keep the apps-as-they-are? Maybe limited download availability?
Or will I have to take plunge back into app-building?
The requirement of a Storyboard launch screen is only when you need to submit an app update. If you are not wanting to update your app any more, then it won’t stop working because of this new requirement.
Regarding distribution outside of the App Store, you could use Adhoc distribution which requires you to know the device ID’s of the devices you want to install it to.

Remove support for iPhone with new updated version of app

We released few versions of our app with universal support ( i.e. app is supported both on iPhone and iPad). Now with new version of our app (1.14) we want that this version should be available to iPad only. This means 1.14 should be available only on iPad and iPhone user may not able to install it. But when we change setting in Xcode from Universal to iPad only it gives error while uploading ipa to app store that if previous version of app supported iPhone then in updated version of app we cannot remove iPhone support. Now we are looking for solution to this problem. Please guide us what are way to over come this issue. Due to this issue we have to delay our app release so kindly give us possible suggestions as soon as possible.
There is no good way of doing what you want. Apple deliberately don't want you removing functionality for existing users.
Maybe the only way forward is to remove your current app from sale and submit a new, iPad-only version. You'll lose your reviews, sales rank, etc.

Upload Application to app store with iPad support and later on iPhone Support

I have an application which is practically done and ready to be issued as an iPad version, but the problem is that later on i need to have an iPhone version of it to be submitted using the same bundle and the same app id. I know that i need to create a different storyboard or use the auto-layout, so coding and developing wise i already have it figured out, but for now i need to submit the iPad version of it and after on submit an update containing the iPhone version. Is there any pointer i should keep in mind or any special details to watch out from? Many thanks
Just upload your first version with configuration stated below screenshot
After when u want to upload with both then do config stated in belowed screenshot
It's simply possible to update your iPad app with your new universal app. nothing any importent changes for configuration at iTune but you must know well how to develop the Universal app

Apple to reject any apps that access UDIDs,don’t support Retina, iPhone 5 displays?

Got news from TNW, which states, "Starting May 1, the App Store will no longer accept new apps or app updates that access UDIDs. Please update your apps and servers to associate users with the Vendor or Advertising identifiers introduced in iOS 6."
My question is quite simple, how about OLDER APPS that have been released before May 1st and do access UDIDs? Also, what if the app doesn't support retina display? Do they remove it from the App Store?. If so, I am afraid of hearing YES.
Its very bad that apple not giving permission to access UDIDs, but there are some work arounds. Check out the link
Whatever, apple wont remove any app from appstore which is already reviewed by them.
They will not remove older Apps but its better to Update it with new rules like if it doesn't have retina support than it'll not useful for the retina iPhone & in current scenario Majority of users using retina iPhones only so its good to update the Application.
Hope this helps.
I don't think so if Apple need to remove the current app that recently access UUID it takes time to review before remove them out.

Testing in a iOS 6.1 jailbroken device without Hackulo.us and Apple developer ID

first of all, I know there are many questions similar to this one, but, they are old and the answers in them unfortunately no longer work, since the game has changed without Hacklo.us to do part of the process.
Basically, I want to develop for iOS and test the apps I make, and later in the future I may want to submit them to the Apple Store, but for now I'm not willing to pay 99$ to join the Apple iOS developer program just to use my apps in my iPhone.
I have a jailbroken iPhone 4S with iOS 6.1.
The only posts I found about how to do this, either use Hackulo.us (that went down about 2 months ago) or something called Jailcoder that is also offline and they also seem to work with only old versions of XCode/iOS (not clear about that point).
Any new progresses on how to to this with the present conditions?
Simple. After building the app, just use some utility (SSH, iExplorer, etc.) to copy the app bundle to the /Applications directory on the device. After that, either run the uicache tool or respring the iPhone to make the application appear on the home screen.

Resources