Skip to content
AppNorth
Log in

Reference

Versions

The installation snippets currently advertise SDK version 0.2.0 from https://github.com/victorgxn/appnorth-ios. This is the repository's configured installation version; it is not an assertion that every source change is already present in a published binary.

View Markdown

Supported integration

The native product is the AppNorth Swift library for iOS 16 and later. The source package declares Swift tools version 5.9. Apps install the compiled XCFramework through Swift Package Manager; use Install for the current dependency snippet.

Native on-device translation is conditionally available on iOS 18 and later. Basic community and chat integration does not require that optional translation feature.

The hosted dashboard, roadmap and changelog are browser surfaces for the iOS product. The repository's browser support policy targets the two latest stable Chrome, Edge, Firefox and Safari versions; local tests do not establish physical-device coverage.

API and persisted formats

The SDK talks to the /api/v1 contract. SDK package version, API contract version and persisted cache/queue format version are separate values. A package update does not imply that persisted data can be discarded or that a server endpoint changed.

Optional response fields can be added without requiring every client to read them. Changes to required fields, routes or established semantics need an explicit compatibility and migration review.

Update an integration

  1. Read the release notes for the exact package version you plan to install.

  2. Update the Swift Package dependency and resolve it in Xcode.

  3. Build the host app against that binary; do not rely only on examples compiled against the source checkout.

  4. Exercise anonymous participation, verified identity, account changes, private feedback, chat and a recoverable network failure.

  5. Check idempotent retries and any custom cache or queue storage before rolling out.

Keep the previous dependency resolution available for rollback. If a persisted format changes, preserve pending submissions and their idempotency keys or provide a visible recovery path. Do not silently erase queued user content.

Release verification

The repository's release checks include SDK tests, shared contract checks, the native example, a secret scan and XCFramework packaging. Publication, compatibility against a deployed server and physical-device validation require separate evidence.

The Swift API reference describes the checked-in source surface. Confirm availability in your selected release before adopting a symbol that was recently added. No historical release changelog is inferred from the current source tree.