Add iOS app implementation plan and architecture documentation - #67
Open
shellen wants to merge 3 commits into
Open
Add iOS app implementation plan and architecture documentation#67shellen wants to merge 3 commits into
shellen wants to merge 3 commits into
Conversation
Lays out a 5-phase roadmap for building the Expo + WebView iOS companion app based on the existing build spec, covering project scaffolding, fetch bridge, native folder access, polish, and App Store distribution. https://claude.ai/code/session_01G9YWzKz5uVxSwMf17RFeaU
The plan was missing context about how the desktop app is now Tauri (not Swift) and how articles actually reach the phone. Adds a detailed "How Articles Get to Your Phone" section explaining iCloud Drive, Dropbox, Google Drive, and Syncthing workflows, plus a note clarifying that the iOS Swift module is separate from the desktop Tauri shell. https://claude.ai/code/session_01G9YWzKz5uVxSwMf17RFeaU
Adds a detailed plan for on-device article fetching in the iOS app. The extraction pipeline (fast-xml-parser, Readability, linkedom, Turndown) is pure JS and ports directly. Paywalled content uses WKWebView login with WKHTTPCookieStore instead of Chrome cookie decryption. https://claude.ai/code/session_01G9YWzKz5uVxSwMf17RFeaU
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
2 participants
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.
Summary
This adds comprehensive documentation for the PullRead iOS companion app implementation, detailing the complete roadmap from project scaffolding through production release, including a novel on-device sync engine that ports the extraction pipeline to React Native.
Key Changes
Phase 1-5 implementation plan: Structured breakdown of iOS app development from Expo project setup through App Store submission
Folder access architecture: Detailed explanation of how users select and persist access to cloud-synced folders (iCloud Drive, Dropbox, Google Drive, Syncthing) using iOS security-scoped bookmarks
Phase 6: On-device sync engine: Novel approach to enable phone-only users and offline reading
fswith nativeFolderAccessModule.writeFile()bun:sqlitewithexpo-sqlitefor URL deduplicationArchitecture rationale: Comparison of Expo + WebView against alternatives (Capacitor, PWA, full React Native rewrite, native Swift), justifying the chosen approach
Implementation details:
.minimalBookmarkfor iOS)Future features roadmap: Highlights, notes, share extension, widgets, background refresh, Spotlight search, Shortcuts integration
Notable Details
The plan emphasizes code reuse: the existing self-contained HTML/JS viewer (~400KB) runs unchanged in a WebView, while a native Expo module handles iOS-specific folder access. The sync engine reuses the desktop's pure-JavaScript extraction libraries without modification, making the iOS app capable of full RSS syncing without requiring the desktop app.
https://claude.ai/code/session_01G9YWzKz5uVxSwMf17RFeaU