Advanced Platform and Feature Guide
This parent page covers platform publishing, advanced operation capabilities, and server-side in-app purchase capabilities. After completing the basic engine integration, premium games or projects with monetization needs can use this page as the entry point for advanced integration documents.
1. Scope
For games with high quality, stable retention, or clear monetization potential, MiniGame may recommend platform publishing based on target market, content type, and platform strategy. After entering platform publishing, games usually need additional adaptations for platform operation capabilities, review rules, data requirements, and monetization flows.
Advanced capabilities mainly cover:
Platform publishing adaptations such as Meta Instant Games and TikTok mini games.
Platform login, sharing, invitations, leaderboards, campaigns, assets, and review requirements.
Server-side order validation, delivery confirmation, order repair, reconciliation, and risk control for in-app purchase games.
Configuration isolation, capability fallback, and data attribution for multi-platform publishing.
2. Documentation
| Category | Document | Use Case |
|---|---|---|
| Platform Publishing | Meta Instant Games Integration Guide | Platform capabilities, review, and operation adaptation for Meta Instant Games |
| Platform Publishing | TikTok Mini Game Integration | Capability integration, review submission, and operation adaptation for TikTok mini games |
| Payment Capability | Game Payment Backend API Guide | Server-side validation, delivery, order repair, reconciliation, and error handling for in-app purchase orders |
| Engine Basics | Game Engine Integration Guide | Complete engine integration first if the basic SDK integration is not yet done |
3. Platform Publishing Adaptation
Platform publishing is not just package upload. Platforms usually impose requirements on user identity, content compliance, sharing flows, incentive mechanisms, privacy compliance, asset specifications, loading performance, and operation campaign capabilities.
Recommended sequence:
Complete the basic engine SDK integration first and make sure the game runs stably in the standard MiniGame environment.
Choose the Meta Instant Games or TikTok mini game integration document based on the target platform.
Encapsulate platform capabilities in a dedicated adapter layer so core gameplay does not directly depend on a specific platform.
Complete assets, privacy information, content rating, payment declarations, and operation configuration according to platform review rules.
Verify login, sharing, payment, return flows, error recovery, and data reporting in the test environment.
4. In-App Purchases and Server-Side Validation
If a game includes in-app purchases, client-side payment completion does not mean business delivery is complete. The server must validate against platform orders and ensure the delivery flow is idempotent, traceable, and compensable.
For in-app purchase games, focus on:
Server-side order validation must rely on trusted platform callbacks or query APIs.
Delivery APIs must be idempotent to avoid duplicate delivery from repeated notifications.
Client-side payment status should handle processing, success, failure, cancellation, and timeout.
Order ID, user identifier, product identifier, amount, currency, platform, environment, and callback logs should be retained.
Reconciliation, order repair, and error handling should be verified before production launch.
For implementation details, see Game Payment Backend API Guide.
5. Multi-Platform Maintenance Suggestions
Drive differences with platform configuration instead of duplicating business logic.
Build unified interfaces for platform capabilities such as login, sharing, payment, ads, and data reporting.
Centralize platform-specific parameters, review assets, environment URLs, and feature switches.
Provide explicit fallbacks for unsupported capabilities to avoid uncontrolled branches across platforms in the same version.
Establish platform-level data observation dimensions to diagnose platform differences and operation results.
6. Launch Checklist
The target platform and required capabilities are confirmed.
Platform login, sharing, return flows, lifecycle, and error recovery are verified.
If in-app purchases are involved, server-side validation, idempotent delivery, order repair, and reconciliation are verified.
Review assets, privacy policy, content description, and test accounts required by the platform are ready.
Platform configuration and production environment parameters cannot be mixed.
Post-launch data monitoring and issue diagnosis paths are in place.
