Private beta
Close the feedback loop inside your app
Event-triggered surveys, a feedback board, releases and store reviews, all from one Swift package. Your team works every answer from a single dashboard.
Everything users tell you, in one place.
Survey answers, feature requests, bug reports and store reviews stop living in five different tools. One SDK puts them in your app, one dashboard puts them in front of your team.
What you use today
What wandkit does instead
A survey that fires on app open
Surveys triggered by an event you already sendLive
Feedback buried in email and reviews
A feedback board your users vote onLive
Anyone can post straight to a public board
Every SDK post waits for your team to approve itLive
Two store consoles to keep checking
App Store Connect and Google Play on one boardLive
Screenshots pasted into Slack
Screenshot bug reports filed from the appLive
Promo codes and a spreadsheet for referrals
Referral links, rewards through RevenueCatBeta
Event analytics in one tool, surveys in another
Analytics on the events you already sendComing soon
A new build for every copy change
Copy and locales updated without a releaseComing soon
Links that open the store and lose the context
Deep links that land on the right screenComing soon
A help centre in Safari, outside the app
Help suggested for the screen they are onComing soon
Ask on the event, not on open.
Send an event you already track. wandkit decides whether a survey shows, and which one.
One inbox, one triage.
Answers, posts and bug reports land in one queue, tied to the user who sent them.
Reword it without a release.
Survey copy lives on the server. Fix a confusing question and the next user sees it.
From the question to the answer.
One loop, built into the SDK. Every step below ships today.
- Step 01
Ask
Send an event you already track. wandkit shows the right survey, or nothing at all.
- Step 02
Collect
Answers, board posts and screenshot reports land in one inbox.
- Step 03
Triage
Approve what came in from the SDK, merge the duplicates, and Slack pings the team.
- Step 04
Tell them
Set the status and reply in public on the board. Everyone following the post gets a push.
Four surfaces live, one in beta. Four on the way.
One SDK, and you turn on the parts you need. Everything writes to one user profile, so a survey answer and a feature request come from the same person.
Change the question without shipping a build.
Survey copy lives on the server, not in your binary. Keep the definitions in your repo, review them like any other change, and take the answers out as NDJSON.
- Server-driven copyReword a question, no app release
- Forms as codewandkit forms pull, diff, push
- Trigger rulesNth occurrence, cooldown, app version
- BranchingA different follow-up per answer
- Response exportNDJSON straight from the CLI
- Slack and Discord16 event types you can toggle
See it running in your own app.
wandkit is in private beta, so we onboard teams one at a time. Tell us about your app and we will walk you through it and get you set up.
What a demo covers
- A project and an API key for your app
- Your first event-triggered survey, built with you
- The feedback board switched on, with post approval and voting
- A look at the release board and store reviews
Frequently asked.
An in-app feedback and survey platform for iOS apps, plus a dashboard where your team works the results. Surveys trigger on events you already send, and the same SDK opens a feedback board inside your app, where posts are approved by your team before they go public.
Add the Swift package, call WandKit.configure(apiKey:) once at startup, then WandKit.identify() after sign-in. Sending an event is one line. The SDK has no runtime dependencies and targets iOS 15 and up.
You pick an event and a rule: the exact Nth time it happens or every Nth time, a cooldown so nobody sees it twice, and an app-version condition. When your app sends the event, wandkit answers with a survey or with nothing at all.
Every post that comes from the SDK arrives pending and waits for someone on your team to approve it. That is not a setting you can switch off, it is how the board works. While a user is typing a title we also show similar existing posts, so they vote instead of filing a duplicate.
Yes. Question text, options and button labels live on the server, so rewording a confusing question takes effect for the next user. You can also keep the definitions in your repo with wandkit forms pull and push, review them in a pull request, and export responses as NDJSON.
iOS 15 and up. There is no Android or React Native SDK yet. On the dashboard side the release board covers both App Store Connect and Google Play, and you can reply to store reviews from either.