Step by step,
build your own WeChat mini program.

Prepare the accounts and their separate credentials.

1. 在 WeChat Official Accounts PlatformRegister your own mini program, or sign in if you already have one; from the target mini program's Development management / Development settings page, obtain the AppID and AppSecret
2. Keep the official account already bound to Myriad. In the Myriad Developer Centre → Developer keyscreate or select a key with the relevant operating and XApp development permissions, then download the TXT for connecting the builder.
3. The mini-program AppSecret is entered only by an administrator in the Myriad Operations Centre; the developer key is for WorkBuddy tools. Neither may go into mini-program front-end code, logs, SMS codes or runtime tokens.

An official account and a mini program are two WeChat applications. A bound official account does not mean you have a mini-program account; a temporary WorkBuddy trial cannot replace the credentials this setup requires. WeChat's current pages, entity requirements and qualifications follow the official prompts.

Register your mini program first.

1. Open In the Operations Centre's WeChat Mini Program list, choose the official account already connected to Myriad and click Add existing mini program.
2. Under Register credentials, fill in the name, AppID and AppSecret, then click Verify and register. Make sure the credentials belong to the mini program you are building.
3. You can register first and configure domains and app binding afterwards; registration alone does not enable runtime capability.

Allow exactly the domains you actually use.

1. Open Allow domains in the Myriad wizard, then find the server domain settings in the WeChat mini-program console.
2. Add the API address the wizard shows to request legal domains; in production this is usually https://x.wanxiangdashi.com
3. If you use file, image or material downloads, add the actual download domain the wizard shows to downloadFile. Do not guess OSS domains, and do not allow only the website www domain.
4. If a WeChat interface requires an IP allow-list, enter the server egress IP the wizard shows. Save, then verify with the skip-domain-check debug option turned off.

Allowing a domain only permits network requests; it grants no extra access to data or private files. Runtime still checks the current account, app and specific resource permissions.

Choose which XApp's business to share.

1. Choose a published XApp under the same official account, or in the same tenant and not yet attached, that you are entitled to managepublished XApp. If none fits, prepare and publish one with the XApp guidefirst, then return to the wizard.
2. Enable logic data, text agent, products and membership, private files and other capabilities as needed, then save.
3. Confirm the AppID, official account, bound XApp and enabled state in the list are correct. Today one XApp maps to one mini program.

Binding shares business accounts and resources; it does not copy XApp pages. The mini program needs its own native front end; existing official-account login keeps working and not every account needs a UnionID.

Let the builder check the project before you write pages.

1. 在 Developer Centre → WeChat Mini ProgramGet the Myriad Masters mini-program builder ZIP and import it in WorkBuddy under Expert · Skills · Connectors → Skills → Add skill → Upload skill; the exact buttons follow the current client.
2. Drag your developer key TXT into WorkBuddy and say "connect this Myriad developer key, then continue with my mini-program requirement". An existing valid Myriad connection can be reused. The pinned script needs Node.js 18 or later and requires no separate Python or npm dependencies.
3. State that this isNative mini programs, and provide the target AppID or an existing project. The builder reads project.config.jsonand queries the real official account, XApp, capabilities and source versions; when several projects exist, say which one first.
4. Have the host read the latest SDK and XAUI native style templates, and connect WeChat login, first-time phone linking and the enabled business capabilities; never put the developer key or AppSecret into a page.

Use the Myriad Masters mini-program builder to build a booking mini program. First check the project AppID I choose, the actual bound XApp, the enabled capabilities and logic-table permissions. If anything is missing, tell me exactly where to fix it — do not claim the connection succeeded. Pages: service introduction, booking form and my bookings; use the Myriad native SDK and XAUI styles. Log in when the user actively uses a business feature, linking on first use through a verification code to the phone number of their Myriad account. Business data uses the bound XApp's logic tables; local storage must not replace the database. Give me the page, field and permission plan first, and only modify the project or save cloud source after I confirm.

MCP and the developer key serve the build phase; the mini-program SDK uses the business runtime session. Guides and tool documentation update independently from the server; before updating the project SDK, keep and check your existing changes.

Save the source, then pin the version you will release.

1. Confirm the project directory and upload scope, then save source with the builder. The snapshot goes into the mini program's own private workspace and does not overwrite the bound XApp's web code.
2. Check the returned source version, digest and byte count. On a save conflict, pull the cloud version into a new directory and compare; never overwrite someone else's changes. If the network result is unclear, check the history first.
3. When ready to release, state the source version and WeChat version number, have the builder pin it and export to a new directory. The export must match that pinned record.

Your machine holds the development project, Myriad's private OSS holds source history, and WeChat stores and distributes the compiled runtime package after upload. Saving source or pinning a version is not uploading to WeChat. Never put keys, client-private data or unrelated files into the project.

Test on a real device first, then upload, submit and release.

1. Open the export directory in a signed-in WeChat DevTools, check the AppID and version number, turn off the skip-domain-check debug option, and test pages, login, permissions, data, agents and file downloads.
2. On first use of Myriad capability, link the user by verification code to the phone number of their Myriad account. Then check the same account's data and membership entitlements, and the message shown when access is denied.
3. Once you confirm the upload, use WeChat DevTools or an authorised official CLI on your machine. If you use WorkBuddy's share panel, bind your own mini-program account through its official flow, and separately check the domains Myriad needs.
4. Complete trial, submission and release under version management in the WeChat console. Categories, filing, verification, privacy guidance and industry requirements follow the WeChat console prompts; verify separately that source is saved, pinned, uploaded, submitted and released.

Deliver against real capability, never skipping failure states.

• Check at least: first-time phone linking, later logins, empty data, insufficient permission, double taps, paging, network loss, unclear write results, and task cleanup after leaving a page.
• Today it supports accounts, logic-table records, the text agent, product and membership lookup, and authorised file download; native payment, runtime file upload and multimodal agents are not connected yet.
• Signing out only ends the local runtime session; pages must clear private data from display. It does not unbind the WeChat identity or undo writes already performed.
• Re-check the connection when business credentials or bindings change; after upgrading guides or the SDK, still test the existing project and WeChat trial build. Costs follow your Myriad plan and each provider's actual rules, including WeChat.