Free Mobile App Development SOW Template

This Statement of Work governs the development of [App Name] by [Agency Name] ("Agency") for [Client Name] ("Client") on [Platforms: iOS / Android / Both via React Native / Flutter]. The Agency will develop the application features defined herein, conduct QA testing, and submit the app for App Store / Google Play review. This SOW is screen- and feature-specific. Any screens, features, or platforms not listed require a signed Change Order.

• Technical architecture planning, API design, and project setup
• Development of [X] screens as listed in the attached screen inventory
• User authentication: email/password sign-up and login, password reset
• Core feature set as specified: [list key features — e.g. user profiles, push notifications, in-app feed, search]
• Backend API development (if applicable): [specify endpoints and data models]
• Integration with [specified third-party services: e.g. Firebase, Stripe, Google Maps]
• Push notification setup via [FCM / APNs]
• Offline mode and local data caching for core screens
• Device testing on [X] physical devices per platform (latest and one prior OS version)
• Performance and security review pre-submission
• App Store (iOS) and/or Google Play (Android) submission and submission issue resolution
• 30-day post-launch bug-fix period for issues within agreed scope

• Screens or features not listed in the attached screen inventory
• Web application or admin dashboard (separate engagement)
• Third-party integrations beyond those listed above
• In-app purchases, subscription billing, or monetisation beyond what is listed
• Augmented reality, machine learning, or AI features
• Wearable (Apple Watch, Wear OS) support
• Tablet-specific layouts (phone layout only unless specified)
• App Store Optimisation (ASO), marketing, or post-launch growth strategies
• Maintenance, feature updates, or OS compatibility patches after the 30-day post-launch period
• Any feature, screen, or integration not explicitly listed in this SOW

1. Week 1–2Architecture, design handoff review, and dev environment setup
2. Week 3–7Sprint 1 — authentication, navigation, and core screens
3. Week 8–14Sprint 2 — primary features and backend integration
4. Week 15–19Sprint 3 — secondary features, notifications, and polish
5. Week 20–22Internal QA and bug-fix sprint
6. Week 23–24Client UAT (User Acceptance Testing) on TestFlight / Google Play Internal Track
7. Week 25–26App Store and Google Play submission
8. Week 27–30App approved and live

One (1) User Acceptance Testing (UAT) cycle is included per platform. UAT feedback must be submitted as a written bug report within ten (10) business days of TestFlight / Internal Track access being granted. Confirmed bugs (deviations from the agreed spec) are fixed at no charge. Requests for new features, additional screens, or UI changes during UAT are Change Orders. Post-submission changes that require App Store re-review are billed at $[rate].

Total project fee: $[Amount]. Payment schedule: 30% ($[Amount]) upon signing; 30% ($[Amount]) at Sprint 2 completion; 20% ($[Amount]) upon client UAT sign-off; 20% ($[Amount]) upon App Store/Google Play approval and go-live. Invoices are payable within ten (10) business days. Source code is not transferred until all invoices are settled. Overdue invoices accrue interest at 1.5% per month.

Mobile app scope changes are high-cost. Any additional screens, features, platforms, integrations, or design changes after development begins require a written Change Order with a cost and timeline estimate before work proceeds. The Agency will provide estimates within five (5) business days. Verbal approvals are not authorised.

• Approved, developer-ready UI/UX designs (Figma or equivalent) covering all [X] screens will be provided before development begins
• Client will provide Apple Developer Program and Google Play Developer Console access (or create accounts) before the submission phase
• Client-supplied third-party API credentials (payment processors, mapping services, etc.) will be provided before integration begins
• Client will nominate QA testers for the UAT cycle and provide consolidated feedback within the UAT window
• App Store and Google Play review times are outside the Agency's control — rejections due to platform policy changes are handled at $[rate]
• The screen inventory attached to this SOW is fixed at signing. Additional screens require a Change Order
• Backend hosting costs (cloud servers, database) are the Client's responsibility

The project is accepted when: (1) all screens in the screen inventory are developed and functional; (2) UAT feedback has been addressed; (3) the app is live on the App Store and/or Google Play; and (4) Client provides written acceptance, or fails to respond within seven (7) business days of go-live. The 30-day bug-fix period begins at acceptance. Source code is delivered upon receipt of final payment.