When Apple says “no”

Whether for prestige, snobbery or because the business depends on it, Apple is, without a doubt, the great reference when it comes to Apps.Without fear of exaggeration, if an App is not in the Apple Store, it does not exist or is not worthy of existing. It is that crude. This is what the Cupertino company uses when it comes to being more demanding and careful every day in the application acceptance criteria. In fact, they can be so picky that the reasons for rejection range from the most varied to the ethically and professionally correct. Luckily, almost all of them are fixable. The main reason why people in Apple decides to reject the publication of an App in its store is easy to guess: the lack of informationApple requires all kinds of details to be checked before validating an App, so it is not surprising that throughout the process some detail is missed that, however insignificant it may seem, is especially relevant for the final certification. Another key element to overcome for the publication of an application in the Apple Store is that there is no “bugs”. Apps must be functional at 100% and any failure means that they are rejected. Maximum demand for the maximum guarantee and prestige. Apple, like us, does not want failures in its products. Another element, apparently a personal judgment, is the third major reason for invalidating an App: that is complex. Apple technicians want applications that are simple for the user; and when they say simple they mean that everyone knows, at a glance, how they work. They admit that this means more work for developers but “it is worth it”. And in that they must be given the benefit of the doubt. In a smaller group are those rejections caused either because the images or names used do not correspond to the contents of the App, because these same contents are illegal or fraudulent or even due to the similarity of this App, basically in the name or description rather than in its functionality, with other existing ones. Finally, of course, an App will always be rejected if it is attempted trick Apple. That is, if, for example, we give it lower security and child protection ratios than the App should really have. Although we are convinced that no one wants to deliberately deceive you, even if it is by mistake, lying is not right. Finally, in the top10 of Reasons why Apple returns an App The best way to fix bugs is to make sure that this is a test or beta version. With these, no testing, or you go to 100% or nothing at all. The worst thing of all is that falling into any of these faults, more minor than serious, brings about something much worse than the review of the App or the data provided: it delays the already slow Apple publication process. A process that, on average and without problems, is situated in the two weeks.