There are more app development companies than any buyer can evaluate, and the portfolios all look the same because they are all screenshots. Four questions, asked in writing before any commercial conversation, will remove most of the field in an afternoon. None of them is about technology, and all of them are about whether the arrangement will still work for you in a year.
Ask four things before hiring an app development company: can I download three apps you built today, is server-side work inside the quote, whose developer accounts does it ship under, and what does month two cost. Vague answers on any of the four predict the problems that appear in month three.
Question one: can I download three apps you built, today?
Not screenshots. Not a case study PDF. Store links you can install on your own phone in the next five minutes and use. This single question removes a surprising share of the field, and it is entirely reasonable to ask before any pricing conversation.
When you have them, look past the visual design. Does it feel fast? What happens when you turn off wifi mid-task? Is there a crash on an older device? Those things tell you about engineering rather than about the designer.
Question two: is server-side work inside this quote?
If your app has accounts, stores data, sends notifications or takes payment, there is backend software behind it. It is invisible in a mockup and it is frequently the larger half of the work. It is also the most common thing quietly excluded from a low quote.
Ask for it as its own line with its own number. A firm that folds it into a single figure has either not scoped it or is hoping you will not notice until the change order. We break the components down in the piece on what an app costs to build.
Question three: whose developer accounts does it ship under?
The correct answer is yours: your Apple Developer account, your Google Play account, your repository, from day one rather than transferred at the end. An app published under an agency's store account is genuinely difficult to move, and it is the regret we hear most often from businesses on their second app team.
This belongs in the contract rather than in an email thread. Ask for it in writing and treat hesitation as the answer.
Question four: what does month two cost?
Operating system updates, device testing, crash monitoring, store listing maintenance and iteration. Budget 15 to 25 percent of the build cost annually. A firm that has not thought about this has not shipped many apps, because everyone who has knows launch is roughly the halfway point.
An unmaintained app does not simply look dated the way a website does. It eventually breaks on a new OS version and disappears from the store, without warning.
Two answers that should end the conversation
- We can build anything. Everyone can build anything given enough money. What you want is a firm that tells you what they would not build, and why.
- Everything is included. If nothing is excluded, nothing has been defined. Ask for the exclusions list in writing, with pricing for changes, before you sign.
What good scoping actually looks like
A firm worth hiring will insist on a discovery step before quoting a fixed number, and will produce a written specification covering screens, rules, integrations and edge cases that you keep regardless of who builds from it. That document is what makes competing quotes genuinely comparable, and it is worth paying for on its own.
We publish how we scope this on our mobile app development and custom software pages, including the cases where we would tell you not to build.
And the question to ask yourself
Do you need an app at all? If the value is content or a straightforward transaction, a responsive website reaches everyone with no install friction and no store review. Apps earn their place through repeat use. A good development company will raise this before you do, even though it costs them the larger project.
Frequently asked questions
How do I choose an app development company?
Ask four things in writing before any pricing conversation: can I download three apps you built today, is server-side work inside this quote, whose developer accounts does it ship under, and what does month two cost. Vague answers on any of the four predict the problems that surface in month three.
What should I look for in an app development portfolio?
Store links you can install rather than screenshots. Then test the apps yourself: does it feel fast, what happens when the connection drops mid-task, does it hold up on an older device. That tells you about engineering, which screenshots cannot.
Who should own the app and the store accounts?
You should. The app publishes under your Apple Developer and Google Play accounts and the code sits in your repository from day one rather than being transferred at the end. Get it in the contract, because an app under an agency's account is genuinely hard to move.
What is a discovery engagement and is it worth paying for?
A short, separately quoted piece of work producing a written specification covering screens, rules, integrations and edge cases. It is worth paying for because you keep it regardless of who builds from it, which is what makes competing quotes genuinely comparable.
What are the warning signs when hiring an app developer?
Two answers should end the conversation: we can build anything, and everything is included. The first avoids the useful question of what they would not build. The second means nothing has been defined, which is where scope disputes begin.