Source handover
A source package needs an agreed repository snapshot, dependency information, build instructions and a clear account of licences and ownership. It is not automatically an installable app.
Understand device testing, signing ownership, distribution and source-code handover responsibilities.
A source-code ZIP, an installable Android APK, an Android App Bundle and an iOS testing arrangement serve different purposes. The agreement must name the intended deliverable and who can build, sign, install or distribute it.
A source package needs an agreed repository snapshot, dependency information, build instructions and a clear account of licences and ownership. It is not automatically an installable app.
Private APK and AAB testing builds can be shared through your project after review. Signing ownership and distribution permissions must be agreed. An AAB is not directly installable; it requires appropriate Android testing or distribution tooling.
Your package identifies its supported platforms. Signing keys, developer accounts, submission work and external fees must be explicitly covered by the agreement. A delivered build is not a promise of store publication or approval.
Review and financial clearance remain separate from preview approval. Only an explicitly authorized release can make private final files available to the owning customer.