Launch day feels like the finish line, but for an app it is closer to the start. The phone in your customer’s pocket will update its software several times this year, and each update can change how your app behaves. Looking after an app is less exciting than building it, and just as important.
Phones and stores keep changing
Apple and Google release new versions of their systems every year, and the app stores regularly ask developers to update tools, privacy details and permissions. An app that is never updated can eventually be removed from a store or stop working on newer phones. A maintenance plan keeps it current, so nobody has to rush.
Security fixes are routine
Apps rely on code libraries and servers that receive security fixes all the time. Applying them quickly and testing that nothing broke is ordinary, unglamorous work. It is also the part that protects your customers’ details, so it should be somebody’s job, with a regular date in the calendar.
Small requests add up
After launch, you and your staff will notice things: a label that confuses people, a report you wish you had, a new service to add. Collecting these and shipping a few each month keeps the app useful. On our plans, small changes are included up to a set number of hours, and anything larger gets a quote first.
What to ask any studio
Whoever builds your app, ask before you sign who will maintain it, what it costs per month, how quickly they respond when something stops working and how you can take the code elsewhere if you need to. Clear answers to those four questions matter as much as the design.
Ask, too, what happens if the studio closes or you part ways. The code, the store accounts and the hosting should already be in your name, so another team can pick them up without starting again.
