Posts get deleted, restricted, and taken down with their accounts.
Nookic keeps the post itself — words, pictures, the author's tags —
on your iPhone, using your own signed-in session. Not the link. The post.
Five things Nookic is for.
The words and the pictures are copied to the device as you save. When the post is edited, restricted, or deleted, your copy is still the one you read.
Every archive arrives labelled — the author's own hashtags, plus a few from a model running on the phone. Edit them whenever. On a recent iPhone there is nothing to paste and nothing to configure.
Two columns, covers at their own proportions, never cropped. Tap one and it fills the screen; tap again for the words.
The collection is on the phone, so it opens on a plane, in a lift, in a queue — and in five years, when the link no longer resolves.
No account to create, no analytics, no server. Nookic has nowhere to send your collection, because there is nowhere. Turn on iCloud sync and it goes to your iCloud — still not to us.
Nookic archives what you can already see, signed in as yourself, on your own device.
Use the share sheet from the app you were reading in. Or copy the link — Nookic notices it the next time you open the app.
You sign in to the site inside Nookic, once, the same way you would in a browser. From then on it reads what your own session can reach.
Text and pictures are stored on the device, tags applied, and the post appears on the wall — ready to read with the network off.
A private collection should be private in the dull, structural sense: there should be no mechanism for it to be otherwise.
Saving a link, or taking a screenshot.
| Bookmark | Screenshot | Nookic | |
|---|---|---|---|
| The words, as text | Only while the link works | Pixels, not text | Kept |
| Every picture | Fetched each time | Whatever fitted the screen | Kept |
| Opens offline | No | Yes | Yes |
| Searchable later | By title, if that | No | Words and tags |
| Survives the post being taken down | No | One screen of it | All of it |
| Needs an account | Usually | No | No |
The ones worth answering before you install anything.
No. You sign in to the site itself, in a web view inside Nookic, exactly as you would in a browser — including scanning a QR code if that is how you normally sign in. The cookie stays in Nookic's storage on the device. There is no server that could receive it.
No. Nookic has no sharing feature, no public page, and no server. If you turn on iCloud sync, your collection is in your own iCloud account, which we cannot reach.
Nookic is for keeping what you are allowed to keep, for your own reading. It signs in as you and sees what you can see — it does not work around anything. Some posts cannot be archived at all, and that is normal: platforms change what they serve to a browser whenever they like.
Not on a recent iPhone — the model runs on the device and nothing leaves it. If you would rather use a hosted model, you can add your own key; then a post's title and text are sent to that provider to produce tags. Images are never sent.
Xiaohongshu (RED), Threads, and X. Each one is its own piece of work — a different page, a different way of hiding what it serves — so the list grows slowly and honestly rather than by claiming everything.
There is one, and it is how Nookic started — but it is a personal build, not something on sale. The iPhone app is the one being made for other people.