About us
A software company that writes the code and builds the interface. Ordinary people use what we make, so every item has to work as soon as it is installed.
Entity details
The information below matches the filing records and our public documents. Where an address field is not filled in, it stays empty instead of guessed.
- Registered legal name
- 青田好游科技有限公司（Qingtian Haoyou Technology Co., Ltd.）
- Brand
- HaoYou Technology
- Registered locality
- Qingtian, Zhejiang, China
- Site domain
- www.qthy.cc
- Contact
- rd@qthy.cc · 188 0688 8608 · Monday to Friday, 9:00-18:00
- Filing numbers
- 浙ICP备2022036331号-1 · 浙公网安备 33112102000156号
- Forms on record
- 7 Product forms
Key facts
- The registered legal name of HaoYou Technology is 青田好游科技有限公司 (Qingtian Haoyou Technology Co., Ltd.), and the registered locality is Qingtian, Zhejiang, China.
- Product definition, interface, servers and release are all in our own hands: from idea to launch, nothing is subcontracted or outsourced.
- We develop our own software. Our product forms cover 7 kinds: website platforms, PC software, mobile apps, mini programs, mini games, open source projects and browser extensions.
- All products share one account system: register once, and the same account works across the products and the clients.
- We take on custom development for websites, desktop software and mini programs; scope and schedule are written down before work starts.
- Desktop software runs locally and never forces you online; user data serves the product function itself and is not collected beyond that.
- Every product carries a versioned change log, supports background updates, and can step back to the previous version when something goes wrong.
- Light and dark modes plus full keyboard access are defaults across our products, not patches added before release.
- Partnerships run through four intents only: channel distribution, custom software, media content and open source. Scope gets agreed first, paper second.
- Contact email rd@qthy.cc, phone 188 0688 8608, service hours Monday to Friday, 9:00-18:00.
How we work
Seven steps, from naming the problem to changing it from feedback. If any step cannot be finished, it goes back to the one before it instead of being skipped.
Name the problem
Write down who is stuck, on what, and when. If that sentence cannot be written, the work does not start.
Pick the form
The same job can be a website, desktop software or a mini program. Choose the cheapest form for the setting it gets used in.
Set the hierarchy
Decide what matters most and what can stay folded away before any talk of color or corner radius. Light and dark modes are settled in this pass.
Build it
Interface and API move forward together. We do not make a product that exists only as static mockups.
Use it ourselves
We use it every day for real work. A feature we cannot keep using does not ship.
Release with notes
Every release carries a version number and change notes, so the diff can be read and rolled back.
Change it from feedback
The feedback channel sits in the page footer, not hidden. After a change, the notes say what changed.
A few internal rules
Every line below is a public promise. Use it to check our products, and to check how we work.
- Subtract first: every time a feature goes in, ask whether a step can go out. Simplicity is the result of design, not luck.
- Say it up front: scope, schedule and fees are written down before work starts. What we cannot do, we say we cannot do — and we never raise the price midway.
- A hard line on data: collect only what the product needs to run, never pass it on, and the privacy policy is the binding text.
- Own every release: update notes say what changed; when something breaks we roll back first and debug after, so users never pay for our mistakes.
- Deliver against acceptance criteria: what counts as done is written down before work starts, and the deliverable must work in real use, not just in a demo.
- Rules before moods: partners, colleagues and internal-startup founders all get the same treatment — the rules are agreed first, then honored for the long run.