Build a game's core loop

Who we are PlayDrop is a platform for casual mobile games built with AI tools. We hire in small paid tests and keep going with the people who land them. The task Build the core loop of a casual one-tap color-clear puzzle as a vertical mobile game that runs inside the PlayDrop app, where it plays like a native game. One playable level is enough. Skip the rest, no menus beyond restart, no accounts, no monetization, no extra content. The gameplay The board is full of colored blocks. You tap to send small shooters across the play area, and each shooter clears blocks of its own color. You keep tapping, managing what fires and when, and work the board down until it is clear. It is one-tap simple, and the whole point is the feel: the motion, the firing, and the satisfaction of clearing blocks. Quick to pick up, easy to play one-handed. You can take inspiration from this App Store game: https://apps.apple.com/us/app/pixel-flow/id6751056652. Play it to get a feel for the pace and the one-tap rhythm. Bring your own visual identity; we are not after a copy. How you build it Built in web tech: TypeScript or JavaScript, Canvas / WebGL / Three.js, Web Audio. No Unity, Godot, or engine web-exports. PlayDrop runs it inside the app through our SDK, so it plays native without you shipping a native build. It runs inside the PlayDrop mobile app using our SDK and CLI. You drive Claude Code, Cursor, or Codex to write the code. We are hiring your eye and your speed with an agent, not hand-coding. How we judge it We grade the player-facing result first. Code architecture is not the point of this test, but the build must run reliably, perform smoothly, and be easy enough for us to launch and inspect. What we look at: How well the core loop reads and feels. Animation, game feel, juice. UI/UX readability on a phone. Visual cohesion and art direction. PlayDrop integration and resourcefulness. Performance, polish, absence of obvious bugs. It has to launch inside the PlayDrop app (or a clearly-noted fallback) for us to evaluate it. What to deliver A live link. A PlayDrop play URL is strongly preferred. A fallback deploy (Vercel, Netlify, Pages) is accepted only with clear notes on what is missing and where you got stuck. A short screen recording of the loop on a phone in portrait. The source, as a repo or a zip. Two or three sentences on which agent you used (Claude Code, Cursor, or Codex) and how, plus what you would improve with more time. To apply Use Claude Code, Cursor, or Codex. We care about your taste, iteration speed, animation sense, UI judgment, and your ability to ship a working PlayDrop build. Send your portfolio with at least one piece showing real motion and UI polish, ideally something interactive you shipped, and one line on how you use one of those agents on real work. Put "good juice" at the top so we know you read this.