cloud-cost-dashboard-ux

Default the date selector to yesterday (index 1 in a reverse-chronological list) instead of today, since billing data from GCP BigQuery exports or AWS CUR lags by 4 to 24 hours. If current-day data is selectable, mark it with a badge like (Partial Data).

Sort change lists by the absolute dollar delta, Math.abs(current - prior), in descending order. This surfaces both unexpected spend spikes and large savings drops at the top, rather than sorting alphabetically or by total cost.

Cloud billing data is digested asynchronously, so the current day's data is partial or lagging by 4 to 24 hours. The apparent drop is an artifact of incomplete telemetry, not an actual spending decrease.

No. Pre-serialize granular daily service and SKU data as JSON maps inside the rendered HTML page, then handle search-as-you-type, sorting, and project filtering client-side. This avoids 1-3 second database latency and extra API costs.

Use soft material hues instead of plain primary colors: soft red like #c5221f with an indicator such as ▲ +$50.00 for increases, and soft green like #137333 with ▼ -$25.00 for decreases. This keeps an accessible, professional enterprise aesthetic.