01

The short answer

Choose Arduboy FX-C if you want constrained Arduino C++ development, a tiny monochrome screen and direct open-source hardware culture; choose Playdate if you want a higher-level Lua/C SDK, simulator, larger display, sound and crank input. On either platform, finish a one-screen game with one verb, one failure state and a restart before adding progression or content.

Programmers and game-design beginners deciding between a deliberately tiny Arduino handheld and a more capable commercial handheld SDK.

02

Before you start

Have these basics ready before choosing parts or flashing firmware.

  1. An Arduboy FX-C or Playdate and the platform’s supported development environment.
  2. Basic programming in C++ for Arduboy or Lua/C for Playdate.
  3. A one-sentence game rule and simple original placeholder art/audio.
03

Choose by constraint and distribution

Arduboy FX-C: You enjoy microcontroller constraints, Arduino C++ and a 1-bit minimalist presentation.

Playdate: You want Lua iteration, a simulator, richer audio/display capability and crank-specific design.

04

Choose one mechanic

Write one sentence: “The player does X to avoid or collect Y.” Pick a mechanic that fits the native controls and can be demonstrated without menus or a tutorial.

  1. One playable character or cursor.
  2. One goal and one fail condition.
05

Install the supported toolchain

For Arduboy, begin with the Arduboy2 library examples in a supported Arduino environment. For Playdate, install the official SDK, run a sample in the simulator and confirm deployment to hardware.

  1. Keep the untouched sample building.
  2. Record toolchain and SDK versions.
06

Build the game loop

Implement input, update and draw as separate steps. Use fixed or bounded timing, reset state from one function, and keep collision rules simple enough to inspect.

  1. Display a score or clear progress state.
  2. Make restart take one button.
07

Design for the actual screen

Use high-contrast silhouettes and test on hardware early; simulator scaling can hide unreadable details. On Playdate, use the crank only when it improves the mechanic rather than as decoration.

  1. Avoid tiny text.
  2. Test motion for flicker and clarity.
08

Study examples without copying

Read an example to learn project structure, asset loading and input patterns, then write your own small loop. Check repository licenses before reusing code, art or audio, and preserve required notices.

  1. Keep a third-party-attribution file.
  2. Use original placeholder assets by default.
09

Finish and package

Add a title, pause or exit behavior, one-minute playtest and clear version number. Give the build to another person without explanation and fix the first point where they cannot start, understand or restart.

  1. Package only required assets.
  2. Write controls in one screen or README.
10

Safety and legal notes

Use code, fonts, art, music and sound only under licenses that permit your intended distribution. Follow each platform’s publishing rules and age/content requirements, and avoid flashing unofficial images to hardware unless you understand the recovery and warranty implications.

  1. Credit dependencies exactly as their licenses require.
  2. Use headphones and sound levels responsibly during repeated testing.
11

Troubleshooting

The game timing differs between simulator and device. Use the platform timing APIs, avoid frame-rate assumptions and profile on hardware.

The build no longer fits or runs reliably. Remove unused assets, inspect memory/storage limits and revert to the last known-good milestone.

Controls feel unresponsive. Separate edge-triggered presses from held input and test button handling at low and high frame load.

12

Next steps

Keep the next experiment small and reproducible.

  1. Compile and run an official sample.
  2. Build a one-screen gray-box prototype.
  3. Conduct one no-instructions playtest and ship version 0.1.