Revclust
DocsPricing
Log inStart free
DocsPricingLog inStart free

Start Here

  • Overview
  • Access and Setup
  • Getting Started

Integration

  • Integrate the SDK
  • Trigger Your First Incident

Verification

  • Verify and Observe

Viewer

  • Viewer Workflow

Help

  • Troubleshooting

Reference

  • SDK Reference

Documentation

Getting Started

What Revclust handles, what you need first, and what the first setup pass should look like.

Before You Start

Before you touch app code, finish Access and Setup. At that point you should already have the public SDK dependency, one app, one rpk_... SDK key, any app release-stage metadata your build already uses, and one chosen flow to wire first.

What Revclust Handles

For the hosted Flutter setup, use the Flutter SDK in package:revclust_flutter_sdk/revclust_flutter.dart and the viewer at /app/incidents and /app/incidents/<pack-id>. Once an incident is accepted, open the incident page with the direct incident link (viewerUrl) or the incident ID (packId).

Normal Setup Path

Initialize the SDK, register a small state snapshot, and call captureInvariantFailure(...) on one chosen failure path. Leave the automatic hooks off for the default hosted path. When the backend accepts the upload, confirm it in the viewer.

Let The SDK Handle Uploads

Use package:revclust_flutter_sdk/revclust_flutter.dart and let the SDK handle uploads for this setup. The app captures and uploads the incident; during verification, open the accepted incident in the viewer. Do not add custom upload code or manage ingest authorization in app code.

On this page

  1. Before You Start
  2. What Revclust Handles
  3. Normal Setup Path
  4. Let The SDK Handle Uploads
TermsPrivacy Policy