pydevices-examples
Examples, integration guides, and an installable PyScript gallery for the PyDevices driver stack.
PyDevices examples show a portable driver stack
A repository of examples, integration guides, and a browser runnable PyScript gallery for the PyDevices driver ecosystem across MicroPython, CircuitPython, and CPython.
What the examples repository demonstrates
This repository is the examples, integration documentation, and browser gallery for the PyDevices driver ecosystem. The README is clear that the reusable product source lives in a separate repository called pydevices, so this repo is not the package source of truth. Instead it shows the portable driver stack in action. The README names several libraries that make up that stack. displaydev and audiodev provide portable display and audio interfaces. events, keys, and multimer provide shared event, key, and timing primitives. appdev is an optional application traffic controller for non LVGL apps. board_configs, board_peripherals, and the hardware drivers connect those interfaces to real boards and to desktop or browser hosts. The README says those libraries are designed to work across MicroPython, CircuitPython, and CPython on microcontrollers, Linux, Windows, Android, browsers, and notebooks. This repository demonstrates that portability by running the same examples in different environments. It is marked alpha quality, with a note that the organization is being prepared for its first external users, so names and APIs may still evolve. For a reader, the value is seeing real code that already runs on many targets rather than reading only abstract claims about portability. The README keeps the focus on demonstrating behavior instead of replacing the main package.
How to try the examples in a browser
The README points to the fastest route as the interactive PyScript gallery, which runs the real examples directly in a modern web browser. The link is given as a page under the project's GitHub Pages site, in the pyscript folder. Because it uses PyScript, the Python examples execute in the browser without a local install, which lowers the barrier to a first look. The README also mentions a standalone browser app or offline PWA as another way to run the examples, built from the same gallery. Screenshots in the README show two example scripts by name. One is paint.py, shown as a paint demo. The other is tiny_toasters.py, shown as an animated graphic. These give a concrete sense of what the driver stack can draw and do on a display. The documentation and product packages are linked from the README, with the pydevices documentation and the product packages site listed as places to go deeper. For someone evaluating PyDevices, opening the PyScript gallery first is the recommended step, since it proves the examples run without setting up a microcontroller or a Python environment. Only after that would you move to the local install and the board specific guides. The gallery is the lowest friction way to confirm the stack works.
How the driver stack stays portable
The README explains portability as a design property of the underlying libraries rather than a feature of this examples repo. The interfaces, displaydev and audiodev, are written to be portable, and the primitives events, keys, and multimer are shared so behavior is consistent across hosts. The board_configs, board_peripherals, and hardware drivers are the layer that maps those interfaces onto real hardware and onto desktop or browser hosts. Because the same interfaces are used everywhere, an example written against displaydev runs on a microcontroller through MicroPython, on a desktop through CPython, and in a browser through PyScript, with the board specific pieces swapped underneath. The README says the libraries target MicroPython, CircuitPython, and CPython across microcontrollers, Linux, Windows, Android, browsers, and notebooks, which is a broad spread of runtimes from one API. appdev is optional and only enters the picture for non LVGL applications that need an application traffic controller. The note that this repository is alpha quality and not the source of truth sets expectations: the APIs shown may change before the first stable external release. The takeaway is that the examples exist to prove the portability claim by running identical code on very different machines, which is the point of shipping a gallery rather than only docs.
Editorial conclusion
The examples repository is written in Python under the MIT license and is marked alpha quality, with the real package source living in the separate pydevices repository while this one demonstrates portability through a PyScript gallery that runs in a web browser.
Community notes