You built the app, nobody downloads it
Getting into the store is not a distribution plan. Installs do not happen on their own, and that work sits outside the software budget.
The app is live. The design is good, it works, there are no bugs. A month passes and the install count is in double digits.
This is the most common disappointment we see. And the cause is almost never the quality of the app.
The store is an archive, not a shop window
The usual assumption: once the app is in the store, people will see it.
They will not. There are millions of apps in the App Store and Google Play. For someone to find you, they either have to search for your name deliberately or appear in a list — and appearing in lists tends to require installs you do not yet have.
The store is not where people discover you. It is where they install you after hearing about you somewhere else.
So where do they hear about you?
The answer is in your business, not in the app. Realistic channels:
Your existing customers. People who already work with you. Your mailing list, your WhatsApp group, a line at the bottom of your invoices.
Physical touchpoints. Your shop, your vehicles, your packaging, your business cards. QR codes still work.
The team in the field. For an internal app, distribution is not marketing — it is rollout: installing it for people, showing them, and closing the old channel.
Your website. If you already have traffic, that is the cheapest route to the app.
Paid ads. They work, but cost per install is usually higher than people expect. Starting here before trying the other channels is an expensive way to learn.
Store search (ASO)
Sometimes people search for the job rather than for you. For that:
The name. Your brand plus what you do. Not "Dafa" but "Dafa — Service Tracking".
Subtitle and description. The first two lines show in the list; the rest is behind "more". Put the most important sentence first.
Screenshots. The only thing people genuinely look at. Instead of raw screens, add a caption to each one explaining what it does. The first two matter most; the rest rarely get swiped.
Category and keywords. What word would your customer type? "Service tracking" or "fault report"? Ask them rather than guessing.
Reviews and rating
Below four stars, installs get noticeably harder. And the earliest reviews stay at the top for a long time.
Two practical rules:
Ask for a review at the right moment — after the user has successfully finished something, not the first time they open the app.
Reply to bad reviews. New visitors read the reply more than the complaint; seeing a team that engages is worth more than one bad review costs.
The forgotten budget line
Distribution rarely appears in a software budget. Yet the difference between a good app nobody uses and an average app everybody uses lives exactly there.
The question to ask before starting: where will the first hundred users come from?
If there is no concrete answer, find one before building. "They'll find it in the store" is not an answer.
Internal apps are a different problem
If the app is for your own team, you do not have an install problem — you have an adoption problem. People install it, use it for a week, and drift back to the old way.
There, distribution means training, closing the old channel, and fixing complaints quickly in the first weeks. It is not technical work, but it decides whether the project succeeds.
We ask this question at the quoting stage. The answer is not our job, but a project without one produces, at best, an app that works and nobody uses — and nobody wants that.