Yield UX: per-second, per-day, or per-milestone?

Every yield display makes an implicit promise about the underlying. A per-second ticker promises continuous accrual and instant liquidity. A daily NAV update promises a fund-like cadence. A milestone display, coupon paid, distribution complete, promises event-driven cashflows. Users calibrate their expectations to the display, not to the offering documents, and support inboxes fill up precisely where the display and the documents disagree.

Per-second tickers belong to instruments that genuinely rebase or accrue continuously, on-chain money market exposure being the clean case. Used there, the animation is honest and quietly mesmerising, and it converts. Used on a quarterly-distribution private credit fund, it is a small lie that compounds: the number climbs, the user tries to exit mid-period, and the gap between animation and mechanics becomes a trust incident.

Per-day updates are the workhorse for anything NAV-based. The pattern that performs best pairs the daily figure with its timestamp and source, NAV as of yesterday, published by the administrator, and shows accrued-but-undistributed income as a separately labelled line. Duller than a ticker. Far fewer support tickets.

Per-milestone displays fit event-driven instruments: coupons, rent distributions, waterfall payments. The effective design centres the next event, expected coupon date and amount, alongside a history of completed ones, and treats the interim period as exactly what it is, a waiting period, rather than faking motion. High-intent allocators respond well to this honesty; it mirrors how the instruments they already hold behave.

The industry's instinct is that motion converts, and for retail speculation it may. For allocators moving real size, the evidence across platforms points the other way: comprehension converts. The displays that correlate with funded accounts are the ones where a user can reconstruct the number, principal, rate, day count, next payment, without a support conversation. Three practices carry most of the weight: label whether a figure is realised or projected, show the calculation basis one tap away, and never animate faster than the underlying updates.

Match the display cadence to the slowest honest layer of the stack. If the asset accrues continuously but redemption settles in two days, the display should carry both truths. If NAV updates daily, nothing on the screen should move faster than daily. The test for any yield surface is brutal and simple: could the user predict, from the display alone, exactly what happens when they press withdraw? If yes, the design converts and retains. If no, the animation is borrowing trust it will have to repay with interest.