Feature requests

A screen where users suggest and vote on features. You moderate it from the Admin console.

Users submit ideas straight from the app. Other users upvote them. You see everything in the Admin panel and can approve, edit, or hide.

It's the pattern used by modern products like Notion, Linear, and Figma: instead of getting scattered emails, you get a prioritized list of what the community wants.

Implementation

Via MCP: ask your assistant "add feedback to my project". It runs add_feature for you. See Kasy MCP.

Run:
```
kasy add feedback
```
This turns on the /feedback screen and creates the chosen backend's collection/table.
To moderate, open the Admin console → Requests tab. Access requires role = "admin" in the database, even in debug: see Admin Console to set it up.

Information

How the user uses it

Settings → Suggest an improvement
Sees the list of suggestions with vote counts
Can upvote the ones they like (1 vote per suggestion)
Can add a new suggestion

The screen is already translated into PT/EN/ES.

How you moderate it (admin)

On the Requests tab you can:

Action	What it does
Hide	Removes it from the public screen without deleting it
Edit title/description	Adjusts the text (in any language)
Mark as delivered	Removes it from the pending list

Why this is useful

Prioritizes by community vote, not by the loudest customer.
Reduces support: questions become public suggestions. Whoever wants it most, votes for it.
Marketing: when you ship the feature, mark it "delivered" and the user who asked for it comes back to check.

Where the data lives

Backend	Where
Firebase	`feedbacks` collection in Firestore
Supabase	`feedbacks` table in Postgres
REST API	`GET/POST /feedbacks` endpoint (you implement it)

Last updated on 08/02/2026