Build a Mini Program with WorkBuddy: From Idea to Trial Version in 14 Days
💡 One-sentence summary: Build a WeChat Mini Program with WorkBuddy — generate from one sentence, revise in the preview, scan a QR code to publish a trial version.
Search for "build a Mini Program with AI" and you'll find either outsourcing price quotes or course schedules that say "learn Mini Program syntax first, then cloud development." This lesson takes a third path: use the managed publishing of WorkBuddy, the desktop AI workbench from Tencent—no dev environment to install, not a single line of code to write—and turn a one-sentence idea into a trial Mini Program you can open in WeChat. The trial version is valid for 14 days, just enough to verify whether "this idea is worth pursuing."
This is Lesson 3 of Route B (building Mini Programs). B1 covered what a Mini Program is, and B2 prepared your account materials—good news: the trial version doesn't even require registering an account first, so set aside the B2 materials for now and bring them out when you operate long-term. This lesson covers "build it + ship it"; the WeChat review required for official launch is covered in depth in B4.
- Not yet familiar with WorkBuddy's interface and task operations? Go through 2.4 WorkBuddy usage first
- Haven't picked a route yet? Go back to 4.0 Scenario Practice: Pick Your Route
What you'll be able to do after this lesson
- Use a one-sentence natural-language requirement to have WorkBuddy generate a native WeChat Mini Program—no dev environment to install, no touching the Mini Program project structure
- State real needs like "data saving, user login, image upload" clearly so WorkBuddy connects the cloud database, identity authentication, and file storage as needed
- Scan a QR code to publish a trial Mini Program valid for 14 days, and send the Mini Program code to up to 15 people to experience it on real devices in WeChat
- Explain clearly the differences among the three tiers—trial version, experience version, and official version—and know why a trial version can't be converted directly to an official one and how to shift gears for long-term operation
Why use WorkBuddy instead of developing from scratch yourself?
Of course you can develop a Mini Program yourself; the difference is who does the work at each step:
| Stage | Develop from scratch yourself | WorkBuddy managed path |
|---|---|---|
| Dev environment | ❌ Set up a local Mini Program dev environment | ✅ Done via desktop conversation, no local dev environment needed |
| Code | ❌ Understand the Mini Program project structure and write the code yourself | ✅ Describe your requirements and a native WeChat Mini Program is generated |
| Cloud services | ❌ Apply for and configure them yourself | ✅ Connect the cloud database, identity authentication, and file storage as needed, no manual entry of technical parameters |
| Publishing | ❌ Handle the full process yourself: registration, code upload, review submission | ✅ Managed publishing assists with code upload, trial version generation, review submission, and version release |
| Account ownership | ✅ Yours | ✅ The Mini Program account always belongs to you |
Note the last row: WorkBuddy "works on your behalf," it doesn't "hold on your behalf"—accounts, data, and subsequent operating rules are all governed by WeChat's official policies.
If you haven't installed WorkBuddy, see the WorkBuddy desktop version in 1.5b Alternative Installation Methods; if you're not familiar with the basic operations, go through 2.4 WorkBuddy usage first.
Your current predicament
- "I want to build an in-store booking Mini Program for my shop, but outsourcing has a queue, and learning to develop myself—I can't even understand the project structure"
- "I've had AI write Mini Program code, but things like cloud service configuration, uploading code, and submitting for review—a chat box can't do those for me"
- "I heard launching requires registration, verification, and filing—I want to give up before finishing even half the process"
When to use this move
When you need:
- A lightweight app that opens instantly by scanning a QR code in WeChat: great for brand showcase, in-store booking, event sign-up, internal collaboration, and lightweight tools
- To validate an idea at minimal cost—the trial version needs no account registration and no review, with real results within 14 days
- Data stored in the cloud: sign-up forms, uploaded images, reading records—still there when you reopen
And you don't want to:
- Set up a local dev environment or study the Mini Program project structure
- Go through the full registration, verification, and filing process before the idea is even validated
- Pay outsourcing money for an unknown
🎒 Preparation Before Starting
- Have read B2 Register a Mini Program Account: the trial version doesn't need an account, but long-term operation does—preparing the materials in advance costs you nothing
- Have WorkBuddy installed and able to log in by scanning a QR code with WeChat—if not installed, go back to 1.5b Alternative Installation Methods; for basic operations, see 2.4 WorkBuddy usage
- A real idea (e.g., "reading list" or "in-store booking"), plus a phone with WeChat installed
- Know the facts: WorkBuddy's free experience tier offers 500 credits per month and can host 10 apps; credits are consumed per task and expire monthly—see the rules in 2.5 Pricing Comparison
- A cup of water ☕
Follow Along with Me
After these five steps, your idea becomes a trial version that can be opened in WeChat. The examples all use the "Reading List" from the official documentation: users log in with WeChat, add books they are reading or have finished, and records are stored in the cloud—swap in your own topic and follow along.
Step 1: Describe your requirements and let WorkBuddy generate a WeChat Mini Program
Why: "Make a mini program" is just as hard for AI to handle as "make a website"; and if you don't specify "WeChat Mini Program," WorkBuddy may generate a web page for you.
Pick any one of the three ways to start:
- On the WorkBuddy home page, go to "Code Development," select "Mini Program," and start creating with a recommended scenario
- Describe your requirements directly in the chat box (example below)
- Already had WorkBuddy build a web page? Just tell it "turn it into a WeChat Mini Program"
Send your requirements in the chat box (Reading List example, from the official documentation):
Create a Reading List WeChat Mini Program. Users can log in with WeChat, add books they are currently reading and books they have finished, and reading records need to be saved to the cloud.You should see: WorkBuddy starts planning and executing tasks, and a "WeChat Mini Program" artifact card gradually appears in the conversation.
💡 Write cloud service requirements in plain language, not technical solutions
When you need to save data, log in, or upload images, just say "reading records need to be saved to the cloud" or "users can upload images"—no need to write specific technical solutions. Just state the actual needs such as long-term data storage, user login, image upload, or multi-user participation, and WorkBuddy will choose the capabilities itself.
Step 2: Preview and accept, then feed your revision requests back
Why: You must see what the AI built with your own eyes before moving on—and the preview in WorkBuddy naturally differs from the real result in WeChat (see the warning below for details). Get the styling and basic interactions right first, and things will be much easier after publishing.
Click the "WeChat Mini Program" artifact card to view the result in the preview area on the right; for anything you're not satisfied with, just say it in the conversation:
Overall it's good, but make three changes:
1. Display the book list in two groups: "Currently Reading / Finished"
2. Put the "add book" entry at the bottom, permanently visible
3. Add a guiding line to the empty state: "No books yet—tap below to add one"You should see: The preview area refreshes with the new version, and the changes only land where you pointed out. Repeat for two or three rounds until you'd be willing to send this mini program's QR code to a friend.
⚠️ Preview ≠ Real device
The preview in WorkBuddy is mainly for checking page styling and basic interactions, and may differ from the actual result when running in WeChat; capabilities like WeChat login require publishing as a trial or experience version first, then testing on a real WeChat device.
Step 3: Confirm enabling cloud services
Why: The Reading List needs to store records, so it needs a cloud database. You don't have to set anything up in this step—WorkBuddy will prompt you during generation whether to enable the corresponding cloud service; just confirm, and it fills in the technical parameters.
Just confirm enabling when prompted during generation. Use the four capabilities as needed:
| Capability | When to use it |
|---|---|
| Cloud database | Store and manage information submitted by users (book lists, sign-up forms) |
| Identity authentication | Support login via phone number, WeChat, or email, and distinguish different users' data or permissions |
| File storage | Upload and save images or attachments |
| Data analytics | View user counts and registration trends |
You should see: The task continues, and you haven't filled in any technical parameters. Later, if you want unified management, go to "Settings > Data Management > Apps" to view each app's publishing status, manage cloud services, find the mini program QR code, and return to the task to continue making changes.
Step 4: Click "Share" to create a 14-day trial version
Why: This is the finish line of this lesson. A trial version doesn't require registering a WeChat Mini Program account in advance or WeChat review—scan the code and send it to others. It's the fastest tier for validating an idea.
Follow these steps in order:
- Click the "Share" button in the top-right corner of the preview area to enter the publishing process
- In the share panel, select "Create Trial Version Mini Program"
- Scan the QR code with WeChat and follow the WorkBuddy service account
- In the service account, tap "Create Trial Mini Program" and complete authorization as prompted on the page
- After receiving the successful authorization notification, return to WorkBuddy and click "Publish"
You should see: After publishing succeeds, click the mini program QR code icon to view and share it—scan the code with WeChat on your phone, and your mini program opens.
💡 This is the unique value of managed publishing
WorkBuddy connects to your authorized mini program account as a WeChat third-party service provider, assisting with code upload, trial version generation, review submission, and version release—you never touched a development tool throughout. Account registration, verification, filing, review, and subsequent operating rules are subject to WeChat's official requirements.
Step 5: Test on a real device and decide whether to operate long-term
Why: The trial version is a "validation tier," not an "operations tier." First get the core flows working on your phone, then compare the three tiers to decide where to go after 14 days.
First, self-check on a real device: go through the core features—WeChat login, adding books, saving records—one by one in WeChat on your phone; for submitted data, close the mini program and reopen it to confirm it's still there. Then send the mini program QR code to friends to try.
WorkBuddy Managed publishing has three tiers in total—read them carefully before publishing:
| Version | Main use | Requires existing account | Requires WeChat review | Key limitations |
|---|---|---|---|---|
| Trial version | Quickly validate the result | No | No | Valid for 14 days, automatically deregistered after expiration |
| Experience version | Debugging and acceptance before launch | Yes | No | Only users with experience permissions can access |
| Official version | Public release and long-term operation | Yes | Yes | Must complete filing and pass WeChat review |
Two paths—pick one:
- Just practicing or validating: Collect feedback within 14 days and let it auto-deregister when it expires. One WeChat account can create up to 5 trial versions, so just open another one for your next idea
- Deciding to operate long-term: In the share panel, click "Unbind," then select "Bind Existing Mini Program Account" again—use the one registered in B2; after the admin scans the QR code with WeChat to authorize, you can publish an experience or official version. A trial version cannot be converted directly to an official version, so this rebinding step cannot be skipped
You should see: All core features work on your phone; you clearly know which path you're taking. If you choose the latter, the official version must pass WeChat review—the next lesson covers that.
📋 Magic Prompts
The instructions in "Follow Along" are examples; the three below are templates for you to reuse: to change the topic, only edit the content in 【】. Use the three in order: 1 produce the requirements sheet → 2 generate the mini program → 3 iterate on changes.
📋 Prompt 1: One sentence → mini program requirements sheet
Expected result: Expand "I want to make a XX mini program" into a complete requirements description that WorkBuddy can handle, specifying "WeChat Mini Program" and cloud service needs.
## Role
You are a mini program product consultant, skilled at turning vague ideas into actionable requirements.
## Task
Organize my idea into a requirements description for an AI development tool. Only organize the requirements; don't write code.
## Input Information
### Required Fields
- Mini program topic: 【one sentence, e.g., "Reading List"】
- Who it's for: 【target users, the more specific the better】
- What they do with it: 【core actions, e.g., "record books being read and finished"】
### Optional Fields
- Should data be stored long-term: 【Yes/No?】
- Should login be required: [e.g., "WeChat login"?]
- Should image uploading be supported: [yes/no?]
## Output specifications
A requirement description of 100 words or fewer, starting with "Create a ... WeChat Mini Program", clearly stating the users, core features, and cloud service needs; then attach a "Feature × Page" checklist table.
## Constraints
- ✅ Explicitly include the words "WeChat Mini Program"
- ✅ Express cloud service needs as real requirements like "save to the cloud" or "allow uploading images"
- ❌ Do not mention technical terms like database, framework, or API
- ❌ Do not plan advanced capabilities like WeChat Pay or live streaming📝 Prompt 2: Generate a WeChat Mini Program from the requirements sheet
Expected outcome: turn the requirements sheet into a native WeChat Mini Program, with cloud services connected as needed, and no web page generated.
## Role
You are a WeChat Mini Program development expert.
## Task
Create a WeChat Mini Program according to the requirements below.
## Input Information
### Required Fields
- Requirement description: [paste the requirements organized by Prompt 1]
### Optional Fields
- Style and feel: [two words, e.g., "fresh, calm"?]
- Required pages: [e.g., "book list page, add page, my profile"?]
## Output specifications
Generate a native WeChat Mini Program; when saving data or login is needed, connect cloud services as needed and state which ones were enabled; provide a preview entry when done.
## Constraints
- ✅ What you build is a WeChat Mini Program, not a web page
- ✅ Entry points to core features are visible on the home page
- ❌ No payments or live streaming in the first version
- ❌ Do not introduce external services that require me to configure them manually✅ Prompt 3: Iterative changes after preview
Expected outcome: state all change requests at once; the AI only modifies the places you name, without affecting other pages.
## Role
You are a WeChat Mini Program development expert, iterating based on user feedback.
## Task
Update the Mini Program according to the change requests below, keeping everything else unchanged.
## Input Information
### Required Fields
- Change requests: [list them one by one, e.g., "1. Group the book list by status 2. Keep the add entry pinned at the bottom"]
### Optional Fields
- Places to check carefully after changes: [e.g., "group titles and count statistics"?]
## Output specifications
Explain one by one what was changed for each request and which pages were touched; for requests not adopted, explain the reasons.
## Constraints
- ✅ Only modify the places you name
- ✅ Explain how to verify the changes in the preview
- ❌ No opportunistic refactoring or overall color scheme changes
- ❌ Do not remove existing featuresCheckpoints ✅
- The requirements state "WeChat Mini Program", and the artifact card shown in the conversation is also a "WeChat Mini Program", not a web page
- Page styles and basic interactions in the preview have been reviewed block by block, and all change requests have been fed back
- Cloud services enabled as needed: cloud database enabled for data storage, identity authentication enabled for login
- The trial version was published successfully, and the Mini Program code can be opened in WeChat on a phone
- Core flows like WeChat login and data saving have been verified on a real device; you know clearly which path to take after 14 days
Pitfall reminders
❌ Not writing "WeChat Mini Program" in the requirements
Symptom: you excitedly describe your requirements at length, but what comes out is a web page — it won't open when scanned with WeChat.
Cause: WorkBuddy can build both web apps and Mini Programs; if you don't specify, it can only guess.
Correct approach: make the first sentence of your requirements "Create a ... WeChat Mini Program"; if a web page has already been generated, just say "turn it into a WeChat Mini Program".
❌ Treating the preview as the real effect inside WeChat
Symptom: the login button works fine in the preview, but WeChat login just fails after being sent to a phone.
Cause: the official documentation clearly states: the preview is mainly for checking page styles and basic interactions, and may differ from the actual running effect inside WeChat; capabilities like WeChat login require publishing as a trial or experience version before testing on a real device.
Correct approach: the preview is for styles, the real device is for functionality. After publishing a trial version, re-run the core flows on a phone instead of trusting only the preview.
❌ Treating the trial version as long-term operation
Symptom: the Mini Program code is printed on materials, but scanning it fails after 14 days; you want to collect payments and find there is no WeChat Pay.
Cause: the trial version is for validation — valid for 14 days, automatically deregistered upon expiry, at most 15 testers, at most 5 per WeChat account, and it does not support WeChat Pay or Mini Program live streaming, cannot be searched, and has no AppSecret; a trial version cannot be directly converted to the official version.
Correct approach: once validation passes, click "Unbind" in the share panel early and bind your own Mini Program account to go with the experience/official version. Don't wait until it expires — the original Mini Program code becomes inaccessible once deregistered.
Advanced tips (optional)
🔧 Preview not enough? Open WeChat DevTools (optional)
When you want to preview in a real Mini Program environment, debug on a real device, or troubleshoot issues, you can have WorkBuddy open WeChat DevTools — closer to the real running environment than the built-in preview, and suitable for when you're stuck on a feature and can't get it working after repeated attempts.
🚀 What you're building isn't actually a Mini Program? (optional)
If all you need is "a link anyone can open", you may not need a Mini Program: WorkBuddy's "web app" likewise comes with cloud database, identity authentication, and file storage as needed, and the official documentation says "no need to buy your own server, and no deployment configuration or daily ops required"; click the share button or say "publish/go live" to get the link.
The criterion is simple: if your audience is inside WeChat, build a Mini Program; if your audience is outside WeChat, build a website — the website route starts with A1 Build a website with AI.
🚀 Official version review rejected? (optional)
After binding an account and publishing the official version, if WeChat rejects it, the share panel will show the full review reasons returned by WeChat, and WeChat's "Service Notifications" will also send a reminder. First revise according to the reasons, publish an experience version to verify on a real device, then resubmit — high-frequency rejection reasons and remedies are broken down on the B5 What to do if the review is rejected page.
Lesson summary
✅ You've completed the "build it + ship it" of making a Mini Program with AI:
- One-sentence requirement → native WeChat Mini Program: state "WeChat Mini Program" in the first sentence, and express cloud service needs in plain language
- Preview acceptance → conversational iteration: the preview is for styles, the real device is for functionality
- Share → trial version: no account, no review, valid for 14 days, at most 15 testers, at most 5 per WeChat account
- Real-device testing → decide the path: for practice, let it expire and deregister; for long-term operation, unbind and bind your own account
| Stage | What you produced | Key points |
|---|---|---|
| Define requirements | A requirement description containing "WeChat Mini Program" | Write cloud services as real needs, not technical solutions |
| Generate and modify | A Mini Program that passes the preview | Artifact card → right-side preview → revise in conversation |
| Cloud services | Cloud database, identity authentication, etc., enabled as needed | Just confirm; fill in WorkBuddy for technical parameters |
| Publish | A 14-day trial version + Mini Program code | No account or review needed, at most 15 testers |
| Decide the path | The decision to practice or operate long-term | A trial version cannot become the official version; unbind and then bind an account |
Today, without writing a single line of code or installing any development tools, your idea has become a Mini Program that can be opened in WeChat — the "build it" step was done for you by AI.
Next lesson preview
In the next lesson, B4 Submitting for review and publishing: a guide to avoiding WeChat review pitfalls, you'll turn what the trial version validated into an official version that can operate long-term. You will learn:
- The standard flow of publishing on WeChat: upload → development version → submit for review → after approval, you still have to click publish manually
- A pre-submission self-check list: name, core features, content safety — what WeChat actually cares about
- How to provide a test account so reviewers don't get stuck on the login page
- Settings the official version can't avoid: ICP filing, privacy protection guidelines, and more
When you're ready, keep B2's account materials at hand and go to B4 →