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

What you need before you start

A Play launch stalls most often on account verification and policy declarations, not on code. Get these ready while the app is still in development.

• A Google account owned by the business, not a developer's personal Gmail. Use an address on your own domain through Google Workspace if you have it, or a dedicated business Gmail with recovery details controlled by a director.
• The right account type. Play Console distinguishes personal and organisation accounts. An organisation account requires a D-U-N-S number as of 2026 (verify the current requirement) and shows the organisation's name and address publicly. A personal account shows the individual's name and, in most cases, a public address.
• Government-issued ID for identity verification, and organisation documents if enrolling as a company.
• A card that can pay a US-dollar fee. Check the international limit on any naira card first, or use a dollar card.
• A privacy policy URL on your own domain. Play requires it for every app, whether or not you think you collect data.
• A developer email and, where required, a public address and phone number that will be displayed on your store listing.
• A signed release build as an Android App Bundle (.aab), plus an upload key managed by your developer.
• Store assets: an icon, a feature graphic, screenshots and text, prepared to Play's current specifications.

If you plan to sell paid apps or in-app products, check Play's current list of supported merchant locations and confirm that a Nigerian business can set up a payments profile.

Step 1: Create and verify a Play Console developer account

The first step is to register as a developer in Google Play Console and complete verification. Google has tightened this process over the past few years, so build in time.

1. Sign in with the business Google account and start developer registration.
2. Choose personal or organisation. For a registered Nigerian company, choose organisation and have the D-U-N-S number, legal name and address ready.
3. Enter developer details: the public developer name, contact email and phone. These are checked, and the email and phone must be verified.
4. Pay the one-time registration fee.
5. Complete identity verification (ID document, and organisation verification if applicable). Google may take several days to confirm.

Two rules matter for new accounts. First, Google requires personal developer accounts created after late 2023 to run a closed test with a minimum number of opted-in testers (12 as of the latest policy; verify) for at least 14 continuous days before they can apply for production access. Organisation accounts are not subject to this requirement, which is one more reason for a business to enrol as an organisation. Second, the details you enter become public: pick a developer name that matches your brand and an email that is monitored. Once the account is active, add your agency or in-house developers as users with the permissions they need (release management, store listing) rather than sharing the owner login. The owner should be the business.

Step 2: Prepare the build and app signing

Google Play requires new apps to be uploaded as an Android App Bundle rather than an APK. The bundle lets Play generate optimised APKs for each device, which reduces download size, something that matters for Nigerian users paying for data. Three technical items your developer must handle:

• Play App Signing. Google holds the app signing key and your developer keeps an upload key. This is mandatory for new apps. Make sure the upload key is stored in a place the business can access if the developer relationship ends.
• Target API level. Play requires new apps and updates to target a recent Android API level. The requirement moves every year; an app built to an old target will be blocked from submission. Confirm the current deadline in Play Console.
• Package name. The application ID (for example ng.com.yourbusiness.app) is permanent once published. Choose it deliberately.

Also prepare for device diversity. Nigerian Android users are spread across budget devices from brands such as Tecno, Infinix, itel and Samsung, many with limited RAM and storage. Test the release build on at least one low-end device, and keep the download size as small as the feature set allows.

Step 3: Create the app and complete the app content declarations

In Play Console, choose Create app, enter the app name, default language, whether it is an app or game, and whether it is free or paid (a free app cannot later be made paid). The console then presents a dashboard of tasks. The App content section is where policy compliance is declared, and it is where Nigerian apps most often get stuck.

Three declarations deserve particular attention. Data safety. This form asks what data the app collects (location, personal info, financial info, device IDs and so on), whether it is shared with third parties, whether transfer is encrypted, and whether users can request deletion. Google cross-checks it against the app's behaviour and third-party SDKs. A payment SDK, analytics SDK or crash reporter each adds to what you must declare. Account and data deletion. If the app allows account creation, Play requires an in-app way to delete the account and data, and a web link for deletion that is listed in the Data safety section. Build this before launch; it is not optional. Financial features. Google Play has country-specific requirements for personal loan apps. As of 2026 its policy for Nigeria requires personal loan apps to submit evidence of approval from the Federal Competition and Consumer Protection Commission (FCCPC) under the digital lending framework, alongside the standard loan disclosures. If your app touches lending, budget time for this and verify the current policy text and FCCPC requirements before you build.

Step 4: Complete the store listing

The store listing is your app's page on Google Play. Google reviews it for accuracy and policy compliance, and customers use it to decide whether to install.

Write the description for a Nigerian reader on a phone: what the app does, who it is for, which cities or areas it serves, and how payment works. Avoid keyword lists, competitor names and unverifiable claims; Play's metadata policy prohibits misleading text, and keyword-stuffed descriptions can be rejected.

Step 5: Use the testing tracks

Play Console offers four release tracks, and using them in order is the cheapest insurance against a bad launch.

• Internal testing: up to 100 testers, available within minutes, no review. Use it for the development team and the business owner.
• Closed testing: invited testers by email list or Google Group. This is the track new personal accounts must use for their mandatory testing period. Use it for staff and a handful of trusted customers.
• Open testing: anyone can join from the store listing. Useful for a wider Nigerian beta with real devices and networks.
• Production: the live release, with optional staged rollout.

For a Nigerian launch, closed or open testing should include people on mobile data in more than one city and on at least one low-end device. Watch specifically for slow image loading, failed OTP delivery on particular networks, payment flows that time out, and screens that break on small displays. Play Console also generates a pre-launch report by running the app automatically on a set of devices. Read it; it catches crashes and accessibility problems before Google's reviewers or your customers do.

Step 6: Submit for review and roll out to production

When the app content declarations, store listing and testing are complete, create a production release, upload the final bundle, write release notes and choose the countries. Include Nigeria and any other markets you serve. Then send the release for review. Google states that review can take up to seven days, and longer in some cases. New developer accounts and apps in sensitive categories (finance, health, apps for children) tend to take longer. Once approved, the app goes live automatically unless you chose managed publishing, which lets you control the exact go-live time and coordinate with an iOS release or a marketing push. Use staged rollout for the first production release and for major updates: release to a small percentage of users, watch crash rates and reviews for a day or two, then expand. If something is wrong, halt the rollout before most customers are affected.

Why Play rejects or removes apps

Google enforces policy at submission and continuously afterwards, so an app can be approved and later removed. The common causes are avoidable.

A rejection arrives with a policy reference. Fix the stated issue, resubmit, and use the appeal process only where the finding is genuinely wrong.

What changes when you publish from Nigeria

Android is the main event. Because most Nigerian smartphone users are on Android, the Play release is typically where the majority of installs, revenue and support requests will come from. Invest in testing here first. Data-conscious users. Download size and data usage influence whether customers install and keep the app. App Bundles, compressed images and sensible caching are not polish; they are conversion factors. Verification and public details. Google's identity and organisation checks are strict and can take time. The public developer name, email and (for many accounts) address appear on your listing, so decide in advance which business details to publish. Regulated categories. Lending, payments and health apps face policy checks that reference Nigerian regulators. Loan apps in particular need FCCPC evidence under Play's financial-services policy (verify current requirements). None of this is legal advice; confirm with the relevant regulator and your counsel. Sideloading is common, but do not rely on it. Many Nigerian users are used to installing APKs sent over WhatsApp. It is not a substitute for Play: APKs shared this way cannot be updated automatically, trigger security warnings, and undermine trust. Publish on Play and share the store link instead. Trust signals matter. In a market with widespread fraud concerns, a verified developer name, a working support email, a clear privacy policy and prompt replies to reviews all influence whether Nigerians install a financial or e-commerce app.

Example (hypothetical): an Abuja school's parent app

Example (hypothetical): a private secondary school in Abuja commissions an Android app so parents can see results, pay fees and receive announcements. The school registers a Play Console organisation account under its CAC-registered name, which requires obtaining a D-U-N-S number first; that takes about two weeks and is started before development finishes. While the build is completed, the bursar's office prepares a privacy policy that describes what the app stores about students and parents, in line with the Nigeria Data Protection Act 2023. The developer confirms that fee payment is a real-world service, so it uses a Nigerian payment gateway rather than Play Billing. The first internal test goes to the school's IT officer and three teachers. A closed test then goes to 30 parents by email, including several outside Abuja who use the app on mobile data. Two issues are found: result PDFs are large and slow to open, and the fee-payment page fails on one bank's card flow. Both are fixed. The Data safety form declares collection of names, contact details, payment information (handled by the gateway) and device identifiers from the crash-reporting SDK. An in-app account deletion option and a web deletion form are added. The production release is submitted with test credentials for a demo parent account and approved after four days. The school uses managed publishing to go live on the first day of term and rolls out to 20 percent of users first, then to everyone after 48 hours with no crash spikes.

Mistakes to avoid

• Registering under a developer's personal Google account. The business should own the account; grant developers user permissions.
• Choosing a personal account for a company. It triggers the closed-testing requirement and shows a person's name and address publicly.
• Losing the upload key. Store it where the business can retrieve it if the developer disappears.
• Filling the Data safety form from memory. Audit every SDK; mismatches lead to removal after launch.
• Shipping without account deletion. It is a policy requirement for apps with sign-up.
• Skipping low-end device testing. A crash on a widely used budget phone becomes a one-star review within hours.
• Ignoring the pre-launch report. It is free and catches obvious crashes.
• Rolling out to 100 percent on day one. Use staged rollout so a bug affects a fraction of customers.

Conclusion

Publishing on Google Play is a sequence of account, build, declaration, listing, testing and rollout steps. The technical work is your developer's; the account ownership, organisation verification, privacy policy, Data safety accuracy and financial-services documents are the business's responsibility, and they take longer than most people expect. Enrol as an organisation, keep the account and keys under business control, declare data practices honestly, test on real Nigerian devices and networks, and roll out gradually. If you are preparing an Android launch and want the build, declarations and Play Console set-up handled correctly, Linestech develops and publishes Android and iOS apps for Nigerian businesses and can help you plan the testing and release process.

Frequently asked questions

Can a Nigerian business open a Google Play developer account?

Yes. As of 2026, developers in Nigeria can register in Play Console as individuals or organisations, subject to identity or organisation verification. Selling paid apps or in-app products depends on Google's current list of supported merchant locations, so check that separately before planning a paid model.

Do I have to run a closed test before launching?

If you register as a personal developer account created after late 2023, Google requires a closed test with a minimum number of opted-in testers (12 as of the latest policy) for at least 14 continuous days before you can apply for production access. Organisation accounts are not subject to this rule. Verify the current figures in Play Console.

How long does Google Play review take?

Google says review can take up to seven days and sometimes longer, particularly for new accounts and for apps in sensitive categories such as finance, health or apps for children. Plan for a week, and add time for at least one round of corrections on a first release.

Can I use Paystack or Flutterwave in my Android app?

Yes, for physical goods and real-world services such as deliveries, product orders, bookings and school fees. For digital content and features consumed inside the app, Google Play's billing system is required under its payments policy. Classify each product before building the checkout and verify the current policy text.

What is the difference between an APK and an Android App Bundle?

An APK is a single installable package. An Android App Bundle (.aab) is the publishing format Play now requires for new apps: Google uses it to generate smaller, device-specific APKs for each user, which cuts download size. Bundles are for uploading to Play; users still receive APKs generated by Play.

Why was my app removed after it had been approved?

Google enforces policy continuously, so an app can be removed later if its behaviour, SDKs or listing no longer match its declarations, or if a policy changes. Common triggers are Data safety mismatches, missing account deletion, expired target-API compliance and metadata violations. Read the notice, fix the issue and resubmit.

Should we launch on Play before the App Store?

For most Nigerian businesses, yes. Android accounts for the majority of local smartphone users, so the Play release reaches more customers sooner and surfaces real-world problems faster. Launch iOS once the Android app is stable, or coordinate both if you serve corporate or diaspora customers who expect iPhone support.

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)
• Nigeria Data Protection Act 2023 — NDPC
• Paystack developer documentation
• Flutterwave developer documentation
• Google Play Console
• Core Web Vitals — web.dev
• Google Search Central Blog