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 for | Strengths | Risks | |
|---|---|---|---|
| Freelancer | A prototype or a small update | Cheap, starts fast | Everything hinges on one person; design, testing and backend aren't in one place |
| Development studio | A product for customers or staff, an MVP and its growth | End to end, one team accountable for the result | You need to check the process and real projects |
| Large integrator | Big programs spanning many systems | Resources, procedures, enterprise compliance | Expensive and slow for a single app |
| In-house team | The app is the company's core product | Full control and deep product knowledge | Slow 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:
- Research. The audience, use cases, competitors in the stores, and what the app should deliver for the business.
- UX/UI design. User flows, prototypes and mockups that follow iOS and Android guidelines, not a website squeezed onto a phone.
- Mobile development. Native or cross-platform, plus the ability to explain why that approach suits your project.
- Backend and admin panel. Server, API, database, a panel for managing content, orders and users, and integrations with your CRM and ERP.
- Testing. On real devices and different OS versions, not just in an emulator.
- Publishing. Preparing store listings, getting through review, and handling reviewers' feedback.
- Support and growth. Updates for new iOS and Android versions, bug fixes, analytics and new features.
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.
- Is it published? Find the app in the App Store or Google Play. Check who is listed as the developer. If it's the client rather than the studio, that's a good sign: the account was set up correctly.
- Is it updated? The date of the last update and the version history show whether the product is alive after launch.
- How does it work? Sign up, go through the main flow and the checkout if there is one. Pay attention to speed, clarity and bugs.
- What do users say? Store reviews and the replies to them say a lot about support.
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.
- The Apple Developer and Google Play Console accounts are registered to the client's company.
- The source code of the mobile apps and the backend lives in a repository the client can access.
- The server, domain, push notifications, analytics and payment services are registered to the company.
- The contract states that exclusive rights to the code and design pass to the client.
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 price before questions. They quote an exact cost without digging into user flows, integrations and admin panel requirements.
- No live apps. The portfolio is only mockups and concepts, with no store links.
- "We'll do whatever you say." The studio never pushes back, never suggests trimming the first release and asks nothing about the business.
- "The accounts are in our name, it's easier." An offer to publish the app under the studio's account.
- No testing in the estimate. "The developers test it themselves," with no separate phase and no devices.
- "We'll sort out support later." It's unclear who will update the app when a new iOS version comes out.
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:
- Which of your apps are live right now, and where can we download them?
- Native or cross-platform: what do you recommend for our project, and why?
- Who builds the backend and admin panel, and how will we manage content?
- How does testing work: on which devices and OS versions?
- Who handles publishing, and what happens if the store rejects a build?
- Whose name will the developer accounts, server and repository be in?
- What goes into the first release, and what would you suggest postponing?
- How often will we see work in progress?
- What does post-launch support include, and how is it billed?
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.
- 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.
- 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.
- Development and testing. The mobile app, backend, admin panel and integrations, all tested before handover.
- 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.




