China's Software Green Alliance said today that the "Software Green Alliance Application Experience Standard 3.0" (green label 3.0) will be effective in May, when the green application testing certification standard will switch from green label 2.0 to green label 3.0.
Green label 3.0 is more stringent in terms of security privacy, permission management, performance, power consumption, stability.
After Huawei AppGallery implements the green label 3.0 standard, applications that originally passed the green label 2.0 test are likely to lose their green logo because they cannot pass the green label 3.0 test.
The Software Green Alliance conducted a mapping test on the mainstream applications of TOP1000 China to help the majority of applications to understand the green application compliance in advance, the test data shows that the green label 3.0 compliance rate is low, only 34%, and applications need to improve according to green label 3.0 standards.
Among the five indicators of green application testing, stability, performance and power consumption are more than 90%, compatibility is 70%, while safety standards testing the lowest rate of compliance, only 56%.
Failure to test for safety and compatibility standards is the main reason for the low compliance rate for applying GREEN LABEL testing.
The main reasons for failure of security standards are over-application of high-risk permissions and privacy breaches, and four of the five tests that affect the rate of security standards compliance, shown in the chart below, are new additions to green label 3.0.
The main reasons for the failure of the compatibility standard are the failure of the new green label 3.0 malicious behavior detection, non-SDK calls, installation behavior detection, and low TargetSDK version satisfaction.
Optimization recommendations
Malicious behavior optimization recommendations, non-SDK interface call optimization recommendations, installation behavior detection optimization recommendations, please refer to the green label 3.0 compliance guide.
Target SDK optimization recommendations: ensure TARGETSDKVERSION>=26, recommend direct upgrade to 28 or more.
(b) Over-requesting of high-risk privileges, with recommendations for optimizing: withdrawal of non-mandatory privileges and scenario use descriptions of the privileges requested, and timely removal of privileges requested but not used.
Privacy Violation Optimization Proposal: Prohibit frequent requests to users for certain permissions that users refuse, harass users, and actively remind users to read the privacy policy when they first open the app.
