Form Field Types

Rytinco Forms includes 9 powerful field types to help you collect exactly the data you need. Each field type is optimized for specific use cases and includes validation and customization options.

Text Field

Single Line Text Input

Best For:

• Names (first name, last name, full name)
• Short answers (city, company name, job title)
• ID numbers, reference codes
• Single-word or short-phrase responses

Configuration Options:

• Placeholder - Hint text (e.g., “Enter your full name”)
• Maximum Length - Limit characters (e.g., 50 characters)
• Required - Make field mandatory
• Validation - Pattern matching for specific formats

Example Uses:

Field Title: "Full Name"
Placeholder: "John Smith"
Required: Yes
Max Length: 100

Comment Field

Multi-Line Text Area

Best For:

• Detailed feedback or comments
• Long-form answers
• Open-ended questions
• Additional notes or information

Configuration Options:

• Rows - Height of text area (3-10 rows)
• Maximum Length - Character limit (up to 5,000)
• Placeholder - Example response
• Required - Mandatory completion

Example Uses:

Field Title: "How can we improve?"
Placeholder: "Tell us about your experience..."
Rows: 5
Required: No

Tip

Comment Field Tips:

• Use for questions that need detailed responses
• Keep optional unless truly required
• Consider character limits for data management

Email Field

Validated Email Input

Best For:

• Email address collection
• Newsletter signups
• Contact forms
• Account creation

Built-in Validation:

• Format Checking - Validates email structure
• Domain Validation - Checks for valid domain
• Required - Mandate email entry
• Unique Check - Prevent duplicate emails (optional)

Example Uses:

Field Title: "Email Address"
Placeholder: "you@example.com"
Required: Yes
Validation: Strict format checking

Email Field Features

Auto-complete:

• Suggests common email domains
• Works on mobile keyboards
• Improves completion speed

Error Messages:

• Clear validation feedback
• “Please enter a valid email address”
• Helps users correct mistakes

Phone Field

Phone Number Input

Best For:

• Contact phone numbers
• SMS marketing opt-ins
• Appointment callbacks
• Support line contacts

Configuration Options:

• Country Code - Default country prefix
• Format Validation - Specific format requirements
• Required - Mandatory field
• Placeholder - Example number

Example Uses:

Field Title: "Phone Number"
Placeholder: "+27 82 123 4567"
Country: South Africa
Required: Yes

South African Considerations

Local Format Support:

• Accepts local formats (082 123 4567)
• International format (+27 82 123 4567)
• Validates South African mobile prefixes

Radio Group Field

Single Choice Selection

Best For:

• Mutually exclusive options
• Yes/No/Maybe questions
• Selecting one from many
• Clear, distinct choices

Configuration Options:

• Options - List of choices
• Default Selection - Pre-selected option
• Required - Must select one
• Layout - Vertical or horizontal

Example Uses:

Field Title: "Preferred Contact Method"
Options:
  - Email
  - Phone
  - WhatsApp
Required: Yes
Layout: Vertical

Best Practices

Option Ordering:

• Most common first
• Alphabetical for long lists
• Logical progression (e.g., sizes: Small → Medium → Large)

Number of Options:

• 2-5 options ideal
• Use Dropdown for 6+ options
• Avoid overwhelming users

Checkbox Field

Multiple Choice Selection

Best For:

• Select multiple items
• Interest/skill selection
• Feature preferences
• Agreement checkboxes

Configuration Options:

• Options - List of choices
• Default Selections - Pre-checked items
• Required - Must select at least one
• “Select All” - Option to select all choices

Example Uses:

Field Title: "Interests (Select all that apply)"
Options:
  - Marketing
  - Technology
  - Design
  - Business Strategy
  - Other: [text field]
Required: At least one

Special: Single Checkbox

Use a single checkbox for:

• Terms and conditions agreement
• Newsletter opt-in
• Consent confirmations
• “Remember me” options

Dropdown Field

Select from List

Best For:

• Long lists of options (6+)
• Country/region selection
• Department/role selection
• Date selection (month, year)
• Saving space on form

Configuration Options:

• Options - List of choices
• Default Selection - Pre-selected value
• Required - Must select one
• Placeholder - “Select an option…”
• Searchable - Type to filter options (for long lists)

Example Uses:

Field Title: "Country"
Options: [All 190+ countries]
Placeholder: "Select your country"
Required: Yes
Searchable: Yes

Dropdown vs Radio

Use Dropdown When:

• More than 5 options
• Space is limited
• Options have natural order (countries, dates)

Use Radio When:

• 5 or fewer options
• All options should be visible
• Quick selection is important

Rating Field

Star or Number Rating

Best For:

• Satisfaction surveys
• Product reviews
• Service ratings
• NPS-style scoring
• Quick feedback collection

Configuration Options:

• Scale - 1-5 stars or 1-10 points
• Labels - Text for min/max (e.g., “Poor” / “Excellent”)
• Required - Must provide rating
• Half Stars - Allow 0.5 increments (optional)

Example Uses:

Field Title: "How satisfied are you with our service?"
Scale: 1-5 stars
Labels:
  - 1 star: "Very Dissatisfied"
  - 5 stars: "Very Satisfied"
Required: Yes

Rating Scale Guidelines

1-5 Scale:

• Use for general satisfaction
• Easy to understand
• Quick completion

1-10 Scale:

• Use for detailed feedback
• NPS calculations
• More granular data

Labeling Tips:

• Always label the extremes
• Use clear, emotional language
• Match labels to context

Boolean Field

Yes/No Toggle

Best For:

• Simple binary decisions
• Opt-in/opt-out questions
• Confirmation steps
• True/false data collection

Configuration Options:

• Labels - Custom Yes/No text
  • Default: “Yes” / “No”
  • Custom: “Accept” / “Decline”, “Opt In” / “Opt Out”
• Default State - Start as Yes or No
• Required - Must make a choice

Example Uses:

Field Title: "Subscribe to our newsletter?"
Labels:
  - Yes: "Yes, keep me updated"
  - No: "No, thanks"
Default: No
Required: Yes

Common Boolean Use Cases

Marketing Consent:

"I agree to receive marketing emails"
Yes: "Yes, I agree"
No: "No, I don't want marketing"

Terms Acceptance:

"I agree to the terms and conditions"
Yes: "I Agree"
No: "I Do Not Agree"
Required: Yes (form won't submit without Yes)

Feature Enablement:

"Enable notifications?"
Yes: "Yes, notify me"
No: "No, disable notifications"

Field Combinations

Common Form Patterns

Contact Form:

1. Text (Name) - Required
2. Email (Email) - Required
3. Phone (Phone) - Optional
4. Comment (Message) - Required

Event Registration:

1. Text (Full Name) - Required
2. Email (Email) - Required
3. Phone (Contact Number) - Required
4. Dropdown (Ticket Type) - Required
5. Radio (Dietary Requirements) - Required
6. Checkbox (Workshop Sessions) - Optional

Feedback Survey:

1. Rating (Overall Satisfaction) - Required
2. Radio (How did you hear about us?) - Required
3. Checkbox (What did you like?) - Optional
4. Comment (Additional feedback) - Optional

Order Form:

1. Text (Customer Name) - Required
2. Email (Email) - Required
3. Phone (Phone) - Required
4. Dropdown (Product) - Required
5. Radio (Size/Variant) - Required
6. Boolean (Express Shipping?) - Optional

Validation and Logic

Field Validation

Required Fields:

• Marked with asterisk (*)
• Form won’t submit if empty
• Clear error messages

Format Validation:

• Email: Must be valid format
• Phone: Must match expected pattern
• Text: Can enforce character limits

Conditional Logic

Show/Hide Fields:

• Show additional fields based on previous answers
• Example: Show “Other” text field when “Other” is selected
• Keep forms clean and relevant

Mobile Considerations

Field Type Mobile Behavior

Optimized for Touch:

• Radio buttons: Large tap targets
• Checkboxes: Easy to select
• Dropdowns: Native mobile picker
• Rating: Touch-friendly stars

Keyboard Types:

• Email: Shows @ and .com shortcut
• Phone: Shows numeric keypad
• Text: Standard keyboard

Next Steps

Learn how to manage responses:

→ Form Responses

Return to Forms overview:

→ Forms Overview

---

Looking for advanced form features? Contact support to learn about custom validations and integrations.