Know what your app is doing in the field.
GATillPulse is the observability layer of TillDev, built for how apps actually run in the field — real networks, a wide device and OS spread, and connections that aren't always there. You add one SDK to your React Native or Flutter app and it reports crashes, unhandled errors, slow screens, network failures and pre-crash friction back to your workspace. TillPulse groups them into issues, ties each to a release, deobfuscates stack traces with your uploaded symbols, and routes what matters to alerts. The same SDKs also emit the security telemetry that TillShield acts on — one pipeline, two products.
The moving parts
Five things, in the order you meet them:
- Project — one app you observe. It has a DSN (the public key your SDK sends to) and an environment (development, staging, production) that decides how loudly it alerts.
- Events — the raw reports the SDK sends: a crash, a caught error, a performance sample, a network timeout, a security signal.
- Issues — events fingerprinted and grouped, so a crash that happens ten thousand times is one row you can triage, assign and resolve — not ten thousand.
- Releases — the version an event came from. Upload source maps, ProGuard mappings or dSYMs per release so stack traces read as your original source instead of minified noise.
- Alerts — rules that watch issues and reach you on Slack or a webhook when a trigger is crossed. See Alerts.
Get your first events flowing
The fastest path: create a project, drop the SDK in, and watch the dashboard light up.
| Page | What you’ll do |
|---|---|
| Getting started | Create a project, grab its DSN, and send your first event end to end. |
| Dashboard tour | Read the issue stream, drill into an event, and follow an issue to resolution. |
| Environment variables | Wire the DSN and environment through your build so dev noise never pages you. |
Install the SDK
Pick your framework — both capture crashes, errors, performance and network out of the box:
| SDK | Notes |
|---|---|
| React Native | One init call. Native crash capture needs a dev/release build — not Expo Go. |
| Flutter | Wrap runApp; Dart errors, platform crashes and network traces flow automatically. |
Run it in production
| Page | What it covers |
|---|---|
| Alerts | Route new issues, regressions and spikes to Slack or a webhook, with quiet periods. |
| Source maps | Upload and manage per-release symbols so stack traces point at your source. |
| Deployment | Mark releases as you ship so regressions are attributed to the version that caused them. |
TillPulse shares a workspace with the rest of TillDev. The security signals your SDKs report feed TillShield, and you can automate projects, releases, symbols and alerts from the CLI.