Glossary
App feedback terms, defined
Clear definitions of in-app feedback, SDK, triage, crash reporting, and developer product concepts.
- In-app feedback
- User feedback collected directly inside a mobile or web application — without redirecting to a survey, email, or external form. In-app feedback captures context (screen, app version, user ID) that external methods miss, and has significantly higher response rates.
- Feedback SDK
- A software development kit (SDK) that developers add to their app to enable in-app feedback collection. A feedback SDK typically provides a built-in UI overlay (so you don't have to build one) and a submission API for sending feedback data to a backend dashboard.
- Feature request
- A structured user submission asking for a new capability or improvement to an existing product feature. Feature requests are distinct from bug reports — they describe desired future behaviour rather than current broken behaviour. Well-structured feature request tools allow voting and grouping.
- Crash report
- An automated or user-initiated report capturing the state of an application at the moment it crashed — including stack trace, device model, OS version, and app version. Crash reports help developers reproduce and fix bugs that only appear in production.
- Feedback triage
- The process of reviewing incoming user feedback, categorising it by type (bug, feature, support, feedback), assessing priority, and routing it to the appropriate team or backlog. Effective triage requires a dashboard that makes it fast to read, filter, and act on feedback at volume.
- API ingest
- An HTTP endpoint that accepts feedback submissions programmatically — without requiring the SDK's built-in UI. Useful when you want to build a fully custom feedback UI while still sending data to a centralised dashboard.
- Feedback loop
- The cycle of collecting user feedback, acting on it (fixing bugs, building features), and communicating changes back to users. A tight feedback loop — where users see their input influence the product — dramatically improves retention and user trust.
- Closed testing (Google Play)
- A mandatory stage in the Google Play Store release process where apps must be tested by a minimum of 20 users for at least 14 consecutive days before qualifying for production release. Closed testing is required for new developer accounts publishing apps on Google Play.
- Multi-project dashboard
- A feedback management interface that consolidates submissions from multiple apps or projects in one place. Essential for indie developers managing several apps simultaneously, or agencies building apps for different clients.
- NPS (Net Promoter Score)
- A single-question survey metric asking users how likely they are to recommend a product (0–10 scale). NPS is often used as a proxy for user satisfaction but works best when paired with qualitative in-app feedback that explains the score.
Related:Feedback SDK
Related:Feedback SDK
Related:Feedback triage
Related:In-app feedback
Ready to collect in-app feedback?