All posts
Product

App Store Release Ownership for Mobile Product Teams Hiring Offshore Developers

Published on 19 Nov 2026

app-store-release-ownership-for-mobile-product-teams-hiring-offshore-developers

When a product team hires offshore mobile developers, the company should own every account and key that can publish or update the app. The offshore team should run the pipeline that prepares releases, using roles the company can revoke at any time. In practice, the business holds the Apple Developer Program account, the Google Play Console account, the signing credentials and the over-the-air (OTA) update channel. Engineers get only the access they need to build, test and submit.

724SOFTWARE is a Vietnam software team that ships React Native, Flutter and native mobile apps and has delivery experience across 10+ countries, and its engineers work inside client-owned repositories and tools by default. Ownership of the release pipeline determines whether you can change partners, add engineers or recover from a lost laptop without re-publishing your app.

TL;DR

Apple's App Review Guidelines say apps should be submitted by the person or legal entity that owns or has licensed the app's intellectual property. A vendor should never publish your app under its own account.

  • Separate "who owns" from "who operates." The client holds the owner seats. The offshore team gets scoped user roles.

  • Enrol in Google Play App Signing so that a lost upload key becomes a reset request rather than a dead app listing.

  • Keep iOS certificates and provisioning profiles in a client-owned encrypted store, never on one engineer's machine.

  • Require client approval for every OTA push to production, with a named approver documented in your release log.

About the Author: This guide comes from the mobile delivery team at 724SOFTWARE, a Vietnam-based technology company with 200+ professionals (58% senior-level). The team has delivered mobile products including a South Korean fan-engagement app with 500,000+ downloads, as a long-term dedicated team.

Who should own the App Store and Google Play accounts when an offshore team builds your app?

Release ownership starts with one rule: the business whose brand appears on the store listing owns the publishing account.

What the store rules say (fact):

- Apple's App Store Review Guidelines and Developer Program License Agreement require developers to own all intellectual property in their app, or to hold explicit legal permission to use it.

- Apple applies these requirements to React Native apps exactly as it does to native apps.

- Apple's App Review Guidelines (guideline 5.2.1) say apps should be submitted by the person or legal entity that owns or has licensed the intellectual property and other relevant rights.

- Google Play also prohibits IP infringement.

Author's opinion: use Google's flexibility as little as possible. If a vendor holds the store account, you will eventually have to move the app, and that move tends to land during a funding round or acquisition due diligence.

What to do:

- Register both accounts in the company's legal name.

- Assign the Apple Account Holder seat and the Play Console owner seat to a named employee, and document a backup holder.

- Invite offshore engineers as individual users. Never share the owner login.

Which release assets need an owner, and who should hold each one?

Account ownership is only the first layer. Several smaller assets also control releases.

Asset

Owner

Offshore team access

 

Apple Developer Program account

Client (Account Holder)

Scoped App Store Connect role per engineer

Google Play Console

Client (owner)

Per-app permissions; production release only by agreement

Android app signing key

Google, via Play App Signing

None

Android upload key

Client-owned secret store

Used by CI only

iOS certificates and provisioning profiles

Client-owned encrypted store

Pulled by CI at build time

Expo organisation and OTA channels

Client

Member role

Source repository

Client

Write access per named engineer

Push keys, analytics, crash reporting

Client

Read or scoped access

Production release approval

Named client product owner

Prepares the release candidate

How should iOS provisioning profiles be handled with an offshore team?

iOS signing is where ownership most often drifts without anyone noticing. A distribution certificate's private key is created on whichever machine generated the certificate request. If that machine was a contractor's Mac, the private key becomes unrecoverable when the contractor leaves.

iOS provisioning profiles bind your app ID to a certificate. If that certificate cannot be renewed or used, builds stop signing and releases stall.

Controls that prevent this:

- Generate certificates under the client's Apple account and store them encrypted in a client-owned private repository using fastlane match, or in EAS-managed credentials inside the client's Expo organisation.

- Let CI pull credentials at build time so individual engineers do not need distribution certificates on their laptops.

- Revoke and regenerate credentials whenever team membership changes.

How does Google Play app signing reduce the risk of a lost key?

Android carries the same key-custody risk as iOS. Google Play App Signing reduces it by splitting signing into two keys.

Think of the app signing key as a company seal kept in a bank vault, and the upload key as a courier's ID badge. Google holds the seal and stamps every build that reaches users. Your CI pipeline only carries the badge, which proves to Google that a build came from you.

If the badge is lost, the account owner can request an upload key reset and keep shipping updates. Before Google managed the seal, a lost self-held signing key meant you could no longer update the existing listing.

For offshore engagements, this means the most valuable Android key never sits with the delivery team at all.

What does React Native CI/CD look like when the client owns the keys?

A React Native CI/CD pipeline turns the ownership table into enforcement, because people stop handling credentials directly. Two common setups:

  • Expo EAS Build: builds run in Expo's cloud, credentials live in the client's Expo organisation, and EAS Submit sends builds to the stores.

  • A fastlane React Native setup: fastlane lanes handle builds, match handles signing and uploads go to TestFlight and Play testing tracks, all running on the client's own CI runners.

Recommended checkpoints:

1. A merge to the main branch triggers a signed build using credentials held by CI.

2. The build goes automatically to TestFlight and the Play internal testing track.

3. QA signs off against an agreed test plan.

4. The client's product owner promotes the build to production. The offshore team may submit for review if that task is explicitly delegated.

724SOFTWARE engineers use Claude Code and Cursor in normal delivery work for code generation and review. In a release pipeline, that means pipeline scripts are reviewed with the same care as app code. A human still owns the approval at step 4.

Who should approve OTA updates in React Native?

OTA updates bypass the app store review process, so they require explicit client approval before production deployment.

Treat OTA updates that React Native teams push through tools like EAS Update as production releases. Apple's guidelines limit what downloaded code may change, including any change to the app's primary purpose. Check the current guidelines before relying on OTA for anything beyond fixes.

Controls:

- Use separate channels for development, staging and production.

- Require client approval for every push to the production channel.

- Pin updates to a runtime version so JavaScript never ships against an incompatible native build.

- Keep a tested rollback command ready.

If a bad update reaches users overnight, 724SOFTWARE's follow-the-sun model provides incident response in under 10 minutes, 24/7. The client still owns the rollback decision.

Frequently Asked Questions

Can an offshore agency publish our app under its own Apple account?

It should not. Apple's App Review Guidelines say apps should be submitted by the person or legal entity that owns or has licensed the app's intellectual property, so keep submission under your own account.

Do Australian visa rules apply to offshore developers who stay in Vietnam?

No. The engagement is typically governed by local employment law or contractor agreements. Relocating a developer to Australia would require visa sponsorship, such as the Skills in Demand (subclass 482) visa, which replaced the Temporary Skill Shortage visa in December 2024.

What should the contract cover?

It should cover IP assignment, the list of client-owned release assets, credential handover and access revocation when the engagement ends.

Does ISO 27001 address intellectual property?

Yes. ISO 27001 requires policies for meeting legal, regulatory and contractual IP obligations. ISO 9001 Clause 8.5.3 covers safeguarding customer property. 724SOFTWARE is aligned with ISO 27001:2022 and ISO 9001 standards and is GDPR compliant.

How quickly can a React Native team start?

724SOFTWARE typically embeds one senior engineer, validates the fit against a live sprint, then scales from 1 to 50+ pre-vetted engineers within 2 to 4 weeks.

What happens to access when the engagement ends?

Remove all user roles, rotate the upload key and CI secrets, and regenerate iOS certificates.

About 724SOFTWARE

724SOFTWARE is a Vietnam-based technology company that builds web and mobile applications as a long-term partner through dedicated teams, embedded staff augmentation and offshore development centres. Its 200+ professionals deliver from its own offices in Hanoi and Ho Chi Minh City, with billing based on actual working hours and direct client visibility into delivery performance. As a selected Anthropic partner in Vietnam, its engineers use Claude Code in day-to-day delivery. The company reports a 95% client retention rate.

Next step: before your next sprint, fill in the ownership table above with a named person for every asset. If you want a Vietnam software team that works inside that structure from day one, talk to 724SOFTWARE at https://724software.com.vn/.

Share this article

Product

Shrimpie Tran

AI Engineer

Keep Reading

Explore more from our experts.

View all

Stay ahead with our insights.

Get the latest on software design, strategy, and what's working in the field.

We respect your inbox. Unsubscribe anytime from any email.