By ChartNothing Product Team · Updated · 6 min read
A worked explanation of a Hyperliquid Account Suite dashboard: which values lead, which charts are meaningful, and how the same feed is reduced for phone and watch surfaces.
Reading the account pulse
The worked Account Suite starts with account equity as the primary value and open PnL as the immediate change context. Withdrawable value and margin use help distinguish available capital from capital committed to positions. Position count, notional exposure, and leverage add scale without pretending that scale equals performance.
A negative open PnL is rendered with its sign and currency; a positive result is not silently converted into a percentage. Margin use remains a percentage. Keeping units separate prevents a visually tidy but misleading chart that overlays dollars, percentages, prices, and counts on one axis.
What belongs in a chart
Account-value and PnL history belong in line or area charts when the portfolio response contains at least two valid timestamped points. Position exposure can use bars when there are several positions to compare. A lone current position is better represented by a compact risk panel and detailed row because one bar has no trend and little comparative value.
The dashboard preserves the capture time and interval metadata. It does not manufacture intraday candles, reconstruct mark-price history, or infer past liquidation distances from the latest response. This keeps the example honest and makes missing history visible to the user and template builder.
- Account value history: currency line.
- PnL history: currency line or area with zero reference.
- Multiple positions: bounded exposure or PnL comparison.
- Single position: risk summary and table, not a decorative bar.
Reducing the feed for iPhone and Apple Watch
The full web page can show metrics, two history charts, and an open-position table. A medium iPhone widget has less room, so it uses the same feed but selects equity, open PnL, a short history sparkline, and freshness. The watch surface is smaller again: one primary value, one secondary value, a risk/freshness state, and a carefully reduced sparkline where the complication family permits it.
This is a reduction problem, not a separate data integration. Publishing the template marks one owner feed app-ready. Signed-in native account sync selects that feed and caches the latest widget payload for WidgetKit and watch surfaces.
What we inspect during a smoke test
A useful end-to-end test checks more than whether the request returned HTTP 200. We confirm that the wallet is preserved through sign-in, the connector records one logical run, current and historical responses merge correctly, the template validates against the payload, Publish to App sets the active recipe, and the native client can decode the same feed.
We also inspect failure states: an invalid wallet must stop before provisioning, a current-state failure must fail the run, unavailable history must not create a fake chart, and stale data must keep its captured time. Those checks are what turn a screenshot-friendly demo into a product contract.
Frequently asked questions
Why is notional exposure not the main chart?
Notional exposure describes position scale, not account performance. Equity, PnL, risk, and actual history usually answer the user's first questions more directly.
Can the example place or close trades?
No. It is read-only and does not request trading permission.
Does the phone show every web table column?
No. Native widgets use a deliberate compact projection of the same feed; the signed-in app can provide the fuller account view.