本文来源:https://mp.weixin.qq.com/s/F-Up-W1jxB6Va37ONeSxAA
若有版权问题,请来信告知:13951431913#139.com 或在右方提交评论。
开头:一个副局长干了件出圈的事
这几天有个新闻,我觉得特别值得展开说说。
北京密云分局副局长谢陨石,自掏腰包花了不到30块钱,用一个月时间,自己搓出了一个防汛小程序,叫"叫应"。
上了热搜,腾讯还追送了10亿token。
不到30块钱。一个救命小程序。副局长。自己搓的。
谢陨石大学学的是土木工程,编程是保持了二十多年的爱好。但他自己说,真正让这个小程序做出来的,不是编程技能——是他在规自系统分管地灾防汛工作,每年汛期都在协调转移工作,太知道暴雨夜里几十号人挨个打电话问"走了没走"有多痛苦。
他的原话:"以前我们组织了几十号人大半夜挨个打电话'走没走'啊,这是一个很耗时耗力的过程,我一想现在都AI时代了,现在有没有更智能的方式,能把这个信息很流畅地给传递出来。"
效果呢?以前16个涉地灾镇的预警下发和人员转移统计,要几十人通宵打电话。现在1个人,1小时,搞定。7月10号到12号北京那轮暴雨,"叫应"首次实战投入使用,扛住了。
他用的工具是 WorkBuddy 和 CodeBuddy(你可以理解为针对程序员的WorkBuddy)。
这件事戳人的地方在于:AI时代,最值钱的不是代码能力,是你对问题的理解。
谢陨石赢在他知道该做什么、数据从哪来、谁该看什么。他把需求告诉AI,AI帮他拆解任务、编写和调试代码,一步步把想法变成了真正能用的App。
你可能会想:我又不是副局长,我又不会编程,这跟我有什么关系?
关系大了。这篇就是手把手教你怎么用 WorkBuddy 的小程序开发专家,做出自己的第一个小程序。不用写一行代码,每一步都有截图,跟着做就行。
谢陨石相关新闻截图(来源:新京报官微)
这篇教程你能得到什么
看完这篇,你能做到:
- 从零开始,在WorkBuddy里做出一个能在手机上运行的小程序
- 全程不写代码,只跟AI对话
- 知道每一步该做什么、该看什么、卡住了怎么办
整个过程分8个阶段。先看全貌:
小程序开发全流程程图(8步流程,绿色=跟AI对话、橙色=手动操作、蓝色=测试预览)
别被8步吓到。前3步就是聊天,4和5是注册和安装(一次性的事),6到8是测试和发布。真正需要你动脑的,是第1步——把你的想法说清楚。
开始之前:你需要准备三样东西
| 工具 | 用途 | 要花钱吗 | 在哪弄 |
| WorkBuddy | 跟AI对话,生成代码 | 免费可用 | workbuddy.cn 下载 |
| 微信公众平台账号 | 注册小程序,拿AppID | 免费 | mp.weixin.qq.com |
| 微信开发者工具 | 导入代码、编译预览 | 免费 | 微信官方下载 |
三样都是免费的。如果你只是自用练手,不用花一分钱。如果要对外发布,微信认证费用大概30块——跟谢陨石花的差不多。
![]() |
![]() |
WorkBuddy + 微信公众平台 + 微信开发者工具
第一阶段:把你的想法说清楚
这一步最关键。不是技术活,是表达活。
1.1 打开 WorkBuddy,找到小程序开发专家
打开 WorkBuddy,看左侧菜单栏,找到"专家"入口。点进去后,你会看到上百个不同领域的专家。在搜索框里输入"小程序"或者"微信小程序",就能找到小程序开发方向的专家。
专家中心页面截图
点击专家卡片右上角的“召唤”,进入对话界面。就这么简单——你不需要配置任何开发环境,不需要装任何东西,第一步先跟专家聊上。
1.2 第一句话怎么说
这是最关键的一步。不要说"帮我做个小程序"——太模糊了,AI不知道你要什么。
给你一个可以直接抄的模板:
我想做一个微信小程序,给[谁用],解决[什么问题]。核心功能:1、[功能1:用一句话说清]2、[功能2:用一句话说清]3、[功能3:用一句话说清]数据来源:[你的数据从哪来,比如手动录入、从现有表格导入]使用场景:[什么时候用、在哪用、多久用一次]权限要求:[不同角色看到的东西一不一样]
你看,这不是技术语言,是业务语言。谢陨石说的是防汛的事——"能录入每个镇的隐患点和包保人名字,暴雨时能实时看谁转移了谁没有,村里的同志只能看自己村的数据"。没有一个技术词。
举个真实的例子。 假设你开了一家社区小店,你想做个小程序让街坊们能看商品、下单。你这么说:
我想做个微信小程序,给社区里的街坊用,让他们能看我家店里的商品、下单,我能在后台接到订单。核心功能:1、商品列表页:展示商品图片、名字、价格2、下单页:选商品、填数量、留电话3、订单管理页:我能看到所有订单,标记"已接单""已完成"数据来源:商品信息我手动录入使用场景:街坊们微信打开就用,不用下载App权限要求:顾客只能看商品和下单;只有我能看订单管理页
1.3 专家会怎么回应
发出去之后,专家不会直接开始写代码。它会先问你几个问题,把需求挖得更清楚。
这种方式叫"问题卡片"——专家把需要确认的问题一条条列出来,你逐条回答就行。
比如针对上面那个小店的需求,专家可能会问:
- 顾客下单后怎么付款?这决定了我们是否需要接入微信支付(需要营业执照和企业资质)。
- 后端数据(商品、订单)存储在哪里?这直接影响开发速度和运维成本。
- 你打算怎么录入和管理商品信息(上下架、改价格等)?
- 你的店主要卖什么类型的商品?这影响页面UI设计和商品展示方式。
你不需要懂技术,只需要回答业务问题。
比如回答如下:
到店自提 + 云开发 + 小程序内管理后台 + 生鲜果蔬店
这一步可能会来回几轮。别急,每一轮都在帮你把模糊的想法变清晰。
一个很重要的习惯: 认真看专家每一步输出了什么。第一次做陌生任务时,你脑子里并不清楚下一步该干什么。专家的输出里往往藏着"接下来我们需要做什么"的线索。它问什么,你就认真回答;它给方案,你就判断是否符合需求。不确定就先按它的建议来,后面发现不合适再改。
第二阶段:专家帮你生成PRD
2.1 PRD是什么
几轮对话之后,专家会把你俩讨论的内容整理成一份文档,叫PRD——产品需求说明书。
你可以把它理解成一份"这个小程序要做什么"的总结。里面会写清楚:
- 小程序的目标用户是谁
- 有哪些页面(Tab)
- 每个页面放什么内容
- 用户怎么操作
- 数据怎么存
2.2 怎么看PRD
你不用懂技术,但你要能判断这份PRD跟你想做的东西一样不一样。
检查方法:问自己三个问题。
- 页面够不够?有没有漏掉的功能?
- 操作流程对不对?顾客从打开到下单,跟你设想的流程一样吗?
- 权限分得对不对?谁能看什么,跟你实际业务一样吗?
如果不对,直接告诉专家哪里要改。比如"我还需要一个'热销推荐'位放在首页顶部"或者"管理员还需要能导出订单"。
PRD确认之后,后面的开发就基于这份文档来。所以花点时间看清楚,比后面返工强。
第三阶段:设计线框图
PRD确认后,专家会进入下一步:设计每个页面的线框图。
线框图就是页面的"草图"——用简单的方框和文字标出每个位置放什么。不是最终样子,但能让你看出页面的大致结构。
比如首页的线框图可能是这样的:
看到线框图后,你可以提反馈。比如"商品卡片改成一行一个,大图展示"或者"分类标签放搜索框下面"。这些调整现在做很方便,等代码写完再改就费劲了。
每个页面都会出一个线框图,逐个确认。
第四阶段:注册微信小程序,拿AppID
前面三步都是跟AI聊天,不用装任何东西。从这一步开始,需要你手动操作了。
AppID可以理解为这个小程序的"身份证号"。一个小程序对应一个AppID,后面的开发工具要用它来识别你的项目。
4.1 注册小程序
打开 mp.weixin.qq.com,点击右上角"立即注册"
选择注册类型,点"小程序"、
填写邮箱。注意:这个邮箱不能是已经注册过微信公众号、微信开放平台、或绑定过个人微信号的邮箱。如果你常用的邮箱都不行,注册一个新的就行。然后激活邮箱
去邮箱收验证码,然后回来输入验证码
填写主体信息。个人就选"个人",需要身份证和微信扫码验证。企业就选"企业",需要营业执照。
4.2 找到AppID
注册完成后,登录小程序后台:
- 左侧菜单点"开发与服务" → "开发管理"
- 在"开发者管理"页面,就能看到你的AppID
把AppID复制下来。等下要发给WorkBuddy的专家,它会把这个AppID写进项目配置里。
小提醒: AppID不是密钥,不用特别保密。但AppSecret(也在那个页面)是密钥,不要给别人看。
第五阶段:下载安装微信开发者工具
微信开发者工具是用来导入代码、编译预览、调试小程序的官方工具。
5.1 下载
- 搜索"微信开发者工具"或者直接访问https://developers.weixin.qq.com/miniprogram/dev/devtools/download.html
- 根据你的电脑系统选版本:Windows选Windows版,Mac选Mac版
5.2 安装
下载完双击安装包,按提示一步步装就行。没有什么需要特别配置的,一直点"下一步"就行。
5.3 登录
安装完打开,用你的微信扫码登录。登录后会看到这个界面:
到这一步,准备工作就全部完成了。接下来回到 WorkBuddy,让专家开始写代码。
第六阶段:专家生成代码,你导入测试
6.1 让专家开始开发
回到 WorkBuddy 的对话,PRD和线框图都确认了,AppID也拿到了。现在跟专家说:
PRD和线框图都确认了,我的AppID是 wxXXXXXXXXXX。请开始开发。
专家会开始生成代码。它会一个页面一个页面来——先做首页,给你看代码和效果说明,确认后再做下一个页面。
6.2 代码长什么样
专家生成的代码会包含几个文件。你不用懂这些文件的内容,但要知道它们是干什么的:
| 文件类型 | 后缀名 | 干什么用的 | 你需要看吗 |
| 页面结构 | .wxml | 决定页面放什么内容 | 不用看 |
| 页面样式 | .wxss | 决定页面长什么样(颜色、大小) | 不用看 |
| 页面逻辑 | .js | 决定页面怎么运转(点按钮会怎样) | 不用看 |
| 配置文件 | .json | 小程序的基本设置 | 不用看 |
| 项目配置 | project.config.json | 包含你的AppID | 确认AppID对就行 |
你不需要打开这些文件去读代码。你只需要把整个项目文件夹拿到开发者工具里导入,看效果。
6.3 把代码导入开发者工具
专家写完代码后,会给你一段操作指引。通常是这样的:
- 专家会把项目文件保存在你的电脑上某个位置(或者告诉你保存到哪)
- 打开微信开发者工具,点"导入项目"
- 选择项目文件夹所在的路径
- AppID会自动从项目配置里读取(如果没自动填,手动粘贴你的AppID)
- 点"创建"
如果选择“微信云开发”,需要先到https://cloud.weixin.qq.com/cloudbase 按照提示,开通云开发。
6.4 点编译,看效果
创建后,点“信任并运行”。
如果一切正常,右侧的模拟器里就会显示你的小程序页面了。
6.5 遇到报错怎么办
第一次编译可能不会一次通过。别慌,这是正常的。
常见的报错有两种:
第一种:缺少文件或路径不对
报错信息里会写"Cannot find module xxx"或者"文件不存在"。把报错信息复制粘贴发给WorkBuddy的专家,它会帮你修。
第二种:语法错误
报错信息里会写"SyntaxError"或者"Unexpected token"。同样复制粘贴发给专家,告诉它是在哪个文件里出的错。
处理报错的关键原则: 不要自己尝试改代码。把完整的报错信息发给专家,让它来修。你只需要判断修完后效果对不对。
6.6 逐个页面测试
编译通过后,逐个Tab点一遍,测试每个功能:
- 点首页的商品卡片,能不能进下单页?
- 在下单页选数量、填电话,能不能提交?
- 提交后,订单管理页能不能看到这条订单?
- 订单状态能不能切换?
每个功能都试一下。发现问题就截图或描述发给专家,让它修。
这个节奏很重要。 很多人第一次用AI开发,恨不得一句话生成整个App,结果拿到一堆代码看不懂,就放弃了。正确做法是:先做最小的、最能解决痛点的那一个功能,跑通了再扩展。
谢陨石花了一个月,不是一个月写代码,是一个月在反复试——这个功能该怎么设计,那个数据从哪来。他自己说:"只要把架构搭好,数据库怎么做、后台怎么做、前台怎么做,剩下的事交给AI就行。"
第七阶段:在手机上预览
在开发者工具里测试通过后,你可以在手机上体验你的小程序了。
- 在开发者工具顶部,点"预览"按钮
到这一步,你就正式拥有了一个能在手机上运行的小程序。
拿着手机给朋友看——"这是我做的小程序"——那种感觉,跟第一次学会骑自行车差不多。
第八阶段:上传和发布(选做)
如果你只是自用,到上一步就结束了。如果要对外发布,还需要几步:
8.1 上传代码
在开发者工具顶部点"上传",填一个版本号(比如1.0.0),点确认。代码就上传到小程序后台了。
8.2 在小程序后台提交审核
登录 mp.weixin.qq.com,进入"管理" → "版本管理",找到你刚上传的版本,点"提交审核"。
8.3 审核通过后发布
微信审核通常需要1-7天。审核通过后,在小程序后台点"发布",你的小程序就正式上线了。
对外发布需要的前置条件:
| 条件 | 费用 | 说明 |
| 微信认证 | 个人版免费,企业版约300元/年 | 企业版需要营业执照 |
| ICP备案 | 免费 | 小程序也需要备案,在小程序后台操作 |
| 类目选择 | 免费 | 根据小程序内容选择对应类目 |
如果你只是练手和自用,不用走这些。先用WorkBuddy把功能做出来,跑通了再考虑发布。
完整演示:从一句话到一个小程序
我把上面的流程用一张表串起来,让你看全貌:
| 步骤 | 你做什么 | 专家做什么 | 大约耗时 |
| 1. 描述需求 | 填模板,发第一句话 | 问你5-8个问题 | 5分钟 |
| 2. 回答问题 | 逐条回答 | 整理需求 | 10分钟 |
| 3. 确认PRD | 看PRD,提修改 | 生成PRD文档 | 5分钟 |
| 4. 确认线框图 | 看草图,提修改 | 生成每个页面线框图 | 10分钟 |
| 5. 注册小程序 | 按步骤注册 | — | 15分钟 |
| 6. 安装开发工具 | 下载安装 | — | 5分钟 |
| 7. 生成代码 | 说"开始开发" | 逐页面生成代码 | 15-30分钟 |
| 8. 导入测试 | 导入、编译、测试 | 修bug | 15-30分钟 |
| 9. 手机预览 | 扫码体验 | — | 1分钟 |
总计大约1-2小时。第一次做会慢一些,后面熟了会快很多。
常见问题
Q:需要会编程吗?
不需要。整个过程中你不用写一行代码。你做的是描述需求、判断对错、测试反馈。
Q:做一个小程序要花多少钱?
纯练手和自用:0元。对外发布:个人版免费认证,企业版约300元/年认证费。谢陨石花的不到30块钱,主要是token费用。
Q:大概要多久?
第一次做,大约1-2小时能做出一个简单的小程序。谢陨石做"叫应"花了一个月,但那是一个涉及16个镇、多级权限、实时数据的复杂系统。
Q:做出来的小程序能用吗?
能在微信开发者工具里运行,能手机扫码预览。如果要让别人也能搜到和使用,需要走发布流程(认证+备案+审核)。
Q:生成的代码质量怎么样?
对于一个简单的自用小程序,够用了。如果要做复杂功能,可能需要反复调试。谢陨石的原话是"代码还没有那么规范"——但够用就行,先跑起来再说。
Q:卡住了怎么办?
把报错信息或问题描述发给专家,它会帮你解决。如果是流程上不知道下一步做什么,直接问专家"下一步我该做什么"。
Q:数据安全吗?
小程序的数据存在你自己的微信小程序云开发环境里(或者你指定的服务器)。谢陨石的小程序设了四级权限——管理员、区级调查员、镇级用户、村级用户——各自只能看自己权限范围内的信息。你的小程序如果涉及别人的隐私数据,一样要想清楚谁能看什么。
Q:能用AI做App吗?还是只能做小程序?
WorkBuddy 的小程序开发专家专注微信小程序。如果你想做App或其他平台的应用,可以找对应方向的专家。
Q:一个小程序能做多大?
理论上没有限制。实际中,功能越多,你需要跟AI来回沟通的轮次就越多。建议从最小功能开始,跑通了再扩展。
三个场景的现成指令
如果你不知道怎么开口,下面三个场景直接抄,把括号里的内容换成你自己的:
场景一:信息收集类
我想做个小程序,给[社区志愿者]用,收集[小区独居老人的日常状况]。核心功能:录入老人信息、每日打卡记录状态、异常自动标红。数据来源:手动录入。权限:志愿者只能看自己负责的老人。
场景二:预约排班类
我想做个小程序,给[团队成员]用,方便[排班和调班]。核心功能:查看本周排班、申请调班、主管审批。数据来源:主管录入基础排班。权限:普通成员看自己的,主管看全部。
场景三:展示接单类
我想做个小程序,给[客户]用,[展示我的服务项目和价格,客户可以直接预约]。核心功能:服务列表、在线预约、预约确认通知。数据来源:我手动录入服务项目。权限:客户只能看和预约,我能管理所有预约。
谢陨石的经验,对你有用的一条
谢陨石说他一九九几年上大学的时候拿过计算机大赛一等奖,"技能也没丢,还在不断学习"。但让"叫应"这个小程序做出来的,不是他三十年前的编程技能,是他三十年里在规自系统攒下的防汛经验。
他说了一句话我觉得特别对:"只要把架构搭好,数据库怎么做、后台怎么做、前台怎么做,剩下的事交给AI就行。"
"把架构搭好"——这就是你在做的。你说需求、你判断对错、你测试反馈,就是在搭架构。代码是AI写的,但架构是你的。
如果你在某个领域干了很多年——医生、教师、基层干部、小店主、财务——你脑子里那些"这事一直很烦但没人解决"的痛点,就是你最好的需求文档。程序员不知道你的痛点,你知道。以前你没办法把痛点变成工具,现在WorkBuddy能帮你搭这座桥。
AI 不缺写代码的能力。缺的是知道该写什么的人。
你的经验,就是最好的需求文档。
Source: https://mp.weixin.qq.com/s/F-Up-W1jxB6Va37ONeSxAA If you have any copyright concerns, please email 13951431913#139.com or leave a comment on the right.
Opening: A deputy bureau director did something remarkable
There's been a news story lately that I think is especially worth diving into.
Xie Yunshi, Deputy Director of the Miyun Branch in Beijing, spent less than 30 yuan out of his own pocket and, over a month, built a flood prevention mini-program called "Jiaoying" (Alert Response) by himself.
It trended on Weibo, and Tencent even awarded an additional 1 billion tokens.
Less than 30 yuan. A life-saving mini-program. A deputy director. Built by himself.
Xie Yunshi studied civil engineering in college, and programming has been a hobby he's maintained for over 20 years. But he says the real reason this mini-program came to be wasn't his coding skills— it was his role managing geological disaster and flood prevention work within the planning and natural resources system. Every flood season, he coordinated evacuation efforts and knew all too well how painful it was to make dozens of phone calls late at night asking, "Have you left?"
His words: "Before, we had dozens of people making phone calls in the middle of the night asking 'Have you left or not?' It was extremely time-consuming and labor-intensive. I thought, we're already in the AI era now—could there be a smarter way to deliver this information smoothly?"
The result? Previously, issuing disaster warnings and tracking personnel evacuations across 16 towns required dozens of people working through the night on the phone. Now, one person can handle it in one hour. During the heavy rain in Beijing from July 10–12, "Jiaoying" was used in its first实战 operation and held up.
He used WorkBuddy and CodeBuddy (think of it as WorkBuddy built specifically for programmers).
What makes this story so compelling is this: In the AI era, what's most valuable isn't coding ability—it's your understanding of the problem.
Xie Yunshi won because he knew what needed to be done, where the data came from, and who needed to see what. He told the AI the requirements, and the AI helped break down tasks, write and debug code, and gradually turned his idea into a real, usable app.
You might be thinking: I'm not a deputy director, and I don't know how to code. How does this relate to me?
It relates a lot. This article will walk you step by step through how to use WorkBuddy's mini-program development expert to build your first mini-program—without writing a single line of code, with screenshots at every step. Just follow along.
Screenshot of news about Xie Yunshi (Source: Beijing News Official WeChat)
What you'll get from this tutorial
After reading this, you'll be able to:
Build a mini-program that runs on your phone from scratch in WorkBuddy
Never write a single line of code—just chat with AI
Know exactly what to do, what to look for, and what to do when you get stuck at each step
The whole process is divided into 8 stages. Here's the full picture:
Mini-program development full-process diagram (8 steps; green = chat with AI; orange = manual operations; blue = testing and preview)
Don't be intimidated by the 8 steps. The first three are just chatting. Steps 4 and 5 are registration and installation (one-time tasks). Steps 6 to 8 are testing and publishing. The step that really requires your thinking is Step 1—clearly articulating your idea.
Before you begin: You need to prepare three things
All three are free. If you're just building it for personal practice, it'll cost nothing. If you plan to publish it publicly, the WeChat verification fee is about 30 yuan—roughly the same as what Xie Yunshi spent.
WorkBuddy + WeChat Official Platform + WeChat Developer Tools
Phase 1: Clearly articulate your idea
This step is the most critical. It's not a technical task—it's a communication task.
1.1 Open WorkBuddy and find the mini-program development expert
Open WorkBuddy, look at the left menu bar, and find the "Experts" entry. Click in, and you'll see hundreds of experts across different fields. In the search box, type "mini-program" or "WeChat mini-program" to find experts in mini-program development.
Screenshot of the expert center page
Click "Summon" on the top-right corner of the expert card to enter the chat interface. That's it—you don't need to configure any development environment or install anything. Step one is simply starting a conversation with the expert.
1.2 How to phrase your first message
This is the most important step. Don't say "Help me build a mini-program"—it's far too vague, and the AI won't know what you want.
Here's a template you can copy directly:
Notice this isn't technical language—it's business language. Xie Yunshi described flood prevention matters: "Can I record hazard points and responsible persons for each town, see in real time during heavy rain who has been evacuated and who hasn't, and let village staff only see data for their own village?" Not a single technical term.
Here's a realistic example. Say you run a small community shop and want to build a mini-program so neighbors can browse products and place orders. You'd say:
1.3 How the expert will respond
After you send it, the expert won't immediately start writing code. Instead, it'll ask you a few questions to clarify the requirements further.
This method is called "Question Cards"—the expert lists out each question that needs confirmation, and you answer them one by one.
For example, based on the shop scenario above, the expert might ask:
How should customers pay after placing an order? This determines whether we need to integrate WeChat Pay (requires a business license and enterprise credentials).
Where should the backend data (products, orders) be stored? This directly affects development speed and operational costs.
How do you plan to add and manage product information (listing, delisting, price changes, etc.)?
What types of products will your shop mainly sell? This influences the page UI design and product display method.
You don't need to understand the technical side—just answer the business questions.
For example, you could respond as follows:
This may take several rounds of back-and-forth. Take your time—each round is helping you turn a vague idea into something clear.
A very important habit: Pay close attention to what the expert outputs at each step. When doing a new task for the first time, you won't always know what comes next. The expert's output often contains clues about "what we need to do next." Answer their questions seriously; when they provide a plan, judge whether it matches your needs. If you're unsure, follow their suggestion for now and revise later if needed.
Phase 2: The expert generates a PRD for you
2.1 What is a PRD
After several rounds of conversation, the expert will organize your discussion into a document called a PRD—Product Requirements Document.
You can think of it as a summary of "what this mini-program should do." It will clearly include:
Who the target users of the mini-program are
What pages (tabs) it has
What content goes on each page
How users interact with it
How data is stored
2.2 How to review the PRD
You don't need to understand the technical details, but you need to be able to judge whether this PRD matches what you want to build.
Here's how to check: Ask yourself three questions.
Are all the pages there? Any missing features?
Are the operation flows correct? Does the customer journey from opening to placing an order match your设想?
Are the permissions set correctly? Can the right people see the right things, matching your actual business needs?
If something is wrong, tell the expert directly what needs to change. For example, "I also need a 'Hot Deals' section at the top of the homepage," or "The admin also needs to be able to export orders."
Once the PRD is confirmed, the rest of the development will be based on this document. So it's worth taking the time to review it carefully—it's better than reworking things later.
Phase 3: Design wireframes
Once the PRD is confirmed, the expert moves to the next step: designing wireframes for each page.
A wireframe is like a "sketch" of a page—using simple boxes and text to indicate where each element goes. It's not the final look, but it lets you see the general page structure.
For example, the wireframe for the homepage might look like this:
After seeing the wireframe, you can provide feedback. For example, "Make the product cards one per row with larger images," or "Move the category tabs below the search bar." These adjustments are easy to make now—it's much harder to change them after the code is written.
A wireframe will be generated for each page, one by one for confirmation.
Phase 4: Register a WeChat mini-program and get the AppID
The first three steps involve only chatting with AI—you don't need to install anything. Starting from this step, you'll need to perform manual operations.
The AppID can be understood as the mini-program's "ID number." Each mini-program corresponds to one AppID, which the development tools will use to identify your project.
4.1 Register the mini-program
Open mp.weixin.qq.com, click "Register Now" in the top-right corner, select the registration type, click "Mini-Program," fill in your email. Note: This email cannot already be registered with a WeChat Official Account, WeChat Open Platform, or tied to a personal WeChat account. If none of your usual emails work, just register a new one. Then activate the email—go to your inbox to get the verification code, come back and enter it, and fill in the entity information. For personal use, select "Personal," and you'll need your ID card and WeChat scan verification. For businesses, select "Enterprise," and you'll need a business license.




4.2 Find the AppID
After registration is complete, log into the mini-program admin console:
On the left menu, click "Development & Services" → "Development Management"
On the "Developer Management" page, you can see your AppID
Copy the AppID. You'll need to send it to the WorkBuddy expert later so it can write the AppID into the project configuration.
Quick tip: The AppID is not a secret key, so no need to keep it overly confidential. But the AppSecret (also on that page) is a secret key—don't share it with anyone.
Phase 5: Download and install WeChat Developer Tools
WeChat Developer Tools is the official tool for importing code, compiling and previewing, and debugging mini-programs.
5.1 Download
Search for "WeChat Developer Tools" or go directly to https://developers.weixin.qq.com/miniprogram/dev/devtools/download.html
Choose the version based on your computer system: Windows for Windows, Mac for Mac
5.2 Install
After downloading, double-click the installer and follow the prompts. There's nothing special to configure—just keep clicking "Next."
5.3 Log in
After installation, open the tool and log in by scanning with your WeChat. After logging in, you'll see this interface:
At this point, all preparations are complete. Next, return to WorkBuddy and have the expert start writing code.
Phase 6: The expert generates code, you import and test
6.1 Have the expert start developing
Return to the WorkBuddy chat. Both the PRD and wireframes are confirmed, and you have the AppID. Now tell the expert:
The expert will start generating code. It will do it page by page—first the homepage, showing you the code and effect description, and only after confirmation will it move on to the next page.
6.2 What the code looks like
The code generated by the expert will include several files. You don't need to understand what's inside these files, but you should know what they're for:
You don't need to open these files to read the code. You just need to take the entire project folder and import it into the Developer Tools to see the results.
6.3 Import the code into Developer Tools
After the expert finishes writing the code, it will give you a set of instructions. It usually looks something like this:
The expert will save the project files somewhere on your computer (or tell you where to save them)
Open WeChat Developer Tools and click "Import Project"
Select the path to the project folder
The AppID will be auto-filled from the project configuration (if it doesn't auto-fill, manually paste your AppID)
Click "Create"
If you choose "WeChat Cloud Development," you'll need to first go to https://cloud.weixin.qq.com/cloudbase and follow the prompts to activate Cloud Development.
6.4 Click "Compile" and see the results
After creation, click "Trust and Run."
If everything goes smoothly, your mini-program pages will appear in the simulator on the right.
This moment is pretty magical—you haven't written a single line of code, yet the mini-program is actually running.
6.5 What to do if you encounter errors
The first compilation might not succeed on the first try. Don't panic—this is normal.
There are two common types of errors:
Type 1: Missing files or incorrect paths
The error message will say something like "Cannot find module xxx" or "File does not exist." Copy and paste the error message to the WorkBuddy expert, and it'll help you fix it.
Type 2: Syntax errors
The error message will show "SyntaxError" or "Unexpected token." Again, copy and paste it to the expert and tell them which file the error occurred in.
The key principle for handling errors: Don't try to fix the code yourself. Send the full error message to the expert and let it handle the fix. Your job is simply to judge whether the result is correct after it's fixed.
6.6 Test page by page
Once the compilation passes, click through each tab and test every feature:
Can clicking a product card on the homepage take you to the order page?
On the order page, can you select quantity, fill in your phone number, and submit?
After submission, can you see the order on the order management page?
Can the order status be updated?
Test each feature. If you find issues, send screenshots or descriptions to the expert and have it fix them.
This pace is important. Many people using AI development for the first time want to generate the entire app in one sentence, get a bunch of incomprehensible code, and give up. The right approach is: Build the smallest, most essential feature that solves the core pain point first, get it running, and then expand.
Xie Yunshi spent a month—not a month writing code, but a month of repeated iteration—figuring out how this feature should be designed, where that data comes from. He said himself: "As long as you get the architecture right, leave the database, backend, and frontend to AI."
Phase 7: Preview on your phone
After passing tests in Developer Tools, you can experience your mini-program on your phone.
At the top of Developer Tools, click the "Preview" button
At this point, you officially have a mini-program that runs on your phone.
Show it to your friends on your phone—"This mini-program was made by me"—that feeling is about the same as riding a bike for the first time.
Phase 8: Upload and publish (optional)
If you're only using it personally, you're done at the previous step. If you want to publish it publicly, a few more steps are needed:
8.1 Upload the code
Click "Upload" at the top of Developer Tools, enter a version number (e.g., 1.0.0), and click confirm. The code is now uploaded to the mini-program backend.
8.2 Submit for review in the mini-program admin console
Log into mp.weixin.qq.com, go to "Manage" → "Version Management," find the version you just uploaded, and click "Submit for Review."
8.3 Publish after review approval
WeChat review typically takes 1–7 days. After approval, click "Publish" in the mini-program admin console, and your mini-program goes live.
Prerequisites for public publication:
If you're just practicing or using it personally, you don't need to go through these steps. First use WorkBuddy to build the features, get them running, and then consider publishing.
Full walkthrough: From one sentence to a complete mini-program
I've laid out the above process in a table so you can see the full picture:
Total time is approximately 1–2 hours. The first time will be slower; once you're familiar, it'll be much faster.
Frequently asked questions
Q: Do I need to know how to program?
No. Throughout the entire process, you won't write a single line of code. Your job is to describe requirements, judge correctness, and test and give feedback.
Q: How much does it cost to build a mini-program?
Pure practice and personal use: 0 yuan. Public release: Personal accounts get free certification; enterprise accounts cost about 300 yuan/year for certification. Xie Yunshi spent less than 30 yuan, mainly for token fees.
Q: Roughly how long does it take?
For the first time, you can build a simple mini-program in about 1–2 hours. Xie Yunshi spent a month on "Jiaoying," but that's a complex system spanning 16 towns, multiple permission levels, and real-time data.
Q: Will the mini-program actually work?
It can run in WeChat Developer Tools and be previewed by scanning a QR code on your phone. To let others search for and use it, you need to go through the publication process (certification + filing + review).
Q: How's the quality of the generated code?
For a simple personal-use mini-program, it's more than enough. If you want complex features, you may need to iterate and debug multiple times. Xie Yunshi's own words were "the code isn't quite standardized yet"—but it's usable, and getting it running comes first.
Q: What if I get stuck?
Send the error message or problem description to the expert, and it'll help you resolve it. If you're unsure what to do next in the process, just ask the expert, "What should I do next?"
Q: Is the data secure?
The mini-program's data is stored in your own WeChat Mini-Program Cloud Development environment (or your specified server). Xie Yunshi's mini-program has four-tier permissions—administrator, district-level surveyor, town-level user, village-level user—each can only see information within their own permission scope. If your mini-program involves others' private data, you'll need to think through who can see what.
Q: Can AI make an App, or only mini-programs?
WorkBuddy's mini-program development expert focuses on WeChat mini-programs. If you want to build an App or applications for other platforms, you can find experts in those corresponding directions.
Q: How big a mini-program can be built?
Theoretically, there's no limit. In practice, the more features you want, the more rounds of back-and-forth you'll need with the AI. It's recommended to start with the minimal features, get them running, and then expand.
Ready-made prompts for three scenarios
If you're not sure how to start, you can directly copy from the three scenarios below—just replace the content in parentheses with your own:
Scenario 1: Information collection type
Scenario 2: Appointment and scheduling type
Scenario 3: Display and order-taking type
One useful takeaway from Xie Yunshi's experience
Xie Yunshi said he won first prize in a computer competition when he went to college in the early 1990s, and "my skills haven't faded—I'm still learning." But what made the "Jiaoying" mini-program happen wasn't his programming skills from thirty years ago; it was the flood prevention experience he'd accumulated over thirty years working in the planning and natural resources system.
He said something I found especially insightful: "As long as you get the architecture right, leave the database, backend, and frontend to AI."
"Get the architecture right"—that's exactly what you're doing. You state the requirements, judge correctness, and test and give feedback. That's how you build the architecture. The code is written by AI, but the architecture is yours.
If you've worked in a certain field for many years—doctor, teacher, grassroots official, small shop owner, accountant—the pain points you've long thought of as "this has always been frustrating but never solved" are your best requirement documents. Programmers don't know your pain points; you do. Previously, you had no way to turn those pain points into tools. Now, WorkBuddy can help you build that bridge.
AI doesn't lack the ability to write code. What it lacks are people who know what should be written.
Your experience is the best requirement document.



















