React Native App Statement of Work Template

Count everything. A deliverable a client cannot count is a deliverable a client can expand.

1. 2.1A React Native (Expo managed workflow) application for iOS and Android built from one shared TypeScript codebase.
2. 2.2The 14 screens listed in Appendix A, including onboarding, authentication, home feed, item detail, search, cart, checkout handoff, profile, settings and four empty or error states.
3. 2.3Email and password authentication plus Sign in with Apple and Google Sign-In against the client's existing identity provider.
4. 2.4Push notifications for the three notification types listed in Appendix B, delivered through Expo Notifications or Firebase Cloud Messaging.
5. 2.5Integration with the client's documented REST API endpoints listed in Appendix C. The API itself is provided by the client.
6. 2.6One production build per platform submitted to App Store Connect and Google Play Console under the client's developer accounts.
7. 2.7A handover pack: repository access, environment variable inventory, build and release runbook, and a 60-minute recorded walkthrough.

Name what the engagement does not include. These are the lines your PMs will cite most often.

1. 3.1Design, development or hosting of backend services, databases or admin panels.
2. 3.2Tablet-optimized layouts, iPadOS split view, Apple Watch, Wear OS, widgets and App Clips.
3. 3.3Offline-first data sync beyond caching the last loaded feed for read-only display.
4. 3.4In-app purchases, subscriptions and any payment processing inside the app.
5. 3.5Localization into languages other than US English, and right-to-left layout support.
6. 3.6Ongoing maintenance, OS upgrade compatibility work and store listing optimization after the warranty period.
7. 3.7Accessibility certification or third-party audit. The app targets the platform accessibility guidelines for listed screens only.

Each screen in Appendix A includes two rounds of consolidated revisions at the high-fidelity build stage. A round is one written list of changes delivered by the client's named product owner within five business days. Additional rounds, or changes to an approved screen after its round closes, are handled under the Change Control clause.

Acceptance needs a measurable test and a window. Without both, delivery never formally ends.

1. 5.1Each user story in Appendix A passes on the supported device matrix: iPhone 12 and newer on iOS 17 and 18, and Android 12 to 15 on the four reference devices listed in Appendix D.
2. 5.2No open defects of severity 1 (crash or data loss) or severity 2 (core flow blocked) at release candidate.
3. 5.3The client has ten business days to test each release candidate. Silence after ten business days counts as acceptance.
4. 5.4Store rejection caused by app code is fixed at no charge. Rejection caused by client content, account status or policy questions is supported at the hourly rate.

Tie each dependency to a date so a late input has a known effect on the schedule.

1. 6.1The client provides a stable staging API with documented endpoints and test credentials before the build phase begins.
2. 6.2The client holds active Apple Developer and Google Play developer accounts and grants the agency access within five business days of kickoff.
3. 6.3Final copy, imagery and legal text (privacy policy, terms) are delivered before the screen they appear on enters build.
4. 6.4One product owner on the client side consolidates feedback and has authority to approve screens.
5. 6.5Push notification content and triggers are defined by the client in writing before notification work starts.

Any request that adds a screen, a platform, a device class, an integration or a notification type, or that changes an approved screen, is a change. The agency will reply within two business days with a written change order stating the work, estimated hours, cost at the rates in Schedule 1 and schedule impact. No change work starts until the client's product owner approves the change order in writing. Approved changes adjust the fee and the timeline together.