How to Build a Customer App in Nigeria

What a customer app is, and what it is not

A customer app is a mobile application published by a single business for the people who already buy from it, giving them a faster way to do the things they do repeatedly: order again, pay, book, track, renew, or ask for help. It is branded, it is tied to a customer account, and it connects to the business's own systems. It is not:

• A marketplace app, which connects many sellers to many buyers and has to solve supply and demand on both sides.
• A start-up product, which has to find customers as well as serve them.
• A staff or operations app, which is used by your own team to capture work.
• A website in a wrapper. If the app only shows the same pages as the site, customers have no reason to install it.

Customer apps in Nigeria typically fall into a few patterns: reorder apps (gas, water, groceries, pharmacy refills, uniforms), account and billing apps (internet providers, schools, estates, subscriptions), booking apps for regular services (laundry pickup, cleaning, car servicing), loyalty and rewards apps (restaurants, supermarkets, fuel stations) and service apps (insurance claims, utility faults, delivery status). Many combine two patterns; almost none should attempt all five at launch.

Should you build one? Three tests

A customer app is worth building when the answers to three questions are yes. If any answer is no, fix that first or choose a lighter tool.

1. Do customers deal with you repeatedly? Monthly refills, weekly orders, termly payments, recurring bookings. A one-off purchase (a wedding cake, a land survey) does not justify an install. The article on whether Nigerian SMEs need a mobile app treats this threshold in detail.
2. Do you have enough active customers? A few hundred repeat customers can justify a focused app; a few dozen cannot. Below the threshold, a WhatsApp Business setup with a catalogue, payment links and a simple web portal will serve better and cheaper.
3. Is your operational data in a system? The app can only show order status, balances and delivery times if your business records them somewhere other than a notebook. If not, the first project is the backend or a simple business management system, not the app.

Where a business passes tests one and two but fails three, the practical route is to build the backend and a web portal first, then add the app when the data is reliable. The guide on how to build a customer portal for your business covers that route.

Core features of a customer app for a Nigerian business

The table below separates features most customer apps need from those that depend on the business model. Build the first column in version one; add from the second column only where the customer's repeat job requires it.

Two features deserve emphasis. First, the "core repeat action" should take no more than three taps from opening the app. Second, the admin dashboard is not optional: an app whose orders land in nobody's inbox is worse than WhatsApp. The related guide on how to build a mobile app with an admin dashboard explains what staff need to see.

How to build a customer app: ten steps

1. Name the job. Write one sentence: "Customers use the app to (action) without (current friction)." Example: "Customers reorder their monthly gas refill without calling and waiting for a price." Everything not serving that sentence is deferred.
2. Map the current journey. How does a customer do the job today, on WhatsApp or by phone? Where do they wait, repeat themselves or send screenshots? Those points become the app's screens.
3. Write the requirements. Screens, fields, statuses, notifications, payment methods, roles for staff, and the systems the app must connect to. A short, precise document prevents scope drift and makes quotations comparable. The mobile app requirements checklist for Nigerian businesses is a useful template.
4. Choose the platform approach. For a customer app aimed at Nigerian consumers, Android is the priority; iOS follows. A cross-platform framework (Flutter or React Native) usually delivers both from one codebase at reasonable cost. Native is justified only for specific hardware or performance needs.
5. Design for the cheapest phone your customers use. Small app size, light screens, readable at low brightness, working on slow data with clear loading and offline states. Test the designs on a mid-range Android device, not only on a designer's monitor.
6. Build the backend and admin dashboard first. Customer accounts, orders, statuses, prices, notifications and integrations live here. Staff should be able to run the business from the dashboard before customers see the app.
7. Integrate payments and messaging. Paystack, Flutterwave, Monnify or similar for cards, transfers and virtual accounts; SMS or WhatsApp for OTP and confirmations; push notifications for status. Automate payment confirmation through webhooks so staff never confirm transfers by screenshot.
8. Test with real customers. A closed beta with 20 to 50 friendly customers for two to four weeks reveals address problems, confusing screens and payment edge cases. The mobile app testing checklist lists what to cover.
9. Publish. Google Play first (one-time developer registration fee, historically US$25; verify current fee), then the Apple App Store (yearly programme fee, historically US$99; verify). Prepare privacy policy, screenshots and store listing text in advance; the publishing guides in this cluster walk through both stores.
10. Run the adoption plan. Installation does not happen on its own. The section below sets out what works.

What changes for Nigerian businesses

Building for Nigerian customers changes several defaults that overseas templates assume.

• Phone number is the identity. Customers do not want to create passwords or remember emails. Phone-number login with an OTP by SMS or WhatsApp matches how they already identify themselves to you. Keep a fallback (call verification or staff-assisted login) for numbers that fail to receive SMS.
• Bank transfer is a first-class payment method. Card payments alone will lose orders. Offer transfer to a dedicated virtual account per order or per customer so confirmation is automatic, plus pay-on-delivery where the business already accepts it.
• Addresses need landmarks. Street numbering is inconsistent in most cities. Address entry should include a landmark field, a map pin, and the ability to save "Home", "Office" and "Mummy's shop" as named locations. Delivery staff should receive both the pin and the text.
• Android first, small size. The majority of your customers will be on Android devices with limited storage. Every megabyte and every unnecessary permission reduces installs.
• WhatsApp remains the escalation channel. A visible button that opens a chat with the customer's account number pre-filled keeps trust intact and stops the app from feeling like a wall between the customer and the business.
• Power and data interruptions. Show the last known status when offline, queue actions where safe, and never lose a half-completed order because the connection dropped.
• Trust and data protection. Customers give you phone numbers, addresses and payment details. A clear privacy notice, minimal permissions and sensible security are required under the Nigeria Data Protection Act 2023 and are also what makes customers comfortable. Verify current obligations with the Nigeria Data Protection Commission (NDPC) or a qualified adviser.
• Exchange-rate exposure. Cloud hosting, push services, map APIs and SMS gateways are often priced in US dollars. Budget recurring costs with room for naira movement.

Example (hypothetical): an Ibadan cooking-gas refill company

Example (hypothetical): a cooking-gas retailer in Ibadan delivers refills to about 1,800 households and small restaurants from two filling points. Orders arrive by WhatsApp and phone; the price per kilogram changes with supply; customers ask for the current price, agree a quantity, transfer money, send a screenshot and wait. Two staff spend the day answering the same price question and matching screenshots to orders. The company passes all three tests: monthly repeat purchases, a customer base in the low thousands, and an order book already kept in a spreadsheet system. It commissions a customer app with one job: reorder a refill in under a minute.

• Login: phone number and OTP; existing customers are pre-loaded from the order records so their addresses appear on first login.
• Reorder screen: cylinder size, quantity, today's price shown live, saved address with landmark, preferred delivery window.
• Payment: transfer to a virtual account displayed in the app (confirmed automatically) or card via a gateway; cash on delivery for long-standing customers.
• Status: confirmed, filled, out for delivery, delivered, with a push notification at each step and the rider's first name and phone number when dispatched.
• Staff dashboard: orders by delivery window and area, price updates pushed to all customers, rider assignment, daily reconciliation.
• WhatsApp button: opens a chat with the order number pre-filled for any exception.

Adoption is driven by placing a sticker with the download link and a first-order discount on every delivered cylinder, and by staff replying to price questions on WhatsApp with "Today's price is in the app, and you can order directly there." The example is illustrative; a real business would measure installs, repeat orders in the app and the change in WhatsApp volume over the first three months.

What a customer app costs in Nigeria

The figures below are indicative 2026 ranges for Nigerian projects; actual quotes vary with scope, vendor, integrations and the exchange rate. One-off development is separated from recurring costs.

Cost drivers to watch: the number of payment methods, whether the backend already exists, the quality of your customer and product data, and whether you need iOS at launch. Compare two or three written quotations on the same requirements document; a cheaper quote that omits the admin dashboard, offline handling or payment webhooks is not cheaper. The full app development cost guide for Nigeria explains the drivers in more depth.

Getting customers to install and keep the app

Adoption is the stage most customer-app projects fail. Customers already have a channel that works, and the app has to be visibly better for the job they repeat. The practices below are what businesses in Nigeria have found effective; the right mix depends on your customers. Make the first install easy:

• Pre-load existing customers so the first login shows their history and addresses.
• Put the download link everywhere the customer already sees you: WhatsApp auto-replies, invoices, receipts, delivery packaging, shop counters, Instagram bio.
• Use a short link or QR code; a direct Play Store link converts better than "search for our app".

Give a reason tied to the job:

• A first-order discount or free delivery in the app.
• A benefit that only the app can give: live price, live status, instant payment confirmation, priority slots.
• Staff should redirect routine requests to the app consistently and kindly, not refuse to help.

Keep customers using it:

• Notifications that are useful (status, due dates, price changes) rather than promotional noise.
• Reorder in three taps; saved details never asked twice.
• A visible WhatsApp button so nobody feels trapped.
• Fix reported problems quickly and tell the customer it was fixed.

Measure:

• Installs, first-order completion, repeat orders in the app, share of orders through the app versus WhatsApp, and uninstall rate. Review monthly for the first six months.

Mistakes to avoid

• Building everything in version one. A five-pattern app takes a year and launches late. One job done well earns the right to add the next.
• Launching without a staff dashboard. Orders that land in a database nobody watches are lost orders. Staff tooling is part of the customer app.
• Card-only payments. Bank transfer and pay-on-delivery are how many customers pay. Omit them and orders fall back to WhatsApp.
• Password logins. Nigerian customers will not remember a password for a gas app. Phone number plus OTP.
• Ignoring app size and low-end devices. A heavy app on a 32GB Android phone gets uninstalled the first time storage runs low.
• No adoption plan. The app is published, nobody is told, and after three months the owner concludes customers do not want apps.
• Treating the app as an advert. Promotional pushes every day teach customers to disable notifications, which kills the status alerts that made the app useful.
• Skipping the privacy notice and permissions review. Both app stores and the NDPA require it, and customers notice when an app asks for contacts or microphone access it does not need.

Conclusion

A customer app in Nigeria succeeds when it is built for one repeated job, connected to real operational data, designed for phone-number login, bank transfers and low-end Android devices, and launched with a deliberate adoption plan rather than a hopeful store listing. Pass the three tests, write a short requirements document, build the backend and staff dashboard before the customer screens, test with real customers, and measure installs against orders for six months. If you already have repeat customers and the routine of orders, payments and status questions is filling your WhatsApp lines, an app is a reasonable next step. If the data is still in a notebook, fix that first. Linestech designs and builds customer apps for Nigerian businesses, from the backend and admin dashboard to Play Store and App Store publishing, with Paystack, Flutterwave and WhatsApp integration. Tell us the one job your customers repeat most and we can outline a focused first version and an indicative budget.

Frequently asked questions

Can we build the app on top of our existing website or WhatsApp ordering?

Often, yes. If the website already has customer accounts, orders and a backend, the app becomes another front end to the same system, which reduces cost and keeps data consistent. WhatsApp ordering has no backend to reuse, but the order history can be imported to pre-load customers. The article on turning a website into a web app describes the shared-backend approach.

Do we need both Android and iOS at launch?

For most Nigerian consumer bases, Android first is the sensible choice, with iOS added once the Android version is stable and adoption is proven. If your customers are largely corporate or affluent, iOS may matter from the start. A cross-platform build keeps the option open without doubling the cost.

How do customers pay inside the app?

Through a payment gateway (cards, transfers, USSD where offered), through a virtual account number for direct bank transfer with automatic confirmation, or by pay-on-delivery recorded by the rider. Offering at least the first two is standard. Gateway fees apply per transaction and should be checked against the provider's current schedule.

What if a customer has a problem the app cannot handle?

The app should have a WhatsApp and call button that opens a conversation with the customer's account or order number already included. Staff then see the same record in the dashboard. The goal is not to remove human contact but to make it rarer and better informed.

How long does it take to build a customer app?

An indicative range is two to four months for a focused first version and four to seven months for a standard app with payments, notifications and a dashboard, including a closed beta. The largest variable is how quickly the business can supply clean customer, product and price data and make decisions on scope.

Who owns the app and its code after it is built?

That depends on the contract. Insist on written terms that transfer ownership of the source code, the store accounts and the backend to your business on final payment, and that the developer accounts for Google Play and Apple are registered in the company's name. The articles on app development contracts and code ownership explain what to look for.

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 Commission (NDPC)
• Paystack developer documentation
• Flutterwave developer documentation
• Apple Developer Program
• Node.js documentation