@idapt/browser-app-sdk 0.2.0 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -7,14 +7,18 @@ in-idapt app the glue beyond plain API calls:
7
7
 
8
8
  - the **cookie auto-connect** (auto sign-in for your app, no key handling),
9
9
  - per-app **key/value data** (`client.data.*`) and your app's **bundle reader**,
10
- - the workspace **data plane** `client.kv` (Datastore KV), `client.blobs`
11
- (object store), `client.tables` (structured documents), and `client.realtime`
12
- (broadcast / presence / live subscribe),
10
+ - realtime broadcast, presence, and live subscribe through `client.realtime`,
13
11
  - the **React hooks** (`@idapt/browser-app-sdk/react`) — including
14
- `useChannel` / `usePresence` / `useLiveQuery` for realtime,
12
+ `useChannel` / `usePresence` for realtime,
15
13
  - the full v1 API surface (it composes
16
14
  [`@idapt/sdk`](https://www.npmjs.com/package/@idapt/sdk)).
17
15
 
16
+ Pre-GA/default-off products are not part of the browser-app SDK public surface
17
+ while their feature flags are off. That includes workspace Data Plane
18
+ (`Datastore/KV`, Blobs, Tables), Repositories, Hub/store, workspace Skills, and
19
+ Functions. Use `client.data.*` for an app's own per-(user x app) KV; it is a
20
+ separate runtime surface backed by `/api/browser-app/data/*`.
21
+
18
22
  There is **no off-idapt local mode** and **no `window.Idapt` IIFE** — an app
19
23
  built with this SDK must run on idapt (the cookie bootstrap needs the idapt
20
24
  origin). `connect()` throws if the app is not served by idapt.