Optimal way to merge 2 apps

Searching for insight on the best and most compliant way to essentially merge two apps. They have the same functionality but one is much more advanced than the other, although the legacy app has a higher user count. Instead of letting both run, we want to push the legacy app an update with the code from the new app and ultimately kill the newer one. What is the best way to do this? Is it allowed to simply push the source code from new app to legacy and update the identifier? We do not wan't to break any app store rules and want to limit the potential of losing users by forcing them to download a new app.

Up vote post of rrbears Down vote post of rrbears
425 views
Posted by
rrbears
Reply
Add a Comment

Replies

So they are both published on the Appstore ? You were lucky not to have one refused for spam.

Is the problem that they are paying apps ?

What I would do:

  • Update the legacy app 1 (legacy) with the code of app 2 and publish it. In the notes to reviewer, explain precisely what you are doing.
  • Publish a last version of app 2 and let users know it will be discontinued. In the notes to reviewer, explain here also precisely what you are doing.
  • Then they will have to upload the new app in the future
  • After some time, remove app 2 from the Appstore.

But that does not solve the payment issue (you may have to contact developers support to get some advice).

Could you detail your pricing policy for app1 and app2 ?

Posted by
Claude31
Up vote reply of Claude31 Down vote reply of Claude31
Add a Comment

@Claude31 thank you for your response. Apologies for not being precise: the "new" app and legacy app are not visually the same at all. They have the same purpose but different branding, different design and a slightly different UX. They are both free to download.

Posted by
rrbears
Up vote reply of rrbears Down vote reply of rrbears
Add a Comment