QUICK ANSWER
How much does app development cost?
Using the stated U.S. role-hour model, illustrative commissioned-project scenarios run from about $19,000-$41,000 for a single-workflow web proof to $98,000-$195,000 for a production web app, $234,000-$469,000 for cross-platform mobile plus backend, and $522,000 or more for complex or regulated work. These are planning scenarios, not quotes or market averages.
An app budget becomes useful only when it names the work behind the number. User roles, data rules, backend behavior, integrations, delivery platforms, testing, release work, and ongoing operations all change the estimate.
This guide uses a transparent U.S. labor-cost proxy and four explicitly scoped planning scenarios. Replace every rate, hour, provider charge, and unknown with your own evidence before treating the result as a budget.
Planning assumptions behind the ranges
Every worksheet number is editable. The static scenario ranges are useful only when the scope and exclusions resemble your project. They are not Playcode subscription prices.
| Assumption | Value used | Why it changes the estimate |
|---|---|---|
| U.S. employee-cost proxy | Developer $97/hour, QA $74/hour, interface design $74/hour, and project management $73/hour. | These rounded loaded employee-cost proxies are derived from BLS medians. They are not contractor or agency bill rates and should be replaced outside this context. |
| Role-hour bands | Each scenario states low and high hours by role; the editable worksheet exposes the same four role streams as individual inputs. | The bands are page-authored assumptions, not survey averages. Unknown workflows, providers, migrations, or policies can reopen them. |
| Contingency | 15% for the bounded proof, 20% for production web, 25% for shared-code mobile, and 30% for complex scope. | These are editorial planning reserves tied to named uncertainty. They do not replace discovery or authorize unpriced scope. |
| Productive capacity | Total role-hours and elapsed calendar time are separate outputs. | Adding people does not divide duration linearly. Critical paths, coordination, stakeholder decisions, and external queues remain. |
| Recurring charges | Provider usage and ongoing support are excluded from the build ranges unless explicitly entered. | First-year total cost requires the build estimate plus launch support and twelve months of actual operating inputs. |
| Self-build cash and founder time | A self-built app can require less cash labor than a commissioned project, while still consuming owner time, tools, testing, provider usage, and rework. | Founder or owner time is excluded unless its hours and economic rate are entered in the worksheet. Lower cash spend is not the same as zero cost. |
EDITABLE PLANNING WORKSHEET
Model your app cost and timeline
Replace the example hours and costs with your scope. Rates are rounded U.S. employee-cost proxies from the dated methodology, not freelancer or agency quotes. Planning totals are rounded to the nearest $1,000 so the worksheet does not imply false precision.
Self-build boundary: A founder using an AI builder may spend less cash than these commissioned-project scenarios by doing the work personally. Founder or owner time is excluded unless you enter those hours and an economic rate in a role row. Paid tools, provider usage, testing, and rework remain.
| Role stream | Editable rounded rate | Editable hours | Staffed hours/week | Labor subtotal | Stream duration |
|---|---|---|---|---|---|
| Discovery and project management | USD/hour | $8,800 | 6 weeks | ||
| Product and interface design | USD/hour | $8,900 | 6 weeks | ||
| Application development | USD/hour | $87,300 | 15 weeks | ||
| QA, accessibility, and security checks | USD/hour | $17,000 | 7.5 weeks |
labor = sum(role hours x rounded role rate)
build before contingency = labor + one-time inputs
planning build = build before contingency x (1 + contingency percent)
annual operations = monthly operations x 12 + annual inputs
planning year one = planning build + launch support + annual operationsCopy the scope and estimate boundary
Keep this record with a brief or quote request. It makes the scope, custom rates, operating assumptions, unknowns, and planning-only status visible together.
Turn role-hours into a planning timeline
The simplified critical path is the longest role stream after dividing its hours by real staffed capacity. Add external lead time, acceptance testing, review queues, and a named reserve. This is a reasoned planning estimate, not a delivery promise.
Longest role stream: 15 weeks
Planning calendar estimate: 23 weeks
planning calendar = longest staffed role stream
+ provider or stakeholder lead time
+ acceptance and device testing
+ external review input
+ timeline uncertainty reserve- Work is not perfectly parallel; dependencies can make the real critical path longer.
- Adding people does not divide the calendar estimate linearly because coordination remains.
- Store and provider review inputs are planning allowances, not approval or timing guarantees.
- Re-estimate when scope, staffed capacity, provider access, or acceptance criteria change.
How this app cost model works
The worksheet separates labor, one-time launch inputs, recurring operations, and uncertainty. It shows the arithmetic so you can challenge each assumption instead of trusting one unsupported average. For the supported web-app path, see how Playcode Cloud runs backend, data, and recovery.
Start with role-hours, not screen count
Estimate discovery, interface design, development, and quality work from the workflows, roles, records, integrations, and release surfaces. The example loaded rates divide the latest BLS median hourly wage for each occupation by the broader professional-occupation wage share of total compensation.
Sources: [bls-oews-2025], [bls-employer-costs-2026]
Add the real delivery path
A responsive web app, installable web app, shared-code mobile app, and separate native apps create different signing, device, store, review, and release work. Price those obligations explicitly instead of using a single platform multiplier.
Sources: [apple-membership], [apple-review], [google-play-account], [google-play-testing], [google-play-service-fees]
Model usage and support separately
Build cost does not include an automatic operations allowance. Estimate runtime, storage, transfer, payments, messages, maps, monitoring, support, and incident response from expected units and the current provider terms.
Sources: [firebase-pricing], [stripe-pricing], [maps-pricing], [twilio-sms-pricing]
Price quality and uncertainty as work
Security and accessibility are lifecycle activities with concrete requirements and evidence. Mobile verification and regulated health-data safeguards can materially expand design, implementation, review, and operations. Unresolved data, provider, moderation, offline, policy, and support decisions should trigger re-estimation or a discovery phase, not a hidden fixed percentage.
Sources: [nist-ssdf], [wcag-22], [owasp-masvs], [hhs-hipaa-security]
What this estimate includes
The owner is app project cost: behavior, data, backend services, integrations, platforms, team effort, release work, and operations. For a content or marketing site, use the website cost guide. Native distribution is a separate boundary; review the iPhone app guide and Android app guide. For narrower planning decisions, use the AI app development cost guide, custom software development cost guide, SaaS development cost guide, MVP development cost guide, or the build vs buy software guide. This guide also absorbs the closely related duration question because cost and time depend on the same scope and capacity inputs.
Included
- Product discovery, acceptance criteria, interface design, implementation, testing, launch, and handoff.
- Roles and permissions, data lifecycle, backend behavior, files, jobs, notifications, search, and recovery.
- API and provider setup, retries, rate limits, duplicates, reconciliation, and outage handling.
- Responsive web, PWA, cross-platform mobile, and separate native delivery obligations.
- Recurring runtime, provider usage, support, maintenance, policy, security, and accessibility work.
- A duration method based on critical-path role streams, staffed capacity, external queues, and uncertainty.
Not included
- Generic website project cost, website redesign cost, and vendor subscription comparisons.
- A universal average app price, guaranteed delivery date, or agency and freelancer bill-rate benchmark.
- Taxes, legal advice, customer acquisition, customer-support staffing, and provider usage not entered by the reader.
- Guaranteed App Store or Google Play approval and any fixed external review time.
- A claim that Playcode packages, signs, or submits native iOS or Android apps.
Four illustrative app development cost scenarios
These are commissioned-project planning scenarios using the assumptions above. They are neither market averages nor Playcode product prices. The upper bound is not a ceiling.
Single-workflow web proof
Testing one important user job before funding a production platform.
- One-time
- $19,000-$41,000 planning range, including a 15% contingency.
- Recurring
- Not included; enter the actual runtime, domain, provider usage, and owner support hours.
Includes
- 190-410 total role-hours across discovery, interface design, development, and quality checks.
- Role bands: discovery 20-40 hours, design 20-50, development 120-250, and quality 30-70.
- One user role, 5-8 primary screens, simple records, email/password authentication, and responsive web delivery.
Excludes
- Payments, imported legacy data, offline synchronization, regulated data, and native packaging.
Uncertainty: Low only when the single workflow, records, acceptance criteria, and owner are already known.
Sources: [bls-oews-2025], [bls-employer-costs-2026], [wcag-22]
Production web app
A browser-delivered product with several roles, real data, and an operating owner.
- One-time
- $98,000-$195,000 planning range, including a 20% contingency.
- Recurring
- Usage-dependent runtime plus monitoring, recovery, provider meters, and support.
Includes
- 920-1,820 total role-hours.
- Role bands: discovery 80-160 hours, design 80-160, development 600-1,200, and quality 160-300.
- Two or three roles, production backend and database, admin workflow, files, one ordinary API, monitoring, and recovery.
Excludes
- Native store release, regulated data, complex migration, unusually strict availability, and extensive offline behavior.
Uncertainty: Medium until the API contract, data lifecycle, support target, and expected usage are confirmed.
Sources: [bls-oews-2025], [bls-employer-costs-2026], [firebase-pricing], [nist-ssdf], [wcag-22]
Cross-platform mobile plus backend
A product that needs iOS and Android distribution with a shared backend and app code where practical.
- One-time
- $234,000-$469,000 planning range, including a 25% contingency.
- Recurring
- Backend and provider usage, store accounts, release operations, device coverage, and support.
Includes
- 2,100-4,200 total role-hours.
- Role bands: discovery 150-300 hours, design 150-300, development 1,400-2,800, and quality 400-800.
- Authentication, data, push notifications, backend, store packaging, release work, and a representative physical-device matrix.
Excludes
- Regulated data, separate native codebases, unusually complex offline synchronization, and guaranteed store approval.
Uncertainty: Medium to high because shared code does not remove signing, permissions, platform defects, review, or release work.
Sources: [bls-oews-2025], [bls-employer-costs-2026], [apple-membership], [apple-review], [google-play-account], [google-play-testing], [owasp-masvs]
Complex or regulated app
Several roles with sensitive data, complex migration or integrations, formal evidence, or demanding operating behavior.
- One-time
- $522,000-$1.25 million or more, including a 30% contingency.
- Recurring
- Case-specific controls, evidence, provider contracts, monitoring, incident response, and specialist review.
Includes
- 4,500-10,800 total role-hours.
- Role bands: discovery 300-800 hours, design 200-500, development 3,000-7,000, and quality or evidence 1,000-2,500.
- Complex permissions, audit needs, sensitive data, migration or integration risk, and extensive quality evidence.
Excludes
- A universal compliance checklist, legal advice, and any promise that the upper range is a ceiling.
Uncertainty: High. Fund discovery and professional review before accepting a fixed build commitment.
Sources: [bls-oews-2025], [bls-employer-costs-2026], [nist-ssdf], [wcag-22], [owasp-masvs], [hhs-hipaa-security]
What changes the cost of developing an app
Price the actual work in each category. “One integration” and “ten screens” are not useful units when they hide provider failure handling, data rules, or release obligations.
| Category | One-time | Recurring | Main drivers |
|---|---|---|---|
| Product scope and interface Discovery, acceptance criteria, user roles, workflows, content, information architecture, interaction, visual design, and accessibility. Sources: [bls-oews-2025], [bls-employer-costs-2026], [wcag-22] | Role-hours for product management, interface design, development, and quality work. | Content changes, user research, accessibility regression checks, and continued product decisions. | Distinct workflows and permission levels rather than screen count alone.; Localization, content, device coverage, and interaction complexity. |
| Data, backend, and migration Authentication, account recovery, permissions, records, files, jobs, notifications, search, history, export, deletion, backups, and recovery. Sources: [bls-oews-2025], [bls-employer-costs-2026], [firebase-pricing], [nist-ssdf], [hhs-hipaa-security] | Architecture and implementation hours plus data cleanup, mapping, rehearsal, rollback, and reconciliation where required. | Runtime, database operations, storage, transfer, backups, monitoring, and support. | Data relationships, validation, lifecycle, concurrency, audit history, and legacy quality.; Availability, recovery, and incident-response targets. |
| Integrations and metered providers Provider setup, credentials, API or webhook work, rate limits, retries, duplicates, timeouts, reconciliation, commercial approval, and outage behavior. Sources: [stripe-pricing], [firebase-pricing], [maps-pricing], [twilio-sms-pricing] | Implementation, sandbox, failure tests, provider review, and launch setup. | Transactions, messages, phone numbers, maps, storage, transfer, and other billable units. | Read-only versus two-way or money-moving behavior.; Account, region, permission, compliance, and reliability constraints. |
| Platform, release, and operations Browser and device coverage, packaging, signing, permissions, store metadata, review responses, monitoring, runbooks, training, and launch support. Sources: [apple-membership], [apple-review], [google-play-account], [google-play-testing], [nist-ssdf], [owasp-masvs] | Platform-specific build, device testing, account setup, store assets, submission, and launch readiness. | Developer memberships, release operations, OS/browser/SDK updates, incident response, and continued support. | Web, installed web, shared-code mobile, or separate native delivery.; Store policy, physical-device coverage, support hours, and external review queues. |
Use uncertainty to decide when to estimate again
Count unresolved scope items instead of hiding them inside one padded number. Zero to two unresolved items may justify a 10-15% reserve; three to five need a 20-25% reserve and named decisions; six or more need discovery before a build commitment. This is an editorial rubric, not an industry statistic.
What moves the estimate
- User roles, approval rules, data lifecycle, retention, deletion, or migration are unresolved.
- A provider contract, credentials, payment flow, retry behavior, or commercial approval is unknown.
- Offline conflicts, native capabilities, store policy, sensitive data, or moderation obligations are unclear.
- Expected usage, files, messages, maps, AI units, support hours, availability, or recovery target is missing.
Re-estimate when
- A role, workflow, platform, integration, regulated-data category, or migration enters or leaves scope.
- A provider changes pricing, access, policy, approval, quota, or supported behavior.
- A prototype reveals new data states, error paths, device constraints, or operational ownership.
- The accepted quality, support, availability, recovery, accessibility, or security target changes.
Recurring app costs after launch
Do not use a universal maintenance percentage. Build the operating estimate from expected workload, current provider meters, service level, dependency surface, and actual owner hours.
| Cost | Cadence | Planning range | Boundary |
|---|---|---|---|
| Runtime, data, and observability Sources: [firebase-pricing] | Monthly usage plus periodic review | Usage-dependent; enter reads, writes, storage, transfer, functions, logs, alerts, and backup needs. | No-cost quotas can help a small start, but usage beyond the quota can be pay-as-you-go and budget alerts do not necessarily cap charges. |
| Payments and store fees Sources: [stripe-pricing], [apple-membership], [google-play-account], [google-play-service-fees] | Per transaction plus program or account cadence | Use the current fee for the exact market, transaction, program, install state, and billing path. | Stripe currently lists 2.9% plus 30 cents for successful domestic U.S. online-card transactions; other cases differ. Google Play says its service fee depends on market, transaction, program, install state, and billing path; its newer US, UK, and EEA structure rolled out from 2026-06-30. Store service fees are separate from account fees. |
| Messages and maps Sources: [twilio-sms-pricing], [maps-pricing] | Per billable unit, sender, number, or map SKU | Usage-dependent; forecast message segments and the exact map, route, or place events. | Destination, sender type, carrier fees, registration, SKU, volume tier, and failed-message behavior can all change the bill. |
| Maintenance and operating ownership Sources: [nist-ssdf], [wcag-22], [apple-review], [google-play-testing], [owasp-masvs], [hhs-hipaa-security] | Monthly support and per-release work | Owner hours for incidents, dependencies, OS/browser changes, content, moderation, policy, accessibility, and security. | Estimate the real support window and evidence obligations. A percentage of initial build cost does not describe the workload. |
Choose the next investment, not just the lowest number
The cheapest path is the one that tests the biggest risk without quietly dropping a mandatory capability.
The core job works in a browser, demand is unvalidated, and no native-only device behavior is essential.
Choose: Build a web-first proof and test the workflow before funding native packaging.
Tradeoff: You postpone app-store distribution and native-only capabilities while learning faster.
Links, fast iteration, shared backend and data, and lower channel overhead matter more than app-store presence.
Choose: Fund a production web app.
Tradeoff: Installed mobile behavior and platform-specific integrations may remain limited or require a later track.
App-store presence, push or device integration, installed behavior, or mobile UX is a hard requirement.
Choose: Budget cross-platform mobile plus separate iOS and Android release work.
Tradeoff: A shared codebase can reduce duplicate implementation but not platform testing, signing, permissions, review, or support.
Platform-specific performance, frameworks, capabilities, or experience justify independent implementation.
Choose: Fund separate native tracks and a shared-backend coordination plan.
Tradeoff: You accept duplicated implementation, broader specialist staffing, and two release surfaces.
Six or more uncertainty items remain, or a provider, migration, or sensitive-data assumption can invalidate the architecture.
Choose: Fund discovery, a technical proof, or migration rehearsal before committing to a fixed build.
Tradeoff: You spend earlier to avoid pricing fiction and expensive rework later.
No one owns acceptance criteria, data decisions, post-launch operations, or a continuing support budget.
Choose: Defer the build until ownership exists.
Tradeoff: A later start is safer than launching software nobody can operate or maintain.
TEST THE SUPPORTED DELIVERY PATH
Turn the scoped web app into working evidence
Use Playcode Cloud for the backend, data, and recovery layer of a web-first build. Test the real workflows and operating assumptions before funding native distribution or a larger commissioned project.
Explore Playcode CloudPlaycode Cloud supports web apps; native packaging, signing, and store submission remain separate workstreams.
See Playcode plans and current subscription pricingProduct subscription pricing is different from the commissioned-project planning estimates in this guide.
What this model cannot tell you
A transparent estimate is still an estimate. Sensitive, mobile, and regulated products need case-specific professional review. This guide is not legal, security, privacy, accessibility, or compliance advice; qualified owners determine the obligations that apply. Treat every output as a planning conversation and update it when evidence changes.
- The BLS figures are U.S. employee wage and compensation proxies, not agency or freelancer prices and not global rates.
- The scenario role-hours and contingency bands are editorial assumptions, not measured market averages.
- The build ranges exclude provider usage, taxes, legal advice, customer acquisition, and customer-support staffing unless entered separately.
- Security, accessibility, privacy, and regulated scope must be priced from actual controls, evidence, contracts, and professional review.
- OWASP MASVS, NIST SSDF, WCAG, and HHS guidance help identify work to investigate; citing them does not certify or prove compliance.
- Store requirements, review, provider fees, and service pricing change. Recheck the official source before publication or launch.
- AI may compress some implementation effort, but this model provides no universal AI savings percentage.
- Total role-hours do not convert directly into a delivery date because work is not perfectly parallel and external queues remain.
- Playcode builds and hosts web apps; native iOS or Android packaging, signing, and store submission are separate workstreams.
Sources and evidence dates
Primary government, standards-body, platform, and provider sources support the current inputs. Volatile prices and policies were checked on 2026-07-31 and need periodic review.
[bls-oews-2025] U.S. Bureau of Labor Statistics:Occupational Employment and Wages, May 2025
Checked July 31, 2026. Supports: Median hourly wages of $65.38 for software developers, $50.14 for QA analysts/testers, $50.00 for web and digital interface designers, and $49.19 for project management specialists.
[bls-employer-costs-2026] U.S. Bureau of Labor Statistics:Employer Costs for Employee Compensation, March 2026
Checked July 31, 2026. Supports: For private-industry professional and related occupations, wages and salaries were 67.6% and benefits 32.4% of compensation.
[apple-membership] Apple Developer:Become a member
Checked July 31, 2026. Supports: Apple Developer Program membership is 99 USD per membership year.
[apple-review] Apple Developer:App Review Guidelines
Checked July 31, 2026. Supports: Submission and continuing-release work includes completeness, metadata, functional backend or demo access, device testing, privacy, safety, performance, business, design, and legal review criteria.
[google-play-account] Google Play Console Help:Get started with Play Console
Checked July 31, 2026. Supports: Google lists a US$25 one-time Play Console registration fee and account verification steps.
[google-play-testing] Google Play Console Help:App testing requirements for new personal developer accounts
Checked July 31, 2026. Supports: Qualifying personal accounts created after 2023-11-13 need at least 12 opted-in closed testers for 14 continuous days before applying for production access.
[google-play-service-fees] Google Play Console Help:Understanding Google Play's lower service fees
Checked July 31, 2026. Supports: Google Play documents fee variation by market, transaction, program, install state, and billing path, with the newer service-fee structure rolling out in the US, UK, and EEA from 2026-06-30.
[firebase-pricing] Firebase Documentation:Firebase pricing plans
Checked July 31, 2026. Supports: Firebase documents no-cost quotas, Blaze pay-as-you-go usage, product-specific meters, and that budget alerts do not cap charges.
[stripe-pricing] Stripe:Pricing and fees
Checked July 31, 2026. Supports: The standard U.S. page lists 2.9% plus 30 cents for successful domestic-card transactions; other cases have other fees.
[maps-pricing] Google for Developers:Google Maps Platform pricing
Checked July 31, 2026. Supports: Maps pricing is pay-as-you-go by SKU and billable event, with service-specific free caps and volume tiers.
[twilio-sms-pricing] Twilio:SMS pricing in the United States
Checked July 31, 2026. Supports: SMS cost varies by destination, sender type, message segment, phone number, carrier fee, and registration.
[nist-ssdf] National Institute of Standards and Technology:Secure Software Development Framework 1.1
Checked July 31, 2026. Supports: Secure development practices belong throughout the software lifecycle and acquisition discussion rather than in a final one-time check.
[wcag-22] World Wide Web Consortium:Web Content Accessibility Guidelines 2.2
Checked July 31, 2026. Supports: WCAG 2.2 provides testable accessibility success criteria organized around perceivable, operable, understandable, and robust principles.
[owasp-masvs] OWASP Foundation:Mobile Application Security Verification Standard
Checked July 31, 2026. Supports: MASVS groups mobile application security requirements across storage, cryptography, authentication, network communication, platform interaction, code quality, resilience, and privacy.
[hhs-hipaa-security] U.S. Department of Health and Human Services:The Security Rule
Checked July 31, 2026. Supports: Covered entities and business associates must apply appropriate administrative, physical, and technical safeguards to protect electronic protected health information.
App development cost questions
What is the average cost to develop an app?
There is no useful universal average because scope, team, rates, data, backend behavior, integrations, platforms, quality requirements, and operations differ. Use the visible role-hour scenarios as planning examples, then replace every assumption with your project evidence.
What makes an app expensive?
The largest drivers are usually workflow and permission complexity, data lifecycle and migration, backend behavior, integrations and their failure handling, offline behavior, native platforms and device coverage, security or regulatory evidence, and post-launch support. Screen count alone is a weak estimate.
Is a web app cheaper than a mobile app?
It can require less channel-specific work because one browser-delivered app avoids separate store packaging and some platform release operations. A complex web app can still cost more than a narrow mobile app, so compare the same workflow, backend, data, integrations, quality bar, and support target.
Does cross-platform development cut the cost in half?
Do not assume that. A shared codebase can reduce duplicate implementation, but iOS and Android still need platform-specific builds, signing, permissions, physical-device coverage, store assets, review, release, and defect handling. Estimate shared and platform-specific work separately.
Can AI make app development much cheaper?
AI can reduce some drafting and implementation effort, especially for a bounded proof. It does not remove product decisions, data rules, provider credentials, retries and outages, security review, accessibility, device testing, store requirements, or operations. Measure saved hours in the real workflow instead of using a universal percentage.
How long does app development take?
Calculate the critical path from role-hours and real staffed capacity, then add integration lead time, testing, stakeholder decisions, external review queues, and uncertainty. Total hours divided by nominal headcount is not a reliable delivery date because work is not perfectly parallel.
What recurring app costs should I budget for?
Include runtime, database, storage, transfer, backups, monitoring, provider usage, messages, maps, payments or store fees, developer accounts, dependency and OS updates, support, incident response, content or moderation, privacy, security, and accessibility work. Model units and service levels rather than a universal maintenance percentage.
What should an app development quote include?
It should name workflows, platforms, roles, data, backend, integrations, migration, testing, accessibility, security, release work, operations, assumptions, exclusions, acceptance criteria, change process, recurring provider charges, and the support boundary. Ask which unknowns can reopen the price.
What do Apple and Google charge to publish an app?
As checked on 2026-07-31, Apple lists 99 USD per membership year and Google lists a US$25 one-time Play Console registration fee. Store monetization and service fees are separate, vary by program and transaction path, and change over time.
Can Playcode build and publish a native mobile app?
Playcode builds and hosts web apps. It does not currently provide or prove native iOS or Android packaging, signing, App Store submission, or Google Play submission. Use Playcode for a web-first proof or production web app, and budget a separate native track when native delivery is mandatory.
REDUCE SCOPE RISK FIRST
Build the web-first proof before funding every platform
Use Playcode AI to build the working web app and Playcode Cloud to run its backend and data. Test the real workflow, roles, failure states, and demand before you commit to native packaging or a larger delivery team.
Build a web app with PlaycodePlaycode builds web apps. Native iOS or Android packaging, signing, and app-store submission are separate workstreams.