search

cagov / odi-engineering

California Office of Digital Innovation engineering documentation
MIT License
2 stars 0 forks source link

Research alternatives to Tableau; document the drawbacks #85

Closed zakiya closed 1 year ago

zakiya commented 2 years ago

This could also become a blog post eventually

aaronhans commented 2 years ago

Here are the pieces related to this we've written so far and not turned into blog posts: Analysis of movement from Tableau -> D3 on covid19.ca.gov's main dashboard which resulted in 90% reduction in time to interactive: https://docs.google.com/document/d/18MboPkCXAqyf2__VORUp3A_u7wTRc8elFeDPsRwvix8/edit

There is a ton of research behind our Tableau switch because that was a big decision. We got amazing support from CDT who got Tableau's high level engineering and accessibility engineering teams on calls with us to try and eke out all the perf and a11y wins we could before we contemplated making a move to other tools. Here are notes from those meetings: https://docs.google.com/document/d/1DSzm-vnyUgA2qroizhSTJD3fKp8tfi4OeuCOuE8xPiQ/edit#

Here are pages we created out of that research that we used in presentations to CDT leadership to get them onboard with our new technical direction:

I think it is important to make a strong general use case for performance. Here is a paragraph with a lot of backup links written for Golden State Stimulus audit:

A lower performance score results in a poorer performance for site visitors. Slower sites have higher bounce rates, lower visitor conversion rates, lower user satisfaction levels and cause measurable physical stress for visitors.

Thanks for opening this ticket @zakiya

zakiya commented 1 year ago

Moved to Coda.