List view

• Embedded

  We want to support physical computing with an arduino like interface that would work with a different microcontrollers (esp32, RP235x, etc...)

  Due by June 30, 2027
  0% complete0 open0 closed

• WASM

  We have some WASM support, but we want to go as far as being able to support projects like p5.js

  Due by May 31, 2027

  •0/4 issues closed
  0% complete4 open0 closed

• GUI

  We want to enable our users to easily make GUIs with our API. We have a great opportunity to leverage bevy in this regard.

  Due by March 31, 2027

  •0/1 issues closed
  0% complete1 open0 closed

• Audio

  bevy is working to bring a more robust audio engine into their project (https://github.com/CorvusPrudens/bevy_seedling) You can play sounds, apply effects, and route audio anywhere.

  Due by January 31, 2027

  •0/5 issues closed
  0% complete5 open0 closed

• Modern File Formats & Protocols

  We should be able to competently use modern file formats and be able to easily be a part of creative workflows involving professional software. Additionally, we want to support protocols such as CAN, OSC, and DMX

  Due by November 30, 2026

  •0/5 issues closed
  0% complete5 open0 closed

• Full Processing API Coverage

  libprocessing needs to support [Processing](https://github.com/processing/processing4)'s visual engine at the very least. We want to get coverage for all of it https://processing.org/reference

  Due by April 30, 2027

  •0/1 issues closed
  0% complete1 open0 closed

• SIGGRAPH 2026

  Tasks we'll want to accomplish before demoing progress at SIGGRAPH

  Due by July 13, 2026

  •0/1 issues closed
  0% complete1 open0 closed

• Documentation

  We have some documentation. We would like to set a baseline with more of it. * Architecture * How to contribute * Tutorials * Examples from the community

  Due by September 30, 2026

  •0/7 issues closed
  0% complete7 open0 closed

• Stabilization

  Currently we have been living on the edge. The bevy development branch, large gestures of feature development (rightfully) tossed in, without a testing strategy, or continuous integration. In support of [Processing](https://github.com/processing/processing4) we want to ensure that we are able to develop with confidence and able to trust more people to contribute to the project. For this milestone, we would like to: * Know when our examples break * Add visual testing * Version lock our bevy dependency * Set up continuous integration * Be in a state that inspires confidence as we bring a libprocessing powered renderer to Processing

  Due by August 17, 2026

  •0/7 issues closed
  0% complete7 open0 closed