MARSHAL / PRACTICAL GUIDE
Updated
What actually changes a mobile app development quote?
Two quotes for “the same app” can cover very different jobs. One may include only the screens; another may include the data system, account permissions, testing and release work. Before comparing totals, ask each developer to price the same first version and mark the assumptions. Marshal estimates projects against an agreed brief; this guide does not publish a universal price.
Inspect what the Falcon guest preview demonstrates ↗A practical guide from Marshal Studios. Explore the linked project examples and use the checklist for your own brief.
Count workflows, not just screens
A product page is one screen. Finding a product, checking its fitment, keeping a selection and sending an enquiry is a workflow. Describe the successful path and the failures: no matches, missing information, an expired session or a failed connection. The work behind those states can be invisible in a polished mockup.
Separate interface, data system and integrations
Ask which parts the quote includes. Does the app use an existing maintained catalogue, or does someone need to build an administration system too? Which connections have usable documentation and a test environment? Include the person responsible for product data. A dependency marked “we will connect it later” should not disappear from the budget.
Put users and permissions in the scope
Guest browsing, approved dealer access and an administrator who changes products are different responsibilities. If roles are needed, describe what each role can read and change. Include account approval and removal, forgotten-access handling and checks that restricted records stay restricted. A sign-in screen alone does not describe that work.
Agree platform and release work separately
List the devices the audience uses, the supported platforms and whether an installed app is required. Ask what testing is included for each. Record who owns store accounts, supplies listing material and handles release submissions if those are part of the job. A browser preview does not establish an app-store release or approval.
Use the Falcon preview to spot a quote boundary
The public Falcon preview lets you browse categories and product detail screens using a frozen catalogue. It does not expose dealer prices or submit production orders. That distinction matters when estimating: a browsable demonstration and a live account-based ordering product are different scopes. For your proposal, say which experience is being priced.
Ask about costs after delivery
List hosting, third-party services, store-related costs where applicable, monitoring, future platform updates and support. Ask which charges are paid directly by you and which are included in the proposal. Agree what counts as a defect fix and what counts as a new requirement. Confirm current provider charges when you receive the estimate.
Reduce scope by removing dependencies, not hiding work
If the first task is catalogue discovery and enquiry, decide whether payment, delivery tracking or notifications are needed at launch. Leaving them for later can make the first version clearer, but only if the enquiry route actually serves the user. Ask how later additions would affect the data and account design before choosing the cut.
Ask every developer to complete the same quote worksheet
| Work area | What the estimate should state |
|---|---|
| Essential task | The workflow included in version one and the checks that show it works |
| Users and access | Guest, signed-in and administrator responsibilities; approval and restriction rules |
| Data and backend | Existing data source, administration tools, imports and update responsibilities |
| Platforms and testing | Supported devices, platform scope, test coverage and who approves the result |
| Release and handover | Store work if included, account ownership, project files and operating instructions |
| Ongoing costs | Third-party charges, support scope, changes and exclusions |
Before we start
Can you give a price without a full specification?
A conversation can identify a first scope and the unanswered questions. Ask for a written estimate that states its assumptions rather than treating an early number as the cost of every feature you may later add.
Does using the same app technology make quotes comparable?
No. The included workflows, data work, platforms, testing, release and support still need to match. Compare those responsibilities before comparing totals.
LET’S MAKE IT
Tell us what you have in mind.
Based in Gurugram, with primarily online delivery. Clients across India and internationally are welcome.