Skip to content

Conversation

@LiamConnors
Copy link
Member

@LiamConnors LiamConnors commented Dec 31, 2025

image

@LiamConnors LiamConnors changed the title Add scatter app Add embedded Plotly Studio scatter plot builder app Jan 2, 2026
@LiamConnors LiamConnors marked this pull request as ready for review January 2, 2026 17:44
@red-patience
Copy link
Contributor

Neat idea, but I feel like this is the sort of thing we'd use as a consistent pattern or not at all. The idea is to teach folks how to construct their px.scatter params using a tool where they can immediately validate the result?

@Coding-with-Adam
Copy link
Contributor

Neat idea, but I feel like this is the sort of thing we'd use as a consistent pattern or not at all. The idea is to teach folks how to construct their px.scatter params using a tool where they can immediately validate the result?

Good questions @red-patience . Yes, the goal is to teach users how to construct a scatter plot by playing with various parameters. By interacting live with parameter changes (dropdowns) and seeing how the code updates, I was hoping that it would give them a better understanding of how parameter modifications affect the visualization.

And I was hoping to build similar apps for the other common visualizations (bar, pie, line, and others that you and Liam think we should add)

@red-patience
Copy link
Contributor

Neat idea, but I feel like this is the sort of thing we'd use as a consistent pattern or not at all. The idea is to teach folks how to construct their px.scatter params using a tool where they can immediately validate the result?

Good questions @red-patience . Yes, the goal is to teach users how to construct a scatter plot by playing with various parameters. By interacting live with parameter changes (dropdowns) and seeing how the code updates, I was hoping that it would give them a better understanding of how parameter modifications affect the visualization.

And I was hoping to build similar apps for the other common visualizations (bar, pie, line, and others that you and Liam think we should add)

Okay, that's what I thought, thanks for confirming @Coding-with-Adam. Several concerns.

  • Does the Cloud SRE team know about this initiative? We get good traffic on these docs and we can lose user trust when the a part of the page looks broken because of Cloud downtime.

  • There's already a ton going on on this page. I'm hesitant to add another call to action/learning method. Do we know for a fact that this is addressing a need that the page wasn't before? The audience for this page is probably the most code-savvy of all our docs―are the existing examples on the page not enough to help them write 5 basic LOC? I dunno, as a reader this strikes me as "The author doesn't know how to best teach this content so they're throwing a lot of different things at the wall hoping something sticks.")

  • As a user I would expect a tool like this to allow me to experiment with all the different types of scatter plots described on this page, but it looks like it's fairly limited. I can map axes, colours, etc to column names and see the graph change―cool. I'm not familiar with the sample dataset so I still have to translate any learnings to my dataset (but I can't see the sample dataset so I don't even know if it makes sense to model my work from a scatter plot I built using this tool). Feels like I'll just hit a wall really fast and then have to do some local work to keep testing.

  • Additionally, I would want to be extra clear that this is a "meta" app:

    • Not sure I like "builder" in the app title. I see the intention but I feel like we should reserve this term for App Studio contents or App Studio itself. Thoughts on "sandbox" or "playground"? Similarly, the app description should be clearer about its purpose.
    • I'd recommend adding language like "This playground is a Dash app that renders a scatter plot using Plotly Express. It uses Dash core components (link) to add controls for updating the scatterplot. The changes that you make via these controls also update the underlying code, which is printed for demonstration purposes." But even then, folks might notice small changes in that code compared with the examples on the doc page ("why is there no fig.show()?"), which could be enough to create confusion.
  • More distributed sample apps to maintain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants