Describe what you need in WorkBuddy and build booking, enquiry, sign-up and membership into native pages. Once connected to Myriad Masters, the mini program shares business accounts, data and agent capability with the bound XApp.
From learning about a service to booking it, asking questions and receiving material.
Bind the mini program to a published XApp in the Operations Centre and switch on what you need. The Myriad SDK handles the runtime session and API calls; the server still checks the real account and business permissions.
The first time a user touches Myriad capability, they verify with the phone number of their existing Myriad account; afterwards the mini program's WeChat identity carries that link. The existing account system for official accounts and XApps is reused.
Reuse the bound XApp's logic tables for bookings, sign-ups, records and queries. Data follows the existing access and row permissions — other users' records are never exposed.
Connect the agent already bound to the official account, keeping role configuration, knowledge and quota. The mini program and web keep separate conversation context, which suits enquiries and business Q&A.
Show products published under the same official account and look up the current user's membership level and expiry. This is lookup only; native payment is not connected yet.
Users can only download private files they are entitled to. Assets and download domains are described in the setup wizard; the whole OSS space is never opened to the mini program.
The mini program has its own private source space with save, restore and pinned-version export. Native styling follows XAUI colours, type scale, spacing and touch sizes.
These are plannable scenarios, not ready-made templates or shipped client cases. Define fields and permissions first, then build and test on a real device.
Describe the service, collect details, save records and let users check their own sign-up; the console and XApp keep using the same business table.
Present services on native pages, answer questions with the text agent, then hand over to your existing consulting and service flow.
Check products and membership status, and download material you are entitled to. Product entitlements stay managed on the Myriad side.
Register the account and get the AppID and AppSecret from the target mini program's development settings. Already connecting an official account to Myriad does not mean you have a mini-program account.
Choose the official account and verify credentials with the wizard; enter the request and downloadFile domains the wizard shows into the WeChat console, then choose a published XApp you may manage and enable the capabilities you need.
Obtain a developer key with the right operating and development permissions and import the mini-program builder. It checks the binding against the project AppID and guides WorkBuddy to the SDK, styles and tool documentation.
Confirm the project and upload scope, then save source. If there is a conflict, pull and compare first; before publishing, pin the source version and WeChat version number and export to a new directory.
Check the AppID and domains, then test on a real device in WeChat. After upload, submit for review and release through WeChat's version process; saved or exported source does not mean the mini program is live.
| Item | XApp | Native mini programs |
|---|---|---|
| Page form | Web app in a browser | WeChat native pages, written and adapted separately |
| Business access | XApp Bridge | Myriad native SDK; binding confirmed by the actual AppID |
| Accounts and logic data | After first-time phone linking, the same Myriad business account is reused; once bound, the same XApp logic tables and permissions apply | |
| Agents | Same bound role and quota; web and mini program keep separate conversation context | |
| Visuals | XAUI web styles | XAUI native WXSS, one visual language |
| Code and release | XApp workspace and web release flow | Independent private source space; the runtime package is uploaded, reviewed and distributed by WeChat |
Binding shares business resources; it does not convert existing XApp pages into a mini program. One XApp maps to one mini program today. The mini program and the official account each have their own WeChat identity, and the platform does not require UnionID.
The builder ships with setup guidance, examples, MCP tool documentation, a pinned local runner, the native SDK and XAUI styles. For existing projects, check the AppID and the actual binding first, then keep building around your business.
Within the developer key's scope it can query projects, bindings, data structures and source versions to help you build. The AppSecret is entered by an administrator in the Operations Centre and never goes into a chat or front-end source.
It handles WeChat login, first-time phone linking and business requests. The session stays in memory; database, agent and file operations run under the capabilities you enabled and backend permissions.
Online it fetches and verifies guides, examples, tool documentation and project templates from the server; offline it uses cache or bundled content. Only changes to the local runner require reinstalling.
Installing the builder and passing the WorkBuddy marketplace review are two different states; the Developer Centre's distributed version and the open platform's actual status are authoritative. The pinned script needs Node.js 18 or later. Routine guide updates never overwrite your project or plugin files.
Also prepare your own mini-program account, get its AppID and AppSecret, then register in the Operations Centre under WeChat Mini Program, configure domains and bind the XApp. Credentials for the official account and the mini program cannot be mixed.
The first time a user touches Myriad capability, they link via a verification code to the phone number of their Myriad account. Afterwards the mini program's WeChat identity reuses that link; when the session expires they log in again, and authorisation changes are handled as prompted.
Your machine holds the development project; Myriad's private OSS holds mini-program source versions; WeChat stores and distributes the compiled runtime package after upload. Pinning a source version is not the same as uploading to WeChat.
Using the addresses the Operations Centre wizard shows, set the request and downloadFile domains in the WeChat console; private files also require the current user's authorisation. Do not use the dev tool's domain-check bypass in place of real configuration.
Today it supports accounts, logic-table records, the text agent, product and membership lookup, and authorised file download. Native payment, runtime user uploads and multimodal agents are not connected yet, so web features cannot simply be copied over.
Myriad services, SMS, agents, storage and WeChat-side verification follow each provider's current rules and your plan.See Myriad pricing; for category, filing, verification and privacy guidance, follow what the WeChat console actually requires — we do not promise automatic approval.
Decide who you serve, what you store and who can see it, then work through the wizard and builder step by step.
