Open device SDKs

Small on purpose.
Open so you can check.

Events, identity, permission handling, token acquisition, deep links and device callbacks — through public source you can audit. A handful of calls is the whole surface.

Start building free Read the docs

notifie_flutter · 0.1.0-beta.10PUB.DEV

// initialize once
await Notifie.initialize(
  apiKey: env.notifieKey,
);

// product evidence
await Notifie.track(
  'order_shipped',
  properties: {'order_id': id},
);

// enrol the device once; Cloud owns delivery from here
await Notifie.enableNotifications();

Public packages

Native behavior, small application APIs.

Each SDK owns persistence, retries, anonymous identity, token refresh, and lifecycle behavior so application code stays focused on product events.

Swift

CocoaPods release for iOS 15+, with events, APNs tokens, and notification callbacks.

0.1.0-beta.5

Android

Maven Central artifact with events, FCM tokens, and notification handling.

0.1.0-beta.6

Flutter

A thin bridge over the native implementations with durable event and token storage.

0.1.0-beta.10

One conceptual API

Initialize. Identify. Track. Notify locally.

Platform-specific capabilities remain explicit, but the product model stays intentionally small across native and cross-platform SDKs.

app_startup.dartFlutter

await Notifie.initialize(
  apiKey: env.notifieKey,
  onNotificationOpened: (n) => router.open(n.deepLink),
);

await Notifie.identify('user-42');
await Notifie.track('purchase_completed');

// Ask once, when the value is obvious to the user.
await Notifie.enableNotifications();

Public beta — no credit card

Inspect the source. Then run it on a real device.

Start with the public package for your platform, send one event, and watch it arrive in the dashboard.

Connect a real app