Should the new version be released as a separate product?

Question

Marketing

Conditionally there is a certain application. For various reasons (difficult to maintain, initially wrong architecture) I had to rewrite it from scratch. The new version has no common code with the old version, although technically it is the same product. It is positioned as the best replacement for the old one, fewer bugs, more optimization, plus new features as a bonus. Old features are present, but there is no full guarantee that they will work the same, that there are no new bugs, and that they can be found in the same place (i.e. the interface may change, customization logic, several features may be combined or be separated, etc.).
There are two options:

1. Release this update as a new version that will replace the old one with the same name, authorship, and all existing subscriptions will remain unchanged. Just users will receive an update.
   
2. Leave the old application, and release the update as a separate application. Users are notified that the old one will no longer be updated, but can be used at will. Users are required to navigate independently (again, optional)
   

Answer 1

If we are talking about an android application, then in my opinion there is a risk of falling under
https://play.google.com/intl/ru/about/spam-min-fun...
Creation of several very similar applications. If the amount of content in each of these applications is small, it may be worth publishing one application that combines all the content.