Capabilities and forms

The mainstream product forms are developed in-house at HaoYou Technology, and we take on work for others too. How each block is done and where its limits are is written out below, ready to be checked on the spot.

How we choose among seven forms

We pick the form that fits the scenario best on cost and experience. Below: when to choose each form, and what you get.

  • Website platform

    Open a browser and use it. Nothing to install first.

    When to choose
    Content changes often, several people share it, and it has to show up in search results.
    What you get
    A site you can visit: content fully readable by search engines, light and dark modes, content managed in an admin and tied to the same account system.
  • PC software

    Runs on your machine. Faster and steadier with large files and with no network.

    When to choose
    It needs the local file system, batch work, or it has to keep running offline.
    What you get
    An installer with a version number and change notes. Silent updates, and a rollback to the previous version.
  • Mobile app

    The everyday entry point on your phone, sharing one account with the desktop.

    When to choose
    The task has to be finished on a phone and still connect to the desktop client.
    What you get
    A mobile client on the same unified account and message channel.
  • Mini program

    Use it and leave. It takes no storage on your device.

    When to choose
    The need is light, and an install would put people off.
    What you get
    A mini program published in the WeChat ecosystem, with ordering, content and account links built in.
  • Mini game

    Opens on tap. One round is about three minutes.

    When to choose
    Entertainment in the gaps between things, with no download for it.
    What you get
    A mini game that starts on tap, with light save state and a leaderboard.
  • Open source project

    The holes we fell into, turned into shared components the community builds on too.

    When to choose
    A general capability that grew out of internal tools and is worth testing outside.
    What you get
    Public repositories and reusable components. Issues and pull requests are open.
  • Browser extension

    Put the actions you use most inside the window you already have open.

    When to choose
    The same action is repeated in the browser every day.
    What you get
    An extension package and a permission note. We ask for the least permission that works.

Four capabilities, ready to take on

These four support our own products, and can be recombined for yours.

Websites and online platforms

Things that work right in the browser: official sites, tool collections, online platforms shared by many people.

  • Built with search in mind: page content is fully readable by search engines
  • Content updates on its own, without waiting on a development slot
  • Light and dark modes plus full keyboard access are defaults, not patches

Desktop and local software

When it needs local files, offline work or a long stay on the machine, it becomes software that works right after install.

  • Compression, tidying and checksums for large batches of files
  • Background updates, and a bad release can step back to the previous version
  • A portable first approach: dependencies are not pushed into your system folders

Accounts and supporting services

Every product shares one account: register once, use it everywhere.

  • Ordering, payment, activation and entitlements all happen online
  • One account works across the website, the software and the mini programs
  • User data serves the product function itself and is not collected beyond that

Mini programs and mini games

Finish a task or play a round inside WeChat, without installing anything.

  • Ordering, content browsing and account links inside mini programs
  • Tap-to-play mini games with light save state
  • The same account as the website and the desktop software

Three claims, shown as working practice

A claim is not a slogan. Each line maps to a way of working you can check.

Useful

Everything starts by solving one real problem.

Compressing files, finding files, checking answers, building guides. The test for a feature is whether you would open it again next week.

Playful

"HaoYou" is a standard, not decoration.

Does a button answer when you press it? Do you know the progress while something loads? Does an empty screen invite you to do something? These parts do not change the function, and we hold them to the standard we would use for a game.

Effortless

It works right after install. Nobody has to read a manual.

Defaults are chosen for you, and the first screen already has something to do. Where an explanation is needed, we write it into the interface instead of a separate document.