Newbie App Update Question

Getting Started Newbie Questions
#1

I really should know the answer to this, but have to admit when the client asked it got me a little stumped so I thought I’d ask my CL friends.

A potential client has got in touch with regards to an app project. They wish to update an existing app that was built on unspecified frameworks; the problem is that the existing app is tapping into an old data and they want to rewrite the app to hook into their new systems - the problem is they don’t want to loose their existing users.

Not knowing anything of the existing app I claimed it was possible to re-write the app and provide it as an update, but then I started questioning whether this is possible.

I have stressed to the client that I would need the following:

iOS: Distribution/Developer Certificates; Bundle ID; the app will need to be submitted from the same iOS Developer account to iTunes Connect.

Android: Package Name; Private Key to sign the APK file - If the package name and signing certificate do not match those of the existing version, Market will consider it a new application, publish it as such, and will not offer it to existing users as an update.

But then I started to question if this is true; does anybody know if this is the case?

If anybody knows the answer or has experience in a similar scenario I’d be eternally grateful for some advice.

Many thanks…

#2

I think for iOS you will just need to be able to use the same bundle ID but will likely need to also use the same developer account.  If they have their own iOS developer account, you should be good to go.  If another company released it for them on that company’s credentials and you can’t use them, the users will get a new app.  This happened with Huffington Post a while back.  I had two copies of the app on my device after they transitioned to their new provider.   Apple does provide a way to transfer apps to different companies and this could help out.  As for their online data, they will need to have to find a way to migrate that data so that your app can access the data. 

As for Android you will need to use the same package name, and I think you would run into the same “store” issues in that if the original app is deployed on their provider’s account instead of their own Google developer account, then you could run into issues.  Google doesn’t support transferring apps.  You may hit a 2nd snag on Android.  I think apps have to be updated using the same release keystore and if you change the keystore, you have to release a new version of the app.  I’m not 100% sure of this condition, but I think I’ve heard it’s an issue. 

#3

I think for iOS you will just need to be able to use the same bundle ID but will likely need to also use the same developer account.  If they have their own iOS developer account, you should be good to go.  If another company released it for them on that company’s credentials and you can’t use them, the users will get a new app.  This happened with Huffington Post a while back.  I had two copies of the app on my device after they transitioned to their new provider.   Apple does provide a way to transfer apps to different companies and this could help out.  As for their online data, they will need to have to find a way to migrate that data so that your app can access the data. 

As for Android you will need to use the same package name, and I think you would run into the same “store” issues in that if the original app is deployed on their provider’s account instead of their own Google developer account, then you could run into issues.  Google doesn’t support transferring apps.  You may hit a 2nd snag on Android.  I think apps have to be updated using the same release keystore and if you change the keystore, you have to release a new version of the app.  I’m not 100% sure of this condition, but I think I’ve heard it’s an issue.