# Avogadro 2.2 Roadmap

**URL:** <https://discuss.avogadro.cc/t/avogadro-2-2-roadmap/7560>\
**Category:** Development\
**Created:** [September 13, 2026, 7:51pm UTC](https://discuss.avogadro.cc/t/avogadro-2-2-roadmap/7560 "2026-09-13T19:51:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ghutchis](https://discuss.avogadro.cc/user_avatar/discuss.avogadro.cc/ghutchis/32/456_2.png) [@ghutchis](https://discuss.avogadro.cc/u/ghutchis)\
**Post date:** [October 24, 2026, 8:29pm UTC](https://discuss.avogadro.cc/t/avogadro-2-2-roadmap/7560/2 "2026-10-24T20:29:43Z")

</div>

I was thinking about this more broadly as I finished up the 2.1 release and what I wrote in the [long-term vision](https://discuss.avogadro.cc/t/long-term-vision/7557) thread.

I’ll probably revise this over time. **The target date for v2.2 will be 06-Feb-2027** with a string-freeze about 3 weeks earlier.

### Accessibility:

- Add a unified settings dialog, including color options, font sizes, etc.
  - Likely tweaking a few key issues, e.g. F / H contrast, colors options for non-covalent and close-contact rendering, selections…

- Further work on keyboard access for everything
- (ideas welcome)

### Performance:

- Improved rendering speed (e.g., handling trajectories with ~1M atoms at ~60 fps)
  - Right now on my MacBook, I’m getting

- Batched charges for electrostatic potentials
- Molecule speed (i.e., we’re currently copying around entire cubes at times)

### Code Quality:

- Continue improving test coverage / fuzz tests (~70-80% in core, less in rendering and qtplugins)
- Continue modernizing with `clang-tidy` likely with `good-first-issue` and `help-wanted` issues

### Automation / Scripting / RPC:

- Complete the set. Get as many features with RPC commands as possible, not only for automation but because it increases **testing**.

---

_[View the full topic](https://discuss.avogadro.cc/t/avogadro-2-2-roadmap/7560)._