@gram 2
doc blog-ios-guide
t Read .gram files on iPhone and iPad
d Import chosen files or folders, inspect history and search, and understand the iOS app's read-only and data-handling boundaries.
tag guides
view document

::rich
# Read, do not edit

Thegram for iOS is documented as a viewer for iPhone and iPad. It opens .gram documents from folders or files the person chooses, including iCloud Drive and other file providers. The app does not edit the source document. Treat this as an inspection surface: if a decision needs revision, use an authoring client such as the Mac app and verify the resulting file separately.

## Bring a file into the library

Choose a folder or individual file through the system file-provider flow, open a `.gram` document from another app, or put a document in the app’s own Documents folder. The app declares a `.gram` document type and supports opening files in place. For a folder, iOS security-scoped access is retained so the app can revisit the chosen location. The app coordinates file reads and keeps a cache mirror for multi-document recall and semantic indexing; that mirror is not the canonical file. If iCloud has not downloaded a file, the app requests it and reads it on a later refresh.

A practical import sequence is: select the folder or file you intend to read; wait for provider download if needed; refresh the library; open the document; compare its visible title and content with the expected file. For an app-local transfer, Finder file sharing or the Files app can place `.gram` files in Thegram’s Documents folder. Opening a `.gram` from another app adds the single-file source to the library rather than importing it into a mutable iOS editor.

## Use history, graph and search

The iOS README describes document, dashboard, graph, inspector, timeline and search experiences. Selecting a revision changes the views together. Historical display is for review; it is not a write operation. Search can use literal keywords and a local semantic index. The README describes an embedded quantized EmbeddingGemma model and background indexing conditions; semantic results are derived aids, not explicit stored relations or proof that a sentence is true. The cached snapshot and semantic index are app data, not alternate versions of the user’s .gram source.

## Optional account documents (Thegram Vault and Google Drive)

Google Drive is not automatically available simply because the app is installed. The README describes signing in to a Thegram account first, adding a Google account through the server’s `/drive` page, and then seeing `.gram` files from the Drive Thegram folder as a read-only downloaded copy. The reviewed feature branch also lists a Thegram Vault source after sign-in; those account documents are read-only too. The app keeps tokens in Keychain and removes fetched copies when signing out. This route has more identity and network dependencies than opening a local provider file. If you do not need that route, use a file or folder you already control instead.

## Example

A teammate sends `review.gram`. Open it from Files or the mail attachment, check that the document and expected records appear, and use history to inspect how the decision developed. If you need to propose a correction, do not assume an edit control exists or alter the read-only copy outside its owning provider workflow. Ask the document owner for an authoring path, then reopen the resulting canonical file to confirm the change.

## Security and boundaries

The app reads chosen files through system-granted access; a security-scoped bookmark does not mean the app can browse every file on the device. Caches and search indexes are local derived data. Account-backed Drive reads transmit requests and involve Vault plus Google authorization; they are different from local import. The privacy manifest lists account-related data categories such as email, name, user ID, and other user content for app functionality, with tracking declared false. Do not translate that manifest into an unsupported claim that no personal data is processed, nor into a claim that all document content is uploaded. The README specifically describes Drive documents as fetched read-only copies; local and account flows have distinct paths.

For exact current behavior, read the iOS README, project configuration, library implementation and privacy manifest. The iOS beta or distribution state should be confirmed from the official product page at the time of use. This guide does not assert App Store availability or promise editing, synchronization, or full parity with Mac.

## Sources

Based on the checked iOS README, app configuration, library source and privacy manifest, with public product guidance for cross-device context.
::end

SRC ios-readme
d Internal source reviewed at revision df70e4593da82cfae107e989bf029c21bbd42580 on branch frontend/figma-mobile-refinement (not main; README.md; App/Sources/Account/VaultAccount.swift; App/Sources/Library/Library.swift); not publicly available.
t iOS read-only viewer README and account document flow
SRC ios-config
d Internal source reviewed at revision df70e4593da82cfae107e989bf029c21bbd42580 on branch frontend/figma-mobile-refinement (not main; project.yml); not publicly available.
t iOS document and platform configuration
SRC ios-library
d Internal source reviewed at revision df70e4593da82cfae107e989bf029c21bbd42580 on branch frontend/figma-mobile-refinement (not main; App/Sources/Library/Library.swift); not publicly available.
t iOS library access implementation
SRC ios-privacy
d Internal source reviewed at revision df70e4593da82cfae107e989bf029c21bbd42580 on branch frontend/figma-mobile-refinement (not main; App/Resources/PrivacyInfo.xcprivacy); not publicly available.
t iOS privacy manifest
SRC ios-product-page
t Public iPhone and iPad product information
ref https://thegram.one/
K readonly
t iOS is a read-only document viewer
d The app can inspect chosen .gram files and history but does not author changes to the source document.
source ios-readme
source ios-config
supports import-route
K import-route
t iOS reads chosen files and folders
d File-provider access, app Documents, and optional read-only Thegram Vault and Google Drive account documents are distinct sources with different access boundaries.
source ios-library
source ios-readme

K privacy-boundary
d Do not generalize the local-file path into a claim about account-backed authorization or downloaded copies.
source ios-privacy
source ios-readme
t Local import and Drive account flow have different data paths
supports readonly

@gram-history 6
@rev 0 2026-10-12T08:08:28.794Z - 38982adace5cb1f9e8a63610eb7a7729654203b31359d3473c6493c516d00737
@rev 1 2026-10-12T08:14:42.154Z - req=blog-editorial-knowledge-ios-guide-20261012 dig=e40fad5ff24e23fd cdbc632ca507a1c688a04cb049bd4d6f03aaa7c17b1ae9bf95f4a2c6f78f69ae
@@ 67 2 2
X privacy-boundary
t Local import and Drive account flow have different data paths
@@ 72 1 0
@rev 2 2026-10-12T08:40:15.779Z - req=platform-corrections-ios-guide-20261012 dig=ac9e5e1a97971027 kind=SourceImported c34611ad6566744d8c29835ad7254d9972ef220825f9951ba6b24305881314a0
@@ 22 1 1
## Optional Google Drive reading
@@ 24 1 1
Google Drive is not automatically available simply because the app is installed. The README describes signing in to a Thegram account first, adding a Google account through the server’s `/drive` page, and then seeing `.gram` files from the Drive Thegram folder as a read-only downloaded copy. The app keeps tokens in Keychain and removes fetched copies when signing out. This route has more identity and network dependencies than opening a local provider file. If you do not need that route, use a file or folder you already control instead.
@@ 32 1 1
The app reads chosen files through system-granted access; a security-scoped bookmark does not mean the app can browse every file on the device. Caches and search indexes are local derived data. Account-backed Drive reads transmit requests and involve Vault plus Google authorization; they are different from local import. The privacy manifest lists account-related data categories such as email, name, and user ID for app functionality, with tracking declared false. Do not translate that manifest into an unsupported claim that no personal data is processed, nor into a claim that all document content is uploaded. The README specifically describes Drive documents as fetched read-only copies; local and account flows have distinct paths.
@@ 42 2 2
t iOS viewer README
ref https://github.com/clab-one/thegram-ios/blob/main/README.md
@@ 45 1 0
@@ 47 0 1
ref https://github.com/clab-one/thegram-ios/blob/main/project.yml
@@ 48 1 0
@@ 50 0 1
ref https://github.com/clab-one/thegram-ios/blob/main/App/Sources/Library/Library.swift
@@ 51 1 0
@@ 53 0 1
ref https://github.com/clab-one/thegram-ios/blob/main/App/Resources/PrivacyInfo.xcprivacy
@rev 3 2026-10-12T08:56:16.352Z - req=platform-final-fixes-ios-guide-20261012 dig=5cab04fc46d8698b b11dce005aa11d33596823b42ea5959d8e8b0e9490b71a5c849f3dd2dfb62b6e
@@ 64 1 1
d File-provider access, app Documents, and optional read-only Drive copies are distinct sources with different access boundaries.