Feature Request Examples: 12 Real Ones (and How to Write Yours)

A great feature request is easy to spot and surprisingly rare. It names a real problem, not just a pet solution, and gives just enough context to be actionable. Below are twelve examples across common product types, followed by a simple formula you can reuse. Whether you're a user writing requests or a team teaching users how, these show the shape of a good one.

What makes a request good

The best requests lead with the problem, then suggest a solution. "Add a dark mode" is fine, but "Reading the app at night strains my eyes — a dark mode would help" tells you why, which lets you judge priority and maybe find a better fix. Specific beats vague; problem beats feature; one idea per request beats a bundle.

12 feature request examples

1. "Let me export my data as CSV." Problem: I need my reports in a spreadsheet and I'm copying rows by hand.
2. "Add keyboard shortcuts for common actions." Problem: I use this all day and the mouse slows me down.
3. "Support recurring reminders, not just one-time." Problem: I re-create the same reminder every week.
4. "Allow multiple users on one account." Problem: My teammate needs access but we share one login, which is messy.
5. "Add a dark mode." Problem: The bright screen is hard on my eyes at night.
6. "Let me reorder items by drag and drop." Problem: Reordering by editing numbers is tedious.
7. "Send a weekly summary email." Problem: I forget to check the dashboard and miss changes.
8. "Add an offline mode." Problem: I use the app on the train where I lose signal.
9. "Let me filter the list by tag." Problem: With hundreds of items I can't find anything quickly.
10. "Integrate with Slack." Problem: I want notifications where my team already works.
11. "Add two-factor authentication." Problem: This holds sensitive data and I want it more secure.
12. "Let me duplicate an existing item." Problem: I recreate near-identical entries from scratch every time.

Notice the pattern: each pairs a concrete ask with the underlying need. That's what makes them votable and buildable.

The formula for writing a good request

Use this simple structure (it mirrors our feature request template):

[What you want] because [the problem it solves]. Right now I [current workaround].

For example: "I want to duplicate an item because I recreate near-identical entries constantly. Right now I copy each field by hand." One sentence, and the person reading it knows exactly what to build and why it matters.

Turning examples into action

Examples are useful, but they only pay off when requests land somewhere they can be ranked and acted on. A public board lets users post in this format, upvote each other's ideas, and see what gets built — see what a feature request board is for how it fits together.

Create a free board on FeatureRequest, share these examples with your users as a guide, and start collecting requests that are clear enough to act on.