RADAR · PARTICIPATION & DELIVERY
Can a browser game enter a WeChat mini-program competition?
A browser demo proves that a web version exists. It does not establish that the project is already an eligible mini program. This source-based case study offers a decision path for creators with an existing web project. Sources were consulted on October 9, 2026; we did not register an entry.
Identify the deliverable before renaming the project
The activity description requires a WeChat mini-program implementation, excludes mini games and requires official publication through the WeChat public platform during the submission phase, July 17–October 17. Teams may have up to three people; solo participation is also described.
A demo URL, repository or video alone does not establish compliance with that deliverable. Adding a sharing button or calling a game a tool leaves the underlying product and publishing requirements unresolved.
Choose between improving the game and building a different product
Keep the game as a browser project if the game loop is its purpose. Look for opportunities that explicitly accept browser games or interactive work, and spend your effort on controls, loading, levels and reliability.
A separate tool could address a real creator need such as asset organization, production scheduling or parameter records. It needs a useful workflow of its own rather than a tool-shaped wrapper around a game. Ask the organizer about eligibility when the product boundary is unclear.
Treat publication as a separate milestone
Plan distinct steps for the user need, core workflow, platform adaptation, release materials, publication and competition submission. Code completion, a published version and a submitted entry are different states.
Our suggested preflight is to complete one core operation as a new user, exercise invalid input, revisit the project after leaving and compare its actual behavior with its description. This is a development checklist, not an official scoring rubric or a promise about review duration.
Use the deadline for the relevant phase
An activity page can show an overall event period as well as a submission period. Locate the date explicitly attached to the deliverable instead of treating the event end date as the submission cutoff. Do not infer 23:59 when no exact time is stated.
Record the rule URL, phase and time-zone note in your preparation plan. Reserve your own publication and upload buffer. If your remaining time only supports a demo, revise the scope rather than marking an unpublished project as complete.
Sources consulted
Source facts and our planning advice are distinguished above. Current official rules govern any actual entry.
Open the participation planner to record your own checks →