FewchursHow it works
A few simple ideas. Read this once and every guide will make sense.
The pieces
| Word | What it means |
|---|---|
| App | One of your products. Each app has its own board, requests and API key. |
| API key | A secret-looking string that starts with fr_live_. It tells Fewchurs which app a request is for. |
| Board | The list your users see. They can read, vote, comment and suggest new ideas. |
| Request | One idea from a user, with a title and an optional description. |
| Vote | One per person per request. The board can sort by most votes. |
| Comment | A reply under a request. Your replies show a Developer badge. |
Statuses
You set the status of each request from your dashboard. Users see it on the board, so they know what is happening.
| Status | Shown as | Meaning |
|---|---|---|
open | Pending | New. You have not decided yet. |
planned | Planned | You plan to build it. |
in_progress | In progress | You are building it now. |
done | Done | It shipped. |
declined | Declined | You won't build it. |
Who is voting
Your users don't need an account. Each device gets a random ID, called a device ID. Fewchurs uses it to remember who voted for what, so nobody votes twice.
The SDKs make and store this ID for you. If you call the REST API yourself, send it in the X-Device-Id header. Create it once, save it, and reuse it every time.
Use your own user ID if you have one
Emails
Users can follow a request by leaving their email. When you change its status, they get an email. You can also get an email each time someone suggests something new. Turn it on in your dashboard settings.
Limits
| What | Limit |
|---|---|
| New requests | 15 per device, per day |
| Comments | 10 per device, per day |
| Votes | No limit |
Your plan sets how many apps you can have and how many requests stay visible. See pricing.