Two phones side by side on a dark stone table, their screens showing rounded icons in shades of gray, next to a pen, a black notebook and sheets of paper, under blue light coming from the left

App development company: how to choose

By Leonel Rocha · Product Designer

· 6 min read

Short answerGuide

Choose an app company by what it has already shipped to the stores, how it tests before submitting, and who owns the Apple and Google accounts. In 2025, Apple rejected 2.09 million of 9.1 million submissions, and Google blocked more than 1.75 million apps. Also get in writing who updates the app when the stores change the rules.

Short answer

Choose an app company by what it has already shipped to the stores, how it tests before submitting, and who owns the Apple and Google accounts. In 2025, Apple rejected 2.09 million of 9.1 million submissions, and Google blocked more than 1.75 million apps. Also get in writing who updates the app when the stores change the rules.

2.09 million
app submissions rejected by Apple in 2025, out of 9.1 million reviewed
1.75 million
apps blocked by Google before reaching Google Play in 2025
31/08/2026
was Google's deadline for new apps and updates to target Android 16

Finding an app development company is easy. Choosing one is another story. Every proposal promises great design, a short timeline and an app “in the stores.” The difference only shows up later: when Apple rejects the submission, when Google changes a rule, when you want to switch vendors and find out the store account isn't in your name.

This guide is for whoever is paying for the app. It isn't about programming languages or tools. It's about the questions that separate a company that delivers a live app from one that delivers files and disappears. I used the numbers Apple and Google published about their own stores, because they show where projects get stuck.

The stores reject far more apps than you think

Your app only exists for your customers once it passes store review. And that review is strict. According to the 2025 App Store transparency report, Apple reviewed 9,100,620 submissions and rejected 2,093,244. That's almost one in four.

The most common reason is performance: 1,354,418 rejections fell under that section of the guidelines. On its App Review page, Apple says that, on average, over 40% of unresolved issues relate to guideline 2.1, app completeness, which covers crashes, placeholder content and missing information.

Google tightened its filter too. According to the Google Play safety review, published in February 2026, Google prevented more than 1.75 million policy-violating apps from reaching the store in 2025 and banned more than 80,000 developer accounts.

What this means for you: the right company isn't the one that codes fastest. It's the one that knows how to get through review without losing weeks to back-and-forth.

1. Ask for published apps, not portfolio screens

A portfolio full of pretty screens proves someone can design. It doesn't prove the app went live, or that it still works. In the meeting, make three requests:

  • Open an app you published, right in front of me. Download it from the App Store or Google Play, right there.
  • Show me the date of the last update. An app that hasn't been updated in a long time may have been abandoned after delivery.
  • Tell me about a rejected submission and what you did. Anyone who has published apps for a while has been rejected. Anyone who says they never have either hasn't published much or isn't telling you everything.

2. Ask how they test before submitting

A row of phones standing on a dark base lit in blue, each with a different screen of simple shapes, next to a card with a checklist
Before it goes to the store, the app needs to run on different devices and versions. Image: Studio Responsivo

If 40% of unresolved issues at Apple come from incomplete or crashing apps, testing is where your deadline is won or lost. Ask:

  1. Which devices and versions do you test on? A new phone and a three-year-old phone behave differently.
  2. Who tests? If it's only the person who wrote the code, you're missing an outside eye.
  3. Do you use the stores' own testing? TestFlight on Apple and closed testing on Google Play let you use the real app before launch.
  4. What does “done” mean to you? Done on the developer's computer, approved by the store, and live with customers using it are three different dates.

Choosing between a native app, hybrid app or PWA also changes testing and timeline. If you haven't decided yet, I compared the three paths in native app, hybrid or PWA. A good company explains why it recommends one for your case, not just the one it knows how to build.

3. The store accounts must be in your name

This is the most expensive mistake and the one least likely to show up in a proposal. To publish as a company on Apple, the Apple Developer Program enrollment page requires the organization to be a legal entity with a D-U-N-S number, and the person enrolling must have legal authority to sign for the company. The program costs US$99 a year, and the organization's name appears as the app's seller on the App Store.

In other words: if the account is opened in the vendor's name, your app shows up in the store as their product. Switching companies later means transferring the app from one account to another, with the old vendor cooperating. If the relationship ended badly, that can stall your product.

The same goes for everything else: code repository, server, payment gateway, notification service, domain. Anything that holds your business's money or data stays in your company's name, and the vendor gets guest access. The step-by-step for opening the accounts and what goes into the publishing timeline is in how to publish an app on the App Store and Google Play.

4. Find out who will write the code

Plenty of companies sell the project with one team and deliver it with another. Sometimes they outsource to freelancers, sometimes they swap people midway. Neither is a crime, but you need to know. Ask:

  • Is the team yours or hired per project?
  • Can I talk to the people who will build my app?
  • How many projects does this team run at once?
  • How do you use AI in development, and who reviews what it writes?

The answer to that last question says a lot in 2026. Using AI is normal. Having no one review what it produces is what fills the stores' rejection queue.

5. Ask what happens after launch

An app isn't a website that stays up on its own. The stores change their requirements every year, and anyone who doesn't keep up falls behind. Two examples from 2026:

  • Apple: since April 28, 2026, according to Apple's requirements page, every app submitted to the App Store must be built with Xcode 26 and the iOS 26 SDK or later. Your app's next update already has to follow this rule.
  • Google: since August 31, 2026, according to the Android documentation, new apps and updates must target Android 16 (API 36). Apps still below Android 15 stop showing up for new users on newer phones. Google opened extension requests until November 1, 2026, and that deadline is close.

On top of that, since September 30, 2026, Android developer verification applies in Brazil to apps installed on certified phones, including outside Google Play.

In practice: ask who handles these updates, how much it costs and how fast. If the proposal ends on launch day, it's incomplete.

6. Read the contract before the portfolio

A good proposal turns into a clear contract. Before you sign, check that it spells out the scope of the first version, what's out of scope, the delivery date, the definition of “done,” who owns the code and the accounts, and what happens if the date is missed. I listed it clause by clause in software development contract.

Red flags worth more than any sales pitch:

  • A price in the first meeting, without understanding the problem. It's a guess.
  • Yes to everything. Whoever doesn't cut scope pushes the bill to later.
  • A store account opened by the vendor “to speed things up.” It speeds things up today and locks you in tomorrow.
  • Not a word about maintenance. The app will need it in the first year.

How we do it at the Studio

Since 2014, we've launched more than 600 projects for clients in 13 countries. On an app project, we start with a discovery and only then set the price, with the scope in writing and the deadline written into the contract. The dev team is our own. We use Claude Code and Figma for design and build.

The Apple, Google, server and gateway accounts are in your company's name from day one, along with the code and files. And every system ships with an AI agent that runs daily, flags failures, suggests improvements and checks that the data makes sense.

If you are comparing proposals, bring these questions to the conversation with our app development team and see how each one gets answered.

Common questions

How do you know if an app company is good?

Ask them to download, right in front of you, apps they published that still get updates. Ask how they test before submitting to the stores and what they did when an app was rejected. Anyone who answers with concrete examples has been through it.

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

Your company's. On Apple, the organization's name appears as the app's seller in the store. If the vendor owns the account, switching companies later becomes a slow transfer, and the app can get stuck in the middle.

Should you hire a company that outsources its developers?

It can work, but ask who will write the code and whether you can talk to them. When the team changes mid-project, the knowledge about the app leaves with it. Better to know this before you sign.

What happens to the app after it goes live?

It needs regular updates. Apple and Google change their tooling and OS version requirements every year, and an app left alone stops accepting updates or disappears for new users. Agree in the contract on who does this work and how it is billed.

Sources

  1. 2025 App Store Transparency ReportApple · EN
  2. App ReviewApple Developer · EN
  3. Upcoming RequirementsApple Developer · EN
  4. Choosing a Membership: EnrollmentApple Developer · EN
  5. Keeping Google Play & Android app ecosystems safe in 2025Google · Vijaya Kaza · 2026-02-19 · EN
  6. Meet Google Play's target API level requirementAndroid Developers · EN
  7. Android developer verificationAndroid Developers · EN

Related service

Systems and apps

Systems, SaaS and iOS and Android apps from diagnosis to launch, with design, code and AI on the same team

View the service

Written by Leonel Rocha, Product Designer and founder of Studio Responsivo

Adobe Certified Expert · Adobe Instructor Design & Layout · Google UX Designer

News Responsivo

Get the next article in your inbox

Cost, timelines, AI and behind the scenes of shipping products. No spam.

Have an app to get off the ground?

Reply within 2 hours, during business hours.

Message us on WhatsApp

Prefer to write it out? Send the brief

Newsletter

News Responsivo

New articles in your inbox: cost, timelines and AI. No spam.

New Studio articles in your inbox: cost, timelines, AI and what we've learned shipping products. No spam. Unsubscribe anytime.

Check your email.

Your data stays with the Studio. Privacy