FeedbackKit / Build with users
Get closer to your users build together
Skill + MCP for Codex / Claude Code
Connect FeedbackKit in one conversation
From feedback and surveys to fixes and shared progress
Everything happens in your coding agent — no admin dashboard
Open ExploreTry the User Hub
01 / How it works
- User submitsReport a bug, request a feature, start a conversation, or answer an invited survey inside the app.
- Agent readsCodex or Claude Code reviews feedback and survey answers, with authorized diagnostics and user journeys for context.
- Developer actsVerify, fix, and reply. With reply reminders enabled, users see new replies when they return to the app.
- Keep buildingShare progress through your roadmap, changelog, and developer posts. Use surveys to hear what users think next.
02 / Integration
Send the invitation prompt to Codex or Claude Code.
One conversation. Done.
- Request accessJoin the waitlist with your email and app details, then wait for an invitation.
- Connect your agentHand over the invitation prompt to install the Skill, connect MCP, and complete sign-in and authorization in the browser.
- Add the SDKLet your agent help create a product, configure its Product Key, and add the feedback center through Swift Package Manager.
https://github.com/Rabithua/FeedbackKit.git
import FeedbackKitCore
import FeedbackKitUI
let configuration = try FeedbackConfiguration(
productKey: "<publishable-product-key>",
bundle: .main
)
let client = FeedbackClient(configuration: configuration)
FeedbackCenterView(client: client)03 / Supported feedback
- Bug reportsProblems or bugs people meet while using your app.
- Feature requestsIdeas for what to add or improve next.
- A little praiseA bit of encouragement for the developer.
- Just chattingUsers can say a few words without filing an issue.
04 / Surveys
Ask the people using your app what you want to learn.
Build a formCreate surveys with your agent. Combine explanations, choices, text, and numeric inputs across multiple pages.
Invite usersShow an invitation in your app or add a survey link to a developer post. Users accept and complete the form inside the app.
Read the answersResponses arrive as private feedback. Your agent can help review and organize them, and you can reply to keep the conversation going.
Your app controls invitations and presentation. Answered surveys show a completion state; ended surveys stop collecting responses.
05 / Reply reminders
Keep the conversation going when users return to your app.
New repliesAfter you reply through your agent, the app can check for unread replies and show a reminder when users return to the foreground.
Continue talkingOpen the feedback conversation from the reminder to read the reply and add more context.
Your app opts in to foreground checks and the conversation interface.
06 / Update reminders
Before a bug report, check whether a newer version could help.
Find an updateCheck versions in the background when the feedback center opens. Offer an update before a bug report only when a newer version is already known.
Keep reportingUsers can continue reporting or choose to update. Pending or failed checks open the form immediately and never interrupt writing.
Your app supplies the version checker and cache. Update reminders appear only before bug reports.
07 / Private diagnostics
Give each issue more context, with less back and forth.
Follow the cluesAttach sanitized logs, breadcrumbs, and MetricKit crash summaries to help investigate the issue.
User-controlledDiagnostic sharing starts off for every report. A private snapshot is generated and uploaded only after the user explicitly agrees.
The diagnostic module requires a separate app integration. Availability depends on your plan; included in Solo and Studio.
08 / User journeys
See the path users took and understand where things went wrong.
Record the journeyAdd the optional Journey module to record sessions and events that describe how people use your product.
Understand the pathLet your agent review user journeys alongside feedback to investigate the experience and inform improvements.
Journey requires a separate app integration. Adding the feedback interface alone does not enable journey collection.
09 / Other
PrivacyDiagnostics start off for every submission. A sanitized private snapshot is uploaded only with explicit user consent. Journey requires a separate app integration, and survey answers are never public.
AvailabilitySupports iOS / iPadOS 18+ with a SwiftUI interface and an independently usable Core. Your app opts in to survey presentation, reply checks, and version checks.
10 / Plans
✦ Annual plans
| Plan | Price | Capacity |
|---|---|---|
| Free | ¥ 0 | 1 App · No attachments |
| Solo | ¥ 269 / year | 3 Apps · Unlimited storage |
| Studio | ¥ 699 / year | 10 Apps · Unlimited storage |
Free does not include attachments or private diagnostics. Solo and Studio have no total storage cap and include attachments, private diagnostics, webhooks, and App Store changelog imports. Per-file size, attachment count per feedback, and upload rate limits still apply.
Limited offer / Solo annual plan
¥ 199 / year
3 Apps · Unlimited storage