How to Publish an App on the Apple App Store: A Step-by-Step Guide for Nigerian Businesses

What you need before you start

Before anyone touches App Store Connect, a Nigerian business should have the following in place. Each item has caused real launch delays when left to the last minute.

• A legal entity and matching name. For organisation enrolment, Apple checks that the entity exists. Your CAC registration name should match what you enter, exactly.
• A D-U-N-S number for organisation enrolment. This free identifier from Dun & Bradstreet can take days to weeks to obtain or correct, so request it first.
• An Apple ID with two-factor authentication that belongs to the business, not a developer's personal account.
• A way to pay a US-dollar fee. Many naira debit cards have low or zero international spending limits, so a dollar card or virtual dollar card is often needed.
• A public website and business email on your own domain; Apple asks for these during organisation enrolment.
• A privacy policy URL and a support URL on your own domain. Apple requires both.
• A Mac with Xcode, or a cloud build service with macOS machines. Flutter and React Native apps still need to be compiled and signed for iOS on macOS.
• Test devices: at least one physical iPhone; an iPad if the app claims iPad support.

Individual enrolment is faster but shows the person's name as the seller. Organisation enrolment shows the company name, supports multiple team members with different roles, and is what corporate customers expect. For a registered Nigerian business, organisation enrolment is nearly always the right choice.

Step 1: Enrol in the Apple Developer Program

The first step is to enrol the business in the Apple Developer Program. Enrolment is done through Apple's developer website or the Apple Developer app. As of 2026 the programme is available to developers in Nigeria, but confirm the current list of supported countries and the fee on Apple's site before you plan a timeline. The process for an organisation typically runs as follows:

1. Sign in with the business's Apple ID and choose the organisation entity type.
2. Enter the legal entity name, D-U-N-S number, address, website and phone number. Apple verifies these against the D-U-N-S record.
3. Confirm that the person enrolling has legal authority to bind the organisation, or name the person who does. Apple may call or email that person.
4. Agree to the licence agreement and pay the yearly fee. Enrolment becomes active once payment clears and verification completes, which can take from a day to a couple of weeks.

The D-U-N-S record must show the same legal name and address you use with Apple; mismatches are the most common enrolment delay. Apple's verification calls come from outside Nigeria, so make sure the number on file is answered by someone who knows what the call is about. Once enrolled, give your development agency the roles it needs in App Store Connect (Developer, App Manager) rather than sharing the Account Holder login. The Account Holder should be the business owner or a director, because that role signs agreements and controls the account.

Step 2: Prepare the build, signing and privacy requirements

The build is where your developer's work meets Apple's technical rules. Even if an agency handles this, a business owner should understand what is being set up, because several items are legal or commercial decisions rather than code.

Identifiers, certificates and provisioning

• Bundle identifier: a unique reverse-domain string (for example ng.com.yourbusiness.app). It cannot be changed after publication, so choose it carefully.
• Distribution certificate and provisioning profile: these prove the build comes from your account. Xcode's automatic signing handles most of it, but the certificate belongs to your developer account, not the agency's.
• Capabilities: push notifications, Sign in with Apple, Apple Pay and similar features must be enabled on the App ID before the build will work.

Privacy and data requirements

Apple's privacy rules are enforced at review. Your developer needs answers to these questions before uploading:

• What data does the app collect, and is it linked to the user's identity? This feeds the App Privacy section (the privacy "nutrition label").
• Does the app use third-party SDKs that require a privacy manifest? Since 2024 Apple has required manifests for certain common SDKs; check the current list.
• Which permissions does the app request (camera, location, contacts)? Each needs a purpose string that says plainly why. Vague purpose strings are a common rejection.
• Can users create an account? If so, they must also be able to delete it from inside the app (Guideline 5.1.1). Design this in from the start.
• Does the app use encryption beyond standard HTTPS? You will answer an export compliance question at upload; most apps can declare an exemption.

Payments: the rule that catches Nigerian businesses

Apple's Guideline 3.1.1 requires digital goods and services consumed in the app (content subscriptions, premium features, virtual items) to be sold through Apple's in-app purchase system, on which Apple takes a commission. Physical goods and real-world services (food delivery, ride booking, product orders, hotel bookings, school fees) may use your own provider such as Paystack, Flutterwave or bank transfer. Classify each purchase before you build the checkout, because reviewers will test it, and verify the current guideline text since Apple revises these rules.

Step 3: Create the app record in App Store Connect

With the build in progress, create the app record in App Store Connect. This is the container that holds your listing, builds, pricing and review information.

1. Go to My Apps and choose New App.
2. Select iOS (and any other platforms), enter the app name, primary language, bundle ID and an SKU (an internal reference of your choosing).
3. Choose user access if you want to restrict which team members can see the app.

The app name must be unique across the App Store and is limited to 30 characters. If a competitor has taken the obvious name, you will need a variant; decide this early so the brand, domain and store name match. At this stage also set up pricing and availability (free or paid, and which territories; include Nigeria and any diaspora markets, and note that paid apps and in-app purchases require the Paid Apps agreement with banking and tax details from the Account Holder) and app information (category, subtitle, content rights and the age rating questionnaire, answered honestly).

Step 4: Test with TestFlight

TestFlight is Apple's beta distribution tool, and it is the single best way to avoid an embarrassing first review. Once your developer uploads a build from Xcode or a build service, it appears in App Store Connect and can be distributed in two ways.

• Internal testing: up to 100 members of your App Store Connect team. Builds are available almost immediately without review.
• External testing: up to 10,000 testers invited by email or public link. The first build for external testers goes through a lighter Beta App Review, which can take a day or so.

Use external testing for real Nigerian users on real networks. Ask customers or staff in Lagos, Abuja and a smaller city to complete the main flows on mobile data, not office Wi-Fi. Look for screens that hang on slow connections without a retry, OTP and payment flows that fail on specific banks or networks, crashes on older iPhones your developers do not own, and text that overflows on smaller screens. TestFlight builds expire after 90 days. Budget two to three rounds of external testing for a first release.

Step 5: Complete the store listing

The listing is your app's sales page. Reviewers read it to check that the app does what it claims, and customers read it to decide whether to install. Complete the following in App Store Connect for each localisation you support.

Screenshots deserve real effort: they are the first thing a potential customer sees, and Apple rejects screenshots that show features the app does not have. Show the actual app in use.

Step 6: Submit for App Review

When the build is uploaded and the listing is complete, you attach the build to the version, fill in the review information, and submit. The review information section is where many Nigerian apps fail unnecessarily. It needs:

• A demo account that works from outside Nigeria. If your login uses an SMS OTP sent to a Nigerian number, the reviewer cannot complete it. Provide a test account that bypasses OTP or uses a fixed code, and confirm it is active on the day you submit.
• Notes for the reviewer explaining anything unusual: that the app serves Nigeria, that BVN or NIN verification is in test mode for the demo account, that a Nigerian payment provider is used for physical goods, and how to reach the key features quickly.
• Contact information for someone who will respond within hours during the review window.

Apple has said the large majority of submissions are reviewed within a day or two, but plan for up to a week and for at least one rejection on a first release. You can also choose how the app is released after approval: immediately, manually, or on a scheduled date. Manual release is useful for coordinating with a marketing push or a Play Store launch on the same day.

Why apps get rejected, and how to avoid it

Most rejections are avoidable and fall into a small number of categories. The list below maps common causes to the guideline area involved.

A rejection is not a ban. Read the reason, fix the specific problem, respond politely in Resolution Centre and resubmit.

What changes when you publish from Nigeria

For a Nigerian business, the process is the same as anywhere else, but four practical points differ. Paying and getting paid in dollars. The Developer Program fee is USD-denominated, so budget for exchange-rate movement between planning and renewal. If you sell paid apps or in-app purchases, check that Nigeria is currently supported for the Paid Apps agreement and what banking details Apple requires. Reviewers are not in Nigeria. They test from abroad with no Nigerian phone number. Any feature that depends on a Nigerian SIM, a local IP address, BVN lookup or a live bank transfer needs a demo mode. Geo-blocking the app to Nigeria will show the reviewer an error screen and get it rejected. Android comes first for most customers. Most Nigerian smartphone users are on Android, so iOS is often the second launch. It is still worth doing: iPhone users include corporate customers, higher-spend consumers and diaspora, and partners notice when an app is "Android only". Plan both releases and coordinate the dates. Regulated sectors need documents ready. Fintech, lending, health and insurance apps are reviewed against additional guidelines. Have licences, terms and regulatory references ready and cite them in the review notes. This is not legal advice; confirm requirements with your regulator and counsel.

Example (hypothetical): a Lagos pharmacy chain's first iOS release

Example (hypothetical): a pharmacy chain with six Lagos branches already has an Android app for prescription refills and delivery. Corporate HMO clients and a growing number of Lekki customers have asked for an iPhone version. Week 1: the finance director requests a D-U-N-S number using the exact CAC name and head-office address, and obtains a dollar card for the fee. The IT lead creates a business Apple ID with two-factor authentication. Week 2: enrolment is submitted and approved after five working days. The agency is added to App Store Connect with App Manager and Developer roles. Weeks 2 to 4: the agency builds the iOS version from the existing Flutter codebase, adds in-app account deletion and writes purpose strings for camera (scanning prescriptions) and location (delivery address). Week 5: the first TestFlight build goes to 40 external testers. Two problems surface: the payment screen times out on one bank's card flow on mobile data, and prescription photo upload fails on an older iPhone. Both are fixed in build three. Week 6: the listing is completed with real screenshots showing naira prices. The review notes explain that medicines are physical goods delivered by the pharmacy's own riders, that payment uses a Nigerian gateway, and that the demo account uses a fixed OTP. The app is approved on the second submission after a purpose-string fix and released manually to coincide with a WhatsApp broadcast to existing customers. Total elapsed time: six weeks, about one of which was waiting on Apple. Build work ran in parallel with enrolment, which is what kept the timeline short.

After approval: releases, updates and monitoring

• Version updates go through App Review again, usually faster. Bundle small fixes together rather than submitting every day.
• Phased release rolls an update out gradually over seven days, so a bug affects fewer people.
• Crash reports and ratings are visible in App Store Connect. Check both weekly and reply publicly to complaints; Nigerian customers read those replies.
• Annual renewal keeps the app live. If the membership lapses, the app is removed from the store. Put the renewal date in the finance calendar and keep the dollar card funded.
• Guideline changes happen every year; a new privacy or SDK requirement can block your next update if ignored. Ongoing upkeep is covered in our guide to app maintenance cost in Nigeria.

Mistakes to avoid

• Enrolling under a developer's personal Apple ID. If the relationship ends, you lose control of the app. The business should be the Account Holder; the agency gets roles.
• Leaving the D-U-N-S request until the app is ready. It is free but slow, and mismatches restart the clock.
• Assuming a naira card will pay the fee. Check the card's international limit before enrolment day.
• Selling digital subscriptions through a card gateway inside the app. Those fall under in-app purchase rules; physical goods and services do not.
• Forgetting the renewal. A lapsed membership takes the app off the store without warning to your customers.

Conclusion

Publishing on the Apple App Store is a defined sequence: enrol the business, prepare a compliant build, create the app record, test through TestFlight, complete an honest listing, and submit with a demo account that works from anywhere. The technical steps are the developer's job; the account, the legal entity, the dollar payment, the privacy policy and the review notes are the business's job, and starting them early keeps the launch on schedule. For a Nigerian business the extra considerations are paying in dollars, making sure reviewers abroad can use the app, classifying payments correctly, and coordinating the Android and iOS releases. If you are planning an iOS release and want the build, testing and submission handled properly, Linestech develops and publishes Android and iOS apps for Nigerian businesses and can guide you through Developer Program enrolment and App Review preparation.

Frequently asked questions

Can a Nigerian company enrol in the Apple Developer Program?

As of 2026, Apple lists Nigeria among the countries where the Developer Program is available, and Nigerian companies can enrol as organisations with a D-U-N-S number and a matching legal entity. Requirements and country availability change, so confirm the current position on Apple's developer website before planning a launch date.

Do I need a Mac to publish an iOS app?

Yes, in practice. iOS apps must be compiled and signed with Xcode on macOS, even when built with Flutter or React Native. If nobody in the team has a Mac, a cloud build service with macOS machines can do the building and uploading, but someone still needs access to Xcode tools for signing set-up.

How long does App Review take?

Apple has said most submissions are reviewed within about a day or two, and updates are often faster. For planning, allow up to a week for a first release, plus time for at least one rejection and resubmission. Enrolment and D-U-N-S verification add one to two weeks before you can submit anything.

Can I use Paystack or Flutterwave in my iOS app?

Yes, for physical goods and real-world services such as deliveries, bookings, product orders and school fees. For digital goods consumed within the app, such as premium features or content subscriptions, Apple requires its in-app purchase system. Check the current App Review Guidelines, section 3.1, and classify each product before building the checkout.

What happens if my app is rejected?

You receive a message in App Store Connect with the guideline reference and usually a screenshot or explanation. You can fix the issue and resubmit, reply to ask for clarification, or appeal if you believe the decision is wrong. Rejections are routine on first submissions and do not affect future reviews.

Who should own the Apple developer account, the business or the agency?

The business. The Account Holder role should be a director or owner using a company Apple ID; the agency gets Developer or App Manager roles. If an agency insists on publishing under its own account, make sure the contract provides for transferring the app to yours, and understand that transfers have conditions.

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.

• Corporate Affairs Commission (CAC)
• Paystack developer documentation
• Flutterwave developer documentation
• Apple Developer Program
• Core Web Vitals — web.dev
• Flutter documentation