Application design

These articles focus on the decisions behind the fields: purpose, definitions, conditional paths, and review behavior. Start with the application checklist when you already know the product. Read the lender-form introduction when the collection stage is still unclear. For a specific card workflow, follow the product guide rather than importing assumptions from a generic loan form.

Use the collection to develop observable acceptance criteria. Every requested amount should have a defined period and currency; every significant action should have an accurate explanation. The goal is a specification your content, engineering, operations, and review teams can discuss together, not simply a shorter page.