Dijji for iOS.

01Quickstart — two lines.

In Xcode, File → Add Package Dependencies, paste:

https://github.com/urbaneyed/dijji-ios

Pick the modules you want. DijjiCore is required; DijjiPush and DijjiMessages are optional.

Then in your AppDelegate (or App body for SwiftUI):

import DijjiCore

@main
class AppDelegate: UIResponder, UIApplicationDelegate {
    func application(_ app: UIApplication,
                     didFinishLaunchingWithOptions opts: [UIApplication.LaunchOptionsKey : Any]?) -> Bool {
        Dijji.initialize(siteKey: "ws_a647ba153d0911f1b7")
        return true
    }
}

That's it. The SDK auto-captures app_open, app_background, session_start/end, and app_install (once on first launch). Custom events via Dijji.track; user properties via Dijji.setUserProperty; opt-out via Dijji.optOut().

02Configure APNs in Site Settings.

Before any iOS push reaches a device, your Dijji site needs four pieces of Apple credentials. Generate them in the Apple Developer portal, then upload at /app/sites/{site_key}/mobile.

• Auth Key (.p8 file) — Keys → Create new key → check Apple Push Notifications service. Apple gives you a one-time download of AuthKey_<KeyID>.p8. Save it; you can't re-download.
• Key ID — the 10-character identifier shown on the key's detail page.
• Team ID — the 10-character identifier on Membership. Same value across your account.
• Bundle ID — your app's bundle identifier (e.g. com.kaabilprogram.app). Sent as the apns-topic header on every push.

The .p8 contents are encrypted at rest (AES-256-CBC, AES key derived from dijji.cryptoKey in the .env). Decrypted only at push-dispatch time, never exposed via API.

03REST API — five endpoints.

An iOS dev who can't wait for the Swift SDK can integrate against these directly. Same endpoints the Android SDK uses; the only difference is what your client sends as platform.

Push payload received from APNs

When a Dijji-dispatched push arrives, the JSON looks like:

{
    "aps": {
        "alert": { "title": "Welcome back", "body": "We picked 3 jobs for you" },
        "sound": "default"
    },
    "dijji": "1",         // flag to claim Dijji-originated pushes
    "deep_link": "/jobs",
    "trigger_id": "42",
    "push_id": "199"
}

In your UNUserNotificationCenterDelegate, claim notifications with userInfo["dijji"] == "1", fire a push_opened event with push_id + trigger_id, and route on deep_link.

04Rich pushes — add a Notification Service Extension.

For pushes with images on iOS, your app needs a Notification Service Extension. Apple delivers the push to the extension first; the extension downloads the image, attaches it, then hands the result to iOS for display. Without an extension, iOS shows the text-only payload.

Adding one is a 5-line job:

1. In Xcode: File → New → Target → Notification Service Extension. Name it whatever you like (e.g. DijjiNotificationService).
2. Add DijjiPush as a dependency of the new target.
3. Replace the generated NotificationService.swift body with:

import UserNotifications
import DijjiPush

class NotificationService: UNNotificationServiceExtension {
    override func didReceive(_ request: UNNotificationRequest,
                              withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void) {
        DijjiNotificationServiceHelper.handle(request, contentHandler: contentHandler)
    }
}

That's it. The helper looks for image_url in the push payload (which the Dijji backend stamps when you fill the "Image URL" field in the push composer or trigger), downloads it with a 25-second cap, infers the file extension from Content-Type, attaches it as UNNotificationAttachment, and hands the rendered content back to iOS. Falls back to text-only on any download failure rather than dropping the push.

05Privacy by default.

• No IDFA. The SDK uses identifierForVendor (IDFV) only — per-app, never cross-app. Apple doesn't require ATT for IDFV.
• Hashed IPs at ingestion. The client IP is hashed before storage. Reverse-lookup is impossible without the salt.
• No HTTP. All traffic goes over TLS to dijji.com (HSTS preloaded). APNs is HTTP/2 with mutual TLS to Apple.
• Opt-out at runtime. Dijji.optOut() stops all collection and clears the local queue. Dijji.optIn() resumes.
• No third-party SDKs pulled in. Dijji-core has zero dependencies. dijji-messages uses only system frameworks.

06Live Activities — lock screen + Dynamic Island.

iOS 16.1+ adds a new push-driven UI surface: Live Activities show on the lock screen and the Dynamic Island, updated in real time by the server. Dijji's DijjiLiveActivity module handles the APNs side — you keep ownership of the SwiftUI layout, we deliver the state pushes.

1. Add the module to your Package.swift

.product(name: "DijjiLiveActivity", package: "dijji-ios")

2. Declare your ActivityAttributes in your app target

import ActivityKit

struct OrderTrackingAttributes: ActivityAttributes {
  public struct ContentState: Codable, Hashable {
    var status: String         // "Confirmed" | "Out for delivery" | "Delivered"
    var etaMinutes: Int
  }
  var orderId: Int
  var restaurantName: String
}

3. Start the activity + register with Dijji

import ActivityKit
import DijjiLiveActivity

let attrs = OrderTrackingAttributes(orderId: 42, restaurantName: "Baang")
let initial = OrderTrackingAttributes.ContentState(
  status: "Confirmed", etaMinutes: 35
)

if let activity = try? Activity<OrderTrackingAttributes>.request(
  attributes: attrs,
  contentState: initial,
  pushType: .token
) {
  // ONE LINE — auto-registers every push token Apple rotates to.
  DijjiLiveActivity.observe(activity, activityId: "order_42")
}

// When the activity ends:
DijjiLiveActivity.end(activityId: "order_42")

4. Build the widget UI in your Widget Extension

Standard SwiftUI ActivityConfiguration — lock screen + Dynamic Island compact / minimal / expanded. Apple's HIG covers the layout patterns.

5. Push state updates from the dashboard

From /live, pick the user's mobile card → pick "Live Activity update" → type the new content_state JSON. The server signs an APNs liveactivity push and Apple updates the layout on-device within seconds.

From a trigger or journey, queue an action_type=live_activity_update push with action_config = {activity_id, content_state, alert?} — same dispatch path, same dashboard.

07Roadmap.

What's shipped, what's next: