Insights · 5 min read
Mini programs live inside an ecosystem with its own rules. What to look for in a WeChat developer, what to ask, and where hiring goes wrong for foreign brands.
By GGP Editorial
If your customers live inside WeChat, a mini program is the cheapest way to reach them. They do not need to download an app, and they do not need to leave the app they already open fifty times a day. For a brand outside China, this is often the only realistic path into that market. But hiring for this work is not like hiring a web developer, and most foreign brands find that out after a launch stalls.
A WeChat mini program runs inside the WeChat app, not in a browser. The developer writes JavaScript or TypeScript, then uses WXML for structure and WXSS for styles. Both look like HTML and CSS and both are slightly different in ways that matter. The harder skills sit outside the code. A good developer knows WeChat DevTools, the cloud development environment, the WeChat Pay API, and the package size and permission limits WeChat sets.
A junior web developer can read WXML in an afternoon. What takes months is internalising the review process and the category rules. Some industries need extra licences before WeChat will approve a program. WeChat Pay for a foreign brand needs a Chinese entity or a registered service provider, and that paperwork is where most overseas launches get stuck. The code that displays a product list is easy. The identity verification, the payment account, and the first rejection from the review team are the real project.
So when you hire, you are not just paying for code. You are paying for someone who has already been through the rejections and knows how to get past them.
Some brands try to skip the mini program and serve a plain web page inside WeChat. That works for a landing page and nothing more. The browser inside WeChat is limited, you cannot push a notification, and the payment flow is clumsy. A mini program is the format WeChat is designed around, which is why it performs better for anything that has to retain users or take money.
If your goal is awareness, an H5 page is fine and costs very little. If your goal is selling, ordering, or repeat visits, build the mini program from the start. Half-hearted attempts that switch formats later usually pay twice.
A short list of questions separates someone who has shipped from someone who has watched tutorials:
Then run the normal checks. Open live mini programs inside WeChat, call a reference, and give a test task that touches something WeChat-specific. A generic coding puzzle tells you nothing about whether they can handle review.
| Option | Best for | Common risk |
|---|---|---|
| Freelancer | One small release | Stops responding mid-review, no support later |
| Local agency | Meetings in your time zone | Thin WeChat Pay and review experience |
| China-based team | Full build with payment and review | Time zone gap and language |
The third option is usually the best value if you can handle the time zone, because review and payment are exactly where foreign brands lose weeks and money. A team in China already knows the process and usually has contacts who can explain a rejection in detail rather than guessing.
That is the gap we fill. GlobeSoft is a China-based team that has built mini programs for clients in Brazil, South Africa, Singapore, and the US. We work in English and Portuguese, we schedule overlapping hours for calls, and we run a dedicated group so you are not emailing into silence. We have handled WeChat Pay setup for foreign brands more than once, so a rejection is a known problem to us, not a surprise.
Agree on a few things before work starts. Who handles the entity and the payment registration? Will you test on a trial account first? What is the plan for the review loop, since WeChat will likely bounce the first submission? Write the release scope down, because adding features inside WeChat's limits gets expensive quickly.
Plan for the review itself. A first submission is often rejected for reasons that sound minor, like a wording choice on a permission prompt. Budget a week or two for the back and forth and do not schedule your launch for the day after submission. Teams that have done this before will tell you the same thing without being asked.
One tip I give everyone: ask for a screen recording of a previous submission going through review, not just the finished product. A polished demo is easy to fake. The submission history shows whether they have actually shipped anything.
We build and maintain mini programs end to end, including the parts most agencies quietly skip. If you want a straight answer on cost and timeline, get in touch.
Tell us what you are building and where you are today. We typically reply within 24 hours.
