Shiply Platform Overview
Shiply is a client release solution platform launched by Tencent Device Service (TDS). Shiply provides customers with full-scenario release services including platform frameworks, hotfix, app store distribution, remote configuration switches, and remote resources. Shiply distills extensive release experience into standardized release workflows with capabilities to identify and mitigate online release risks. Platform capabilities have been validated by numerous apps with hundreds of millions of users, helping you achieve secure one-stop client releases.
I. Features and Use Cases
1.1 App Hotfix
Fix critical bugs, optimize software performance, patch security vulnerabilities, and improve app stability without deploying a new version.
1.2 In-App Upgrade
Help products implement in-app upgrade functionality, widely used for feature validation, feature experiments, data-driven decision making, and similar scenarios.
1.3 Cross-Platform Frameworks
Two proprietary high-performance cross-platform frameworks that easily achieve one codebase for four platforms: Android/iOS/Harmony/Web, with support for dynamic updates.
- Hippy: Supports React and Vue, with better rendering performance, memory usage, and package size overhead than React Native
- Kuikly: Supports Kotlin, native performance, ultra-lightweight integration (300K), and complete dynamic delivery capabilities
1.4 Flutter Dynamic Delivery
Supports partial page dynamic delivery and full app dynamic delivery for Flutter. Through proprietary VM instructions, runtime performance is far superior to traditional JS and AST approaches, approaching native performance.
1.5 Remote Resources
Remote resources decouple resources from the app, enabling hot updates for resources, significantly reducing package size and improving user download willingness. In H5 and similar scenarios, offline package caching of web static resources can achieve instant loading. The platform supports publishing almost all resource types including Zip, 7z, So, APK, and more.
1.6 Remote Configuration Switches
Without deploying a new version, remote configuration can enable or disable software features, widely used in security control, performance tuning, A/B testing, and feature customization scenarios.
II. Product Advantages and Value
- Multi-platform support: Supports iOS, Android, Harmony, Windows, Mac, Web, and visionOS
- Multi-scenario releases: Supports cross-end artifacts (including but not limited to React Native, Weex, Hippy, Flutter), app upgrades, app store distribution, configuration, switches, and resource releases
- Shifts release safety from "human assurance" to "platform assurance":
- Prevents human-factor risks during releases through standardized, automated secure release workflows.
- Achieves degradation and loss mitigation through rollback capabilities.
- Fixes production issues without releasing a new version through hotfix capabilities.
- Continuously reduces release costs: Supports differential updates for multiple delivery artifact types (saving up to 80%+); supports CDN peak shaving and off-peak scheduling with intelligent rate limiting by time period; reduces network bandwidth and improves mobile download success rates
- Multi-product, multi-task, multi-dimensional release management: Meets complex release collaboration needs for both small teams and large-scale teams.
- High stability and reliability: The team has extensive release experience, serving hundreds of millions of users.
III. Integration and Usage
As a developer, you primarily use Shiply services through the Shiply console and SDK. The complete integration and usage workflow includes the following steps:
3.1 Integration Workflow
3.2 Usage Workflow
Prepare artifacts: Prepare configuration content/material resources/installation packages/patch packages/cross-platform artifacts based on release type
Create release: Create a release task flow, associate release artifacts, and set delivery conditions and release strategies
Test and validate: Add experience allowlist users and perform small-scale effect, compatibility validation, and experience testing
Initiate approval: Request release approval from the release administrator; automatic rollout begins after approval
Gray release: Use phased automatic progressive coverage strategies to reduce release risk
Full release: After the final batch completes and metrics meet targets, fully cover the target system and complete the release cycle