What was confusing while building this app

1) Events vs Markets is essential but unclear

The docs emphasize this distinction, but it is still easy to mix up event-level discovery versus market-level trading. A first-time builder benefits from a concrete example and a visual hierarchy early in the flow.

2) API key derivation wording is confusing

The phrase "Derivation of API keys" can sound like there is an API key to fetch from a dashboard. In practice, the key material is derived after L1 authentication with your wallet signature.

3) Post-signing outcome should be explicit

After successfully signing the EIP-712 message, docs should explicitly state that the app receives or derives:

• apiKey
• secret
• passphrase

This is much easier to understand when docs state the exact output shape up front, before code samples.

4) Allowance step should not imply funded balance requirement

A common uncertainty: do you need pUSD before running approvals? Technically, no — approvals can be signed with zero token balance. The important requirement is collateral balance at trade execution: pUSD for V2 flow and USDC.e for legacy flow.

5) "Set Allowances" needs clearer mental model

The step can feel opaque unless users know exactly what is being approved and for which contracts. Showing the four approvals with contract roles and success verification helps reduce confusion.

Suggested clarity improvements

• Add a visual event → market example before any API calls.
• Rename API key section to "Derive L2 credentials from wallet signature".
• Show exact credential output fields immediately after auth explanation.
• Clarify preflight: "Approvals do not require balance; trading requires flow collateral (pUSD on V2 / USDC.e on legacy)".
• List each approval target with plain-English contract purpose.