Upweight helps app makers collect customer requests, decide what to build, and share progress in one workspace. Gather in-app submissions through the SDK, let customers suggest and vote on ideas on public boards, and import written 1–3 star App Store reviews. Triage reviews into new or existing feedback requests, and merge duplicates to keep supporting feedback together.
An optional RevenueCat connection adds subscription context to matched customer votes, helping you compare requests by monthly revenue as well as vote counts. Imported reviews are not matched to subscribers or revenue-weighted, and revenue information stays out of public boards and SDK responses.
Share direction on a public roadmap and announce shipped work in a changelog. Separately, shipping a request can trigger optional shipped-update emails to eligible, opted-in customers who voted for it; publishing a changelog entry alone does not send them. You can also connect an authorised AI client through MCP to read and triage feedback, inspect revenue rankings, and prepare changelog drafts.
Choose your path
- Workspace owners: start with Getting started, then learn team roles and billing.
- App developers: the SDK connects in-app feedback and votes to your app. SDK setup is an optional onboarding step.
- AI-client users: MCP provides access through an authorised client. Keep access scoped to the workspace you intend to use.
- Board customers: browse a shared board and sign in there to participate. You do not need an owner account.
Set up your workspace
Create an account and organisation, choose a workspace name and slug, then add an app. Optional connections include App Store reviews and RevenueCat. You can skip optional onboarding steps.
Read Core concepts before deciding how to organise feedback across apps.
Collect and prioritize feedback
Use feedback to triage requests, public boards to collect customer ideas, and the roadmap to share direction. Publish completed work in a changelog. Shipped-update emails are a separate delivery capability; publication alone is not a promise of email delivery.
Get help
For AI-client access, read the MCP overview, client setup, and MCP troubleshooting.
Check Troubleshooting for sign-in and visibility problems. Read Security and privacy before sharing customer information.
For in-app feedback, see the SDK overview, Swift SDK guide, and HTTP API reference.