What it means
JSON is the most common interchange format for structured model output: field names, typed values, and arrays the product can validate and render predictably.
Why designers should care
JSON-backed flows need visible schemas, field-level errors, and preview states so users trust machine-readable output before it hits production systems.
Example
A “Generate API spec” tool returns JSON with endpoints and params; the UI renders an editable table, highlights invalid types, and exports only after validation passes.
Common mistakes
- Showing raw JSON blobs with no field labels or human-readable preview.
- Assuming the model always returns valid JSON without retry or repair UX.
- Hiding structure from non-technical users who still need to approve content.
Frequently asked questions
What is JSON?
JSON (JavaScript Object Notation) is a lightweight text format for structured data: keys, values, arrays, and nested objects that machines parse reliably.
Why should designers care about JSON?
JSON-backed flows need visible schemas, field-level errors, and preview states so users trust machine-readable output before it hits production systems.
What are common mistakes with JSON?
Showing raw JSON blobs with no field labels or human-readable preview; Assuming the model always returns valid JSON without retry or repair UX; Hiding structure from non-technical users who still need to approve content.