Survey ยท checkout
How was checkout?
Was checkout easy?
LiveNext user sees it
Publish change

Hi, I'm Marvey.
I live inside your iOS app, and I am how your users talk to you.
Your users are already telling you things.
Survey answers, store reviews, bug reports, feature requests. Five tools, five inboxes, nobody reading all of them.
So I put all of it in one place.
One Swift package in your app, one dashboard for your team.
And I say what is waiting on you.
Not every answer that came in. The ones that need a person today.
It is one loop, built into the SDK.
Ask, collect, triage, tell them. Every step of it ships today.
I ask on the event, not on open.
Send an event you already track, and I decide whether a survey shows at all.
Everything lands in one inbox.
Answers, board posts and screenshot reports, each tied to the user who sent it.
And a question can be fixed without a release.
Survey copy lives on the server, not in your binary.
Change the wording. That is the whole step.
Publish it, and the next user sees the new question. No build, no review, no waiting.
Four surfaces are live.
Surveys, a feedback board, releases and store reviews, and screenshot bug reports.
Four more are on the way.
One SDK, and you turn on the parts you need. Everything writes to one user profile.
Put a real feedback loop in your iOS app.






Send an event you already track. Marvey shows the right survey, or nothing at all.
Answers, board posts and screenshot reports land in one inbox.
Approve what came in, merge the duplicates, and Slack pings the team.
Set the status and reply in public. Everyone following the post gets a push.
Send an event you already track. Marvey decides whether a survey shows, and which one.
Answers, posts and bug reports land in one queue, tied to the user who sent them.
Survey copy lives on the server. Fix a confusing question and the next user sees it.


Survey ยท checkout
How was checkout?
Was checkout easy?
LiveNext user sees it
Publish change