AlternateYou

Connecting the App to a Real Model Backend

The first provider-backed conversation replaced the generation engine without replacing the app's timeline, safety, or persistence boundaries.

The repository records 18 March 2026 as the point when the iOS remote engine connected to the project backend for a first end-to-end model conversation. The important change was not only adding a provider call. It was preserving the app's existing conversation and persistence boundaries while replacing the generation implementation behind them.

The app assembles timeline and memory context, wraps it in a typed live-chat request, and sends it to an app-owned backend. The backend selects the model, calls the provider, and returns a normalized result that the app maps into its existing generation events. Provider credentials stay outside the iOS client.

Later work added environment separation, request validation, task-aware model routing, an app-level access key, timeouts, rate limiting, and usage metadata. Live chat is the integrated remote task. Timeline creation and memory-summary request contracts also exist, but their remote paths remain scaffolded.

The export audit did not repeat a live provider call because the required integration configuration was intentionally unavailable. The milestone is supported by repository history and QA records rather than a fresh remote test.

← Back to AlternateYou