Add a Feedback entry to your app that opens your hosted Ducalis board. Organize feature requests, connect them to backlog work and let users know when the things they asked for ship.
Start collecting mobile feedbackGive users a Feedback entry in a place such as Settings. Start with a hosted board that opens in the mobile browser; choose a web embed when your app’s integration is ready.
Review the idea in Ducalis, link it to an issue and use customer-facing statuses and release updates to keep the author informed.
Alex uses Acme Reader on iPhone and wants to read saved articles on a flight. They tap Feedback and send an Offline reading request through the hosted board. Your team reviews it in Ducalis and links it to Linear MOB-142.
Start with a published board link. For a web-based screen, use the documented widget or full-board embed and verify the experience in your app.
Choose the board, publish it and configure who can access it. Add its URL to your app’s Feedback entry so users can open it in the mobile browser and return to the app after submitting.
Configure board access →The documented JavaScript widget collects feedback on a web page. A full-board embed can show the board inside your product’s web surface. Choose the approach that fits your app.
See the web feedback widget →
Read the full-board embed guide →
If you want the web experience inside a native iOS screen, have your developers validate the WebView integration, sign-in, keyboard, navigation and submission on devices. Ducalis’s documented web embed is the starting point for this implementation.
Review the documented widget setup →A useful request tells your team who needs the feature and what they are trying to do. Ask for a clear description and review any context the customer provides.
For the hosted-link recipe, use the board’s configured sign-in. Being signed in to the iOS app does not by itself sign the user into the feedback board.
For a supported web integration, configure Ducalis SSO to identify the customer and pass supported attributes, such as company or plan. Review your authentication implementation before sharing it with users.
Your team labels the Offline reading idea, checks related requests and keeps the customer-facing summary clear before linking it to work.
┌─ REQUEST IN DUCALIS ───────────┐ │ board Acme feedback │ │ idea Offline reading │ │ author Alex · Acme │ ├────────────────────────────────┤ │ Review request and context │ │ Label: reading experience │ │ Review matching ideas │ └────────────────────────────────┘
Offline reading already has a Linear issue, MOB-142. Link the customer idea to that issue. For a new feature, create an issue in Ducalis or your connected tracker using + New.
Compare the request with other work using impact, effort and customer context. Your team chooses its priority and what to communicate on the public roadmap.
A linked idea keeps the customer request connected to internal delivery. Submission alone does not create or schedule an issue.
Organize requests from all channels → · Prioritize the backlog → · Prioritize Linear issues →
┌─ LINK TO PRODUCT WORK ─────────┐ │ idea Offline reading │ │ issue Linear MOB-142 │ ├────────────────────────────────┤ │ Link existing or create new │ │ Customer context → backlog │ │ Review impact and effort │ │ Team chooses the priority │ └────────────────────────────────┘
Map linked issue statuses to idea statuses such as Planned, In progress and Done. The user can follow progress on the public roadmap; authors and voters can receive status emails according to their preferences.
When Offline reading is available to the intended users, review and approve a release announcement. Explain how to get the update and where to use the feature, then publish it in the changelog.
If tracker Done comes before the mobile release is available, use the documented release-webhook condition. Keep the public status and announcement aligned with the version users can actually access.
Subscribers receive release notes through your configured delivery settings. Status emails and release notes are separate; this recipe does not depend on native push notifications.
Show progress on your roadmap → · Automate reviewed release notes → · Configure voter updates →
These playbooks explain collection and follow-up. Validate the iOS entry, sign-in and web integration using the setup guidance above.
Create a board, add its link to your Feedback entry and test a request with a customer account. Check it reaches Ducalis, links to the right work and receives the intended updates.
Start collecting mobile feedbackSet up your feedback board → · See the full feedback-to-release workflow →