Dartastic RUMDartastic RUM

See exactly what your users see.

Real user monitoring with session replay for Dart and Flutter apps. Watch any session back: every screen, every tap, every error, in the order it happened.

You choose how much of the screen each device records, from an event timeline to full pixels, and every replay opens its traces and logs.

Session replay of the Alpine Trails demo app paused on the Angels Landing trail detail screen, beside a session timeline of screens, taps, errors and spans, the span under the playhead with an Open trace button, and the event list ending in rage taps and a null-check error on checkout
A Pixel replay of the Alpine Trails app with taps on a timeline.

Five levels of detail.

Every session starts as OpenTelemetry events. An added level of capture fidelity that your privacy rules allow and your team needs to replay.

The five levels side by side on the Alpine Trails app: Events with no replay, Outline as plain boxes, Wireframe with text as gray bars, Shadow as a blurred screenshot, and Pixel as the real screen

Events

The session replayed as OpenTelemetry events on its timeline: every screen, tap, network call, span, error and crash, in order. No picture of the screen leaves the device.

Dartastic Observatory replaying an Alpine Trails session recorded as Events: the phone says replay was not recorded, beside the session timeline of screens, taps and spans and the list of events
An Alpine Trails session replayed at Events.

Outline

Adds a box for each major element: app bars, buttons, text fields, pictures and the outer containers. No text and no icons.

An Alpine Trails session replayed at Outline: the phone shows plain boxes for the app bar, cards and containers, with no text or icons
An Alpine Trails session replayed at Outline.

Wireframe

Adds text, icons and the smaller controls, each drawn as a box. Text shows as gray bars, one per line, and no characters leave the device.

An Alpine Trails session replayed at Wireframe: boxes for every card, icon and checkbox, with each line of text drawn as a gray bar
An Alpine Trails session replayed at Wireframe.

Shadow

Adds a real screenshot, blurred into blocks so the app's labels and typed text can't be read. Colors stay, so you see which banner was red and whether an image loaded.

An Alpine Trails session replayed at Shadow: the screen blurred into blocks, its colors kept and none of its words readable
An Alpine Trails session replayed at Shadow.

Pixel

Adds the real screenshot: the screen as the user saw it. Your app can hide what users type, or all text, before the screenshot leaves the device.

Three Visibility Variations
An Alpine Trails session replayed at Pixel: the Where to next? screen as the user saw it, with the Angels Landing and Bright Angel Trail cards
An Alpine Trails session replayed at Pixel.
An Alpine Trails session replayed at Pixel with what users type hidden: the Search screen, its search field a solid gray box, above the Angels Landing and Bright Angel Trail results
Pixel with what users type hidden: the search field replays as a solid box.
An Alpine Trails session replayed at Pixel with all text hidden: the Search screen with every word, button label and trail name a solid gray bar
Pixel with all text hidden: every word replays as a solid bar.

Each level sends everything the one before it sends, plus more of the screen.

Every session connects

Two Dartastic Observatory screens joined by an arrow: in a session replay, the Open trace button under the playhead on the checkout tap is circled, and the arrow leads to that trace's spans, from the alpine_trails app's tap /checkout, checkout and POST to alpine-trails-api's POST /v1/subscriptions with its middleware, request handler and database calls
Under the playhead, Open trace opens the whole trace: from the tap in the app to every span in the API it called.

One session id, everywhere

Spans and logs carry the same session.id as the replay. From a failed checkout span, open its logs, and open the session to watch what the user did before it failed.

The whole session in order

The Session Timeline lays out one session from start to finish: every screen, network call, jank spike and error.

Dartastic AI watches too

Dartastic AI reads RUM sessions alongside traces, metrics and logs, and its answers link to the replay so you can see the moment for yourself. Meet Dartastic AI.

Targeted RUM

Support without Guessing

When a customer calls support, support can find their device, and with the customer's consent, start a RUM recording to see exactly what is going wrong.

The Start RUM dialog for one install, a Google Pixel 8 Pro running app version 1.2.9 (33), not armed, with Wireframe chosen as the fidelity, 1 session to record, expiring in 1 hour, and the Record button
  1. 1. A customer calls

    "Checkout freezes on my phone." Your app records everyone's sessions as Events, so you can see what they tapped but not what was on their screen.

  2. 2. Support finds their device

    In App Installs, search for the start of their email, user id or install id. Each install shows its device, OS and app version, and when it was last seen.

  3. 3. Support chooses what to record

    Choose Start RUM, then the fidelity, from Events to Pixel, and how long to keep recording, from 5 minutes to 8 hours. The request is signed and goes to that one install, in the reply to its own telemetry. No other install hears of it.

  4. 4. The customer says yes

    Their app answers first: with its own screen, naming the fidelity and when recording ends, or with no screen where consent comes with the job. When it asks, recording starts only if they agree, and they can stop it at any time. An app that doesn't answer doesn't record, and support is told so.

  5. 5. Support watches what they saw

    Their sessions arrive in Sessions and Replay, tagged as support recordings, with every trace and log attached. When the time runs out, the device goes back to recording as before.

Only people you allow can start a recording, every recording is in your audit log with who started it, and none can go above the limit forged into your engine.

Powerful insight. Thoughtful safeguards.

Session replay gives developers an extraordinary view into how people use their apps. With that visibility comes a responsibility to protect their users' privacy.

Privacy built into your engine

Some organizations and jurisdictions restrict session replay or certain types of data collection. Dartastic gives you control before you even ship your app.

When you sign up, choose the maximum RUM fidelity your engine will support: Events, Outline, Wireframe, Shadow or Pixel. You can also choose to exclude RUM entirely.

Capabilities you exclude aren't simply switched off. Your limit is forged into your engine, and nothing on the device can go past it. They can't be enabled later with a configuration change.

Choose Pixel and you can also restrict capture of typed text or all text. Your app can always record at a lower fidelity than its engine supports.

Privacy starts on the device

Dartastic applies your fidelity and masking choices before data leaves the device. Capture only what's needed, buffer sessions until something goes wrong and avoid collecting screen content where it isn't necessary.

Responsible by design

Privacy is a shared responsibility. App developers decide what to collect, inform their users and obtain consent where required. Dartastic provides the controls to help them make those choices responsibly. Your engine's limit doesn't replace consent: even a session recorded as Events can identify a person.

France's data protection authority, the CNIL, has published a draft recommendation for session replay providers and app developers, covering consent, data minimization and technical safeguards. Though it is a draft from one EU regulator, Dartastic agrees that it gives good guidance to any organization implementing RUM anywhere in the world.

Powerful enough to see what went wrong. Designed to respect what should stay private.

Private by design

Decided on the device

Fidelity is a switch on the device, and it can never go above the limit built into your engine. Nothing above it is captured, so nothing above it ever leaves the phone.

No text at the lower levels

Events, Outline and Wireframe send no text from the screen and no pixels. Shadow blurs its screenshot so the app's labels and typed text can't be read.

Per app and per screen

Set a level for the whole build with a --dart-define, or change it in code for one screen, like Events on a card-entry screen.

Record when it matters

Keep a short buffer on the device and upload it only when something goes wrong, or stream every frame. Replay is off until you turn it on.

One session rate at every replay level

A session costs the same whether it records Events or Pixel: $0.75 per 1,000 past the sessions your plan includes. A higher replay level costs more only through the bytes it stores, which count toward your plan's ingress like any trace, log or metric. A session buffered until something goes wrong uploads no replay at all.

What your plan includes

  • Cloud Free includes 10,000 sessions and 10 GB of ingress a month.
  • Cloud Standard includes 100,000 sessions and 100 GB of ingress a month.
  • Cloud Pro includes 1,000,000 sessions and 500 GB of ingress a month.
  • Past that, sessions are $0.75 per 1,000 and ingress is $0.40 per GB, billed with the next month's bill.Cloud Free takes no card, and each of its meters stops at what the plan includes.
  • Self-Hosted records unlimited sessions at every fidelity, inside your own network.
See plans and prices

You Control Your Data Meter

The amount of data an application sends can be controlled by sampling flags set at build time or runtime. Traces, metrics and logs are always on by default. RUM is off by default.

Traces use the standard OpenTelemetry sampler, and metrics, logs and RUM have their own sample rates. Lower RUM fidelity reduces ingress.

Watch your first session

Dartastic RUM comes with every Dartastic Observatory plan: Cloud, Dedicated and Self-Hosted. You choose which RUM levels your engine supports when you set up your organization.