Setting up your Apple Developer Account


Once upon a time, all the Appmiral applications were submitted under our own Apple Developer Account. Apple has always been notorious in reviewing apps very thoroughly, yet in 2017 they decided to change the playing fields. An earthquake started in Cupertino hit the entire developer community …

We’re talking about the now infamous App Store Guideline 4.2.6 that was updated, which will result in a lot more individuals and organizations having to create their own App Store (developer) account.

4.2.6 Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences. Another acceptable option for template providers is to create a single binary to host all client content in an aggregated or “picker” model, for example as a restaurant finder app with separate customized entries or pages for each client restaurant, or as an event app with separate entries for each client event.

Appmiral isn’t a template app, at all.

The Appmiral framework is modular solution consisting of over 30 different building blocks. Every app we make is unique, not only by design but in 90% of the cases even in functionality. Nevertheless, Apple sees us as an app generation service meaning each client will need to publish its app under his own Apple Developer Account.

To be honest here, this is the only right approach as well. The festival is the content owner and data owner, so having their own app submitted from their own Apple Developer Account makes total sense.

Now there’s just 1 problem to tackle then … how to set it up?!
Let our manual be your guide in Apple’s sea of configuration.

Get the full manual here