MOBILE APPLICATION DEVELOPMENT AGREEMENT
Pennsylvania, US

Agreement date: [date]

Developer: [full legal name and entity type], of [address], notice email [email] (Developer).
Client: [full legal name and entity type], of [address], notice email [email] (Client).

1. Project and scope
Developer shall design, build, test and deliver the mobile application and related items described in Schedule 1 (App and Deliverables) according to the written functional, platform, interface, accessibility and performance requirements there (Specifications). Platforms, device and operating-system versions not listed are excluded. Hosting, production operations, marketplace management and maintenance are included only if Schedule 1 says so.

This form is for a business software project and does not authorize processing of health, financial, children's, precise-location, biometric or other regulated data unless Schedule 3 expressly identifies the data, lawful basis, controls and required separate terms.

2. Project management and Client duties
The parties shall appoint project contacts. Developer shall use commercially reasonable skill and care and provide status updates at the frequency in Schedule 1. Client shall timely supply decisions, test accounts, content, brand assets, API access, devices and personnel reasonably required. Client delay extends affected dates and may require a signed change order for demonstrable additional cost.

Client shall control product requirements, legal notices, end-user terms, privacy disclosures, app-store account and business rules unless assigned otherwise. Developer may rely on written instructions but shall promptly flag an apparent inconsistency or material technical risk.

3. Milestones, change control and fees
Milestones, Deliverables, dates and fees are in Schedule 1. Developer shall invoice the listed deposit and milestones; undisputed amounts are due within [fifteen] days. Client shall describe an invoice dispute before the due date and pay the undisputed part. Approved, reasonable expenses are reimbursable only if Schedule 1 allows them.

Either party may propose a change. No change to scope, price, dependencies or schedule is binding until both sign a change order describing it. Developer need not begin changed work before signature. Taxes properly imposed on the Services are Client's responsibility, excluding taxes on Developer's net income.

4. Delivery and acceptance
For each Milestone, Developer shall provide the Deliverable and reasonable instructions to run the agreed Acceptance Tests. Client has [ten] business days to test and either accept or give a rejection notice identifying material failures against the Specifications and reproducible details. Developer shall correct verified failures and resubmit. A Deliverable is accepted when Client signs acceptance, deploys it for production use, or fails to timely reject it.

Acceptance does not waive a latent defect or express warranty. A preference, enhancement or unlisted requirement is not a defect and is handled through change control. Production Release occurs only after acceptance, payment of amounts then due and completion of the release checklist in Schedule 1.

5. Intellectual property
Client Materials remain Client's property. Client grants Developer a limited license to use them solely for this project and represents that it has the necessary rights.

Background Technology means Developer's preexisting or independently developed tools, libraries, frameworks, methods, know-how and generic components identified in Schedule 2. Developer owns Background Technology. Third-Party Materials means third-party or open-source components identified in Schedule 2 and governed by their disclosed licenses.

Upon full payment for a Deliverable, and to the extent it qualifies, the parties agree it is a work made for hire for Client. To the extent it does not qualify, Developer hereby assigns to Client, automatically effective upon that full payment, all Developer's right, title and interest in copyright in the custom source code, object code, designs, documentation and other original material created specifically for Client and identified as Assigned Work in Schedule 2. Developer shall sign reasonable confirmatory documents at Client's expense.

Developer retains Background Technology and grants Client a perpetual, worldwide, irrevocable, transferable, sublicensable, royalty-free license to use, reproduce, modify and distribute it only as incorporated in or necessary to use the paid Deliverables. Third-Party Materials are not assigned. Developer shall not include a component whose license requires disclosure or licensing of Client's proprietary source code unless Client approves it in Schedule 2.

6. Repositories, credentials and records
The code repository, branch strategy and delivery format are stated in Schedule 1. Developer shall not place secrets in source control and shall provide Client-owned production credentials through a secure method. At Production Release or termination after payment, Developer shall deliver current source code, build instructions, dependency list, design files and credentials belonging to Client. Each party shall maintain reasonable access controls and promptly revoke unnecessary access.

7. Security and data protection
Developer shall use reasonable secure-development practices appropriate to the App, including dependency review, access control, input validation, protected secrets and correction of known material vulnerabilities before Production Release. The specific security tests and remediation severity periods are in Schedule 3.

If Developer processes personal data for Client, Developer shall process it only on documented instructions, keep it confidential, use reasonable safeguards, assist with legally required responses, bind subprocessors to protective terms and delete or return it at termination, subject to lawful retention. Developer shall notify Client without unreasonable delay after confirming unauthorized access, use or disclosure affecting Client data or production credentials (Security Incident) and reasonably cooperate. Schedule 3 controls where a law requires more specific terms.

8. App stores and third-party services
Client owns or controls marketplace developer accounts unless Schedule 1 states otherwise. Client is responsible for fees, business verification, ratings, product claims and final submission approval. Developer shall prepare a conforming build and provide reasonable submission support. Neither party guarantees approval, continued listing, API availability or compatibility with future third-party changes. Required adaptation after acceptance is maintenance or a change order unless covered by warranty.

9. Warranties
For [sixty] days after acceptance, Developer warrants that each Deliverable will materially conform to the Specifications and contain no code intentionally designed to provide undisclosed access, disable use or introduce malware. Developer's obligation is to correct a reproducible breach or, if correction is not commercially reasonable, refund the fees paid for the affected Deliverable in exchange for stopping its use.

The warranty excludes Client or third-party modifications, misuse, unsupported environments, Client Materials and third-party service failure. Except for express warranties, services and third-party components are provided without implied warranties to the extent law permits. No software can be warranted uninterrupted or error-free.

10. Indemnities
Developer shall defend and indemnify Client from a third-party claim that paid Assigned Work, unmodified and used as agreed, infringes a United States copyright or trade secret. Developer may procure rights, modify or replace the affected item, or refund its fees if use must stop. This duty excludes Client Materials, approved Third-Party Materials, Client specifications that caused the claim, unauthorized combinations or modifications.

Client shall defend and indemnify Developer from a third-party claim arising from Client Materials, Client's product claims, unlawful data instructions or use outside this agreement. The indemnified party shall give prompt notice, allow reasonable control of the defense and cooperate; no settlement may admit its fault or impose an unconsented obligation.

11. Confidentiality
Each party shall protect the other's nonpublic source code, credentials, business plans, security information and data using at least reasonable care and use it only for this project. Disclosure is permitted to personnel and contractors who need it and are bound to protect it, or as law requires. The receiving party shall give advance notice of compelled disclosure when lawful. Trade-secret duties continue while information qualifies; other confidentiality duties continue for [three] years.

12. Termination and transition
Either party may terminate for a material breach not cured within [ten] days after detailed notice, or for insolvency subject to law. Client may terminate for convenience on [fifteen] days' notice and shall pay for conforming work performed, accepted commitments and reasonable wind-down costs through termination. Developer shall deliver paid work in progress and provide the transition assistance and rates in Schedule 1.

Upon termination, each party shall return or delete the other's confidential information as requested, except archival copies required by law. Rights in paid Deliverables survive; unpaid work remains Developer's property and need not be licensed or deployed.

13. Liability and general terms
Except for payment, fraud, willful misconduct, confidentiality or data-security breach, infringement, or indemnity, neither party is liable for consequential, special, punitive or exemplary damages, and each party's aggregate liability is limited to fees paid or payable in the [twelve] months preceding the event. Nonwaivable remedies are not restricted.

Pennsylvania law governs. State and federal courts located in [county], Pennsylvania have jurisdiction. The parties are independent contractors. Developer may use qualified subcontractors but remains responsible for them. Neither party may assign without consent, except with substantially all relevant business to a successor that assumes this agreement.

This agreement and schedules are the entire agreement. An amendment or waiver must be signed. Notices are effective on personal or tracked delivery or acknowledged email. Invalid language is narrowed or severed. Counterparts and electronic signatures are permitted.

SCHEDULE 1 — SPECIFICATIONS, PLAN AND COMMERCIAL TERMS
App purpose, users and platforms: [details].
Specifications and acceptance tests: [details].
Milestones, Deliverables, dependencies and dates: [details].
Repository and delivery format: [details].
Fees, deposit, invoices and approved expenses: [details].
Production Release checklist and app-store responsibilities: [details].
Hosting, support and maintenance, if included: [details or none].
Transition assistance and rates: [details].

SCHEDULE 2 — INTELLECTUAL PROPERTY
Assigned Work: [details].
Background Technology: [details].
Third-Party Materials, versions and licenses: [details].
Approved reciprocal/open-source obligations: [details or none].
Client Materials: [details].

SCHEDULE 3 — DATA AND SECURITY
Data categories and permitted processing: [details or none].
Security controls and tests: [details].
Vulnerability remediation periods by severity: [details].
Approved subprocessors and hosting locations: [details].
Required separate privacy or regulated-data addendum: [details or none].

DEVELOPER
Signature: ____________________ Date: __________
Name and title: [name and title]

CLIENT
Signature: ____________________ Date: __________
Name and title: [name and title]


---
License: 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.
License details: https://contract-templates.getfebruary.ai/license/