Persona che lancia aeroplano di carta

18 November 2026

An App That Works Isn’t Always Ready to Launch

Not every application that “works” is also ready to be released on the market. Find out what makes the difference between a complete app and one that merely works.

Tips

Looking at the application running on the test device, it seems complete: all the screens are there and look great, the core features are in place and the most obvious bugs have been fixed.


It might seem like this is enough to guarantee the release of the application on the stores, and yet it isn’t. We’re often misled by the fact that the whole visible part is right in front of our eyes, but there are other aspects that remain hidden and deserve just as much attention.


The stores’ technical timelines

Anyone who has never done it might think that publishing an application on the stores (Apple Store and Google Play, specifically) is just a matter of filling in a form or something like that. The truth is that there are criteria by which an application is accepted or rejected by the stores.


Who publishes the application?

Applications can be published both by individuals and by organizations. If the application is developed by a third party, the procedure usually requires that:

  • The client company creates its own business account.
  • The software house developing the application joins as a collaborator, so that if one day the company decided to change supplier, it would still have full control over the store.


So, first of all, you need to set up the developer accounts for the company, if this is the first application being published. It’s also necessary to register a D-U-N-S number, that is, a company identification code. The time it takes to obtain one varies; Apple states that it takes up to 5 days, while Google points out that it can even take a month!


Knowing the procedure and the information that will be requested is necessary to avoid unpleasant surprises, such as thinking you’ll have an app in production in a few days and then finding out you have to wait 30 days.


What the approval process looks like

For the application to be approved, developers have to submit a version of the application to a review process; Apple states that 90% of applications get a response within 48 hours, but you may end up in the unlucky 10%, so be careful about making promises to the client.


Timelines may get longer if the review is not successful. The usual reasons this happens are:

  • Functionality issues. If the app crashes, some features don’t work, or there are placeholder texts and broken links, the application may be rejected. Promising features that aren’t included is also a reason for rejection.
  • Privacy issues. When the privacy policy is missing, not all the data collected from users is declared, or more permissions are requested than can be justified by the included features, the stores may refuse publication.


The more complex features are included, the greater the risk that something goes wrong; so think about it before launching an application with a thousand functions right from the first release.


Approval doesn’t necessarily mean publication: once the app has been approved, it can be released automatically, or you can opt for a manual or scheduled release.


Don’t forget the store listings

As a matter of fact, there is a kind of form to fill in: the store listing, which includes various information such as the app description, name, preview screenshots and, in the case of the App Store, also a list of keywords that help users find your app.


Don’t arrive unprepared: it can take time to produce all the required texts, which differ slightly depending on the channel. This aspect shouldn’t be underestimated, because the store is a bit like a search engine and your application’s ranking also depends on the data entered in the listing.


Optimizing the listing even has a name: ASO (App Store Optimization). It’s the equivalent of SEO for websites, and doing it well takes time and study.


Data at hand right from the start

Another aspect that is usually overlooked is monitoring. Finally having the application on the store without knowing who uses it, how and how often is of little value.


Many developers and entrepreneurs, carried away by the enthusiasm of a “finished” application, overlook this aspect and postpone it to a later stage. But data that isn’t collected is lost for good.


Why add analytics tools right away

Analytics tools make it possible to gather essential information, such as:

  • Does the application do what it was developed for? Do users use the main feature?
  • Is there a point where users get stuck? For example, a form that’s too long or a point where slow loading makes them think there’s an error?
  • Which operating systems, devices and app versions are users on?


Collecting this information makes it possible to set priorities for the future, acting on the basis of concrete evidence. What’s more, if a future change were to cause problems, having tracking in place helps trace the problem back to its origin.


How to include analytics without causing damage

All right, maybe I’ve convinced you: you need to add data collection. But how do you do it without running into problems down the line?


First of all, let’s ask ourselves right away what purpose that data will serve. If, for example, we choose to do A/B testing on a feature, we already know we’ll want to understand which variant works best, so we’ll definitely need to track which version of the feature the user received and what outcome it produced.


If tracking too little can leave us without the answers we’re looking for, tracking too much also has its downsides: too much data needs to be cleaned and filtered to provide definitive answers.


Data collection also needs to be tested like any other feature: you need to verify that tracking actually happens, but also that the same event isn’t tracked twice.


Finally, let’s remember that in Europe user consent is required to collect data. The legal side is often underestimated or tackled too late, with the risk, as already mentioned, of the store rejecting the application, with consequences on the timeline.


Preventing errors and monitoring them

What happens if the application needs major fixes immediately? And how do we notice? Once again, these are questions we need to ask ourselves before the release.


Unlike a web platform, where changes are immediate for all users, in mobile development a release requires technical time for approval and for the user to choose to update the app. That’s why you need to plan a way to intervene without a new version.


Remote configuration

There are a number of remotely configurable settings that can be changed without releasing a new update. To implement them, you use tools such as Firebase Remote Config.


What makes this tool useful is that it can:

  • Force a mandatory update. If a feature has been added that is incompatible with the previous version of the application, or if a serious problem is found, you can require the user to update the app in order to keep using it.
  • Show a maintenance notice. For serious malfunctions or special needs, you can suspend use of the application during a maintenance period. Some applications do this on a schedule, often at night.
  • Manage feature flags. When a feature depends on a feature flag, it can be turned on and off without the need for updates, even just for specific users.


Be careful when choosing which features to control remotely: they need to be decided before the release, and whatever is left out can’t be included without an app update.


Error monitoring

But how do we notice that something is going wrong? Sure, two methods are obvious:


Although these tools have their uses too, the best method is to implement an error monitoring system that detects problems even before the user reports them, as well as providing additional information, such as how serious and how widespread they are.


Knowing exactly what’s happening, who it affects and how often allows us to prioritize correctly: an error affecting half of the users, for example, requires a quicker response than one that only affects users with a specific phone model.


But tracking errors also makes it possible to intervene quickly: it gives us the exact point in the code where the error occurs, provides information about the context and allows us to reproduce it, all factors that contribute to the speed of the fix.


But be careful: here too, tracking needs to be implemented before launch, clearly declared on the store and tested to verify that it works.




Ultimately, turning to experts is the best way to release the application not only on schedule, but also complete with all the features that are often underestimated.


If you have an idea for a mobile application and you’re looking for the right team to develop it, we can help. Contact us through the form in our contact section, or send us an email. Book a no-obligation introductory call, and let’s find out together whether we could be the digital partner for your project.