👩‍💻 Looking for the source code? The Castle Flutter SDK is available on GitHub.

Installation

Step 1. Configure with API key

Grab your Publishable API Key from the Castle dashboard settings page and configure the SDK:

import 'package:castle_flutter/castle.dart';

await Castle.configure(publishable_key: "{Publishable-API-Key}");

The Castle SDK collects fingerprint information from the device and sends this information directly to Castle. These requests are batched to optimize device performance. See the last section below, Configuration notes, to make changes to the way Castle collects and batch-processes this fingerprint information.

Step 2. Forward the fingerprint

The Castle Flutter SDK generates a value that we call the request_token. Forward the Castle request_token in relevant requests to your application server.

The request_token value contains a proprietary signature of the mobile device fingerprint. This value should not be used as an identifier. It should be treated as a token. The value will change over time.

You will need to forward the request token as a request header to every request to your API. You can specify this header name in the SDK configuration.

import 'package:castle_flutter/castle.dart';

const requestTokenHeaderName = await Castle.requestTokenHeaderName;
const requestToken = await Castle.createRequestToken;

Map<String, String> requestHeaders = {};
requestHeaders[requestTokenHeaderName] = requestToken;

Step 3. (optional) Additional configuration

• The SDK allows for additional configuration options. Please refer to the documentation packaged with the SDK code for full details. Below is an example.

import 'package:castle_flutter/castle.dart';

// screen tracking and device ID auto forwarding are disabled
await Castle.configure(
  publishable_key: "{Publishable-API-Key}",
  debugLoggingEnabled: true,
  flushLimit: 10, // default: 20
  maxQueueLimit: 100, // default: 1000
  baseURLAllowList: ['https://api.castle.io/']
);

Configuration notes

Queue flushing

The SDK queues API calls to save battery life, and it only flushes queued events to the Castle API whenever the app is installed, updated, opened or closed; when identify is called; or when the queue reaches 20 events. This ensures that the device fingerprint is fully profiled before any requests to your server side.

Automatic screen tracking

When automatic screen tracking is enabled any activities or view controllers shown will automatically generate a screen event. The screen name will use a normalized version of the activities or view controllers title. For more granular control we suggest disabling automatic screen tracking (on by default) and calling screen manually.