Since our last blog post and big update it might have seemed that we were on an extended break, but nothing is less true. Apple and Google haven’t been sitting still, but neither have we. In the past years we have introduced several big changes to keep up with both platforms, keep reading if you want to know what we’ve been up to!
As Apple describes it two-factor authentication is “an extra layer of security for your Apple ID designed to ensure that you’re the only person who can access your account, even if someone knows your password.”
Safety always comes first, so we were on board with this change from Apple, but we also had to think of a way to make it work for our customers. Luckily we found a way to make the multiple login system work and could still keep submitting apps to the Apple App Store.
More about two-factor authentication and the AppMachine designer can be found in our very useful Help Centre.
In order to help users understand an app’s privacy practices before they download the app on any Apple platform, app owners must enter privacy details of their app within App Store Connect prior to being able to publish. With this information, users will be able to learn about some of the data types the app may collect, and whether that data is linked to them or used to track them. You’ll need to provide information about your app’s privacy practices, including the practices of third-party partners whose code you integrate into your app, in App Store Connect.
For AppMachine customers this also means that while answering these questions they should keep in mind that they are (or their client is) seen as the owner of the app, and that in that sense, AppMachine is seen as a third-party partner. This was yet another change that we had to adapt to by creating a new pro-block and researching how our customers could make this work. In this Help Centre article you can read more about how our customers have to deal with App Privacy in the App Store.
Finally, Google made changes in their publishing process, not allowing users to login on Google accounts that run on automation software. This resulted in every app having to be published manually, which we couldn’t do without the help of our customers. We found a fix for this by generating an apk file for every app that the customer can download and then submit themselves. A bonus with this solution is that the apk file can be submitted to every other store that requires an apk file.
As you can see, we really have been working on keeping our platform up to date and working with all the changes Apple and Google throw at us. And we’ll continue to do so in the future!