Canny — Feature requests

Feedback & RoadmapsSee it livefeedback.canny.io

Board navigation and a compact suggestion form sit beside a ranked feature list with vote counts, search, and sorting.

Canny — Feature requests — captured interface — Viewport capture · opening screen

Source capture · 2026-09-05Open full image ↗

Content & media

Why this pattern works

Public feedback portals that combine discovery of existing ideas with an obvious submission route.

Design notes

Surface: Canny public Feature Requests board.
Navigation: Top tabs for roadmap, feedback, and changelog; a left list switches feedback boards.
Layout: Left context and submission area beside a broader list of request rows.
Density: Moderate, using compact vote counters and concise request summaries.
Color: White, pale gray boundaries, muted text, restrained accent controls.
Type: Bold request titles with smaller metadata and board labels.
Pattern: Put existing requests beside the new-request path so visitors can check for duplicates first.
States: Populated public board, signed out; no suggestion or vote was submitted.
Don't: Do not present votes as delivery commitments or hide the distinction between requested and planned work.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Canny — Feature requests
Source: https://feedback.canny.io/feature-requests
Swipefile reference: https://swipefile.design/ref/saas-ui-canny-feature-requests/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Canny public Feature Requests board.
- nav: Top tabs for roadmap, feedback, and changelog; a left list switches feedback boards.
- layout: Left context and submission area beside a broader list of request rows.
- density: Moderate, using compact vote counters and concise request summaries.
- color: White, pale gray boundaries, muted text, restrained accent controls.
- typography: Bold request titles with smaller metadata and board labels.
- pattern: Put existing requests beside the new-request path so visitors can check for duplicates first.
- states: Populated public board, signed out; no suggestion or vote was submitted.
- dont: Do not present votes as delivery commitments or hide the distinction between requested and planned work.

Useful for: Public feedback portals that combine discovery of existing ideas with an obvious submission route.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Public feedback portals that combine discovery of existing ideas with an obvious submission route.

Canny — Feature requests

Make it your own

Keep exploring