Answer the question
In order to leave comments, you need to log in
Changing the package name and release key of a published application, is it worth it?
We ordered the development of a mobile application from the studio, the studio completed the development and released it in the Play Market by signing it with its key, and most importantly, with the package name containing not the application name, but the studio name. (defect in the formation of TK). I am now responsible for maintaining this application and I have questions:
Should I change the package name and re-sign with my key, and upload it all as a new application, and delete the old one? (only for the sake of the branded package name)
Is it possible to change just the package name and put it out with the old key, like an update?
If it is still worth it and it can be done, then what is the best thing to do (would you do) to overtake users from the old version to the new one? (Thought to notify by push)
Answer the question
In order to leave comments, you need to log in
the user does not see the package name anywhere except for the browser search bar and app info (but who goes there ??)
and why create problems out of the blue with the transfer of users .. and if not everyone will switch? What if they get lost along the way? but chsv will be enough - the package is called as it should! :)
find an objective reason to rename. five or six is better. and next write down "damages" from leaving the former name. the answer will come by itself
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question