Sparkle starts from a practical problem: many people can describe the game they want, but they cannot build the project, edit the code, test it, or publish it. Sparkle turns that path into a product flow where the user can describe ideas through chat and gradually get a playable H5 game.

Open SparkleVisit the live platform, try the games, and find the game creation entry.

Product structure

1. The web platform handles discovery and play: home, categories, featured games, detail pages, login, My Games, rankings, likes, comments and sharing. 2. The Windows desktop creator handles creation: local projects, code editing, testing, and uploads for test or production builds. 3. The Android app focuses on mobile play, with native screens around lists and details while H5 games run in WebView.

Creation model

Sparkle does not treat game development as a form. The real creation loop lives in the desktop creator. The agent knows which game and version the user is editing, receives chat instructions, and applies changes to the local project.

Game library

The platform keeps adding original games across merge, memory, runner, matching, slicing, block, 3D and chemistry learning directions. New games prioritize portrait mobile play, real covers, score saving and rankings.

Current focus

The current work is to tighten both play and creation: give H5 games more space on phones, keep common actions out of the play area, and make the desktop creator's create, edit, test upload and publish flow reliable.