Roadmap

Shape Autoplot from real scientific work.

Tell us what your analysis needs next. Strong requests explain the blocked outcome and why it matters; thin requests prescribe a button without the experiment behind it.

Leaderboard

Demand signal, not a promise

Votes show us demand. Nothing is promised until a request is Accepted.

How to write one

A useful request has a spine

Thin: "Add a violin plot."
Better: "I need to compare skewed replicate distributions across batches without leaving the saved workspace."
Great: "I am preparing a materials paper with eight treatment groups. I need a distribution view that survives export, keeps labels readable, and lets me compare tails without rebuilding the figure in another tool."

Feature requests

Submit, vote, and track what changes.

Requests become public GitHub issues behind the scenes, but the program stays here on Autoplot's own site. Use the form for outcomes, context, and the surface where the problem appears.

Voting requires an Autoplot account because one person gets one vote. Discussion lives on the linked GitHub issue for the people who want implementation detail.

What cannot you do today? Why does it matter? Where in Autoplot? How often does this block you? How you picture it, if you already do

Contact email Public display name

Your email is kept private. The public issue shows your display name, request text, and chosen surface.

Public roadmap

Contributor leaderboard

Open

Loading...

Accepted

Loading...

Building

Loading...

Shipped

Loading...

Ready when you are

Have a sharper request? Send it through the roadmap form.