An app development company that will tell you not to build one
Direct answer: Most businesses asking for an app need a web app or a progressive web app, not a native app: it costs a fraction, needs no store approval and reaches customers through a link. We tell you which one you need in a 60-second tool on this page, then quote native, cross-platform, PWA or web builds to the business, with published cost and retention data behind the recommendation.
Roughly half the businesses that ask us for an app need something cheaper, faster and easier to keep alive. Find out which half you are before you spend a dollar.
The tool on the right is a working app, running inside this page. Five questions, real logic, an actual answer at the end. No email required.
Five questions. One honest answer.
We weigh how often people will use it, what hardware it touches, whether it works offline and what you sell inside it — then name the cheapest build that still does the job.
Who opens this thing?
How often does one person use it?
What phone hardware does it need?
Does it have to work with no signal?
What gets sold inside it?
Nothing is stored or sent. Everything runs in your browser.
Four ways to put software in someone's hand
They are not interchangeable, and the gap between the cheapest and the most expensive is roughly an order of magnitude. Most of the value an app development company adds happens in this decision, before anyone writes code.
Fastest, smoothest, and the only option when you need deep hardware access such as background location, tight camera control or heavy on-device processing. You maintain two separate codebases forever, which is exactly as expensive as it sounds.
One codebase ships to both stores. For the overwhelming majority of business apps the user cannot tell the difference, and published industry guidance puts the saving at 30–50% against building two native apps.
Adds to the home screen, sends push notifications, works offline for cached content, and skips app review entirely. No store listing, no 15–30% commission on digital sales, and updates go live the moment you publish them.
Dashboards, booking systems, quoting tools, portals, internal software. If people reach it from a laptop as often as a phone, this is almost always the right answer. We cover this in depth on the web app development page.
There is a fifth option nobody sells you, and it is often correct: fix the mobile experience of the website you already have. A page that loads fast and converts well beats an app that 95% of downloaders abandon inside a month. That is the entire argument of our work as a conversion rate optimization agency, and it applies to software as much as to landing pages.
The two numbers that should decide this
Everyone budgets for the build. Almost nobody budgets for the two things that actually kill apps: people stop opening them, and the stores keep saying no.
Where installs go in 30 days
Average retention by platform, AppsFlyer data as published by Business of Apps. Scale runs to 30%. Separate 2026 benchmark work puts the median app at roughly 4% retention on day 30, with about a quarter of users never opening an app a second time.
Downloads are not the finish line
An app that keeps 5% of its installs after a month needs twenty downloads to hold onto one user. If your plan is to promote the app to your existing customers, you are paying app prices to reach people who already know you.
Retention has one reliable lever, and it is not features. Apps that get a person to a genuinely useful moment inside the first session hold two to three times more of them a week later. That is a conversion problem wearing a software costume, which is why we scope the first screen before we scope the feature list.
And then there is review
Apple reviewed 7,771,599 submissions in 2024 and rejected 1,931,400 of them. In 2025 it reviewed more than 9.1 million and rejected over two million. Google Play is far more permissive on the way in, at roughly 8% rejected in 2025, but removed over two million apps after publication that same year.
Apple's most-cited categories are performance, legal, design and business, in that order. The one that catches small businesses is guideline 4.2, minimum functionality — if your app is essentially your website in a wrapper, it does not get in. That single rule invalidates a large share of the app ideas we are asked to quote.
Share of submissions rejected, 2025
Surfshark analysis of 2025 store data, scale runs to 30%. Rejection is rarely permanent — most are change requests you can fix and resubmit — but each round costs days, and a store account also costs $99 a year with Apple and $25 once with Google before a single line ships.
What it costs over five years, not five months
Build price is roughly half of what an app costs you. Set the four things that actually move the number and watch the rest appear. Every range below comes from published 2026 industry figures, not from us.
How big is the first version?
A focused feature set, one core job done well, published at $15,000–$50,000.
How are you shipping it?
Who is building it?
How heavy is the backend?
Published hosting and infrastructure guidance runs $500 to $5,000 a month depending on traffic, media and real-time features.
Five-year total, all in
$0
Launch extras cover store compliance, transaction fees, legal and privacy work, and the marketing needed to get anyone to install the thing. GoodFirms puts them at 25–35% of project cost, and they are the line that surprises people. Maintenance at 15–20% of build cost per year is not optional either — operating systems change twice a year, and an app that stops working on the current iOS is an app that gets deleted.
If you sell digital goods or subscriptions inside the app, add the store commission on top: 30% standard, 15% for developers under $1 million in annual proceeds through Apple's Small Business Program, and 15% on Google Play subscriptions from day one. Physical products and in-person services are excluded from that commission entirely, which is why a plumbing company and a meditation app have completely different app economics.
These are planning ranges for a conversation, not a quote. Real numbers come out of a scoping call where we look at what you are actually trying to make happen.
How the build actually runs
Six stages, in this order, because each one kills work that the next one would have wasted. The first two happen before you commit to a build budget.
Decide whether it should exist
We map who uses it, how often, and what job it does that your website cannot. If a progressive web app or a better mobile site does the job, we say so here and the conversation gets much cheaper. This is also where we check your idea against Apple's minimum functionality rule, before you find out the expensive way.
Define the smallest version that works
One core workflow, done properly, shipped early. Every feature that survives this cut has to earn its place against the hours it adds. The list of things we deliberately left out gets written down too, so nobody re-argues it in month four.
Design the first sixty seconds
Retention is decided in the first session. We design the path from cold open to a genuinely useful moment before we design anything else, because everything past that point is worthless if people never arrive.
Build in visible increments
You get something installable on your own phone early and often. Two-week increments, working software each time, no six-month reveal. Cross-platform unless there is a hardware reason not to be.
Test on the phones people actually own
Crashes and bugs are the single largest rejection category, and most of them show up on mid-range Android hardware that never gets tested because the team all carry flagships. We test on real devices, not just simulators, and we prepare the review submission properly the first time.
Watch what people do, then fix it
Install to first-use, first-use to return, return to habit. Those three numbers tell you what to build next far better than a feature request ever will. This is the same discipline we apply to conversion optimization, pointed at software instead of pages.
Be honest about which column you are in
We would rather lose the build than take money for something we would advise a friend against. Here is how the two sides usually look.
An app earns its keep when
- People open it weekly or daily as part of doing their job or running their life
- It needs the camera, background location, offline data or hardware a browser cannot reach
- Your field crews, drivers or technicians work where signal drops out
- You are replacing paper, radio calls or a spreadsheet that costs real hours every week
- The app is the product and customers pay to use it
- Push notifications drive a behavior that makes you money, not just noise
You want something else when
- Customers would use it a few times a year, like booking a service or checking an order
- It would show the same content your website already shows
- The real goal is looking modern, and an app is the shape that took
- You have no plan or budget to market the app after launch
- Nobody internally owns it after the agency leaves
- The problem is that your website converts badly, which an app will not fix
That second column is not a soft no. It is usually a redirect to a web app, a progressive web app, or a rebuilt mobile site that costs a fraction as much and gets used more. We build all of those too, so the recommendation costs us nothing to make honestly.
Why hire this app development company
Search Converts has been building and running software since 2012 — custom-coded sites, tools and applications, plus a working portfolio of several hundred properties we build, host and maintain ourselves. Maintenance is not a theoretical line item to us. We pay it every month on our own stuff.
The founder also operates a home-services company outside the agency. That matters more than it sounds. It means the person scoping your app has been the small business owner staring at a five-figure software quote and asking whether it will ever pay for itself, and has answered the phone at seven on a Saturday when the software did not work. Agencies that have only ever billed for software tend to be optimistic about how much of it a business needs.
One practical note on how to shop for this. When you compare an app building company against a design-led app design company against a shop that only supplies app developers by the hour, you are comparing three different businesses. The first sells a finished product, the second sells screens somebody else has to build, and the third sells capacity you have to manage yourself. Ask any mobile app development company which of the three it is before you compare prices, because the quotes are not measuring the same thing.
We also sell every other channel, which removes the incentive to make an app the answer. If the honest recommendation is paid search, a lead generation system or fixing your site, we make money either way, so we say the true thing. Search and AI-search visibility for whatever we build runs through Eye To Ad Media, and regional website work through Denver Web Design.
App development questions we get asked
An app development company scopes, designs, builds, tests and launches software that runs on phones and tablets, then maintains it as operating systems change. In practice the highest-value part of the job happens before any code is written: deciding whether the idea needs a native app, a cross-platform app, a progressive web app or a plain web app, because that single decision changes the cost by roughly an order of magnitude. Search Converts also runs the marketing channels that would promote the app, so the launch plan is built alongside the product rather than handed over afterward.
Published 2026 guidance puts a focused first version at roughly $15,000 to $50,000, a full business app at $40,000 to $80,000, and a complex platform at $80,000 to $250,000 or more. Those figures assume a cross-platform build with a professional team. Building two separate native apps raises it substantially, and offshore teams reduce it by 40 to 70% with a corresponding increase in management effort. Ignore any single average you see quoted, including the widely repeated $171,450 figure, which traces back to research from around 2015.
You need native or cross-platform when the software requires hardware a browser cannot reach, such as background location tracking, deep camera control or reliable offline operation. You need a web app or progressive web app when people use it occasionally, reach it from laptops as well as phones, or when the content is the same thing your website already shows. The tool at the top of this page walks through the five questions that decide it, and gives you a recommendation with the reasoning attached.
Simple apps are commonly estimated at 300 to 600 development hours and two to four months of work. Mid-complexity business apps typically run four to seven months, and complex platforms with 2,500 or more hours of work run well past that. Add time for app review: Apple reviews most submissions within 24 hours, but a rejection and resubmission cycle adds days each time, and roughly one in four submissions is rejected on the first pass.
Apple rejected 1,931,400 of 7,771,599 submissions in 2024, and over two million of more than 9.1 million in 2025. The largest categories are performance problems such as crashes and bugs, then legal issues like a missing or inaccurate privacy policy, then design, then business rules. The rule that catches small businesses most often is guideline 4.2 on minimum functionality, which blocks apps that are essentially a website in a wrapper. Almost every rejection is a request for changes rather than a ban, so it is a delay rather than a death sentence, but it is a delay you can avoid by scoping correctly.
Budget 15 to 20% of the original build cost every year for maintenance, plus $500 to $5,000 a month for hosting and infrastructure depending on how heavy the backend is. Store accounts cost $99 a year with Apple and $25 once with Google. Published guidance also puts launch extras such as compliance, transaction fees and marketing at 25 to 35% of the project cost. The cost model on this page adds all of it up over five years so you can see the real number before you commit.
Only on digital goods and subscriptions sold inside the app. The standard rate is 30%, reduced to 15% for developers earning under $1 million a year through Apple's Small Business Program, and Google Play charges 15% on subscription revenue from day one. Physical products and in-person services are excluded entirely, so a contractor taking bookings or a retailer selling goods pays no commission. If you plan to sell digital subscriptions, that commission belongs in your business model from the start rather than as a surprise after launch.
Average iOS retention runs about 25.4% on day one and 5.3% by day 30, with Android at 20.2% and 3.8%. Benchmark work in 2026 puts the median app at roughly 4% on day 30, and around a quarter of users never open an app a second time. Social and communication apps hold the most, ecommerce and retail the least. The practical takeaway is that installs are a vanity number and the first session is where retention is won or lost.
Tell us what you want it to do
Describe the job in plain language and we will tell you which of the four build paths fits, roughly what it costs, and whether we think it is worth doing. If the answer is no, you get that for free too.
Your information is never sold or shared. We respond within one business day.
Related pages
The platform is one decision; what the site says and how fast it loads are the others. Related reading:
- AI website design — AI website design done properly: what AI defaults produce, why WebAIM found accessibility failures rising in 2026, and how to build for people and mac
- Shopify web designer — Shopify web designer focused on conversion: product pages that answer the shopper, a checkout with nothing in the way, speed on a phone, CRO after lau
- Traffic but no sales — Visitors arrive and nobody calls.
