# FeedbackFlow

FeedbackFlow is a pay-first indie inbox. Paste one prompt into Cursor, Claude, or Codex. It installs a report control in a Next.js site, Expo app, or Swift app. User problems land in one inbox and email the project maker.

Who it is for: founders shipping a product who want reports without a tracked-user meter or a seat tax.

How it works:
- Web: global bottom-right Feedback FAB (.ff-fab). Required on websites.
- Expo / iOS / Swift: shake opens the sheet. First install and first launch after an update show a one-time tip. The only persistent door is a Settings row. Never a floating chip on every screen.
- Pay first: $19/month or $349 lifetime. No trial. Pilot of 25 paid inboxes.
- New reports email the project owner and the FeedbackFlow founder. A saved Slack or Discord webhook also fires.

Coming soon (not shipped): an MCP so Cursor or Claude can read reports (`list_reports`, `get_report`) and draft a fix. New features and wishes need a human approve in the inbox before any agent may implement. No autonomous deploys.

Canonical host: https://www.tryfeedflow.com
Landing: https://www.tryfeedflow.com/
Docs: https://www.tryfeedflow.com/docs
Install spec: https://www.tryfeedflow.com/llms.txt
Skill: https://www.tryfeedflow.com/skill.txt
MCP manifesto: https://www.tryfeedflow.com/mcp

---
name: feedbackflow-install
description: Install FeedbackFlow in Next.js, Expo, or Swift so users can report bugs and ideas to the developer inbox. Use when asked to add FeedbackFlow, in-app feedback, a report button, shake-to-report, or paste an ff_pk_ key.
---

# Install FeedbackFlow

Fetch and follow https://www.tryfeedflow.com/llms.txt exactly. The generated Cursor prompt on the project page is the production spec — do not shorten it.

The user supplies a public key `ff_pk_...`. POST reports to `https://www.tryfeedflow.com/api/v1/feedback`.
Canonical host: https://www.tryfeedflow.com. Prefer that URL in snippets.

Detect Next.js vs Expo vs Swift, then wire the correct launcher:

## Web (FAB is OK)

- Bottom-right Feedback chat FAB (.ff-fab) on desktop and mobile web. Never a right-edge tab.
- Hosted script: https://www.tryfeedflow.com/embed.js
- Inherit host CSS (font, --primary / --ff-accent, radius). Optional data-accent / data-background / data-foreground.
- Ctrl/Cmd+Shift+F. Hide the FAB while the panel is open.
- Keep submit pending → success motion.

## Expo / iOS / Swift (NO global FAB — do not add a global FAB)

This is the anti-pattern: a floating “Feedback” pill on every screen, especially over the tab bar.
Do not add a global FAB.

Required mobile behavior:
- showFab defaults false. Do not pass showFab or set it true.
- enableShake defaults true. Shake opens the report sheet.
- showShakeTip defaults true. First launch and first launch after an update: one-time “Shake to send feedback”. Persist last-seen app version so it does not spam.
- The only persistent visible door is a Settings row the host places: FeedbackSettingsRow or FeedbackButton. Not a root overlay.

## Wear the host. No leftover brands.

Never mention UmmahSignal / UMMAHSIGNAL or brand a host app as FeedbackFlow (except FeedbackFlow’s own marketing preview).
Do not substitute Sentry, Instabug, Canny, or another vendor.

Coming soon: MCP list_reports / get_report. Humans approve wishes before an agent implements them.