PyBLE is developed in public. This roadmap communicates direction rather than promising dates; accepted work is tracked through GitHub issues and milestones.
- iPad external beta through TestFlight
- PBLE/1 editing, run/stop, console, and file workflows over BLE
- Offline Blockly with beginner GPIO and NeoPixel examples
- Browser installation for the exact
esp32-4mbandesp32-s3-n16r8profiles as the v0.4.2 hardware-tested beta; production Chrome install/recovery passed on both profiles - MIT-licensed app, agent firmware, protocol, website, tests, and release tools
- Complete the app, PBLE/1, resource, and remaining firmware release qualification for the exact v0.4.2 bytes
- Complete real-hardware qualification before enabling the ESP32-C3 installer
- Expand user-facing setup, recovery, and board-specific wiring guidance
- Open and document the Android beta distribution path
- Convert remaining pre-public planning references into focused GitHub issues
- Improve automated app-to-board integration coverage
- Stabilize public app and firmware release processes
- Publish a reusable PBLE/1 conformance kit for new board ports
- Define the maintainer process and evidence template for non-ESP32 ports
- Complete accessibility, localization, privacy, and security review
- Establish compatibility and deprecation guarantees for PBLE/1
PyBLE is not limited to ESP32. A proposed port should demonstrate:
- supported MicroPython execution;
- BLE GATT peripheral capability;
- a maintained PBLE/1 agent integration;
- sufficient flash, RAM, and runtime isolation;
- build and protocol-conformance results;
- transfer recovery and filesystem-safety behavior; and
- repeatable HIL evidence on an exact board profile.
Open an issue before substantial porting work so the compatibility contract and validation plan can be agreed first.