That’s why I personally think that all apps should have this mechanism. It saves time and money, decreases the frustration of the developers, and makes supporting the app easier. Having a way to keep the codebase in the app and the back end clean is fantastic.
To reduce the number of pop-ups, show the pop-up for optional updates once and only once. Therefore, interrupting the users each time they start up the app with an update pop-up should be avoided. I want my users to have a good experience with my app and use it often.
Force-updating often will only annoy my users and probably drive them away from using my app. As a user, I sometimes won’t even have the choice to use the app and will be forced to update.Īs an app publisher, I have to be careful to not overwhelm my users. When I look at this feature from the user’s point of view, it can be annoying to always be informed that there is a new update available. How should I implement a new feature in that jungle of ugly patches and what feels like 200 different versions of the same endpoint? Which endpoint should I debug if a new issue arises? It blows up the available number of endpoints and the lines of code in our codebase - and all that just because I have to make sure that old apps still work correctly with my back end. Also, creating more and more endpoints labeled “v1,” “v2,” “vN” doesn’t cut it for me either. What if I have to fix the same endpoint a second time because the fixed app version has another bug? I can’t just always put a patch on the patch and hope that the next developer who touches the code knows what all those if-elses and checks are about. This is never optimal and heavily decreases the codebase’s quality over time. But since we did not have a way to force an update of our app, I had to hack a fix into the endpoint on the back-end code. In some of those cases, the cleanest way to fix the issue was to update the app. As a back-end and app developer, I have seen several software bugs that required either the app or the back end to be fixed.
0 kommentar(er)
