tealtap / Planning your app

App development pricing: understand the scope

Understand app development costs, ongoing expenses, store fees and MVP decisions. Prepare a clear brief and compare proposals on the same scope.

App planning with screen sketches.

Features and screens

Feature depth and the journeys users need.

Platforms

Supported devices, iOS and Android.

Backend and integrations

Shared data and external connections.

Design and prototype

Navigation, states and a testable user journey.

Testing and release

Agreed scenarios, devices and store preparation.

Maintenance

Updates, operating-system changes and defect investigation.

Start with the job your app must do

App development pricing depends on the behaviour behind the screens. A login screen might serve a simple account or connect to a company directory with several permission levels. A useful proposal explains the users, supported scenarios, dependencies and acceptance conditions behind its price.

Read more

We discuss these boundaries before choosing an implementation approach. There is no published project price or starting rate on this page.

Describe what people do today and what should become easier. Explain where work currently moves between phone calls, spreadsheets and existing software. Define a completed task in terms that someone can test. This makes it possible to distinguish essential functionality from attractive additions and to identify assumptions that still require investigation.

Features, platforms and design

Feature depth matters as much as feature count. Booking availability, preventing conflicting reservations, cancellations and reminders are separate behaviours. Offline use may require local storage, retries and a rule for conflicting changes.

Read more

Supporting iOS and Android also involves permissions, device behaviour and validation on each agreed platform. A shared codebase may be an option, subject to the requirements; it is not an automatic saving.

UX and design cover navigation, content, empty states, errors and accessible interaction. A prototype can reveal misunderstandings before implementation. Existing brand assets provide a starting point, but mobile journeys still need to be designed. Languages, tablet layouts and the range of supported devices also influence the work. Agree which variants matter to the first release and which can wait.

Backend and external connections

A backend may handle accounts, roles, shared records, files, search and notifications. An administration interface can be a separate part of the scope. Where a system already exists, its documentation and test environment need review.

Read more

Reading a product catalogue is different from changing stock or creating orders. Data ownership, API availability and failure handling should be explicit.

Payment, calendar and commerce connections introduce external dependencies. Agree who supplies test access and who handles changes by the external provider. Connected hardware adds protocol documentation, firmware readiness and access to representative devices. AI adds data preparation, evaluation and usage costs. Search or chat also needs a fallback when results are unsuitable or the provider cannot respond. We develop native iOS apps in Swift and Android apps in Kotlin, as well as Flutter, React Native and PWA applications. We also build backends and APIs, IoT/BLE apps and AI features. The proposal accounts for integrations and focused technical trials.

One-off work and ongoing expenses

One-off costs

  • Discovery, UX and prototype
  • Development and testing
  • Migration, store preparation and handover

One-off work may include discovery, prototyping, design, development, testing, migration, submission preparation and handover. Ask whether content, translations, account setup and administrator guidance are included. A proposal should identify exclusions as clearly as included tasks. Assumptions about an existing backend or imported data can materially change the scope when those assumptions prove incorrect.

Ongoing expenses

  • Hosting, databases and backups
  • Logging, messaging, API and AI usage
  • Dependency updates and operating-system changes

Ongoing expenses can include hosting, databases, backups, monitoring, messaging, external APIs and AI usage. Their billing drivers may be traffic, stored data or provider plans. Maintenance covers agreed responsibilities such as dependency updates and adapting to operating-system changes. Feature development, support and defect correction need distinct contractual boundaries. Do not assume that a release automatically includes indefinite maintenance.

Store account fees

Apple lists the Apple Developer Program at 99 USD per year. Google lists a one-time 25 USD registration fee for a Play Console developer account. These are external account fees, separate from development work.

Read more

Apple notes regional pricing and local currency availability; check the amount displayed during registration. The official sources are linked below.

Account fees do not cover submission preparation or every possible transaction charge. Store descriptions, screenshots and declarations must match the product. Agree who supplies them and who owns the publishing account. Store review is an external decision, so approval cannot be guaranteed. Account access and ongoing responsibility should remain clear after handover.

Reduce scope through an MVP

An MVP should let a real user complete the central task. A secondary role, an uncommon report or a later integration may be deferred if the main journey still works. Essential security, necessary data handling and basic recovery are part of a usable product.

Read more

Cutting these can create operational problems rather than a useful first release.

Give each phase an outcome and a decision about continuation. For example, an internal workflow could be tested before adding management reporting. This is a planning example, not a client reference or a promised saving. Consider future data needs early so that a smaller first release does not create avoidable rework. The next phase should follow observed needs rather than an unchecked wish list.

Compare proposals and prepare your brief

Ask what will be delivered, how it will be tested and what makes it acceptable. Which assumptions remain unverified? Who provides content, test data and system access?

Read more

What happens if a dependency is delayed? How are changes reviewed and estimated? A headline price alone does not tell you whether proposals cover equivalent work.

Clarify source-code access, design deliverables, licences, store ownership and infrastructure accounts. Ask what operational documentation is included and what support follows release. Start your enquiry with the users, core task, platforms and existing connections. Include known constraints and open questions. Use redacted examples instead of production passwords or unnecessary personal data.

Frequently asked questions

Can you give a price without a full specification?

An initial discussion can identify unknowns and the work needed to define scope. A reliable proposal must state its assumptions, deliverables and exclusions.

Can an MVP reduce initial work?

Yes, when it narrows the product to a complete core journey. Agree what is deferred and how the first release will inform the next decision.

Are store fees development fees?

No. They are external account charges. Submission work and any applicable transaction charges are separate considerations.

Is maintenance automatically included?

Its scope must be agreed. Clarify updates, support, defect correction and additional feature work before release.

Your next step

Describe your core task

Tell us about your users, existing systems and the decisions still open.

Request a quote
Mobile app and connected device illustration
Request a quote

Tell us what you need

A few details and a short description are all we need. We’ll get back to you with the details.

What happens next

  1. Describe the task, with a redacted sample if useful.
  2. An optional AI assistant asks clarifying questions.
  3. A person reviews your request, then we get back to you with the details.
  • Built around your workflow
  • With human review
  • Design, app, maintenance
[email protected]
0 / 4000