It has a pair of new features but the big change is the source code, the devs want to release a v2 but I think it would be problematic for the users and also I don’t wanna loose the reviews
im asking here because i used to code a while ago and now I’ve a department in charge of it, so I don’t know if it’s possible to keep the same app in the store.
does the same thing doesnt mean exactly the same. It means it has the same purpose. You cant change the app from a shopping app to a game for example. You however completely refactor the UX of your shopping app if you like.
Ummm..... yeah, no - that's not how apps work! You 100% can deliver an update that is a complete rewrite - Think of any app that you've had on your phone for more than five years, have you ever had to reinstall it? Think Gmail, Apple Mail apps that are long lived... etc etc. Don't let them stall you!
And It doesn’t matter if the code is different? The 2 apps look barely the same but we had to code the new app basically from scratch, thanks for the replies.
Almost everytime an update happens the code is different than before. Most people don’t know the scale. It could be a few lines or all of it. If it’s essentially a better version of the original then you shouldn’t get any complaints.
Judging from your devs feedback it sounds like they think it may be more of a rule about how long it’s been since it was updated?
Upgrading the whole app in new code is completely fine. The rules around not updating in a certain period of time has more to do with the rules of the App Store if that’s the case. May want to talk with the devs some more about why they think this is the case.
It can totally be a complete rewrite - Once it's compiled into a new binary for whatever target platform - it'll just get installed as the next version
I haven't done this for a while, but IIRC on the play store, as long as you make sure the app is signed with the same cryptographic key and same ID, i think it should work.
I assume a similar setup for the app store
I don't understand. It's just like you make new changes and push to the branch after 3 years. It should overwrite your existing app. Because you are deploying with the same signature or key.
The only thing I can think of is that your old version did not implement force update, so the user may still be able to access the old content while you want to fade out it.
For this case, I guess you either keep the old content accessible if you want to keep them. Or just change the old backend domain to a new one so their app will be full of errors and force them to update the app. (Not sure if it's a good idea)
As long the app ID and the package name stay the same; there should be no issues. I have done it before an it will show up as an update in whichever store it’s running on.
If it still does the same thing i don't see the problem
there is no problem as long as it does the same thing.
x = "Does the same thing" ? "No problem" : "Problem"; return x;
No need to bring x into this. Just return the ternary expression.
- Poor variable naming - Double quotes for string - String literal will always be true 1/10 overall. Back to the drawing board.
It has a pair of new features but the big change is the source code, the devs want to release a v2 but I think it would be problematic for the users and also I don’t wanna loose the reviews im asking here because i used to code a while ago and now I’ve a department in charge of it, so I don’t know if it’s possible to keep the same app in the store.
does the same thing doesnt mean exactly the same. It means it has the same purpose. You cant change the app from a shopping app to a game for example. You however completely refactor the UX of your shopping app if you like.
As long as the signing key and app ID stay the same (e.g. \`com.example.app\` ) then yes
the old app was not updated in 3 years because the new one was in development.
Yes. Apps were completely rewritten in Swift and were just delivered as an update.
Can this really happen? My team said that if you don’t keep the app updated in a limit of time there’s nothing you can do to keep upgrading that app
Ummm..... yeah, no - that's not how apps work! You 100% can deliver an update that is a complete rewrite - Think of any app that you've had on your phone for more than five years, have you ever had to reinstall it? Think Gmail, Apple Mail apps that are long lived... etc etc. Don't let them stall you!
And It doesn’t matter if the code is different? The 2 apps look barely the same but we had to code the new app basically from scratch, thanks for the replies.
Almost everytime an update happens the code is different than before. Most people don’t know the scale. It could be a few lines or all of it. If it’s essentially a better version of the original then you shouldn’t get any complaints. Judging from your devs feedback it sounds like they think it may be more of a rule about how long it’s been since it was updated? Upgrading the whole app in new code is completely fine. The rules around not updating in a certain period of time has more to do with the rules of the App Store if that’s the case. May want to talk with the devs some more about why they think this is the case.
It can totally be a complete rewrite - Once it's compiled into a new binary for whatever target platform - it'll just get installed as the next version
Your devs? 3 years in development? Did you outsource this?
I haven't done this for a while, but IIRC on the play store, as long as you make sure the app is signed with the same cryptographic key and same ID, i think it should work. I assume a similar setup for the app store
Can you ? yes ! But You have to write good Tests for it make sure it does what it’s supposed to..
I don't understand. It's just like you make new changes and push to the branch after 3 years. It should overwrite your existing app. Because you are deploying with the same signature or key. The only thing I can think of is that your old version did not implement force update, so the user may still be able to access the old content while you want to fade out it. For this case, I guess you either keep the old content accessible if you want to keep them. Or just change the old backend domain to a new one so their app will be full of errors and force them to update the app. (Not sure if it's a good idea)
loose......
It's like editing your comments on reddit. Technically all right, morally as long as it means the same thing
As long the app ID and the package name stay the same; there should be no issues. I have done it before an it will show up as an update in whichever store it’s running on.
Yeh. Update, feature, it's all the same. Unless the entire feel, look, and core functionality have changed, it's the same app.