这个页面有中文版 →
Blog / One-person company

Can one person with no coding experience ship a web game with AI in a week?

What it took to build and launch a small web game with AI in five days: who did what, where image generation broke, and how to run with no server.

Short answer

Yes, if the game is small and you check everything the AI produces. We built and launched a web game in five days without writing code by hand. The slow part wasn't code: it was getting images right, which took prompts hundreds of words long. A static host, browser storage and a free counter covered everything a server would have done.

Can one person with no coding experience ship a web game with AI in a week?

Yes, but be strict about what "ship" means. It means a stranger can open a link on their phone and play, not that it runs once on your laptop.

Play it first: the game runs in your phone's browser, with no download and no sign-up.

We just answered this question for ourselves. This October an old fan pairing was suddenly everywhere online again: the Monkey King from Journey to the West and Lin Daiyu from Dream of the Red Chamber, two characters from classic novels that never meet. We decided to turn it into a playable web game. In our version the two are already a couple, and the player plans their days: part-time jobs, cooking, movies, arguments and making up. The game follows the real calendar, has holiday events, and has a gallery to collect. It went from idea to a public first version in five days, and nobody on our side wrote a line of code by hand.

Here is the honest account.

Who did what

An AI coding assistant wrote all of the code: the game engine, dozens of activities, quarrels and make-ups, holiday stories, save files and the deploy script. The human side of the work came down to three jobs:

  1. Saying what we actually wanted. Our first brief was "a romance game," and the AI built a 30-day courtship with an ending. Only when we said "they're already together, there's no ending, and players come back every day" did the game become what it is now. Good code in the wrong direction is wasted.
  2. Playing it and finding problems. On a laptop the title page ran longer than the screen. A title character was cut in half. Design notes we wrote for ourselves showed up in the player's menu. None of this was visible until someone played.
  3. Deciding. The AI suggests a lot. Some of it is great and some of it is noise. A person has to make the call.

The slow part was images

The game plans 105 gallery illustrations, plus character portraits and backgrounds, well over a hundred images in all. At the time of writing, 53 gallery images are live. We used chat-based image tools, and on a free daily allowance we kept roughly fifteen to twenty usable images a day.

The real problem wasn't the allowance. It was that image models draw exactly what you say and guess the rest. Some of our failures:

  • We asked for a character "standing up and pointing at the storyteller on stage to correct him." We got him arguing with empty air, because we never said where the storyteller was or where the character was looking.
  • "She makes a finger heart with her right hand, and covers her mouth with one hand" produced a woman with two right hands.
  • We described the camera as "shooting back from the movie screen," and got two people sitting with their backs to the screen.

What fixed it was writing each image the way you'd write code. Composition: where each person is in the frame. Light and setting. Each character's pose, what each hand is doing, exactly where they are looking, which facial muscles move. Then a line for the most likely mistake. A one-sentence prompt became five hundred to a thousand words, and redraws dropped sharply.

There's also a legal footnote. The US Copyright Office's January 2025 report on copyrightability says AI outputs are protected only where a human author has determined sufficient expressive elements, and it rules out "the mere provision of prompts." So assume your AI art isn't yours to protect, and don't build a business on owning it.

Running a game with no server

The game is static files hosted on GitHub Pages. GitHub's published limits are a 1 GB site and a soft limit of 100 GB of bandwidth a month, which is plenty for a small game. But a static site can be read and never written, which raised two problems.

  • Saves. Progress lives in the player's own browser through localStorage. MDN notes that it has no expiration date but belongs to one site in one browser, and that a private window wipes it when the last private tab closes. So the game offers a backup code that players can copy and paste back in.
  • Visitor numbers. Our first idea was "keep a number in a text file and add one on every click." A browser can't change a file on a static host, and putting a write key in public code would let anyone edit the whole site. We used a free counter service instead. It counts three things and nothing personal: game opens, presses of Start, and clicks through to STARC. Here are the live numbers:
—
game opens
—
pressed Start
—
clicked through to STARC

Counting since October 23, 2026. Live numbers.

How this fits STARC

STARC is a small nonprofit. Its one-person company cohort asks students to spend 8 weeks building a real small product with AI, launch it, find real users, and write down honestly what happened, and no coding experience is required. This game is our own demo of that loop: ship, count, and write up the mistakes. The numbers in this post will change as the game grows, and the counter above is live. You can play it here.

The short version

You can build and launch a small web game with AI without coding. Code isn't the bottleneck. Describing what you want and checking every output is. Write image prompts down to composition, gaze and both hands. Assume AI art isn't yours to copyright. When there's no server, use browser storage for saves and a simple counter for visits.

Related questions

Do I really need zero coding experience?

For a small web game, yes. All of our code was written by an AI coding assistant. What we did was describe what we wanted, play the result, and decide what to change. Being unable to write code wasn't the bottleneck; being unwilling to test would have been.

Can I copyright the AI-generated art in my game?

Probably not on its own. The US Copyright Office's 2025 report says AI outputs are protected only where a human author determined sufficient expressive elements, and that providing prompts alone isn't enough. Your own creative arrangements or edits of the output can be protected.

How do I save players' progress without a server?

Use the browser's localStorage. MDN notes the data has no expiration, but it's tied to one site and browser, and a private window clears it when the last private tab closes. Offer an export code so players can back up their saves.

How do I count visitors without a server or an analytics account?

A free counter service with a "hit" link that adds one and a "get" link that only reads. We count three things and nothing personal: game opens, presses of Start, and clicks through to STARC.

Want to build your own product?

The OPC cohort: 12 students, 8 weeks, one real product with real users.

See the OPC cohort Apply

Last updated: 2026-10-23. Written by the STARC team. Rules quoted here come from our transparency page; if they change, this post is updated.

More questions