App Development Cost Breakdown in Nigeria: Where Every Naira Goes

The cost breakdown at a glance

The table shows how a typical medium-complexity business app budget divides between components. Percentages and naira figures are indicative 2026 estimates for a cross-platform app (one codebase for Android and iOS) with a custom backend and web admin dashboard, built by a Nigerian agency. Actual quotes vary with scope, vendor and exchange rate.

The shares add up to more than 100% at the top of each range because no app is at the top of every line. A content-heavy consumer app spends more on design and front-end; a logistics app with dispatch logic spends more on backend and integrations.

Line 1: Discovery and requirements

Discovery covers the workshops, interviews and analysis that turn "we want an app" into a written scope: user roles, feature list, integrations, non-functional requirements and an out-of-scope list. On a medium app this is one to three weeks of a product lead's time. Some agencies bundle discovery into the quote; others sell it as a separate, smaller engagement before quoting the build. Either is fine as long as it exists. A quote with no discovery line, and no evidence that the scope was worked through, is a quote against assumptions, and the assumptions will surface later as change requests. What it includes: workshops, user and staff interviews, competitor and alternative review, the requirements document, a prioritised feature list, and the estimate itself.

Line 2: UX and UI design

Design is the second-largest line many first-time buyers under-estimate. It covers user flows, wireframes for every screen, visual design in the brand's identity, a clickable prototype and the hand-off package for developers. For a medium app with 25 to 40 screens, that is three to five weeks of a designer's time. Cost rises with the number of distinct screens and states (empty, loading, error, offline), the number of user roles (each role is effectively its own app), and the need for custom illustration or iconography. It falls when the business already has a design system or when the app follows standard platform components closely. A cheap quote often hides thin design: a handful of screens designed and the rest "done in development". The result is inconsistent screens, poor error handling and a product that customers find confusing on first use.

Line 3: Mobile front-end (Android and iOS)

The front-end is the app itself: every screen from the designs, connected to real data, handling every state, working across phone sizes and operating-system versions. It is the largest single line because it is where most of the developer hours go. Three factors set the front-end cost:

• Platform approach. A cross-platform build (Flutter or React Native) covers Android and iOS from mostly one codebase. Two native builds roughly double this line. The native versus cross-platform guide explains when each is right.
• Number of screens and flows. More screens, more roles, more logic.
• Device and offline requirements. Camera, GPS, biometrics, background location, offline caching and low-end device optimisation each add days to weeks.

On a ₦8,000,000 app this line is indicatively ₦2,000,000 to ₦2,800,000, covering roughly eight to twelve weeks of one or two front-end developers. If the quote lists "Android app" and "iOS app" as two full lines with a cross-platform framework, ask why.

Line 4: Backend, database and admin dashboard

The backend is the part customers never see and the business depends on entirely: the API the app talks to, the database holding customers, orders and payments, authentication, business rules, security, and the web-based admin dashboard staff use to run the app. Costs here depend on:

• Custom versus managed backend. A managed service (authentication, database and storage as a service) can cut this line by a third or more for simple apps. Complex business logic, reporting and integrations push towards a custom backend.
• Admin dashboard scope. A basic dashboard for viewing and editing records is a modest addition; a full operations console with roles, reports, bulk actions and audit logs is a second product.
• Data and compliance requirements. Encryption, access controls, audit trails and data-retention rules required for health, finance or personal data under the Nigeria Data Protection Act 2023 add engineering time.

This line is the one most often missing or vague in cheap quotes. An app "without a backend" either stores data on a third-party service you do not control or cannot do anything useful. Insist on seeing what the backend line includes and whether the admin dashboard is inside it.

Line 5: Integrations

Integrations connect the app to external services. Each one has a fixed cost to implement and test, and often a recurring usage cost after launch.

Effort figures are indicative. A customer app with Paystack, OTP and push notifications sits at the low end of the line; an app that must sync with an existing ERP and a bank's API sits at the top and beyond.

Line 6: Testing, QA and security

Quality assurance covers functional testing of every feature, testing across Android versions, screen sizes and iPhones, network testing on slow and dropped connections, payment testing with real small transactions, security review, regression testing after fixes, and support for the business's own acceptance testing. At 10 to 15% of the build, QA is the line most often cut to make a quote look competitive, and the one whose absence you pay for after launch in bad reviews, failed payments and emergency fixes billed by the hour. A quote with no QA line means either that developers will test their own work in passing, or that testing is your job. For apps handling money or personal data, a separate security assessment line (or an external penetration test for fintech) is reasonable and worth paying for.

Line 7: Project management

Project management pays for the person who plans sprints, runs reviews, manages the backlog, chases decisions and content, coordinates designers, developers and QA, and keeps the timeline honest. It is typically 5 to 10% of the build. Freelancer quotes rarely include it, which is one reason they are cheaper; the coordination falls on you. Agency quotes usually do, either as a line or spread across the others. Ask how it is handled either way, because a project with nobody managing it takes longer, and the extra time is not free.

Line 8: Deployment, store publishing and launch

The last build line covers setting up production infrastructure, configuring app signing, preparing store listings and screenshots, completing privacy and data-safety declarations, managing review and rejection cycles, and a staged rollout. It is a small share, indicatively 2 to 5%, but it is real work with real delays if skipped. Note the third-party fees that sit alongside it and are usually paid by the business directly: the Apple Developer Program yearly fee (historically US$99 per year; verify the current amount) and the one-time Google Play developer registration fee (historically US$25; verify). The separate guides to App Store publishing cost and Google Play publishing cost cover these in detail.

The lines that come after launch

The build quote ends at launch; the app does not. Budget these recurring lines separately from day one:

The app maintenance cost guide explains what each recurring line covers and how retainers are structured.

How the breakdown shifts by app type

The percentages in the first table move with the nature of the product. Indicatively:

When you receive a quote, check that the shape matches the product. A marketplace quote where the backend is 15% of the total, or a fintech quote with no security line, is describing a different app from the one you asked for.

What changes for Nigerian app budgets

Some lines are effectively in dollars. Hosting, some SDKs, map APIs, AI services and store fees are billed in US dollars, and Nigerian agencies price the affected lines with an exchange-rate assumption. Ask which lines are dollar-linked and whether the quote is fixed in naira or subject to revision. Payment integration is cheaper than payment operations. Integrating Paystack or Flutterwave is a few days of work, but handling bank transfers that take a minute to confirm, USSD fallbacks and reconciliation adds backend and QA effort that international cost guides do not mention. SMS is a recurring line, not a footnote. OTPs and notifications by SMS are charged per message, and volumes add up for apps with frequent logins. Budget it, and consider WhatsApp or push notifications where they fit. Device testing needs a real device pool. Testing on budget Android phones and older OS versions is essential for Nigerian users; a QA line that assumes emulator-only testing is under-scoped. Compliance is a line for regulated products. Lending, payments and health apps need legal review, data-protection work under the NDPA 2023, and sometimes regulator engagement. These are legitimate costs; confirm current obligations with the relevant body or a qualified adviser. Cheap quotes usually remove lines, not effort. A ₦2,000,000 quote for a medium app has typically dropped discovery, design depth, QA and project management rather than found a cheaper way to do them. The guide on why cheap app development can cost more explains what happens next.

Example (hypothetical): a ₦8,000,000 school app, line by line

Example (hypothetical): a private secondary school in Ibadan with 900 students wants an app for parents to see results and attendance, pay fees through Paystack, receive notices, and message the class teacher; a teacher app for attendance and result entry; and an admin dashboard for the bursar and principal. An indicative agency breakdown might read:

Recurring lines for year one would be budgeted on top: a maintenance retainer of roughly ₦1,200,000 to ₦2,000,000, hosting of perhaps ₦300,000 to ₦500,000, SMS usage, and store fees. The figures are illustrative, not a price list.

How to read a quote line by line

Use this checklist when two or three quotes arrive against the same scope:

• Does every one of the eight lines appear, either separately or clearly bundled?
• Is the backend line specific about the database, API and admin dashboard?
• Are Android and iOS covered, and by which approach?
• Which integrations are included, and which will be charged as extras?
• Is there a QA line, and does it name device, network and payment testing?
• Who manages the project, and is that time included?
• Which lines are dollar-linked, and is the naira price fixed?
• Are recurring costs listed separately from the build?
• Are store fees, hosting and third-party usage the business's responsibility?
• Who owns the code, the designs and the accounts at the end?
• How are changes priced after the scope is agreed?
• What warranty period covers defects after launch?

A quote that answers all twelve questions can be compared with another. A quote that answers four cannot be compared with anything; it can only be trusted or not. The guide on reviewing an app development proposal goes further on evaluating the document itself.

Mistakes to avoid

• Comparing totals instead of lines. Reason: the cheaper total has usually removed something you needed.
• Accepting a quote without a backend or admin dashboard line. Reason: the business will have no way to run the app without a developer.
• Treating QA as optional. Reason: defects found by customers cost more than defects found by testers, and damage trust.
• Assuming integrations are included. Reason: each one is real work; unlisted integrations become change requests.
• Ignoring dollar-linked lines. Reason: the naira price can move before the project ends.
• Forgetting the recurring lines. Reason: an app with no maintenance budget degrades within a year.
• Cutting discovery to save 5%. Reason: it is the line that prevents the other 95% being spent on the wrong product.

Conclusion

An app quote in Nigeria is eight lines: discovery, design, front-end, backend and admin dashboard, integrations, QA, project management and launch, followed by recurring lines for maintenance, hosting, usage fees and store accounts. Indicatively, front-end and backend together take half the budget, design and QA a quarter, and the rest keeps the project on track and gets it live. Read every quote line by line against the same written scope, check the shape matches the type of app, ask which lines are dollar-linked, and treat a missing line as a missing deliverable rather than a saving. If you have received app quotes and want them compared against a written scope, or need a line-by-line estimate for your own project, Linestech can provide an itemised proposal covering each component, with build and recurring costs separated.

Frequently asked questions

Why is design such a large share of an app budget?

Because design decides what gets built. Every screen, state and flow the developers implement comes from the design, and fixing a bad flow after it is coded costs several times more than fixing it in a wireframe. On a medium app, 10 to 15% of the budget on design is normal; a much smaller share usually means the developers are designing as they go.

Can I reduce the front-end cost by launching on Android only?

Yes, somewhat. Launching Android first removes the iOS testing and store work from the first release, though with a cross-platform framework the code cost is mostly shared. The saving is usually 10 to 20% of the front-end line, not half. Plan the iOS release rather than dropping it, since business customers and higher-spending consumers often use iPhones.

What does "backend as a service" do to the breakdown?

Using a managed backend (authentication, database, storage and notifications as a service) can reduce the backend line by a third or more for simple apps and speed up delivery. The trade-off is recurring dollar-priced usage fees, less control over data location, and limits when business logic becomes complex. It suits MVPs; a custom backend suits products expected to grow.

Should a freelancer's quote have the same lines?

It should cover the same work, even if the document is shorter. Freelancer quotes often omit discovery, QA and project management, which is why they are cheaper and why the client ends up doing that work. Ask the freelancer to state how each of the eight areas will be handled, then compare like with like.

How much of the budget goes on the admin dashboard?

For a medium app, the admin dashboard is typically a quarter to a third of the backend line, or roughly 5 to 10% of the total. A full operations console with reporting, roles and audit logs can be considerably more. Scope it explicitly; "admin panel included" without detail usually means a basic record editor.

Are store fees included in the development cost?

Usually not. The Apple Developer Program yearly fee and the one-time Google Play registration fee are paid by the business directly, in US dollars, because the accounts should be in the business's name. Agencies may charge a modest line for preparing listings and managing review, which is part of Line 8.

What is a reasonable contingency for an app project?

Ten to fifteen per cent of the build cost is a sensible reserve for scope clarifications, third-party surprises and exchange-rate movement. Hold it outside the quote rather than telling the vendor it exists, and release it only against written change requests.

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.

• Nigeria Data Protection Act 2023 — NDPC
• Paystack developer documentation
• Flutterwave developer documentation
• Apple Developer Program
• Google Play Console
• MDN Web Docs — web platform reference
• Flutter documentation