Products Developer tools
Available for trialIn-app feedback & bug reports

FeedbackKit

Turn “something broke” into useful context.

FeedbackKit gives users a simple way to show what went wrong. Each report connects the screenshot, application version, and user-approved context your team needs to investigate.

Guided evaluation · Technical discovery · Trial access through our team

iOSAndroidFlutterWeb dashboard
01

Capture a problem while its context still exists

02

Reduce support questions about device and build version

03

Connect customer language to engineering evidence

Built around the
work that matters.

Explore how FeedbackKit works, then talk with us about trial access for your workflow.

01

Screenshot annotations

A report composer can let users point to the part of the screen that needs attention.

02

App and device context

Attach selected version and device information so investigators can understand the environment.

03

Optional diagnostics

attachment Controls can let teams request diagnostic context with clear user consent.

04

Connected investigation

DebugStream and Flowmesh links can connect a report to the relevant session and build.

A clear path from
setup to everyday use.

  1. Capture the moment

    An in-app entry point can open a report while the problem is still visible.

  2. Explain and review

    The user can add a description, annotate the screenshot, and review any included attachments.

  3. Investigate together

    Your team can receive the report context and follow links to connected development tools.

How FeedbackKit
fits together.

A clear division between the product interface, processing layer, and the systems your team already owns.

01In-app composer

A branded report flow for text, screenshot markup, and visible attachment consent.

02Context collector

Collect only configured app, device, navigation, and diagnostic fields.

03Team inbox

Triage, assign, link sessions and builds, and keep the reporter informed.

Built for integration,
not a closed box.

Trial onboarding confirms the exact environment, product boundary, and success criteria for your implementation.

Platforms & surfaces

iOSAndroidFlutterWeb dashboard

Connects with

DebugStream sessionsFlowmesh buildsSupportDockWebhook export
CaptureText, screenshot, annotations
ContextApp-defined and user-reviewed
RoutingProject, build, tag, assignee
StatusOpen, investigating, waiting, resolved
ExportSigned webhook and JSON

Deliberate boundaries
from the beginning.

  • Attachment preview before submission
  • Configurable redaction and field allowlists
  • Per-project retention and deletion controls
  • Authenticated inbox with assignment history

Made for real workflows.

QA teams

For testers collecting reproducible issues across devices and pre-release builds.

Client-facing agencies

For teams that want clearer feedback from customers during acceptance testing.

Mobile support teams

For support staff helping users explain a problem without leaving the application.

Evaluate FeedbackKit
against real work.

We scope the trial around one meaningful workflow, the environments you use, and evidence your team can assess.

  1. 01

    Add the composer to an internal or beta build

  2. 02

    Define allowed context and privacy copy

  3. 03

    Submit real QA scenarios from multiple devices

  4. 04

    Measure report completeness and triage time

What the evaluation includes

Product access for the agreed scope, technical onboarding, implementation guidance, and a review of the findings.

Discuss trial access ↗

Explore with confidence.

A closer look at the scope and trial experience for FeedbackKit.

How can I try FeedbackKit?

FeedbackKit is available through a guided trial. Tell us about your requirements, platform, and evaluation goals; our team will discuss fit, access, and the right trial scope with you.

Does every report automatically include logs?

No. Diagnostic attachments are optional and configurable. The reporting flow shows users what they are submitting.

Do I need DebugStream or Flowmesh?

The basic report flow works independently. Connections to DebugStream sessions and Flowmesh builds provide additional context when those products are used.

Bring us your
real workflow.

Share your platform, requirements, and evaluation goals. We'll discuss the product and arrange a focused trial where it fits.

Request a FeedbackKit trial ↗