← Plugin catalog
Creativity

TinyBulb

Nikita Leonov v1.0.3

Publish the games you make

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Publish games
  • Update games
  • Check a game's status

Cost & access

TinyBulb doesn't sell anything or take payments.

Declared limitations

  • Publishing somewhere else
  • Deleting a game
  • Unrelated request
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 16, 2026. Package observed Nov 16, 2026.

View package source →

Description

From the marketplace listing

Made a browser game with AI? TinyBulb puts it online, where anyone can play it on a phone or a computer. Ask to publish your game on TinyBulb. Your AI packages the game with a cover, an icon and a screenshot, and TinyBulb checks that it runs without network access and works on phones. If something needs fixing, your AI gets a list of fixes and tries again. When the game passes, you get a link: open it, play the game exactly as players will, and tap Publish. You only sign in at that step. To change a game later, ask your AI to update it. You try the new version from a link and publish it when you're happy.

Language: English · Automatically detected from descriptions.

Matches for “html5”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher keywords · listing

games publishing html5

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 16, 2026. Last seen Nov 16, 2026.

Keywords

Files & skills

File archives

Plugin package6 files · 16.8 KBBrowse files →
Skill instructions
building-web-games9.68 KB

View saved version →

---
name: building-web-games
description: Makes browser games feel finished and play well on phones (touch controls, phone layouts, loading screens, game feel, a complete loop from title to game over, testing at phone sizes, cover art), then publishes them on TinyBulb so anyone can play them from a link. Use when building, improving or porting an HTML5 or JavaScript game (canvas, Phaser, three.js, PixiJS, WebAssembly), or when the person wants to publish, share or put a browser game online.
metadata:
  author: TinyBulb
  version: "1.1"
---

# Building web games

Players decide in the first few seconds, on whatever device is in their hand, and more and more often that's a phone. Quick games tend to fall down in the same places: controls that assume a keyboard, panels that cover half a phone, a blank screen while things load, nothing happening when you hit something, and no way to restart. Work through the sections below in order. For an existing game, start by playing it.

## 1. Play it first

Run the game and play a whole session twice: at 390×640 with touch only, and at 1280×720 with mouse and keyboard. Write down everything that's confusing, cut off, unreachable or dull. Fix what players will feel; don't restructure code that works.

## 2. Phones from the start

- **Lay out for the screen you're on.** Keep the computer layout where there's room, and switch to a compact one with media queries on the window's size, such as `(max-width: 600px), (max-height: 500px)`. Size things relative to the window, use `100dvh` rather than `100vh`, and respect notches with `env(safe-area-inset-*)`. Don't just scale the computer layout down.
- **Pick an orientation or support both.** If the game only works one way round, say so (on TinyBulb, `orientation` in game.json asks players to turn their phone). Otherwise lay it out for both.
- **Design controls for thumbs, not a keyboard on screen.** Tap or drag on the play area to aim, move or place things; swipe to steer; a joystick that appears where the thumb lands. Put the controls used all the time in the bottom corners or along the bottom edge. Nothing may need hover, right-click or a key.
- **One input path.** Use pointer events (`pointerdown`, `pointermove`, `pointerup`) so mouse, touch and pen share the code. Keep keyboard controls for computers.
- **Keep the play area clear.** Always on screen: the play area, the controls used constantly, and the few numbers players watch (score, lives, money) in one compact strip along an edge, a fifth of the screen at most. Shops, upgrades, settings and help open from one small button as a panel that closes again; pause while it's open if the player could lose.
- **Keep every feature.** The phone layout tucks things away; it never removes them. Everything a player can do on a computer can be done by touch.
- **Menus win.** While a menu or dialog is open it gets every tap, and game input listens on the play area, not the whole page, so tapping a button never also fires in the game.
- **Never cut anything off.** Text wraps instead of truncating. Panels taller than the screen scroll (`max-height` that fits the window, `overflow-y: auto`), so every item and the close button can be reached. Set `touch-action: none` only on the play area, never the whole page.
- **Make taps easy.** Buttons at least 44 CSS pixels with space between. Name buttons by what's on screen ("tap JUMP", not "press SPACE") when `@media (pointer: coarse)` matches.
- **Sharp and fast.** Scale canvases by `devicePixelRatio` (capped at 2), and keep 60 frames a second on a mid-range phone: reuse objects, cap particles, and avoid touching the page layout every frame.

## 3. The first ten seconds

- **Show something at once.** The first frame is the title screen or a loading screen, never a blank or black page.
- **Show progress for everything big.** Models, textures, sounds, levels and WebAssembly load behind a progress bar or percentage. Keep the page itself small so it appears quickly.
- **A 

Preview of the first 4,000 characters. Read full instructions →

Release notes

First release: publish games to TinyBulb, update them, and check a game's status.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
TinyBulb
Keywords
See keywords
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Publish games
  • Update games
  • Check a game's status

Package observed Nov 16, 2026.

Technical details
First seen
Nov 16, 2026 · 18:00 UTC
Last seen
Nov 16, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6aee31ce5830819182adbdae27243a5b

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.