Developer Response in Android Developer Verification Program Discussions

The Developer Verification Program, which Google offers to ensure application security in the Android ecosystem, led discussions in the developer community. Although the program expects to verify the developer IDs, important concerns about the shape of the application and the steps required have come to the agenda.

Discussions on social networks highlight the following points:

• Bürocratic load: The desired documents and controls in the process of authentication have become time-consuming and cost-effective for developer teams.
• Access restrictions: forced new developer accounts to get approval, especially for independent software developers.
• Instant deficiency: The program reacts to the absence of clear information on evaluation criteria and causes of rejecting. -Equality in practice: It is easier than small teams to adapt to the process of large companies.

Although the developer community understands the security objectives of Google, the existing system design reduces the usability. Discussions on Hacker News platform have been supported with hundreds of comments showing similar concerns. This reveals the need to review Google’s program design. Verification systems that do not provide balance are alerts that they can weaken ecosystem diversity in the long term.