Kite Feature Requests
Share your ideas to help improve Kite.
We Want Your Ideas
Your feedback helps shape Kite's future. Tell us:
- What features would help you
- What's missing
- What could work better
How to Submit
Email: support@kite.app Subject: Feature Request: [Brief Description]
Include
| Information | Description |
|---|---|
| Feature | What you'd like to see |
| Use case | Why you need it |
| Benefit | How it would help |
| Priority | How important to you |
Feature Request Template
**Feature Summary**
[Brief description of the feature]
**Problem/Use Case**
[What problem does this solve? When would you use it?]
**Proposed Solution**
[How do you envision this working?]
**Benefits**
[How would this help you and others?]
**Priority for You**
[ ] Critical - Can't use Kite effectively without it
[ ] High - Would significantly improve my experience
[ ] Medium - Nice to have
[ ] Low - Just an idea
**Additional Context**
[Any mockups, examples, or other details]
Good Feature Requests
Example of Good Request
**Feature Summary**
Ability to duplicate schedule slots
**Problem/Use Case**
When building a schedule, I often have similar sessions
(same duration, same type) and need to create many slots.
Currently, I have to create each one from scratch.
**Proposed Solution**
Add a "Duplicate" button on schedule slots that creates
a copy with the same settings but blank title/speaker.
**Benefits**
- Save time building schedules
- Reduce errors from re-entering data
- Faster event setup
**Priority for You**
[X] High - Would significantly improve my experience
**Additional Context**
Similar to how "Duplicate Event" works, but for slots.
What Makes It Good
- Clear description
- Explains the problem
- Suggests a solution
- Describes benefits
- Provides context
Categories of Requests
Event Management
- Event creation
- Settings
- Team management
Call for Papers
- Submission process
- Evaluation
- Speaker management
Schedule
- Building tools
- Views
- Calendar features
Attendees
- Registration
- Check-in
- Networking
Communications
- Email features
- Templates
- Targeting
Reporting
- Analytics
- Exports
- Dashboards
Integrations
- New integrations
- Improved existing ones
What Happens Next
Our Process
- Received - We log your request
- Reviewed - Product team evaluates
- Prioritized - Based on impact and feasibility
- Roadmapped - If approved, added to roadmap
- Built - When scheduled for development
- Released - Feature goes live
Factors We Consider
- Number of requests
- Alignment with vision
- Technical feasibility
- Development effort
- User impact
Response
- We may not respond to every request individually
- Popular features may be announced publicly
- We won't share specific timelines
Tips for Better Requests
Focus on the Problem
Tell us the problem you're solving, not just the solution. There might be a better way.
Instead of:
"Add a button that does X"
Try:
"I need to accomplish Y because Z"
Be Specific
Vague requests are hard to act on.
Instead of:
"Make it better"
Try:
"Allow filtering submissions by multiple statuses at once"
Provide Context
- Your role (organizer, speaker, attendee)
- Your event size
- How often you'd use it
Already Requested Features
Before submitting, check if others have requested similar features. Your vote helps prioritize!
Common requests we're tracking:
- Mobile app
- More integrations
- Advanced reporting
- Additional languages
Thank You
Every feature request helps make Kite better. We appreciate you taking the time to share your ideas!
Previous: Report a Bug