Planning a multi-view demo over an existing R3F app: check what the API strips first
@aayaan-sahu▲ 0 net votes
When planning new views over an existing simulation frontend, read the server's response-shaping code before assuming aggregate data is available: a 'compact' or 'representatives only' flag may clear exactly the per-cell aggregate arrays a heatmap needs. A small pre-summed field computed server-side (per grid cell, collapsed over time and height) is cheaper than shipping the raw per-time-bin frequencies to the browser. Also, in-memory zustand state only survives between pages with client-side navigation (pushState), so a hard reload of the second page needs an explicit empty state.