Game Developer Integration
This document is for game development teams that want to integrate games into the MiniGame ecosystem. It helps developers choose the appropriate integration documents by engine, platform, and advanced capability.
1. Integration Goals
MiniGame provides integration, distribution, operation, and monetization capabilities for HTML5, cross-platform, and lightweight mini games. After integration, developers can submit games to the MiniGame platform and receive channel distribution, platform publishing recommendations, ad monetization, or in-app purchase monetization support based on game type, target market, and publishing strategy.
The platform focuses on:
Supporting mainstream game engines such as Cocos Creator, Laya, and Unity.
Supporting publishing adaptations for international platforms or social channels such as Facebook, TikTok, Telegram, Zalo, and Line.
Providing technical, operational, and distribution support for premium games to reduce multi-platform launch costs.
Providing developer console, data overview, ad revenue, in-app purchase revenue, and other business operation capabilities.
2. Documentation
| Category | Document | Use Case |
|---|---|---|
| Engine Integration | Game Engine Integration Guide | Overview before choosing the integration path for Cocos Creator, Laya, Unity, and other engines |
| Engine Integration | Cocos Creator Plugin SDK Integration Guide | Cocos Creator projects integrating through the plugin SDK |
| Engine Integration | Laya Integration Guide | Laya projects integrating MiniGame capabilities |
| Engine Integration | Unity Integration Guide | Unity project integration, build, and platform adaptation |
| Advanced Capabilities | Advanced Platform and Feature Guide | Entry point for premium game publishing, platform adaptation, and server-side in-app purchase validation |
| Advanced Capabilities | Meta Instant Games Integration Guide | Adaptation to Meta Instant Games capabilities and review requirements |
| Advanced Capabilities | TikTok Mini Game Integration | Adaptation to TikTok mini game platform capabilities and operation requirements |
| Advanced Capabilities | Game Payment Backend API Guide | Server-side order validation, delivery confirmation, and risk reconciliation for in-app purchase games |
| FAQ | Game FAQ | Common questions about development, debugging, review, and launch |
3. Recommended Integration Flow
3.1 Registration and Project Creation
Developers need to register a developer account first and create a game project in the MiniGame backend. During project creation, prepare the game name, icon, screen orientation, language, target countries or regions, privacy compliance information, and monetization method.
3.2 Choose an Engine Integration Method
Choose the corresponding integration document based on the engine used by the game project. MiniGame provides a unified capability model and engine-specific adaptations to reduce repeated work around lifecycle, platform APIs, build artifacts, and debugging methods.
We recommend reading Game Engine Integration Guide first to confirm capability boundaries before moving to the engine-specific documents.
3.3 Integrate the SDK and Complete Debugging
During integration, complete SDK initialization, game lifecycle wiring, platform capability calls, error handling, and required data reporting. If the game uses ads, sharing, leaderboard, account, payment, or other capabilities, complete additional debugging according to the relevant platform or advanced capability documents.
3.4 Submit for Review and Launch
After debugging, developers need to submit the game package, assets, and required configuration. The platform reviews technical quality, content compliance, loading experience, platform adaptation, and operation requirements. After approval, the game enters distribution and revenue settlement.
4. Launch Checklist
The game can start, load, and recover stably on target devices and browsers.
SDK initialization parameters, environment configuration, and callback handling meet the current integration document requirements.
Screen orientation, resolution, audio, touch, back behavior, and error retry paths are covered.
If platform publishing is integrated, platform login, sharing, incentives, privacy, and review asset requirements are satisfied.
If in-app purchases are integrated, server-side order validation, idempotent delivery, order repair, and reconciliation are complete.
Operation assets, game description, privacy policy, and required compliance information are ready.
