When you build apps for your customers, it is possible that they don’t yet have their own developer account on the App store. Even though it has been possible to publish those apps on your own account, here are some good reasons not to.
When you publish an app on behalf of someone else, you are also taking responsibility for its content. This means that if for some reason the app should run into compliancy issues at some point, your developer account will be held responsible, and could be at risk.
As the App stores evolve, so do their rules. In order to regulate the inflow of new apps on the App store, and moderate the existing ones, Apple and Google are continuously making efforts to keep the apps relevant and up to date. For example, apps that are not updated are eventually (automatically) removed from the stores.
One of the most recent developments have been that developers who are repeatedly publishing apps that look similar in functionality, are being asked to consolidate these apps into one. For example, if you own a Retail store chain, and you are publishing 1 app for each individual store, Apple could ask you to build 1 app representing all the stores.
What does this mean for me?
Being present in the App store is a great way of building your brand, and as these high level marketing tools evolve, it also requires a continuous effort from it’s users in order to stay compliant with the T&C of these platforms you are using to publish your apps. We advise you to always let your customer use their own developer account(s), when it’s time to publish. AppMachine let’s you choose for each individual app, which account you would like to use.
Questions or concerns? Feel free to ask our support team at email@example.com