App Maintenance Cost in Nigeria: What to Budget After Launch
App maintenance cost at a glance
The table places indicative 2026 yearly costs against the three build tiers used across this site. The maintenance column follows the 15 to 25 per cent rule; the other columns are typical additions. Actual figures vary with scope, usage, vendor and the naira exchange rate.
| App tier | Indicative build cost | Maintenance retainer (per year) | Hosting and cloud (per year) | Other recurring |
|---|---|---|---|---|
| Simple MVP | ₦1,500,000 – ₦5,000,000 | ₦250,000 – ₦1,250,000 | ₦150,000 – ₦300,000 | Store fees, small SMS usage |
| Medium | ₦5,000,000 – ₦15,000,000 | ₦750,000 – ₦3,750,000 | ₦250,000 – ₦800,000 | Store fees, SMS, payment fees, maps, analytics |
| Complex | ₦15,000,000 – ₦50,000,000+ | ₦2,250,000 – ₦12,500,000+ | ₦800,000 – several million | As above, plus security testing, compliance, higher support cover |
In practice, year one often costs more than the steady state because launch reveals issues and the business asks for quick improvements. Year two and beyond settle unless the app grows.
What app maintenance actually includes
App maintenance is the ongoing work of keeping a published app working, secure, compliant and useful. It falls into four categories that software teams have used for decades, and each category shows up as a real cost.
- Corrective maintenance: fixing bugs found after launch, including ones that only appear on particular phones or networks.
- Adaptive maintenance: keeping up with changes outside the app. New Android and iOS versions each year, Google Play's target API level requirements, App Store policy changes, updates to the Paystack, Flutterwave or SMS provider APIs, framework and library updates, and expiring certificates and signing keys.
- Preventive maintenance: monitoring crashes and performance, patching security vulnerabilities in dependencies, cleaning up data, reviewing backups and access.
- Perfective maintenance: small improvements that keep the app competitive: a new payment option, a better onboarding flow, a new notification type.
A retainer typically covers the first three fully and includes a fixed number of hours for the fourth. Larger features are scoped and priced separately as phase-two work. Support is often bundled in: a channel for the business to report problems, agreed response times, and periodic reports on crashes, usage and store health.
How maintenance is priced in Nigeria
Nigerian agencies and freelancers use a handful of pricing models. The right one depends on how much the app changes and how critical it is to the business.
| Model | How it works | Indicative 2026 cost | Suits |
|---|---|---|---|
| Percentage-based yearly retainer | Fixed yearly fee at 15–25% of build, paid monthly or quarterly | ₦250,000 – ₦12,500,000+ per year | Most business apps with a known vendor |
| Monthly retainer with hour bank | Fixed monthly fee for a set number of hours; unused hours may roll over | ₦100,000 – ₦1,000,000+ per month | Apps with steady small changes |
| Tiered SLA plans | Basic, standard and premium tiers with different response times and cover | Varies widely by tier | Apps where downtime has a direct cost |
| Pay-as-you-go (hourly or per incident) | No commitment; billed when work is done | ₦15,000 – ₦50,000+ per hour equivalent | Very simple apps with rare changes |
| In-house developer | Salary of a developer who maintains and improves the app | ₦150,000 – ₦800,000+ per month | Products that change continuously |
Pay-as-you-go looks cheapest and often is not. Nobody is monitoring the app, emergencies are billed at premium rates, and the adaptive work (OS updates, store requirements) gets postponed until the app is removed from a store or breaks. For any app that customers or staff rely on daily, a retainer or SLA plan is the sensible default. Ask what happens when the retainer hours run out, whether emergency fixes are inside the plan, and whether the price is fixed in naira for the year.
Recurring costs outside the retainer
The maintenance retainer pays for people's time. Several other recurring costs are paid to third parties, usually by the business directly, and are often left out of the number a business owner first budgets.
| Cost | Indicative 2026 range | Notes |
|---|---|---|
| Hosting and cloud (backend, database, storage, admin dashboard) | ₦150,000 – ₦800,000+ per year | Frequently billed in US dollars; grows with users and data |
| Apple Developer Program | Yearly fee (historically US$99; verify) | Required to keep an iOS app on the App Store |
| Google Play developer account | One-time fee (historically US$25; verify) | No yearly renewal |
| Payment gateway fees | Per-transaction percentage and caps | Charged on revenue, not a fixed cost |
| SMS and OTP | Per message | Scales with logins and notifications |
| Push notification service | Often free at modest volumes | Verify limits |
| Maps, geocoding, distance APIs | Usage-based in US dollars | Significant for delivery and logistics apps |
| AI or LLM API usage | Usage-based in US dollars | For apps with AI features |
| Domain, SSL, email | ₦3,000 – ₦30,000 per year for a domain | Small but easy to forget until they expire |
| Monitoring, crash reporting, analytics | Free tiers common; paid tiers in US dollars | Depends on volume |
For a medium app, these typically add ₦400,000 to ₦1,500,000 a year on top of the retainer, more if the app is heavy on maps or SMS. The website hosting cost guide covers hosting pricing in more depth.
How maintenance cost scales by app type
The 15 to 25 per cent rule is a starting point. Where an app lands in that range, or outside it, depends on how much of the outside world it depends on.
- Loyalty or ordering app for one business: low end. Few integrations, stable features, modest usage. Expect 12 to 18 per cent.
- Booking app: low to middle. Payment and reminder integrations need attention; calendar logic rarely changes. Expect 15 to 20 per cent.
- School app: middle. Seasonal peaks (results day, fee deadlines) demand readiness; multiple roles mean more surface area. Expect 15 to 20 per cent, with peak-period support.
- E-commerce app: middle to high. Catalogue changes, payment options, delivery integrations and promotions keep the backlog full. Expect 18 to 25 per cent.
- Delivery or logistics app: high. Maps, live tracking, rider devices and dispatch logic generate constant adaptive work. Expect 20 to 25 per cent plus significant API usage.
- Fintech or wallet app: highest. Security patching, compliance changes, bank and switch API updates, and mandatory audits. Expect 25 per cent or more, plus separate security testing.
What changes for Nigerian apps
Exchange-rate exposure. Hosting, monitoring, maps and AI usage are dollar-denominated. A retainer fixed in naira does not protect you from a cloud bill that rises when the naira weakens. Ask your vendor to estimate dollar-linked costs separately and review them quarterly. Store compliance is not optional. Google requires apps to target recent Android API levels to remain updatable and visible; Apple requires builds with recent SDKs. An app left untouched for a year or two can be hidden from new users or blocked from updates until it is brought up to date, which costs more as a rescue than as routine maintenance. Verify current requirements on each store's policy pages. Device fragmentation. Nigerian users span a wide range of Android phones, many with limited memory and older OS versions. Each Android release and each popular new budget device can surface bugs that need fixing. Payment and messaging providers evolve. Nigerian payment gateways and SMS providers update APIs, add fraud controls and change sender-ID rules; adaptive work follows each change. SMS costs scale with logins. Apps that use SMS OTP for every login accumulate real monthly bills. Push-based or WhatsApp-based verification, biometric login and longer sessions can cut this line substantially. Power and connectivity affect support. Users on unstable connections report "the app is not working" when the network is at fault. A support process that can distinguish app faults from network faults saves retainer hours. Regulated apps carry extra recurring cost. Lending, payments and health apps may need periodic audits, policy updates and regulator reporting. Confirm current obligations with the relevant regulator or a qualified adviser.
Example (hypothetical): year-one budget for a Port Harcourt delivery app
Example (hypothetical): a dispatch company in Port Harcourt launched a customer app, a rider app and a dispatch dashboard for an indicative build cost of ₦9,000,000. The apps use Paystack for payments, a maps API for tracking and distance pricing, SMS for order updates and push notifications for riders. An indicative year-one maintenance budget looks like this:
| Item | Indicative year-one cost | Notes |
|---|---|---|
| Maintenance retainer (20% of build) | ₦1,800,000 | Monthly, covering fixes, OS and store updates, monitoring, 10 hours a month of improvements |
| Cloud hosting and database | ₦600,000 | Dollar-billed; grows with order volume |
| Maps and distance API usage | ₦400,000 – ₦900,000 | Dollar-billed; the biggest variable |
| SMS order updates | ₦250,000 | Could fall by moving updates to push and WhatsApp |
| Apple Developer Program | Yearly fee (verify current amount) | Paid by the business |
| Monitoring and crash reporting | ₦0 – ₦150,000 | Free tier initially |
| Contingency for phase-two features | ₦900,000 | Held separately, released against scoped requests |
Year one lands indicatively at ₦4,000,000 to ₦4,600,000, or roughly 45 to 50 per cent of the build cost when the dollar-linked usage lines and the phase-two reserve are counted. The retainer alone is 20 per cent; the rest is the cost of running a live, map-heavy product. The scenario is illustrative, not a price list.
What happens if you do not maintain an app
Skipping maintenance does not save money; it defers it with interest.
- Store removal or hidden listings. Apps that miss target API level or SDK requirements can be hidden from new users or blocked from publishing updates until fixed.
- Broken integrations. A payment gateway or SMS provider retires an API version, and payments or OTPs stop working, usually at the worst time.
- Security exposure. Unpatched libraries accumulate known vulnerabilities; an app holding customer data becomes a liability under the NDPA 2023.
- Crashes on new phones. Each OS release changes behaviour; untested apps crash for customers who just bought a new device.
- Loss of the team's knowledge. A vendor who has not touched the code for eighteen months has to relearn it, and charges for the time.
- Expensive rescue. Bringing a neglected app back to compliance can cost as much as a year or two of the retainer you skipped, and sometimes approaches a rebuild. The guide on app maintenance versus app rebuild covers that decision.
How to reduce app maintenance cost sensibly
- Build it well the first time. Clean code, automated tests and a documented architecture make every future change cheaper.
- Use fewer, better integrations. Every third-party service is a future adaptive-maintenance line. Do not add ones you do not use.
- Prefer push notifications and WhatsApp to SMS where customers accept them; SMS is the most expensive routine message.
- Right-size hosting. Start on a modest plan with monitoring and scale when usage justifies it, rather than paying for capacity you may need one day.
- Batch improvements. Releasing small features together in a scheduled monthly or quarterly update reduces testing and review overhead.
- Own your accounts and code. Switching vendors is possible only if the business holds the repositories, cloud and store accounts; it keeps retainer pricing honest.
- Agree a fixed naira retainer with a dollar-cost review. Predictable for the people cost; transparent for the usage cost.
How to compare maintenance quotes
Ask each vendor for the same information:
- What is covered: bug fixes, OS and store updates, security patches, monitoring, support hours, small improvements?
- What is excluded, and at what rate is excluded work billed?
- Response and resolution times for critical, major and minor issues?
- How many hours a month are included, and what happens to unused hours?
- Which third-party costs are paid by the business directly, and what is the vendor's estimate of them?
- Is the price fixed in naira for twelve months?
- What reporting will the business receive, and how often?
- Who holds the code, keys and accounts, and what happens on termination?
Two quotes with the same monthly number can differ by hundreds of thousands of naira a year in what they actually deliver. Compare cover, not headline price.
Mistakes to avoid
- Budgeting only for the build. Reason: the app will need money from the first month after launch.
- Choosing pay-as-you-go for a business-critical app. Reason: nobody watches it, and emergencies cost more than routine work.
- Ignoring dollar-linked usage costs. Reason: maps, hosting and SMS can exceed the retainer for some app types.
- Letting the developer hold the accounts. Reason: you cannot change vendor, and renewals lapse when the relationship ends.
- Postponing store compliance updates. Reason: the app can be hidden or blocked, and rescue costs more.
- Treating every request as maintenance. Reason: large features drain the retainer; scope them separately so the routine work still gets done.
- Not reviewing the retainer yearly. Reason: a stable app in year three may need less cover, and a growing one more.
Conclusion
Budget 15 to 25 per cent of the build cost per year for the maintenance retainer, then add hosting, store fees and usage-based costs for SMS, payments, maps or AI, several of which are billed in US dollars. For a medium app that means indicatively ₦1,000,000 to ₦5,000,000 a year all in, more for map-heavy or regulated products. Choose a retainer or SLA plan over pay-as-you-go for anything customers depend on, keep the accounts in the business's name, separate large features from routine cover, and compare quotes by what they include rather than by the monthly figure. If your app is live and you want a clear maintenance plan with fixed naira cover and transparent third-party costs, Linestech can review the app and propose a retainer sized to how it is actually used.
Frequently asked questions
Is the 15 to 25 per cent rule based on the original build cost or the current value?
On the original build cost, adjusted for any major features added since. If an app cost ₦6,000,000 and a ₦2,000,000 phase-two module was added, budget maintenance on roughly ₦8,000,000. The rule is a planning heuristic, not a formula; the real driver is how much of the app depends on external systems that change.
Can I maintain the app myself to save money?
Routine content and catalogue changes should be done by the business through the admin dashboard at no developer cost. Code-level work, OS updates, security patches and store compliance need a developer. A business without technical staff should keep at least a light retainer or a reliable vendor on call.
Does maintenance include new features?
Small improvements are usually included within a monthly hour allowance. Larger features are scoped and quoted separately. A good retainer states the allowance clearly; if a request will take more than the allowance, the vendor should say so before starting.
How much does it cost to update an app for a new Android or iOS version?
For a well-built app, a routine OS update usually consumes a few hours to a few days of work, which a retainer absorbs. An app that has been neglected for two or more OS versions can need weeks of work, billed separately if there was no retainer.
Why is hosting billed in dollars, and can I avoid it?
Most cloud providers price in US dollars. Some Nigerian hosting providers offer naira-denominated plans that suit simple backends; for apps needing global infrastructure, managed databases or scale, dollar-billed cloud is common. Either way, budget the line separately and review it when the exchange rate moves.
What should the vendor report each month?
At minimum: crashes and their fixes, uptime, store status and any policy notices, hours used against the allowance, third-party usage against estimates, and any risks coming up, such as an SDK deadline or an expiring certificate. If a vendor reports nothing, you are paying for cover you cannot verify.
When does it make sense to stop maintaining an app?
When it no longer serves customers or staff, when a replacement is live, or when the maintenance and rescue cost exceeds the cost of a rebuild that would serve the business better. Until then, an unmaintained live app is a liability rather than a saving.
Sources and further reading
Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.
