A row of switched-off smartphones on a dark table, one screen glowing blue

How to Choose a Mobile App Development Company Without Regrets

Finding a mobile app development company is easy. Finding the right one is not. There are plenty of studios, every portfolio looks polished, and estimates for the same project can differ several times over. A wrong choice is expensive: six months of work, an app that fails store review, and code nobody but the original team can maintain.

At Sphere we build websites, mobile apps and web services, so we see this decision from both sides: what clients ask, and what they should be asking. Here is how the types of contractors differ, what an app development studio should be able to do, and how to vet it before you sign.

Who builds apps: freelancer, studio, integrator or in-house team

The first question is not which studio to pick but which type of contractor you need. The answer shapes your budget, speed and risk.

Best forStrengthsRisks
FreelancerA prototype or a small updateCheap, starts fastEverything hinges on one person; design, testing and backend aren't in one place
Development studioA product for customers or staff, an MVP and its growthEnd to end, one team accountable for the resultYou need to check the process and real projects
Large integratorBig programs spanning many systemsResources, procedures, enterprise complianceExpensive and slow for a single app
In-house teamThe app is the company's core productFull control and deep product knowledgeSlow hiring, and the team costs money between releases too

For most companies that need an app for customers, partners or employees, a studio is the sensible choice. An in-house team usually comes later, once the product has proven its value and is under constant development.

What a full-service studio should cover

End-to-end app development is about more than programmers. An app is built from several layers, and when one of them is outsourced, accountability gets blurry. Make sure the app development company handles all of it in-house:

The backend is where many contractors fall short. An app without a well-designed server and admin panel looks great in a demo, but in production every content change turns into a ticket for a developer.

How to vet a studio's portfolio

Screenshots in a pitch deck prove nothing: you can draw mockups for an app that never shipped. The main test is simple: download the apps in the portfolio and try them yourself.

Ask the studio to walk you through one project in detail: what the brief was, who was involved, what went off plan and how it was solved. A studio that actually built the app answers confidently and with specifics. For example, we built a mobile app for a VPN service from start to finish and can take it apart stage by stage.

Process, team and who owns the result

Process

Ask how the work will run week by week: what the phases are, what you get after each one, how often you'll see demos. A good answer is concrete: research ends with a document and a map of user flows, design with a clickable prototype, and development runs in iterations with test builds you install on your own phone.

Team

Find out who will work on the project: project manager, designer, mobile developers, backend developer, QA engineer. Ask which of them are on staff and which are brought in for the project. That isn't necessarily bad, but you need to know who is accountable for the result.

Code and accounts

This is what clients remember too late. An app lives in a developer account in the store, and the developer accounts must be registered to the client, not to the studio or one of its employees. A published app can be transferred to another account, but that's a separate procedure with its own conditions, and it's easier to get it right from the start.

Red flags when choosing an app developer

Some warning signs show up at the very first meeting. Be wary if an iOS and Android developer does the following:

A studio that names a price without asking a single question about your business is estimating an average project, not yours.

Questions to ask a studio at the first meeting

Take this list to your meetings and compare how several contractors answer before you hire a mobile app developer:

Compare the scope, not just the totals. Two estimates that differ by a factor of two often describe two different projects: one includes research, an admin panel and testing, the other only the app screens.

How we build mobile apps

Sphere is a digital agency in Paris. We run an app through the same four stages as any other product, and at each one the client gets a clear deliverable.

  1. Analysis, structure and messaging. We get to know the business, research the audience and competitors, and describe the user flows and every screen. By the end it's clear what goes into the first release and why.
  2. Visual language and design. Prototypes and design from scratch, no templates, in several style options. We account for how users are used to doing things on iOS and Android.
  3. Development and testing. The mobile app, backend, admin panel and integrations, all tested before handover.
  4. Launch and growth. Publishing to the stores, updates, analytics and new features based on data about how people use the app.

We bring our own ideas instead of just following the spec, and we treat deadlines as a measure of the quality of our work. You can see projects we've delivered in our app and website development work, and read about the team and our approach on the About Sphere page.

FAQ

How much does it cost to build a mobile app?

There is no off-the-shelf price. The budget depends on the number of screens and user flows, the platforms (iOS, Android or both), backend complexity, integrations with your CRM, ERP and payment providers, and the scope of design and testing. Ask the studio to break the estimate down by phase and feature so you can see what you are paying for and what can move to a second release.

Freelancer or app development studio: which is better?

A freelancer works for a prototype or a small update to an app that is already live. If you need a product with design, a backend, an admin panel, store publishing and ongoing support, a full-service studio is the safer bet: it has a team for every stage and does not depend on a single person.

Should we build for iOS and Android at the same time?

Usually yes, if your audience is broad: most markets have a significant share of users on both platforms. Cross-platform development lets you ship both versions from a single codebase. Starting with one platform makes sense when your audience clearly sits on it or when you need a quick pilot.

Whose name should the App Store and Google Play developer accounts be in?

Your company's. An app is published under the account owner's name, and moving it to another account later is harder than setting everything up correctly from the start. The studio gets access to the accounts as an invited team member.

Who owns the app's code once development is finished?

The contract decides that. Standard practice is that exclusive rights to the code, design and documentation pass to the client once paid for, and the source code lives in a repository the company has full access to. If the contract says nothing about it, add the clause before work begins.

Let’s discuss your project
Related reading