Blog

How to choose an app development company: 12 questions

5 min read
Illustration: a checklist of questions being ticked off one by one beside a handshake.

In short: Choose the team that asks you the best questions, shows you live apps they built, and puts scope, ownership and support in writing. Price matters, but a cheap quote for the wrong scope is the most expensive kind. Below are twelve questions to ask every company on your shortlist, and what a good answer sounds like.

Before you start: know your own answer

You will get better answers if you can say who the app is for, what they do today instead, and the one job it must do. You do not need a specification. If you want a guide, see how to describe your app idea so it can be built.

About their work

  1. Can I use an app you built that is live today? Screenshots are easy to make. A live app you can sign up for shows real work. Ask which part they built.
  2. Who will actually work on my app? Ask for names and roles. Find out whether the people on the sales call are the people who build it, and whether any work is subcontracted.
  3. Can I talk to a past client? A short call with someone who has been through a project tells you more than any case study.

About scope, price and time

  1. What questions do you have about my idea? A team that quotes without questions is quoting a guess. Good questions show where your idea still needs a decision.
  2. What exactly is included, and what is not? Ask for screens, platforms and integrations in writing, plus whether design, testing, store submission and launch are in the price.
  3. How do you price changes? Ideas change during a build. You want to know how a change is estimated and approved before it happens.
  4. How often will I see working progress? Weekly working screens beat a big reveal at the end. Short cycles catch mistakes while they are cheap.

Rates vary widely by location. Clutch's pricing data lists $50 to $99 an hour for companies in the United States and $25 to $49 for several other countries. Compare total cost for the same scope, not hourly rates alone.

About ownership and access

  1. Who owns the code when the project ends? Do not assume. The US Copyright Office's circular on works made for hire explains that a commissioned work only counts as made for hire if it falls into one of nine listed categories and both sides sign a written agreement saying so. App code is not on that list, so ask for a written assignment of the copyright to you, and have a lawyer check it.
  2. Whose accounts will the app live in? The Apple and Google developer accounts, the domain, the hosting and the code repository should be in your name, with the developer given access.

About quality, launch and after

  1. How do you test, and how do you handle security? Ask what they test on, and how they protect user data. For phone apps, the OWASP Mobile Application Security Verification Standard (MASVS) is a public standard you can ask them to work against.
  2. Who handles the store submission and launch? Store review, privacy labels and launch-day monitoring are real work. Make sure someone owns them.
  3. What happens after launch? Apps need updates for new phones and operating systems, bug fixes and support. Ask what that costs and how fast they respond. Our post on the real cost to keep an app running after launch lists what to budget for.

Red flags

  • A firm price and date before anyone has asked you a question.
  • No live work you can try, only mock-ups.
  • Vague answers on code ownership or accounts.
  • Pressure to sign quickly, or a discount that expires tomorrow.
  • No plan for what happens after launch.

Green flags

  • They suggest a smaller first version than you asked for, and explain why.
  • They write the scope in plain English you can check without reading code.
  • They tell you when something is a bad idea, including when no-code or an existing product would do.

How we answer these

We run apps of our own that you can try today, including OwnSites, ProfVault, Wanderply, Homeroom, Brandreel and Shop the Reel. When you send us an idea, we read it ourselves and reply with questions and a plan. You see the screens before code is written, and the app goes live on your own domain. More in how we build an app, from idea to launch, and on security in how we protect the data in our apps.

Questions and answers

What should I ask an app developer before hiring?

Ask to use a live app they built, who will do the work, what is included and excluded, how changes are priced, who owns the code and accounts, how they handle security, and what happens after launch.

Do I automatically own the code an agency writes for me?

Do not assume so. The US Copyright Office's circular on works made for hire sets strict conditions for commissioned work. Get a written assignment of copyright in your contract and ask a lawyer to review it. This is general information, not legal advice.

Is the cheapest app development quote a good idea?

Only if it covers the same scope as the others. Ask each company to list what they included. A low price for a smaller scope is not a saving.

Talk it through with us

Ask us these twelve questions too. We would rather you compare carefully. If you would like a second pair of eyes, ask for a free app idea review. If you are ready to talk about building it, tell us about it on our contact page. A few honest sentences is enough to start.