Planetfall

A note before the review: the developer has not published a licence for this game (no LICENSE file in the repository, no statement in the README). It's published here credited to Chia-Wei Ku by name with a link to the developer's own GitHub repository, and with a same-day takedown offer standing if they would prefer it not be hosted here.

Planetfall's developer wrote a genuinely thoughtful postmortem alongside the game's source code, and it's worth taking at face value: inspired by Star Citizen's seamless planet-to-space transitions, the goal was to reproduce that feeling in a 2D platformer with a hard 13-kilobyte budget. What shipped is a small, atmospheric exploration game about a lone robot travelling to five planets, landing carefully enough not to crash, and hunting down a satellite station on each one using a sound-based radar before taking it offline.

Gravity, camera rotation, and a real failure state

The best idea here, confirmed directly in the shipped source, is how movement direction is defined. Rather than a fixed "up is always up" coordinate system, the camera rotates with the player so that "up" always means away from whichever planet's curved surface they're currently walking on — meaningful because these are round worlds, and walking toward what would be the south pole on a flat-coordinate game would otherwise leave the player upside down and confused about which arrow key means "forward." Reading the code confirms the actual mechanic: gravity pulls toward the nearest planet's centre, velocity is tracked continuously, and landing too fast triggers a genuine failure state with the message "You must land carefully" rather than a forgiving bounce. A 2018 competition judge's own comment — "died on impact" — confirms this isn't a theoretical risk; it's a real consequence real players ran into.

Controls: real touch support, once tested with a genuine press

Given this shelf's whole premise, the touch claim behind Planetfall's Mobile category win was tested directly rather than taken on faith, and it needed a second attempt to confirm properly. An instantaneous synthetic tap on the title screen did nothing — the same false negative found testing other js13k entries this cycle, caused by the game's key-state model clearing all "pressed" keys the instant a touch ends, which a zero-duration synthetic tap can outrace. Retesting with a genuine sustained touch-and-release started the game immediately, and a subsequent held press on the screen's left third visibly walked the character and correctly advanced the in-game tutorial from its movement prompt onward — the same result a desktop arrow key press produced in a separate test. The control scheme itself, reading the source, divides the screen into thirds and maps each to a movement key exactly like a virtual d-pad would, which is a sound, simple design for a platformer this size.

The one control-adjacent rough edge that showed up consistently: every tutorial prompt displays its keyboard binding — "[←][→] Move," "[↑] Jump" — even in a touch-only session, with nothing to tell a mobile player which screen zone corresponds to which bracketed key. The mechanism works once you know where to touch; the game just never quite tells a touch-only player where that is.

The first thing every phone visitor will see is a bug

This is worth stating plainly rather than softening: the title screen's own logo is a real, reproducible interface failure on exactly the device class this shelf is built to serve. Reading the shipped code shows the "P L A N E T F A L L" title text rendered with a flat 72px font setting and no width-based scaling applied, unlike nearly every other draw call in the game (which route through a zoom-aware transform function). The practical result, confirmed in testing: on a 390-pixel-wide phone screen, only the middle few letters of the title are visible, with the rest running off both edges, and the instructional text underneath it suffers the same fate. It doesn't block play — the invisible "start" trigger still covers the full screen — but it is the literal first impression this game makes on a phone, and it's a genuine, unforced bug rather than a design choice.

Presentation

The five planets earn their place in the developer's own postmortem as the game's centrepiece. Aolea, the cyberpunk city world tested directly here, renders as layered purple-and-navy skyscraper silhouettes with glowing neon window strips, and reading the planet data structure in the source confirms each of the other four worlds carries its own distinct palette and parallax background layers rather than a reskinned template. It's a genuinely well-art-directed game for something built under a hard size limit.

Final verdict

Planetfall earns its Mobile category win with a real idea — camera-relative movement across round, gravity-bearing worlds — executed with a failure state that has teeth and five planets that each look and feel distinct. What holds it to a 7.5 is squarely a first-impressions problem: a title-screen text overflow that greets every single phone visitor before they've touched anything, and tutorial hints that never quite translate their keyboard bindings into the touch zones a mobile player actually has. Neither undoes what is, underneath, a genuinely original and well-realised small game.