Noughty Tours iOS SDK
Not written yet
These pages are a placeholder. The structure mirrors the Web SDK so the two read the same way, but the content below is not yet verified against the shipping iOS SDK.
To fill these in, we need: the SDK's public interface (the Swift package or its generated headers), its distribution channel, and its minimum deployment target.
What this section will cover
The iOS SDK is expected to ship the same two halves as the Web SDK — a typed data client and ready-made screens — over the same data model and the same authentication model.
| Page | Content |
|---|---|
| Installation | Swift Package Manager / CocoaPods, deployment target |
| Quick start | From an empty app to a tour on screen |
| Authentication | Token provider, and the shared JWKS trust model |
| Client | Tours, floors, rooms and scans |
| Views | The equivalents of the four React screens |
| Types | Swift model types and enumerations |
In the meantime
The Web SDK documentation is accurate about everything that lives on the server side — the tour hierarchy, scan statuses, visibility and slugs, the presigned upload flow, and the whole token-minting recipe. Only the client-side API surface differs.