Choosing an app store and Google Play launch service Canada businesses can rely on means getting three answers before you sign: what publishing will cost, how long it will take, and what could stop it. This guide sets out a 2026 launch plan that answers all three. It is written for the people who will own the app once it is live. Where Apple or Google sets a figure that changes often, we say so and point you to the page that sets it.
What an app store and Google Play launch service in Canada covers
A store launch runs in a fixed order:
- Developer accounts. An Apple Developer Program membership and a Google Play Console account, both registered under the correct legal entity.
- Listings and metadata. Name, description, category, age rating, screenshots and support contact, written for each store.
- Privacy policy and privacy labels. A live policy page, Apple's App Privacy answers and Google's Data safety form. Both must match what the app collects, including what its analytics and push-notification libraries collect.
- Build upload. A signed release build sent to App Store Connect and the Play Console.
- Testing. TestFlight for iOS, and a closed test on Google where the rules require one.
- Submission and review. Each store approves the app or returns specific reasons.
- Release. You pick a date, or a staged rollout on Google, and the app goes live.
You decide the things only you can decide: the legal entity behind the accounts, the app name and listing wording, the substance of the privacy policy (it describes your data), pricing, and final approval to submit. Eskore runs build configuration and signing, drafts the listings and privacy answers, submits to both stores, handles review feedback and resubmissions, and manages the release.
Store rules also shape the build, so they belong in the plan from the start. Apple's App Review Guidelines require apps that let users create an account to let them delete it inside the app. A login-gated app needs a working test account for the reviewer. If these are designed in, launch is a checklist. If they are found at submission, launch becomes a rebuild.
What publishing on the App Store and Google Play costs in 2026
Neither store charges per app. Both charge per developer account, and one account can publish several apps.
| Account | Fee (USD) | Renewal | What to know |
|---|---|---|---|
| Apple Developer Program (individual or organisation) | 99 | Yearly | Required to publish on the App Store |
| Apple Enterprise Program | 299 | Yearly | Does not allow App Store distribution, so it is not the route for a store launch |
| Google Play Console registration | 25 | One-time | No annual renewal. Prepaid cards are not accepted |
Both stores also take a share of paid sales and in-app purchases:
- Apple: 30% standard. The Small Business Program reduces this to 15% if your proceeds in the previous year were no more than USD 1 million. You must enrol to get the lower rate.
- Google: Third-party guides report a service fee of 10 to 30%, depending on market and programme. Those guides are not the source, so check Google's own commission schedule before you model revenue.
Confirm the account fees on Apple's enrolment page and in Google's Play Console help before you pay. The larger costs are the build, the backend and ongoing updates, which are scoped separately.
Canadian pricing and the Google fee date
We have not published Canadian-dollar figures. Apple and Google set prices by storefront and currency, so a Canadian business may be charged a local price rather than the USD figure converted at its bank's rate. Check the price shown for Canada on Apple's enrolment page and on Google's Play Console help page on the day you pay. Record the figure and the date you checked it, because prices and exchange rates both move.
Google's service fee structure has been changing. The sources we checked disagree on whether the change reaches Canada and, if it does, when. We have not published a date. Check Google's own fee page before you plan around one.
GST or HST may apply to the developer fees and to Eskore's invoice, depending on your registration and circumstances. Ask your accountant. This is not tax advice.
Personal or organisation accounts: which suits your business
A personal account is registered to one individual, and that person's identity and payment details sit on it. An organisation account belongs to the business under its legal name. For a company with a payments profile, the organisation account is the right choice. If the person behind a personal account leaves or loses access, recovering the app becomes a problem.
Apple organisation enrolment needs a legal entity, a D-U-N-S number and documents that match the legal name and the payments profile. A D-U-N-S number is a nine-digit business identifier. Third-party guides put Apple's organisation verification at one to two weeks, plus up to five business days for a D-U-N-S number. Those are estimates, not Apple's published timelines, and real times vary. A mismatch between the name on your D-U-N-S number, your Apple enrolment and your bank sends the application back and adds more time.
Start enrolment early, in parallel with the build rather than after it, so a slow verification does not move your launch date.
The 14-day closed test and the 12-tester rule
Personal Google Play accounts created after 13 November 2023 must run a closed test before they can apply for production access. The test needs at least 12 testers opted in continuously for 14 days. Sources say organisation accounts are exempt. Confirm both points on Google's Play Console help page on the day you publish, because older guides still circulate.
In practice:
- Recruit testers early and confirm they have Google accounts and will install the app.
- Recruit more than 12. If someone opts out and the count falls below 12, the 14 days may restart.
- Ask testers to keep the app installed until the test ends.
- Put the 14 days into the calendar as a fixed block. They cannot be compressed.
A dated launch calendar, built backwards from launch day
The calendar below counts weeks back from release day (week 0). It assumes a personal Google Play account, so the closed test applies. If your organisation account is confirmed exempt on Google's help page, the closed-test weeks drop out and the Google track moves earlier. Do not assume the exemption until you have checked it.
| Week | Step | Gate |
|---|---|---|
| −10 to −8 | Confirm the legal entity, obtain the D-U-N-S number, start Apple organisation enrolment and Google registration | Both accounts verified |
| −8 to −6 | Draft listings and privacy policy. Publish the policy at a stable URL. Draft privacy labels and Data safety answers | Policy URL loads. Answers match the SDK list |
| −6 to −4 | Configure, sign and upload the build. Test on TestFlight and the Play internal track. Recruit at least 12 testers | Signing keys stored in a vault you control |
| −5 (day 0) | Start the Google closed test with 12 or more testers opted in | Test is live |
| −4 | Submit the build to Apple | Apple review begins |
| −3 (day 14) | Closed test ends. Apply for production access on Google | 14 days complete |
| −3 to −2 | Google and Apple review. Handle any feedback | Both reviews complete |
| −2 to −1 | Buffer for one resubmission cycle | Fixes approved |
| 0 | Release on both stores | Launch |
On Google, the closed test sets the earliest possible date. Its 14 days cannot be shortened, and production review follows it. On iOS, the date follows Apple's review and any rejection. Plan launch day around whichever store finishes last.
Review times vary. Different guides report Google's review of a closed-test application as anywhere from about a day to seven days, and new accounts may take longer. Apple's review time is not fixed. One vendor reports 24 to 48 hours, but that is a single unverified figure. Plan for the slower end and check each store's current guidance before you set a date.
When a store rejects an app, it cites the guideline involved. You fix the problem, reply or resubmit, and the app returns to the queue. A small fix costs one review cycle. A rejection that exposes a larger problem costs more, which is why the buffer matters.
You can launch on both stores at once if both accounts are ready. In practice the Google closed test often sets the date, so plan around the later store.
What a fixed-scope launch includes
A fixed-scope launch covers store listings and metadata for both stores, the privacy policy and labels, build configuration and signing, submission to Apple and Google, handling of review feedback and resubmission, release management and post-launch support.
Before any launch work begins, the written scope, fixed price and launch date are agreed. If the scope changes, the change, its price and its effect on the date are written down before work starts. Launch comes at the end of a build, so if the screens have not been tested yet, clickable prototypes and UI/UX design should come first. You can see recent app work in our case studies.
Common App Store and Google Play rejection causes
The causes below map to rules in the stores' published review guidelines and policies. Each one is preventable:
- Placeholder text, such as "Lorem ipsum", "TODO" or "test", in a listing or on a screen.
- A privacy policy that is missing, unreachable or does not describe what the app collects.
- Privacy labels or Data safety answers that do not match the analytics or push SDKs in the build.
- A login screen with no working test account in the review notes.
- Account creation without in-app account deletion.
- Broken links, unfinished features, or a crash on first launch.
A pre-submission checklist catches most of these. Before each submission, confirm there is no placeholder text, the policy URL loads, the privacy answers match the SDK list, the reviewer account works, account deletion works, and the app runs cleanly from a fresh install.
Who owns the accounts and the code
The business should own its developer accounts, its app listings and its source code. Not the agency, and not a reseller.
Some providers rent out or resell developer accounts. The risk is simple. If the account sits with someone else, that person decides whether you can publish an update. If the arrangement ends or the account is suspended, the app can go with it. A new listing starts with no reviews and no ratings, so that loss is hard to recover.
The structure we recommend:
- Your own person holds the account owner or account holder role.
- The agency works under a limited role, such as app manager or developer, which you can remove.
- The code lives in a repository under your organisation.
- Signing keys and recovery contacts are stored in a vault you control.
- The handover is written down at launch.
Eskore works on this basis. You own the code and the accounts.
Stack choices that affect store submission
The build approach changes how the submission goes. React Native with Expo, Flutter, and native Swift and Kotlin each produce different build and signing steps. Each handles native modules differently and brings its own review considerations. Expo projects need care with native modules that the store build must include. Flutter depends on plugin support for each platform. Native projects mean two codebases, two signing setups and two sets of platform rules.
Firebase commonly handles push notifications and analytics, Supabase can provide the backend and authentication, and Node.js often runs the APIs. Each of these SDKs feeds your privacy answers, so the launch checklist has to include them. For the build itself, see our mobile app development services. If the app connects to a wider system, custom software development covers the back office it talks to, and cloud setup for your app backend covers hosting. If the app has a companion website or portal, web development covers that side.
Launching in the US: New York, Austin, Raleigh and Denver
The store accounts, USD fees and review process are the same for a business in New York, Austin, Raleigh or Denver. What changes is the legal entity behind the account, and entities are formed and maintained at state level.
Three points to check before you start enrolment:
- Name matching. The legal name on your D-U-N-S number, your Apple enrolment and your bank account must match. A US LLC or a Canadian corporation needs to exist before the organisation account is set up.
- State filings. Each state has its own rules. New York requires newly formed LLCs to complete a publication requirement within a set period after formation. Texas, where Austin sits, requires franchise tax reports from LLCs. North Carolina (Raleigh) and Colorado (Denver) both require periodic reports. Confirm the current requirements for your state before you rely on any of them.
- Banking. A US entity usually needs an EIN from the IRS before a business bank account will open. The payments profile on the store account has to match that bank account.
If you are still choosing a structure, LLC formation and filings covers the registration steps, and our guide to US LLCs for Canadians in Toronto sets out the tax check to run first. Tax treatment is a question for your accountant. Eskore has offices in Toronto, Thornhill, London and New York, so US clients can work with the New York office and Canadian clients with the Toronto or Thornhill teams, on the same plan.
Plan your app store and Google Play launch with Eskore
A dependable app store and Google Play launch service in Canada starts with the accounts, not the upload. Get the legal entity and enrolments moving early, build the closed-test weeks into the calendar, and agree the scope, price and launch date in writing before work begins. That is how a launch stays on schedule, whether you are based in Toronto or Austin.
Book a free 30-minute scoping call and we will agree the scope, fixed price and launch date in writing before any work starts.