WeDispatch 1.2.1: My audios and the usage panel
A short update in the wake of the client-area redesign: the My audios screen and the monthly usage panel both gain robustness.
Version 1.2.0 redrew ten screens of the client area. As often after a redesign on that scale, a few adjustments followed close behind. Here they are.
The My audios screen
The client area is rendered on the server, then the interactive parts (the search box, the filters, the "load more" button) take over in your browser. My audios is the screen that leans on that handover most, since it combines a list, three filters and a counter that switches between singular and plural on its own.
Its internal organisation has been reworked so each side has directly what it needs, without depending on the other. The screen opens more crisply, and its mechanics are considerably easier to build on.
The usage panel, made defensive
The panel showing your monthly usage on the overview screen depends on a database read. It is now isolated: if that read answers badly, the panel disappears and the rest of the page carries on displaying normally. An unavailable figure should never cost you a whole screen, a rule we are applying gradually everywhere a panel depends on an external source.
One more check before every release
Client-area screens are computed on demand, per account and with that account's data: they are never built at compile time. So we added a check to our verification chain that reads the code rather than rendering it, and refuses to let server and browser share what cannot be shared. It was run across all ten redrawn screens and now runs before every release.
What comes next
Next up on our side: an automated verification pass that opens every dashboard screen with a genuinely loaded account, on top of the unit tests. It is the best way to see the client area the way you see it.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo