Three Wot UI Starter Templates for uni-app, Compared
uni-app projects share a tedious, repetitive setup tax — routing, state, requests, linting — that burns hours before any feature code appears. These three templates represent the main strategies for eliminating that tax, and the choice between open configurability, strict conventions, or pre-built business features directly shapes how a team onboards, refactors, and collaborates with AI coding tools.
Starting a uni-app project with Wot UI still means wiring up routing, Pinia, UnoCSS, request libraries, and subpackage optimization by hand — a half-day chore that repeats with every new project. Three starter templates now eliminate that boilerplate, each with a distinct engineering philosophy. The official wot-starter combines independent open-source plugins into a transparent, customizable base. oiyo-starter pushes further into convention-over-configuration territory, using the Oiyo framework to collapse routing, layouts, and auto-imports into a single config file and a set of directory rules that also play well with AI coding agents. The community-driven unibest ships with login interception, pagination, i18n, OpenAPI generation, and CI/CD for Mini Programs, prioritizing immediate business capability over minimalism.
All three templates handle Wot UI component auto-import and style adaptation identically, so the choice hinges on engineering preferences rather than component compatibility. wot-starter suits teams that want full visibility into their toolchain and the freedom to modify it. oiyo-starter appeals to developers willing to accept framework-level conventions in exchange for less configuration maintenance, though its core framework uses a commercial license that requires review. unibest fits projects with common business patterns like authentication and paginated lists, where a richer starting point cuts more initial work.
The maintainer's practical advice: clone all three, add a page, write one API call, and pick whichever causes the least friction. Templates are tools, not lifelong commitments.
A template's documentation quality directly reduces the maintainer's support burden — comprehensive docs mean fewer repetitive questions in community channels, which the maintainer frames as a form of 'slacking off' that actually scales better.
oiyo-starter's convention density is explicitly pitched as an AI-coding advantage: when an agent doesn't need to guess file locations or config files, it generates correct code in fewer turns, saving both API costs and developer frustration.
The commercial license on Oiyo's core framework introduces a real adoption gate for corporate teams that the other two templates avoid entirely, making the 'official' label carry a licensing caveat that may surprise developers who assume official equals fully open.
unibest's richer feature set comes with a discoverability cost — more directories and configs to understand on first open — which the maintainer warns can lead to accidentally deleting infrastructure code mistaken for demo code.