Before Integrating Livestreaming into a WeChat Mini Program: AppID, Categories, Domains, Channels and Permissions
Before adding POLYV livestreaming, verify the Mini Program AppID, category and player permissions, H5 domains, test channel and login routes.
A company with an existing WeChat Mini Program should verify five inputs before adding a POLYV livestream room: its own AppID and entity, service category and player permissions, web business domains, POLYV account and channel, and the identity and navigation interfaces. These inputs determine whether a WebView, native Mini Program SDK, or uni-app mp-weixin component can be integrated and approved.
Verify AppID, categories, domains, test channel and business routes before choosing WebView, native or uni-app integration.
01 / Confirm the entity and the actual use case
Record the production and test AppIDs, entity verification, service categories, launch date and review owner. List the required capabilities separately: live viewing, replay, chat, co-hosting, products and sharing. A retail promotion and a paid course have different permission and access requirements. A supplier demo Mini Program cannot establish that the company’s own AppID has the same permissions.
02 / Map permissions and domains to the chosen route
A WebView project must inventory the initial H5 URL, every redirect destination and the business domains configured in WeChat. Product navigation back into the Mini Program also needs an H5-to-Mini-Program route and, where applicable, WeChat JS-SDK setup. A native viewing page must check the “Polyv观看” plugin’s eligible categories and authorization, live-player component permission, or the video option. Co-hosting additionally requires the relevant live-pusher, camera, microphone and privacy conditions. These are separate checks.
03 / Prepare a real POLYV test channel
Create a POLYV account and test channel, then record its channel ID, live and replay states, viewing restrictions, chat and interaction settings. For uni-app, obtain the polyv-live-watch package and place it in src/wxcomponents as described in the official integration guide. Native projects should follow the corresponding SDK documentation. Keep business tokens, member identity and order logic on the company’s server.
04 / Assign owners and evidence
The product owner defines the viewing and commerce flow; the Mini Program developer checks AppID, build and plugin settings; the H5 developer owns domains and web navigation; operations configures the channel; QA prepares iOS and Android devices. The kickoff output should include permission status, a domain inventory, channel ID, test accounts and a route map. Each missing item needs an owner and due date.
05 / Reserve a small-window playback test
POLYV documents background playback for Mini Programs. A native viewing page requests the feature from its active native player; a WebView live page uses a native intermediary page. Availability depends on WeChat and OS versions, category and permissions, account settings and player state. Test the path from the live room to a product page and back on target iOS and Android devices.
06 / A kickoff checklist with owners
For every row, mark ready, awaiting approval or requiring integration, and assign an owner. An application for permission is not evidence that the target AppID already has it.
| Check | Evidence to collect | Owner |
|---|---|---|
| AppID and entity | Production/test AppIDs and verified entity | Mini Program admin |
| Category and player | Service category, plugin authorization or live-player permission, video option |
Product and Mini Program developer |
| Co-hosting | If required, live-pusher, camera, microphone and privacy setup |
Mini Program developer |
| WebView domains | Initial, redirected and product intermediary domains; JS-SDK safe domain | H5 developer |
| Channel | Test channel ID, live/replay states, access and chat settings | Livestream operations |
| Business interfaces | Login, product route, order attribution and share return | Business engineering |
| Devices | Target iOS/Android, WeChat versions and networks | QA |
Version this checklist and link it to the POC and launch regression records whenever a permission, domain or channel setting changes.
Frequently Asked Questions
Does the video route enable every viewing-room feature? No. It is a player option with its own scope; co-hosting and other capabilities require separate checks.
Does the uni-app component also cover apps and H5? This wxcomponents integration targets the WeChat Mini Program mp-weixin build. Apps and H5 use their respective POLYV solutions.
When should this checklist be reviewed again? Recheck permissions, domains and channel settings after the experience build and before final review.
Further Reading
Continue with Choosing a WeChat Mini Program Livestream Player: Plugin, live-player and video Permission Boundaries and Integrating a POLYV Viewing Room into a uni-app Mini Program: From wxcomponents to Device Testing. For the overall integration choice, see the WeChat Mini Program SDK guide. The Chinese edition covers the same task for local teams.
About POLYV
POLYV supports WebView, native SDK and uni-app WeChat component viewing routes. Use the selection guide to prepare channels, permissions, player choices and domains before implementation.