Releasing an App upgrade after changing the underlying technology

Hi

We have an app which has historically been built in Swift. We're developing a completely new version in React Native which we plan to release soon.

Is there any reason why we can't release this as a straightforward app upgrade to our existing users, assuming we sign it with the usual credentials?
Any reason why it might need to be released as a separate app?

Also, if we're releasing through our existing app account, is there any reason why our vendor name (and our users' IDFVs) might change?

Many thanks!

Is there any reason why we can't release

Have you a problem to release or is it a preventive question ?

I don't think there should be any problem.

Did you read this:
https ://reactnative. dev/docs/publishing-to-app-store
It's preventative (or speculative).

Someone has questioned our assumption that we'll be able to go from app version (e.g.) 1 created in Swift to our new app version 2 in React Native.

We also think it should be OK, but can't find any explicit mention of this kind of use case in any documentation.
So just go and submit the app update. That will be a direct answer to any objection.

I'm not familiar with React, but that should not cause problem (just as with SwiftUI). That's what their doc states at least.

You should ask to React directly.

Don't forget to close the thread once done (and post what you confirmed).

We also think it should be OK, but can't find any explicit mention of this kind of use case in any documentation. 

You would never find it.
Many rules describe what you cannot do, but none of them list up all the things what you can do.

You should better mind if your app follows the App Store Review Guidelines and Human Interface Guidelines.
Some of the app framework might be violating the guidelines.
Thanks for your replies. Much appreciated.

I'll update and close the thread when we've reached a conclusion.
Releasing an App upgrade after changing the underlying technology
 
 
Q