Proposal: The retail-to-dev-kit model for specific commercial HarmonyOS Next developers as an option
Game changing model option to addressing past-issues around propertiary Android EMUI bootloading issues from FOSS Android developers/users in future global HarmonyOS Next updates
The idea of retail consumer devices being turned into development kits is a powerful concept that has been successfully implemented by companies like Microsoft with the Xbox One. If we learn and adopt a similar path for Huawei devices (e.g., smartphones, tablets, IoT devices), it could significantly boost the developer ecosystem around HarmonyOS, OpenHarmony, and Oniro. Here's how this could work and what it would mean:
What Microsoft Did with Xbox One
Retail-to-Dev Kit Conversion: Microsoft enabled any retail Xbox One console to function as a development kit, allowing developers to create and test games directly on consumer hardware.
Developer Mode: A "Developer Mode" was introduced, which could be activated on retail devices, unlocking tools for development and testing.
Access to SDKs: Developers gained access to the Xbox SDK, documentation, and support, enabling them to build and publish games for the platform.
How Huawei Could Implement a Similar System
Expanding concept on the Developer Mode via Settings in HarmonyOS Next for future updates
Developer Account Requirement: To enable custom OpenHarmony and Oniro ROM support, users would need to sign in with a verified developer account, ensuring accountability and security.
Retail-to-Dev Kit Conversion
Unlocked Bootloader (Optional): For advanced developers, Huawei could allow bootloader unlocking via Developer Mode on HarmonyOS Next/5.x.x+ versions, enabling custom OS installations (e.g., OpenHarmony, Oniro based distros).
Driver Availability: The access to proprietary drivers and kernel modules, ensuring full hardware functionality for custom OS builds. Open sourcing HongMeng kernel as an additional kernel for standard to light systems on OpenHarmony base and Oniro as an option for custom developers and vendors with Huawei collaboration, could be the key to that bridge while coexisting with available Linux Kernel, LiteOS and other kernels like UniProton.
2. Developer Tools and Resources
HarmonyOS SDK: Developers would already gain access to the HarmonyOS SDK, including APIs, libraries, and tools for building apps and services.
Oniro/OpenHarmony Support: It could extend support to OpenHarmony and Oniro, providing SDKs and documentation for these OSes as well.
Testing and Debugging Tools: Built-in tools for testing, debugging, and profiling apps on retail devices.
3. Publishing and Distribution
AppGallery Integration: Developers have the ability and choice to publish via AppGallery Connect and/or Eclipse Oniro Developer Portal with their developer account their apps and custom OS builds to Huawei's AppGallery and other app distribution stores on Oniro e.g. Oniro App Store and on OpenHarmony, reaching a global audience.
Open-Source Repositories: Already accessible open-source repositories for OpenHarmony and Oniro, encouraging collaboration and community contributions via Gitee and GitHub.
4. Benefits of This Approach
Ecosystem Growth: By turning retail devices into dev kits, it would attract more developers to its platform, expanding the HarmonyOS and OpenHarmony ecosystems.
Cost Efficiency: Reducing the only option of separate dev kits reduces the costs for some developers as an option.
Market Differentiation: It could position itself as a developer-friendly brand, competing with Apple and Google in the developer space.
For Developers
Lower Barrier to Entry: Developers could start building for HarmonyOS/OpenHarmony without needing specialized hardware.
Real-World Testing: Testing on retail devices ensures apps and OS builds perform well in real-world conditions.
Monetization Opportunities: Developers could monetize their apps and custom OS builds through Huawei's AppGallery or other channels.
For Users
Customization: Users could install custom OS builds (e.g., OpenHarmony, Oniro) or experimental apps, tailoring their devices to their needs.
Access to Innovation: A thriving developer ecosystem would lead to innovative apps and services for Huawei devices.
5. Challenges and Considerations
Security Risks: Enabling Developer Mode and bootloader unlocking could expose devices to malware or unauthorized modifications. Primary vendor would need robust safeguards (e.g., verified developer accounts, secure boot).
Fragmentation: Allowing custom OS builds could lead to fragmentation, making it harder for primary vendor to maintain a cohesive ecosystem.
Support Burden: It would need to provide ongoing support for developers, which could strain resources.
Regulatory Compliance: Some regions may have strict regulations around device modifications, requiring primary vendor to navigate legal complexities.
6. Potential Implementation Steps - some already implemented
Expanding Developer Mode: Expanding the Developer Mode toggle in HarmonyOS Next settings, accessible with a verified developer account for unlocking bootloading.
Already Providing SDKs and Tools: Release HarmonyOS, OpenHarmony, and Oniro SDKs with comprehensive documentation.
Enable Bootloader Unlocking: Allow bootloader unlocking for advanced developers, with clear warnings about risks hidden via Developer Settings.
Already Hosting Developer Resources: AppGallery Connect developer portal with forums, bug tracking, and collaboration tools.
Already Ensures Security: Implemented secure boot on HarmonyOS Next, verified developer accounts, and regular security updates to protect devices.
Resolving the 5. challenges and considerations associated with turning retail Huawei devices into development kits (as outlined in the previous response) requires a combination of technical solutions, policy measures, and community engagement.
Here’s a detailed breakdown of how primary vendor could address these challenges:
Security Risks
Problem: Enabling Developer Mode and bootloader unlocking could expose devices to malware, unauthorized modifications, or security vulnerabilities.
Solutions:
Secure Boot with Developer Keys:
Implement a secure boot process that allows only signed OS builds (using developer-generated keys) to boot on the device of HongMeng Kernel base, supporting U-boot bootloader and Eclipse Oniro’s Libhybris and musl implementation on OpenHarmony Linux kernel standard subsystem on the userland that also contains POSIX compatible musl-libc, LLVM modules with HiSilicon vendor support that communicates with properitary HongMeng kernel reused Linux ABI & AOSP driver modules for Huawei legacy AOSP-based factory mobile devices, former Windows-powered Intel PC devices and future OpenHarmony-based devices.
Maintain a whitelist of verified developer keys to prevent malicious software from running.
Sandboxed Developer Mode:
Restrict Developer Mode to a sandboxed environment unlocking bootloader phase in the settings, isolating it from the main system to prevent unauthorized access to sensitive data or hardware.
Regular Security Audits:
Conduct regular security audits of developer tools and SDKs to identify and patch vulnerabilities.
User Warnings and Consent:
Display clear warnings about the risks of enabling Developer Mode with unlocking the bootloader, requiring explicit user consent.
Remote Lock/Unlock:
Allow primary vendor to remotely lock or unlock devices in case of security breaches or misuse.
7. Fragmentation
Problem: Allowing custom OS builds and modifications could lead to fragmentation, making it harder for primary vendor to maintain a cohesive ecosystem.
Solutions:
Standardized APIs and Compatibility Layers:
OpenHarmony and Oniro base provides, including Huawei vendor HarmonyOS Next/5.0+ itself standardized APIs and compatibility layers to ensure apps and services work seamlessly across different OS builds.
Certification Program:
OpenAtom OpenHarmony and Eclipse Oniro has a certification program for custom OS builds, ensuring they meet OpenHarmony base compatibility and security standards before being distributed with Huawei complying the standard certification for it’s own adapted OpenHarmony-based HarmonyOS Next with it’s HongMeng Kernel base.
Modular OS Design:
Design HarmonyOS and OpenHarmony with a modular architecture, allowing developers to customize specific components without breaking core functionality.
Community Guidelines:
Publishing clear guidelines for developers to follow when creating custom OS builds, minimizing deviations from the standard ecosystem.
8. Support Burden
Problem: Providing ongoing support for developers could strain primary vendor resources, especially with a growing developer community.
Solutions:
Community-Driven Support:
Building a community-driven support system with Volla where experienced developers help newcomers, reducing the burden on Huawei’s internal teams.
Tiered Support Model:
Offering tiered support levels, with basic support (e.g., forums, documentation) available to all developers and premium support (e.g., direct assistance) for enterprise or paid developers.
Comprehensive Documentation:
Invest in high-quality, up-to-date documentation, tutorials, and sample projects to help developers troubleshoot issues independently.
Automated Tools:
Develop automated tools for testing, debugging, and profiling apps, reducing the need for manual support.
9. Regulatory Compliance
Problem: Some regions have strict regulations around device modifications, requiring primary vendor to navigate legal complexities.
Solutions:
Region-Specific Policies:
Eclipse Oniro region-specific policies for Developer Mode and bootloader unlocking, ensuring compliance with local laws (e.g., EU GDPR, cybersecurity regulations, CRA - Cyber Resilience Act) which is embedded into OpenHarmony base itself.
Transparency and Accountability:
Maintain transparency about how developer tools and custom OS builds are used, and ensure accountability through verified developer accounts.
Partnerships with Regulators:
Work closely with regulators to ensure Huawei’s developer ecosystem aligns with legal requirements and industry standards.
User Consent and Data Protection:
Ensuring that enabling Developer Mode with unlocking the bootloader setting does not compromise user data protection or privacy.
10. Additional Considerations
Developer Onboarding:
Developer Portal:
AppGallery Connect already has a centralized developer portal with access to SDKs, tools, documentation, and community forums. Eclipse Oniro side could so something similar with a dedicated unified open developer portal for Oniro App Store side, including AppGallery itself and other app distributions for both Oniro and OpenHarmony-based distros, including game companies like GoG and Valve Steam collab.
Incentives for Developers:
Offering incentives such as grants, competitions, or revenue-sharing programs to attract developers to the platform which has been done from HMS ecosystem side in the past and in China with HarmonyOS Next.
Hardware Compatibility:
Driver Availability:
Providing open-source or easily accessible proprietary drivers for key hardware components (e.g., GPU, cellular modems) to ensure full functionality for custom OS builds.
Already accessible open source U-boot repo access with HiSilicon vendor is a first clear step into this direction on Gitee and GitHub mirrors provided by both OpenAtom and Eclipse Foundation.
Hardware Abstraction Layer (HAL):
An already robust developed HAL to abstract hardware differences, making it easier for developers to create OS builds that work across multiple devices on OpenHarmony and Oniro ecosystem.
Already Long-Term Maintenance establishment:
Open-Source Governance:
OpenAtom and Eclipse Foundation collaboration with a governance model on OpenHarmony and Oniro, that ensure long-term maintenance and updates for the open-source ecosystem.
Backward Compatibility:
The minimum developer baseline already established within OpenAtom, Eclipse Foundation and Huawei, where there is backward compatibility for apps and OS builds, minimizing disruptions for users and developers.
11. Conclusion to these solutions
By implementing these solutions, it can effectively address the challenges of turning retail devices into development kits while fostering a thriving developer ecosystem. Key takeaways:
Security: Use secure boot, sandboxing, and regular audits to mitigate risks.
Fragmentation: Standardize APIs, introduce certification programs, and provide modular OS designs.
Support Burden: Leverage community-driven support, tiered models, and automated tools.
Regulatory Compliance: Adopt region-specific policies, ensure transparency, and partner with regulators.
This approach would enable Huawei to balance developer freedom with security and stability over it’s own commercial properitary HarmonyOS Next OS platform and ecosystem with unlocked bootloader option support on top of the open source core, OpenHarmony alongside Oniro connecting to OpenHarmony, positioning itself as a leader in the open-source and developer-friendly device market.
Overall Conclusion
Adopting a retail-to-dev-kit model similar to Microsoft's Xbox One strategy would be a transformative move. By enabling retail devices to function as development kits could:
Foster a vibrant developer ecosystem around HarmonyOS, OpenHarmony, and Oniro.
Attract developers and tech enthusiasts to its platform, driving innovation and adoption.
Position itself as a leader in open-source and developer-friendly practices.
However, this approach requires careful management of security, fragmentation, and regulatory compliance to ensure long-term success from a realistic standpoint and a business standpoint. If executed well, it could revolutionize the ecosystem and solidify its position in the global tech landscape. And leave out the cars, no Developer Mode for those!