Apps and mini-programs for work that happens outside the office

Customer apps, field-service tools, and internal operations apps. We design the flow, build the client and the admin side, and help you launch.

What we build

  • iOS and Android apps: customer-facing products and internal tools, built with a cross-platform or native stack depending on the requirements.
  • WeChat mini-programs: membership, booking, ordering, redemption, and service workflows inside WeChat.
  • H5 / mobile web: a lightweight entry point for campaigns, forms, and simple customer journeys.
  • Admin dashboard: orders, users, content, permissions, reports, and exports.

Typical modules

Accounts and roles, customer profiles, orders, scheduling, photo capture, location check-in, notifications, payments, statements, and reporting. We start with the smallest set that makes the core workflow work.

An MVP, not a monster

Most first releases should answer one question: does the core workflow work in the real world? We scope an MVP around that question, put it in front of real users, and add modules only after the first one is stable.

This is usually faster and cheaper than building every imagined feature before launch. It also gives you real feedback instead of a long specification document.

Platform choice

App, mini-program, or H5 is a business decision as much as a technical one: where your users are, what device features you need, how you acquire customers, and how you will maintain the product. We write down the trade-offs before recommending a stack.

FAQ

App questions

Should we build an app or a mini-program?
If your customers already use WeChat and the workflow is lightweight, a mini-program is often the faster start. If you need deep device access, offline work, or a standalone brand presence, a native or cross-platform app may fit better. We compare the trade-offs in writing.
Can you build the admin dashboard too?
Yes. Most projects need an operations back office for orders, users, content, and reports. We scope it together with the client-facing app.
How do you handle app-store submission?
We prepare the build, privacy documentation, and listing materials, and assist with submission. Approval is controlled by Apple and Google, so we cannot guarantee a review outcome.
Can it work offline?
For field service, inspection, and warehouse apps, yes — with local caching and sync. The offline rules are part of the requirements, not an afterthought.
CONTACT

Have a workflow that lives in chat groups?

Tell us who uses it, what they do on a phone, and what the back office needs to see.