Feature requests
Build an in-app Suggest a Feature conversation
Let iOS customers describe the outcome they need by voice or text, then ask follow-up questions that give developers enough context to evaluate the request.
What this workflow actually does
A feature name rarely tells you the whole problem. A person asking for folders might need to organize a shared project, archive completed work, or find a recent export. Paydirt can ask what they were trying to accomplish and preserve the exact explanation.
Add a Suggest a Feature entry to a discoverable location such as Settings. The host app controls the button and presentation; the remotely configured form controls the opening question and follow-up guidance.
Give the coding agent the actual placement and delivery choice. Existing cancellation forms can remain separate so product requests do not get mixed with trial or subscription cancellation reasons.
A strong fit for
- ✓ on a Suggest a Feature button in Settings
- ✓ Teams building an iOS app with a coding agent
- ✓ Optional voice or text conversations
Not designed to replace
- — Required account or onboarding fields
- — Automatic changes to the product based on an answer
From trigger to exact answers
01
Choose a discoverable entry point
Use a Settings row or help menu entry that is available when the customer has something to share.
02
Ask about the desired outcome
Start with what the customer wants to accomplish, then clarify the workflow or limitation behind the requested feature.
03
Keep routing explicit
Store the response in Paydirt and optionally connect a selected Slack channel for product feedback.
04
Review before committing
Read the exact answers, identify repeated needs, and have a developer decide which requests merit investigation.
Give your coding agent a concrete placement
Connect Paydirt through the developer guide, then use this request. Replace the example location with the actual screen or action in your app. The agent needs repository access and Xcode to build the iOS target.
Add a Paydirt feature requests form to this iOS app.
Place it on a Suggest a Feature button in Settings.
Start with: “What would you like to be able to do in this app?”
Use settings_feature_request as the placement metadata.
Keep it optional and offer text and voice answers.
Store responses in Paydirt; ask me about Slack routing.
Build the app and show me the form for a test response.What reaches Slack
- • The complete accepted question-and-answer conversation
- • An Audio or Text marker for each answer
- • Placement metadata intentionally supplied by the app
- • One message per completed conversation when Slack is connected
Know the limits
- • Paydirt is not a public voting board, roadmap, or ticket tracker.
- • A feature request is feedback, not permission for an agent to change code or promise a release.
- • The host app must provide the menu item or button that opens the form.
Questions developers ask
Does Suggest a Feature need RevenueCat or StoreKit?
No. A manually presented feedback form works without subscriptions or a purchase SDK.
Will Paydirt automatically implement requests?
No. Coding agents can read authorized responses, but product decisions and code changes need a separate instruction from the developer.
Ship the smallest useful feedback loop
Install one form at a real product moment, send the completed raw conversation to one Slack channel, and verify it in the app before expanding.
Start setup