Conversation
Ports Connect, Agents, Chat and Feed from the SwiftUI app to Expo SDK 57 against the same mobile API. Lives outside the pnpm workspace. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N4Td1Sf9cr1ZvAJ3uowaNJ
Header buttons become Stack.Toolbar items and menus, buttons render as SwiftUI glass buttons through @expo/ui, the composer sits in a GlassView, and message long-press uses the SwiftUI context menu. Android and web keep React Native fallbacks. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N4Td1Sf9cr1ZvAJ3uowaNJ
- Install expo-updates with a fingerprint runtimeVersion so JS-only changes can ship to iOS and Android without store review, and add eas.json with preview and production channels. No update server is configured yet. - Add a config plugin that adopts Expo's ExpoAppSceneDelegate. Apps built with the iOS 27 SDK are killed at launch without the UIScene life cycle, and the generated AppDelegate doesn't use it. - Point the ios/android scripts at development builds, which prebuild switched them to. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Entire-Checkpoint: 01M3FNHDC0WP1BCHNMEZCNPJY0
…to claude/project-thread-y7mv3u
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a complete Expo (SDK 57, React Native 0.86) prototype of the Roost mobile application, enabling evaluation of React Native viability against the existing SwiftUI implementation.
Summary
A new
apps/mobile-expoapplication that ports four core screens from the SwiftUI app (apps/ios) to run on iOS, Android, and web platforms. The prototype connects to the same/api/mobile/v1API using device tokens, allowing it to run against a real Roost server or the native UI fixture.Key Changes
expo-secure-store(Keychain on iOS, SecureStore on Android, localStorage on web)lib/api.ts): Complete port of the Swift API client with bearer token auth, error handling, and user-facing error messageslib/conversation.ts): Revision-based polling, pending payload reuse after network failures, and message deduplicationlib/session.tsx): Secure connection storage and agent list cachingThemes.jsonNotable Implementation Details
.ios.tsxand.tsxsuffixes for SwiftUI integration on iOS while maintaining Android/web compatibilityreact-native-gesture-handlerfor swipe-to-reply with haptic feedbackhttps://claude.ai/code/session_01N4Td1Sf9cr1ZvAJ3uowaNJ