When you pay a developer to build or customize an app, it is natural to assume you own the code. In practice, ownership depends on what was agreed in writing. This guide explains what to check before a project starts. It is general information, not legal advice.
Why it matters
If you do not own the source code, you may be unable to move to another developer, add features, fix bugs or sell your business with the app included.
What "owning the source code" should cover
- The full application source code, not only the compiled app.
- Design files, images, icons and other assets.
- Build configuration and documentation.
- Access to your Apple Developer and Google Play accounts, registered in your name.
- Any backend code or API configuration you rely on.
Ready-made apps vs custom projects
With a ready-made app that includes source code, such as our WooCommerce multi-vendor mobile app or Shopify app, you receive the code and can customize it. With a custom project, ownership of the new work should be stated in the contract.
A simple checklist before you sign
- Ask: "Will I receive the full source code at handover?"
- Get the answer in writing, in the contract or quote.
- Confirm who holds the developer accounts and signing keys.
- Check how third-party libraries and licences are handled.
- Agree what happens to the code if the project is paused or cancelled.
How we work
Our apps include full source code, and we agree deliverables in writing before customization starts. See our app customization and Flutter development services, or request a quote.
Frequently asked questions
Who owns the source code when you hire an app developer?
It depends on your agreement. Without a written contract, the developer may keep the copyright even though you paid. Always agree in writing that you receive the full source code and own the finished work, including build files, assets and developer account access.