> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flow-board.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Text Input

> Use Text Input to collect typed responses such as names, emails, numbers, or short notes.

## What it is

**Text Input** collects a typed response from the user.

## What it's best for

Use it when the answer is free-form and should be entered directly rather than chosen from a list.

## When to use it

* Name
* Email
* Website or profile link
* Numeric answers
* Short or multi-line feedback

## When not to use it

* Do not use it when the answer comes from a short list of options. Use [Selection List](/components/selection-list) or [Wheel Picker](/components/wheel-picker).
* Do not ask for more typed fields than the screen truly needs.

## How to add it in the dashboard

1. Open the screen in the dashboard.
2. Add **Text Input** from the **Components panel**.
3. Select the field on the **canvas**.
4. In the **properties panel**, set the label, placeholder, and input behavior.
5. Adjust styling so the field feels easy to notice and easy to complete.

## Key parameters

| Parameter           | What it changes                                  | When to adjust it                                                |
| ------------------- | ------------------------------------------------ | ---------------------------------------------------------------- |
| Label               | Tells the user what to enter                     | Use concise language with one clear request                      |
| Placeholder         | Shows example or guidance inside the field       | Use it to reduce hesitation before typing                        |
| Keyboard type       | Matches the keyboard to the expected answer      | Use email, number, phone, or URL when relevant                   |
| Auto-capitalization | Changes how typed text is capitalized            | Use it to reduce formatting errors                               |
| Required            | Marks the field as necessary                     | Enable it only when the answer is truly essential                |
| Background          | Changes the field fill                           | Use it to create contrast against the screen background          |
| Text styling        | Changes the appearance of the user’s typed text  | Adjust it for readability and brand fit                          |
| Label styling       | Changes the look of the field label              | Use it to keep form hierarchy clear                              |
| Placeholder styling | Changes the look of helper text inside the field | Use it when the field needs more guidance but should stay subtle |
| Border and radius   | Controls the field outline and shape             | Use it to make the field feel more defined or softer             |
| Padding             | Controls inner breathing room                    | Increase it when the field feels cramped                         |

## Example use cases

* Ask for an email before sending a personalized plan
* Capture a first name to tailor the next screen
* Collect a short goal statement before suggesting a product path

## Best practices

* Keep the label specific and short.
* Use the right keyboard type to reduce friction.
* Ask only for the information needed for the next decision or experience.
* Keep form screens short and easy to complete.

## Common mistakes

* Using vague labels such as “Information”
* Adding too many fields to one screen
* Relying on placeholder text instead of a clear label

## Related components

* [Selection List](/components/selection-list)
* [Wheel Picker](/components/wheel-picker)
* [Text](/components/text)
* [Button](/components/button)