Flavia Mbuki
Flavia MbukiVenture Builder · Africa
← Back to portfolio
Fun build · Off the clock
Single HTML file Vanilla JS + CSS 3D Kociemba two-phase solver Zero runtime dependencies

CubeGuide: GPS for your cube

A web app that walks anyone through solving a Rubik's cube, one move at a time, with a live 3D twin of the cube in their hands. No notation to learn, nothing to install.

I build ventures for a living, and this is what building looks like when nobody is paying for it. One file, one weekend problem: my cube sat unsolved on my desk, and every tutorial assumed I wanted to memorise algorithms. I didn't. I wanted turn-by-turn directions.

Role
Designed & built solo
Form
One 116 KB HTML file
Solver
cubejs (Kociemba), bundled inline
Renderer
Hand-built CSS 3D, no WebGL
Status
Live, playable below
▶ Play with it See how it's built

Four screens, one promise

The whole product fits in four screens. Each one exists to keep a frustrated beginner moving: scan, turn, check, done.

CubeGuide home screen: GPS for your cube, with 3D live twin, fewest moves and no notation needed feature cards

HomeThe pitch in one line, three promises, one button. Nothing else to decide.

CubeGuide scan screen: an unfolded cube net being painted color by color, with camera scan and demo scramble options

ScanCapture each face with the camera, paint the net by hand, or load a demo scramble.

CubeGuide guide screen: turn the front face counter-clockwise, shown on a highlighted 3D cube next to the expected result

GuideOne move at a time: the twin on the left shows the turn, the right shows what you should see after.

CubeGuide solved screen: cube solved in 22 moves with time elapsed and share buttons

SolvedTime, move count, share. Then solve another one.

The design

Every cube tutorial teaches notation first and solving second. CubeGuide inverts that: it treats the cube like a navigation problem, and the user like a driver, not a student.

Decision 01

No notation, ever

Instead of "F' U R", the app says "Turn the Front face counter-clockwise, so the top edge rolls to the left", with the face named by its centre colour. The jargon never surfaces.

Decision 02

A twin, not a diagram

Two live 3D cubes: "Now, do this" with the turning face highlighted, and "Result", what your cube should look like after. Matching two pictures beats decoding one arrow.

Decision 03

One move per screen

A progress bar, "move 4 of 22", and a single confirm button. Undo and rescan are the escape hatches when hands slip. The user is never more than one step from recovery.

The methodology

Under the hood it is a pipeline: capture the cube's state, solve it optimally, then translate machine notation into human turns.

01
Capture the state

The camera scans each face square by square (with a manual paint-the-net fallback), keyed to the centre squares, which never move. The state is validated before solving: nine stickers of each colour, no impossible cubes.

02
Solve it properly

The state feeds a bundled cubejs implementation of Kociemba's two-phase algorithm, the same family of solver behind speed-cubing tools. It returns a solution around 20 moves instead of the 100+ of beginner methods.

03
Translate for humans

Each solver move is rewritten into plain language and rendered on the CSS 3D twin. The trickiest engineering was here: solver notation is defined cube-relative, screens are viewer-relative, and one sign error makes every animation turn the wrong way.

04
Verify at every step

The app tracks the expected state after each confirmed move. If reality drifts from the model, a mid-solve rescan re-anchors it, the cube equivalent of GPS rerouting.

Features

📷
Camera face scanPoint the camera at each face; a guided overlay captures the nine stickers.
🎨
Paint-the-net fallbackNo camera? Tap a colour, tap the stickers on an unfolded net.
🎲
Demo scrambleOne tap loads a valid scramble so anyone can try the guide without a cube.
🧭
Beginner & advanced modesPlain-language turns for beginners; compact notation for cubers.
↩︎
Undo & mid-solve rescanWrong turn? Step back, or rescan the cube and get a fresh route.
🏁
Timer, moves & shareFinish screen with solve time, move count and a shareable result.
Why this is on a venture builder's portfolio: it is the same discipline I apply to ventures, scope ruthlessly, ship something whole, and design for the least expert user in the room. Built solo, with AI as the pair-programmer.

Sixty seconds from scrambled to solving.
Try it with the demo scramble.