GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing docs.buzzkit.dev — Introduction - BuzzKit BuzzKit sends, segments, schedules and automates mobile push through a REST API, a dashboard and an iOS SDK, using your own Apple and Firebase credentials. Run it hosted on buzzkit.dev or self-host the same codebase.
Identify, then sendIdentify a subscriber with your own user id, then send. BuzzKit answers 202 with a message id, works out which devices are reachable, fans out through a durable queue with retries, and records every attempt per device.SendingTarget one subscriber, a topic, a saved segment or an inline expression, with retries and a full delivery ledger. SchedulingHold a message until a moment, in a fixed time zone or in each subscriber’s own. SegmentsSaved, versioned conditions over attributes, events and activity, evaluated at send time. WorkflowsVersioned specs with waits, branches, loops and fetches that run per subscriber. Topics and preferencesA notification settings screen for your app with no backend code. Multi-tenancyA tenant per customer, each with isolated subscribers and credentials, behind one key. How it fits togetherYour backend calls the API with a workspace key. A workspace holds your team and billing; a tenant inside it is the isolation boundary that owns subscribers, credentials and sends. Simple apps use the default tenant and never think about it. A platform sending for its own customers gives each customer a tenant and picks one per request with a header. Your app embeds the iOS SDK with a client key. The SDK registers the device, identifies the user by the id you already use, and tracks events. Those events feed segments and trigger workflows. |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |