Read the original article：What are the key best practices when preparing a new wearable app version?
Question
What are the key considerations and best practices when preparing and configuring a new application version for wearable devices, including App ID, project structure, platform compatibility, application naming, local environment setup, and version management?
Short Answer
When preparing a new application for wearable devices, several critical aspects must be considered to ensure compatibility, seamless updates, and reliable testing:
- App ID Continuity Maintaining the existing App ID is recommended for new device versions to ensure continuity with previous releases. Reusing the same App ID preserves user data and preferences, facilitates seamless updates, and avoids fragmentation in app management. Creating a new App ID would disrupt update paths and complicate the user experience, so it is preferable to adapt the existing ID for any new device-specific changes.
- Project Structure and Module Inclusion Package names should remain unchanged in the new project to maintain compatibility with prior configurations. Including all relevant modules—such as entry, shared libraries, and application modules—is recommended to preserve project dependencies and shared resources, enabling accurate reproduction of observed issues. If all modules cannot be included, the application module should at minimum be part of the project to focus testing on critical functionality while minimizing project complexity.
- Platform Compatibility The new application should be created as a full HarmonyOS App to support the HML/JS/CSS architecture and interactive UI features. Using an Quick App is not recommended for this purpose, as it is designed for background modules and does not provide full UI or interactive capabilities. Creating a HarmonyOS App ensures proper packaging, deployment, and compatibility with the device hardware and software environment.
- Application Naming and String Conflicts Issues such as application names appearing without spaces or with formatting inconsistencies are often caused by reusing the same string key across multiple modules. The solution is to define module-specific string keys in configuration files. This ensures correct display of application names, proper readability, and consistent behavior across devices and modules.
- Local Environment Setup A proper local environment is essential for testing .hap files and verifying device-specific behaviors. This includes correct IDE versions, SDKs, APIs, and project configurations. Setting up the environment allows developers to build, sign, and test .hap files locally, ensuring UI behavior, animations, and interactions function correctly even without a physical device. This reduces testing delays and improves the accuracy of issue identification and resolution.
- Version Management and Build Errors Updated builds may produce errors related to app version during testing, such as “App version is too low.” These issues must be clarified and addressed to ensure that testing and deployment can proceed smoothly. Proper version management is essential for maintaining consistency across builds and preventing disruptions in the testing workflow.
Applicable Scenarios
- Developing and updating applications for wearable devices or smartwatches.
- Situations requiring continuity with previous releases while adding new device-specific functionality.
- Environments needing accurate reproduction of issues across multiple modules.
- Cases where UI and interactive elements must be fully supported on the target platform.
- Workflows requiring local environment setup for testing and verification of device-specific behaviors.
- Scenarios where version management is critical to avoid build and deployment errors.
