Revclust
DocsBlogPricing
Log inStart free
DocsBlogPricingLog 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, and any app release-stage metadata your build already uses.

What Revclust Handles

For the Revclust Flutter integration, use the SDK in package:revclust_flutter/revclust_flutter.dart and the viewer at /app/incidents and /app/incidents/<pack-id>. Once an incident is accepted, open it 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(...) where your app detects a failure. Leave the optional automatic hooks off for the initial integration. When the upload is accepted, confirm it in the viewer.

Let The SDK Handle Uploads

Use package:revclust_flutter/revclust_flutter.dart and let the SDK handle uploads. The app captures and uploads the incident; during verification, open the accepted incident in the viewer. No custom upload or authorization code is required.

On this page

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