Duplicate work
Multiple screens ask for the same resource and quietly multiply traffic, decoding, and battery cost.
Production networking for Swift 6.2+
Stop rebuilding your network layer.
NovaNetworkClient turns typed requests, shared work, cancellation, resilience, authentication, offline delivery, and realtime connections into one coherent system.
✓ Zero third-party runtime dependencies · Apache 2.0
ProfileViewGET /users/42
→HeaderViewGET /users/42
→RetryCacheAuthMetrics
200One response, two typed values
451automated tests
90%+unit coverage policy
3library products
0third-party dependencies
The real problem
Networking starts simple.
Production doesn't.
Policy sprawl
Retry loops, cache rules, auth locks, and cancellation flags accumulate across services and view models.
Invisible failure modes
Offline writes, reconnects, rate limits, and token expiry appear only after the happy path ships.
One execution model
Describe intent once. Let policies do the hard work.
A stable request identity gives Nova one place to coordinate callers and apply production behavior. The API stays explicit while the infrastructure stays reusable.
Explore the architecture →- 1Describe
Method, URL, body, headers, and authentication scope form a typed request.
- 2Coordinate
A deterministic fingerprint joins equivalent in-flight work and tracks each subscriber.
- 3Execute
Resilience, cache, auth, transport, decoding, and telemetry run through one pipeline.
Batteries included, decisions exposed
A production stack, not another thin URLSession wrapper.
Adopt the pieces you need today without painting the next feature into a corner.
Shared in-flight work
Equivalent callers join one request. Each caller keeps independent cancellation semantics.
Resilience policies
Retry, rate limiting, circuit breaking, and HTTP-aware caching live in one execution pipeline.
Authentication refresh
Coordinate token refresh and prevent a burst of unauthorized requests from becoming a refresh stampede.
Offline delivery
Queue writes, replay them deliberately, and model recovery instead of hiding it behind a transport wrapper.
Realtime & transfers
Use WebSocket, Server-Sent Events, multipart uploads, downloads, and progress APIs from the same package.
Observable by design
Inspect lifecycle events, metrics, diagnostics, and deterministic test support without replacing the client.
Declarative endpoints
Generate request construction from an annotated Swift type, or generate whole endpoint types from an OpenAPI document.
Record and replay
Capture real traffic into a reviewable cassette and replay it in tests, previews, and offline demo builds.
Diagnostics you can see
Record what the client did, read retry waterfalls, and export a HAR that opens in any network inspector.
Authentication
OAuth 2.0 with PKCE, every grant, safe token storage, and one refresh shared by every caller.
Query layer
Server state by key for the screens that render it, with stale reads, shared fetches, and optimistic mutations.
From ad hoc to intentional
Keep business code about the request—not the machinery around it.
WITHOUT A COHERENT CLIENT
- Task dictionaries in every feature
- Retry rules copied between services
- Refresh locks tied to UI state
- Logs that cannot explain shared work
WITH NOVANETWORKCLIENT
- Stable request identity
- Composable, explicit policies
- Coordinated auth and cancellation
- Lifecycle events and metrics
Small surface, serious behavior
Your first typed response stays readable.
The simple case remains simple. Production capabilities are configured around it instead of leaking into every call site.
Read Getting StartedProfileService.swift
let request = APIRequest(
method: .get,
url: apiURL.appending(path: "users/42")
)
let profile: Profile = try await client.load(
request: request,
authScope: "current-user"
)✓ Typed, cancellable, observable, and shareable
Learn by building
From first request to production confidence.
01
Build your first request
Decode a public API response into a small Sendable model.
02Share concurrent requests
See equivalent callers join one in-flight network operation.
03Add bounded resilience
Choose deliberate retry, caching, and typed error boundaries.
04Model typed endpoints
Move repeated server operations behind reusable endpoint types.
Built for the code after the prototype
Ship the network layer once.
Start with one typed request. Add production policies when your app needs them.