5 Things to Consider Before Launching Your Fi
If you’re entering the lucrative world of FinTech mo...
There Are Professional Sand Casting Papers Published On This Site
TestFlight has suddenly entered the top 10 of the total App Store (free) list, and since then, it has dominated the top 1 of the app category tools (free) for 9 consecutive days. in addition, the total estimated number of downloads of TestFlight for iOS has reached 185w+ in recent weeks, and the highest number of downloads in a single day is 33w.
Table of Content
In fact, TestFlight is not an unfamiliar product for iOS developers; at the WWDC developer conference in 2014, Cory officially proposed that the App Store would fully support TestFlight, and TestFlight has become a must-use tool for iOS developers to test apps since then. TestFlight has become a must-have tool for iOS developers since then, and was officially launched on the App Store in 2014, with an exclusive module in the backend of iTC.
In recent years, Apple has been improving and updating the functions of TestFlight, and the benefits it brings to developers are gradually coming to the fore.
When a new product or a new feature is launched, developers need to conduct a lot of research to determine whether the new feature can effectively reach the target group and how the target group reacts to the new feature. The Beta App launched in TestFlight can directly collect users’ personal information, usage information, crash logs and other information to help developers improve and make up for the shortcomings of the product more efficiently.
Using TestFlight to conduct internal testing for the App that will be on the App Store can actually play a role in the pre-publicity of the App. Although the internal test quota is limited, but “first to try”, “the first batch of internal test users” and other titles are also can also be users have a sense of satisfaction, and can even prompt users to spontaneously promote. This is somewhat similar to the advance reservation of some large handheld games for internal testing.
According to the monitoring of Seven Wheat data, the number of apps shelved in App Store China in recent January is up to 8.3w+. In recent years, national regulation and Apple’s policies have become stricter, so when a product cannot be put on the App Store as scheduled for some reason, developers may use TestFlight to launch an internal test version of the product, inviting no more than 10,000 users for internal testing, and the time limit can be as long as 90 days, so that the product can get a group of stable users before it is officially put on the App Store.
Before setting up TestFlight in iTC backend, you should first understand what kind of products are suitable for setting up this function. Firstly, if you want to launch new products or new features, you can understand the bug and product experience problems; secondly, if the App cannot be listed on App Store normally for some reasons, you can use TestFlight to distribute.
In the setting of inviting internal testers, developers can invite internal testers and external testers to test the App, where internal testers refer to App Store Connect users with different functions in the developer team, up to 25 people, and each member can test on a maximum of 30 devices. External testers are people outside of the team and can invite up to 10,000 people.
1. Open iTC backend, select the app you want to test in “My App”, and select TestFlight in the toolbar.
2、Click “Test information” in the bottom left corner, select the main language, enter relevant test information, Beta App review information and license agreement in this interface. Developers can submit builds that invite external testers only if they submit complete test information.
b. Beta App Review Information, including “Contact Information” (including last name, first name, phone number, and email), “Login Information” (including username and password), and “Review Comments “. The “Review Notes” can be filled with additional information about the App that may help speed up the review, but cannot have demo account details and cannot exceed 4,000 characters.
Note: The information entered for the Beta App can be different from the App information that developers upload to the App Store later.
3. Upload a build version. Only one build per release can be reviewed at a time, and only after that build is approved can the developer continue to submit other builds. Also, only the first build of each version needs to be reviewed, and additional builds submitted afterwards may not need to be fully reviewed. When a build is approved, users with “admin” functions will receive an approval email. The opposite will be shown as “rejected”. And the validity of the approved build is 90 days.
4. After clicking “Testers and Groups”, select “Add External Testers” or “Create New Group”, developers can name it according to their needs.
Note: Developers can choose to create only one group of testers and add each build they want users to test. You can also choose to create multiple groups and add different builds for each group.
5. Add the builds to the group. After selecting the group to which you want to add a build, click the “Add” button and select the platform and version according to your needs in the pop-up menu. However, only one build can be added at a time.
6. When selecting “testers” for the group you want to test, developers can invite testers via public link, email or both.
a. Invite using a public link. Click “Enable public link” and confirm in the dialog box. At the same time, set the number of beta testers using this public link in the “Number of beta testers”, which ranges from 1 to 10,000. After that, developers can share the test link in various channels and wait for users to test it.
b.Invite using the tester’s email address. Click on the “Add” button next to “Testers” and choose the developer’s desired option between adding new testers using email addresses, adding existing testers that you have previously added, or importing testers from a CSV file. Testers who are then targeted for invitation will receive an invitation email and, if accepted, will be able to start testing via the link.
Note: After testers accept the invitation, they will be directed to download TestFlight in the App Store and experience the accepted internal test version in this App.
7. Check the information related to testers. Under “Testers and Groups”, click the group you want to view. The “Status” column allows you to view the status of the beta testers. Users invited by email will be shown with their names and email addresses, while users invited by public link will be shown as anonymous. You can also view the number of crashes for each build version and the number of times it runs in the foreground for at least two seconds, while the displayed status can be divided into invited, accepted, and installed.
8. Collect tester feedback. Testers using iOS13 can send feedback via TestFlight 2.3 for iOS or later, or directly from the Beta App via screenshot. Developers can view this tester feedback in the “Feedback” section of App Store Connect. For testers using devices with earlier versions of iOS, feedback will be sent to the email address provided by the developer in the “Test Information” section. The shared information is shown below.
TestFlight is an official Apple tool that helps developers understand their product bugs more comprehensively and provide effective data to improve their products when new products and features are launched; moreover, it can effectively improve product exposure and user cultivation, so developers can use TestFlight in conjunction with their own products to help promote their products.