What kind of product to build?

Use through a link

Websites & web apps

The idea, one link away.

Users complete the task through a link, without installing first.

Does this form fit your project? Check these four points

Which projects fit this form?: Portfolios, reference sites, forms, calculators, bookings and team tools whose main work fits a browser and benefits from link sharing.
What should be ready before you start building?: Builders validating an idea for phone and desktop users without installation friction, willing to check screen sizes and maintain needed hosting/data services. Beginners can start with one small flow.
Which projects should consider a different form?: Projects requiring system control, sustained background work or extensive local-file operations beyond the target browser’s capabilities. Offline use, a camera or a home-screen icon alone does not rule out a PWA; test the actual browsers.
Which missing prerequisites should you resolve first?: Builders who require system features but will not check browser limits, or expect shared data without arranging data services, access rules and upkeep.

Mini programs

Event information & sign-up

One platform first

Mini programs

Build where the users already are.

Users already gather on a platform and use the service inside it.

Does this form fit your project? Check these four points

Which projects fit this form?: Sign-ups, bookings and member services with an existing audience on WeChat, Alipay or Douyin, when the platform supports the required features and account eligibility.
What should be ready before you start building?: Builders who can choose one platform, reach its real users, and check account eligibility, permissions, review and release requirements.
Which projects should consider a different form?: Projects needing a universal link across unrelated platforms, or capabilities unavailable on the chosen platform. Code and eligibility are not automatically portable between platforms.
Which missing prerequisites should you resolve first?: Builders without a known platform audience or required account eligibility, or who cannot accept platform review and constraints. Resolve these before implementation.

Mobile apps

A daily journal

Check devices and distribution

Mobile apps

Turn a good idea into an everyday app.

Phone-first use benefits meaningfully from an installed app.

Does this form fit your project? Check these four points

Which projects fit this form?: Frequently used phone tools needing substantial device integration or complex mobile interaction, such as field capture or offline workflows. First check whether a mobile website already suffices.
What should be ready before you start building?: Builders with a real target phone who can start with one OS and handle packaging, permissions, distribution and update tests. A previous website is not required; a suitable local or cloud build setup is.
Which projects should consider a different form?: Small content displays, one-off forms and occasional link-driven use where installation adds more burden than value; test a mobile website first.
Which missing prerequisites should you resolve first?: Builders without a target device or testing route, unwilling to handle permissions/installations, or needing immediate public delivery without distribution prerequisites.

Desktop apps

A file-organizing assistant

Check the target OS and installation

Desktop apps

Make a tool for repetitive tasks.

Work happens on a computer and needs local files or system capabilities.

Does this form fit your project? Check these four points

Which projects fit this form?: Batch file organization, media processing, local search and offline desktop work where installation provides useful file access or system integration beyond a browser solution.
What should be ready before you start building?: Builders who can choose one OS, test on it, and handle installation, permissions, upgrades and recovery. One OS is easier to verify than three at once.
Which projects should consider a different form?: Projects for occasional phone use, shared work without local integration, or users who cannot install software. A simple batch task may need only a script rather than a complete desktop UI.
Which missing prerequisites should you resolve first?: Builders lacking the target OS for testing, unable to support installation/updates, or planning destructive batch work on originals without preview, backup and recovery.