Developer documentation

Build against a small, explicit contract.

Drel is an iPhone push utility and focused web container. These docs distinguish what is available now from future work, so an integration does not depend on browser cache, undocumented fields, or native privileges.

Start here

Send a push

Bark-compatible paths and a JSON API create a notification and optional HTTPS destination.

Read Push API →

Open a web tool

Pages run in a Store-safe container with a documented runtime object, not native Bridge access.

Read container behavior →

Keep an app offline

A signed, hash-verified package can make a registered web app launchable without WebKit cache.

Read offline packages →

Give an agent the contract

The versioned Drel app-development skill contains templates, checks and graceful fallbacks.

Read the skill →

Security model in one minute

A push address is a bearer capability. Keep it out of screenshots, logs, source control and public URLs. The official delivery service processes the request in order to deliver it; it is not an end-to-end encrypted secret channel. Do not put credentials, recovery codes, financial data or private content in a notification title, body, route or URL.

What Drel does not do

  • A remote page does not receive native Bridge, file, photo-library, clipboard or approval powers merely because it opened in Drel.
  • A Web App Manifest alone does not make a page an offline app. Durable offline launch requires a verified package and a user-initiated install.
  • A successful API response means the relay accepted the request; it is not a guarantee that a particular device displayed it.