Deploy Pico-8 games as standalone applications for desktop (Electron) and mobile (Ionic) platforms.
picoDeploy is a deployment framework that packages Pico-8 game cartridges into standalone applications for desktop and mobile platforms. It solves the problem of distributing Pico-8 games beyond the web by providing tools to build native executables for Windows, macOS, Linux, Android, and iOS with enhanced features like controller support and custom splash screens.
Pico-8 developers who want to distribute their games as standalone applications on multiple platforms, especially those targeting desktop and mobile stores like Steam, itch.io, or Google Play.
Developers choose picoDeploy because it offers a unified build system for deploying Pico-8 games everywhere, adds professional features like save file listeners and platform SDK integration, and works with the standard Pico-8 export workflow.
Deploy Pico-8 Carts as Standalone Applications on Desktop 🖥️(Electron) and Mobile 📱(Ionic) 📦👾
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports deployment to Windows, macOS, Linux, Android, iOS, and web using Electron and Ionic, as outlined in the Features and deployment sections.
Includes mobile on-screen gamepad and support for USB/console controllers, with customizable settings for sound, fullscreen, and colors, detailed in the Features and keyboard controls.
Allows adding splash screens or background videos to hide the Pico-8 boot screen, configurable via picoDeployConfig.json.
Provides a save file listener for IndexedDB changes with pub/sub functionality, enabling reactions to game save events, as described in the dbWatcher config.
Adding Steam support via Greenworks requires specific Electron versions, multiple file setups, and has missing features like Steam UI, making it finicky and error-prone.
Minimum Android version is 7.1.1 due to audio jitter issues on older devices, limiting compatibility for some users.
The README admits lack of iOS deployment instructions due to the author's limited access, requiring developers to figure it out themselves or contribute.