Apple developers should all feel that Apple’s official review of the App Store is getting stricter and stricter. Many app developers can only choose iOS enterprise signature or TF signature. Through these two methods, they can be implemented without going through the App Store. Distribution, which is more friendly to developers who need to test and distribute. These two signature methods have helped many developers who cannot put their APPs on the shelves to fulfill their dreams, and they have been continuously updated, which has also brought benefits to users. Good experience, the effect is exactly the same as the App on the App Store.
So, how does the iOS signature help the APP to complete the internal test distribution?
The ios enterprise signature is also called the IPA enterprise signature. We can simply understand it as an Apple developer account with a particularly high authority. Installing on mobile phones is the best choice for Apple developers to conduct internal testing. More importantly, there is no limit to the number of installations, and it is the most ideal way for developers to sign.
TF signature is also called TestFlight, which is one of the most stable signature methods at present. It is a distribution mode officially recognized by Apple. Many users use TestFlight redemption codes to redeem corresponding applications, such as utility tools, social software beta versions, etc. , Many developers use testflight to exchange for internal testing. At the same time, testflight can also download some apps that cannot be downloaded in the app store. Now many of those apps use links to directly jump to testflight for automatic exchange and download. Only one link is enough, which is much more convenient than going to redeem.
In fact, the iOS signature can be selected according to the developer's own needs. Generally speaking, those with higher stability requirements will choose more super signatures. If there is a requirement for the fee, choose the enterprise signature if the fee is not high, but it will inevitably be dropped. Obtaining signatures is only the first step, and the second step is to distribute. Let's take the Dandelion internal test distribution platform as an example to introduce the detailed distribution process:
First, log in to Dandelion, click "Publish Application" to enter the release page.
Second, drag and drop the App installation package (ipa file or apk file) to the "Upload Now" area to directly upload the app file.
Third, click "My Apps" - "Add Blank App" (use it if there is no installation package for the time being)
Fourth, after the upload is complete, please fill in the application name, package name, app type, application introduction, application icon and other information as required. After completing the filling, click the "Add Application" button to complete the addition of the application.
It should be noted that according to the requirements of national laws and regulations, the distribution of App internal testing must be reviewed. After 1-10 minutes, the review is completed, and the compliant App can be distributed through QR codes or links.
In addition, the Apple App needs to be signed by the enterprise first, and Dandelion also supports uploading applications through Mac version and Windows version clients, as well as API.
I have been using Dandelion for four or five years, and it has been very stable. If there is a better platform, please leave a message and let me know, thank you