Is It Out of Scope? — Web development
Is building a mobile app version out of scope for a web development project?
Yes. A native or cross-platform app is a different codebase, stack, and deployment process (app store review, platform-specific APIs) than a website — not an extension of the existing web build regardless of how much backend logic could theoretically be shared.
The website is built and live. The client asks for "the app version" next, sometimes assuming the backend already does most of the work so the app should be quick. Depending on approach (native iOS/Android, or a cross-platform framework), building an app means a new frontend codebase, different platform APIs, app store submission and review, and often new backend endpoints designed for mobile usage patterns rather than a straight port of the website.
Is it out of scope?
Yes. Even where the existing backend or API can be reused, the app itself — its UI layer, platform-specific behavior, offline handling, push notification support, app store compliance — is a substantial, separate build. This is true whether the team plans to build native apps or a cross-platform app; either way it's a new codebase and a new set of platform requirements the original web SOW never covered.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — Scopes the engagement to the website build — a mobile app, even one reusing backend logic, is a separate deliverable with its own codebase and platform requirements.
Example contract wording
Example contract wording (illustrative, not legal advice)
The current scope is the web build. A mobile app is a separate project — even reusing [the API/backend], it means a new app codebase, platform-specific development, and app store submission, which is a different scope of work and timeline than the site. I can put together an app-specific proposal if you'd like to move forward with that.
How MarginFlow flags it
MarginFlow checks the deliverables list for any mention of a mobile app or app store presence before classifying — where the scope is web-only, a request to build an app (even one described as "just a wrapper around the site") is flagged outside_scope, with the explanation noting that app store submission and platform-specific work are involved regardless of how the client is framing the ask.