MOBILE APPLICATION DEVELOPMENT AGREEMENT
MOBILE APPLICATION DEVELOPMENT AGREEMENT
Delaware, US
Effective date: [date]
Client: [full legal name and entity type], of [address] (Client).
Developer: [full legal name and entity type], of [address] (Developer).
1. Project
Developer shall design, build, test, and deliver the mobile application and related items stated in Schedule 1 (Deliverables) for [platforms and versions]. Schedule 1 states functional requirements, supported devices, accessibility target, integrations, environments, milestones, acceptance tests, exclusions, and responsibilities. Store publication, user adoption, revenue, ranking, and uninterrupted third-party services are not promised.
Client shall timely provide accurate requirements, brand assets, test accounts, decisions, lawful content, privacy instructions, and access identified in Schedule 1. Developer may rely on those materials but shall promptly identify an apparent inconsistency or security risk.
2. Milestones and changes
Developer shall deliver each milestone by the target date, subject to documented Client delay and approved changes. Within [number] business days after delivery, Client shall perform the stated tests and either accept in writing or give a reproducible list of material failures against Schedule 1. Developer shall correct those failures and resubmit. A milestone is accepted when Client confirms acceptance or uses it in production, but payment or limited testing does not waive a latent defect.
Any change to scope, architecture, platform support, deliverable, price, or schedule requires a signed change order stating the effect. Developer need not perform changed work before approval. If a platform or integration changes materially, the parties shall evaluate a change rather than treating new requirements as a defect.
3. Fees and expenses
Client shall pay the milestone fees in Schedule 1 within [number] days after an accurate invoice and applicable acceptance. The total fee is $[amount]. Developer must obtain written approval before incurring a reimbursable expense. Client may withhold only a reasonably disputed amount and shall timely pay the rest. Taxes are allocated as required by law and separately stated.
4. Security, data, and accounts
Developer shall use reasonable secure-development practices, dependency review, access controls, secret management, and testing proportionate to Schedule 1. Developer shall notify Client promptly of a confirmed unauthorized access to Client data in Developer's custody and cooperate in required response. Client determines the application's lawful notices, consents, data uses, retention, age restrictions, regulated-data requirements, and production security configuration unless Schedule 1 expressly assigns a task.
Production signing keys, store accounts, domain names, cloud accounts, and analytics accounts shall be registered to and controlled by Client when practicable. Developer may access them only as needed and shall return or transfer credentials at handoff. Developer shall not use live personal data in testing unless expressly approved with safeguards.
5. Intellectual property
Client retains Client materials. Developer retains tools, libraries, processes, generic code, know-how, and materials developed independently of this project (Developer Materials). After full payment for a Deliverable, Developer hereby assigns to Client all of Developer's right, title, and interest in the original source code, object code, designs, documentation, and other custom work created specifically as that Deliverable, including copyright rights, and shall sign reasonable confirmatory instruments. To the extent a custom Deliverable qualifies as a work made for hire, the parties so agree; the assignment applies regardless.
Developer grants Client a perpetual, worldwide, royalty-free license to use, reproduce, modify, distribute, display, perform, and sublicense Developer Materials embedded in an accepted Deliverable as needed to use and exploit it. Developer shall obtain written assignments or sufficient licenses from its personnel and subcontractors.
Developer shall disclose third-party and open-source components, versions, licenses, notices, and material restrictions before acceptance. Developer shall not knowingly include code requiring disclosure of Client's proprietary source code without prior written approval.
6. Warranties and support
Developer warrants for [number] days after final acceptance that the Deliverables materially conform to Schedule 1, contain no knowingly introduced malware, and do not knowingly infringe a third party's intellectual property. The remedy is prompt correction or, if correction is not commercially reasonable, refund of fees allocable to the unusable Deliverable. The warranty excludes unauthorized modification, unsupported environments, Client materials, and third-party changes.
Post-acceptance maintenance, store submissions, service levels, and enhancements are included only if stated in Schedule 2. Nothing excludes a remedy that cannot lawfully be excluded.
7. Confidentiality and termination
Each party shall protect the other's nonpublic business, technical, security, and customer information with reasonable care and use it only for this Agreement. Exceptions apply to information lawfully public, already known without restriction, independently developed, or rightfully received from another source. Required disclosure is permitted after prompt notice when lawful.
Either party may terminate for a material breach not cured within [number] days after detailed notice. On termination, Client pays for accepted work and usable work in progress delivered at the agreed rates; Developer returns Client materials and provides paid-for work, credentials, and a current repository export. Sections intended by their nature to survive do so.
8. General
The parties are independent contractors. Delaware law governs. Neither party may assign the Agreement without consent, except to a successor acquiring substantially all relevant business and assuming the obligations. This Agreement and its Schedules are the entire agreement. Amendments and change orders require signatures. Notices take effect on receipt. The parties agree to transact electronically; retainable electronic records and lawful electronic signatures are effective. If a provision is unenforceable, the remainder survives.
SCHEDULE 1 — SPECIFICATION AND COMMERCIAL TERMS
Platforms; requirements; accessibility; integrations; exclusions; Deliverables; repository; milestones; target dates; acceptance tests; Client dependencies; fee allocation; data categories; security standard; approved components: [details].
SCHEDULE 2 — SUPPORT, IF ANY
Term; covered versions; response targets; maintenance fee; exclusions: [details].
CLIENT: ____________________ Name/title: [name and title] Date: [date]
DEVELOPER: ____________________ Name/title: [name and title] Date: [date]
Licensed under CC BY 4.0. Attribution is required when you publish or redistribute this Template or an adapted version to the public. Attribution is not required merely because you use or adapt the Template for your own business or legal purposes, including preparing, negotiating, signing, or exchanging an agreement with a counterparty. License details.