> ## Documentation Index
> Fetch the complete documentation index at: https://learn.playlab.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Adding starter inputs
> Collect information from users before they start interacting with your app. Covers all input types, configuration, and best practices.
Starter inputs let you collect information from users before they begin interacting with your app. They make conversations more focused, structured, and personalized.
**Preview required**
Always preview your app to test how starter inputs behave. Confirm they collect the right information and that required fields appear as intended before sharing.
**Why this matters**
Well-designed starter inputs streamline interactions, collect what you need upfront, and make your app more useful. They are often essential for purposeful, structured conversations.
## Watch how to add starter inputs
A short walkthrough of building with starter inputs in a Playlab app.
## How to add starter inputs
On the right-hand navigation in your app editor, click the **Inputs** button. The starter inputs configuration panel opens.
Click **Add Starter Input** to begin.
Pick from the available input types:
* **Short Text:** brief responses like names or short answers
* **Long Text:** longer responses like descriptions or feedback
* **Dropdown:** select a single option from predefined choices
* **Checkbox:** select multiple options from predefined choices
* **File Upload:** accept files up to 5MB (images, PDFs, CSVs, and more)
For each input, set:
* A clear, descriptive label
* Whether the input is required or optional
* Helpful placeholder text to guide users
* At least two options for dropdowns
* Multiple options for checkboxes (users can pick any combination)
Arrange inputs in a logical order, then preview your app to test them.
Reference the collected information in your app's instructions and prompts. Update prompts to incorporate user-provided data, test how the inputs change the conversation, and refine based on what you see.
## Best practices
A few patterns that have worked:
**Keep it focused.** Only ask for information that is essential for your app to work.
**Match the input type to the data.** Short text for names; long text for detailed feedback; dropdowns for single-choice; checkboxes for multi-select; file upload for documents or images.
**Make labels clear and specific** so users know exactly what to provide.
**Use placeholder text** to give examples or clarification.
**Arrange inputs in a logical sequence** that matches the flow you want.
**Balance required and optional fields.** Too many required fields can feel overwhelming.
**Test with different inputs** to make sure your app handles every response gracefully.
**Preview before publishing** so you experience your app from the user's side.
## FAQ
Five types: **Short Text** for brief responses, **Long Text** for extended responses, **Dropdown** for single-choice from predefined options, **Checkbox** for multi-select from predefined options, and **File Upload** for files up to 5MB (images, PDFs, CSVs, and more).
There is no strict limit, but keep them focused. Too many inputs creates friction and overwhelm. Ask only for what your app actually needs to function.
Yes. Be aware that removing inputs returning users have relied on can create confusion, and adding new required inputs can break the experience for them. For significant changes, consider a new version of your app.
Reference specific inputs in your app's instructions and prompts, customize the conversation flow, process uploaded files for relevant data, and use checkbox selections to personalize responses.
Yes, every user who opens your app sees the configured starter inputs. If you need different inputs for different audiences, create separate versions of the app.
Your app proceeds without that data. Make sure your app's logic handles missing optional inputs gracefully.
Yes. Files uploaded through starter inputs can be processed in your app: analyzing CSV data, extracting text from PDFs, or using images as reference material. Include instructions in your app for how to handle uploads.
**Dropdown** when users should pick exactly one option from a limited set. **Checkbox** when users might pick multiple options that aren't mutually exclusive. Both ensure consistent, predictable responses and prevent typos compared to free text.
## Need support?
Email [support@playlab.ai](mailto:support@playlab.ai) if you run into any issues with starter inputs.
***
Last updated: 05-13-2026