Device Storage and Offline Use
Orrique separates your content from data it can download again. Your collection and diary remain usable offline. Public catalog browsing may need a connection after its rebuildable local database has been cleared.
Open Device Storage
Section titled “Open Device Storage”- Open Settings.
- Under Data and Planning, choose Device Storage.
- Review Offline collection, Rebuildable downloads, Enhanced background removal, User-created assets, and Managed by iOS.
Pull down on the page to refresh its measured sizes.
What stays offline
Section titled “What stays offline”The following are personal journal content and are not removed by Clear Rebuildable Downloads:
- owned fragrances, containers, shelves, and manual entries
- diary entries, formulas, ratings, and personal notes
- saved bottle photos and catalog photos already attached to an owned fragrance
- backups, pending changes, and Share Studio user images
You can add, edit, move, archive, and remove collection items without the public catalog. Catalog matching, shared facts, and public image lookup can wait until the device is online again.
How catalog downloads work
Section titled “How catalog downloads work”Catalog synchronization stores text, compact bottle outlines, framing, an image-availability flag, and a local text-search index in a rebuildable on-device database. It does not download a bottle image with every catalog row. Orrique builds the complete database once, then applies changed public records in bounded pages and skips payload or index work when a row is unchanged. Lightweight deletion checks keep removed public records from lingering without rewriting the complete catalog. Routine search and browsing read bounded pages from that database instead of loading the complete public catalog into memory.
Bottle, base, and note images load only when a screen needs them. Collection can update saved crop details from metadata without opening every cover image. If an owned fragrance has a public catalog image but no saved photo, Orrique can attach that image as a normal journal photo so it remains available offline.
This order lets names, notes, search results, and bottle shapes appear before heavier images finish.
Storage behavior and limits
Section titled “Storage behavior and limits”The catalog database grows with the public text catalog and has no fixed byte cap. Device Storage shows its measured size. Image, lookup, diagnostic, and semantic caches keep the fixed limits below.
| Rebuildable area | Limit or behavior |
|---|---|
| Catalog data and text search | Rebuildable local database seeded once, then updated in bounded changed-record pages without catalog image payloads; size follows the public catalog |
| Bottle and base images | 12 MB, oldest unused images removed first |
| Note images | 4 MB, oldest unused images removed first |
| Local semantic search | 4 MB, limited to owned and recent catalog candidates |
| Web lookup results | 2 MB total, with entry limits and expiry |
| Diagnostics | 2 MB and a fixed file count |
On the first launch after this update, Orrique converts existing catalog downloads once. That pass can briefly use more processing. During this safety phase, the catalog total can include both the database and the previous compressed copy.
Personal content can grow when you add fragrances, photos, diary entries, backups, or design assets. Orrique targets about 80 KB for each stored journal photo, although transparent or highly detailed images can be larger. Catalog photos attached to owned scents count as saved photos. That growth represents content you chose to keep and is reported separately where Orrique can measure it.
Temporary in-memory image allowances adapt to the device instead of reserving one fixed amount everywhere. While a photo or uploaded Share Studio mark remains mounted onscreen, it keeps its last complete decoded frame through ordinary cache eviction, so an unrelated card edit does not replace it with a placeholder. Orrique clears rebuildable memory images when it enters the background or receives memory pressure. This can make an image decode again later, but it never deletes a saved journal photo or design asset.
Returning after the system closes Orrique
Section titled “Returning after the system closes Orrique”The system can reclaim a suspended app when another app needs memory. On iPhone or iPad, a Live Activity can remain visible because the system presents it separately from the Orrique app process.
Orrique saves a small device-local record of your last main section and stable detail path. If iOS later launches a new Orrique process, the app restores that location after the private journal is ready. On iPhone, restoration starts from the last real tab. On iPad and Mac, it can also restore a consumer section from the sidebar. An incoming widget, notification, Shortcut, Spotlight result, or app link still takes priority and opens its requested destination.
Transient sheets, one-time actions, and unsaved editor state are not reopened automatically.
Orrique does not run a keepalive task. Before suspension it releases the shared rebuildable image cache and loaded processing models. It keeps the few image frames still mounted onscreen for the system’s later app-switcher snapshot. Returning gives durable queued deliveries one bounded attempt and coalesces refresh work instead of starting a polling loop. A photo-heavy screen can therefore decode saved images locally again, but your journal and downloaded disk caches remain available.
Clear rebuildable downloads
Section titled “Clear rebuildable downloads”Choose Clear Rebuildable Downloads, then confirm. Orrique resets downloaded catalog data to its bundled offline baseline and removes temporary browsing images, note images, local semantic vectors, web lookup results, and retained diagnostics.
It does not remove your collection, diary, manual entries, saved photos, backups, pending changes, or Share Studio images. Public data can download again as you use the app online.
Enhanced background removal
Section titled “Enhanced background removal”Standard background removal uses Apple’s on-device Vision tools and works without an extra Orrique download.
The optional enhanced model is about 42 MB after installation. Installing it requires about 160 MB free while the model downloads, extracts, and prepares. Orrique downloads it only after you confirm from Device Storage. You can remove it at any time, and standard removal continues to work.
Orrique accepts only the verified asset pinned into the installed app. It checks the exact CloudKit record, version, size, and archive fingerprint before extraction. It then prepares and loads the model in temporary storage and checks its required input and output before replacing the installed copy. A failed download, verification, preparation, or replacement leaves an already verified installation unchanged.
Older compiled caches do not contain the required verification receipt. Orrique discards those unverified caches after this update, so Enhanced background removal may show as not installed until you download it once again. Standard Vision removal remains available before the download and while you retry.
If the download cannot reach the model catalog or fails verification, Orrique does not keep a partial installation. Check the connection and available space, then choose Download Enhanced Model again.
Orrique unloads the enhanced model from memory when the app moves to the background or the system reports memory pressure. It also releases loaded Natural Language model references when the app enters the background. Removing the enhanced model from Device Storage deletes its installed files, including older Orrique model versions. Natural Language assets remain managed by the operating system and load again only when a semantic search needs them.
Storage managed by iOS
Section titled “Storage managed by iOS”Apple Intelligence, Foundation Models, Natural Language embeddings, Vision, and OCR can use assets managed by the operating system. Orrique does not download those assets into its own cache and cannot accurately include or remove them from Device Storage. Use iOS or macOS storage settings for the complete device-level app footprint.