User-facing text must describe what a person gets or does. Internal names, codes, and IDs are for the system. They are not for the user.
By Pawan Nayar · from the LLOS AI Learning record
User-facing text must describe what a person gets or does.
Internal names, codes, and IDs are for the system. They are not for the user.
A developer must use words that describe the user's experience. The text should not show internal system names or codes. These codes are like a secret language for the computer. Users do not understand this language. When users see internal codes, the product can feel unfinished or confusing. The text should always focus on the user's goal or action.
A developer creates a learning application. The application has different parts. One part is called 'F band' in the code. If the user sees 'Loading F band…', the user will not understand. The user will understand 'Opening your Discover journey…' because it describes what the user will experience.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
The word "band" is an internal term. It describes how content is organized for developers.
An AI model should never show internal codes like 'bandKey F/I/U/P' or 'section S1/S2'. It should not display format names like 'mcq_one_correct'.
A good plan for a design tool includes a detailed product document. This document describes all features.
An AI model can have hundreds of voices. These voices are grouped into categories.
User-facing text must describe what a person gets or does. Internal names, codes, and IDs are for the system. They are not for the user.