When you hit a long piece in the phone browser that you actually want to sit with, use the system share sheet and pick 成书. The phone extracts the article; EPUB, Markdown, HTML and plain text are packed on device. PDF still uses the conversion API. The file opens in WeChat Reading, KOReader, or another app.

Once the format and destination are set, it does not need to sit in the background. You only see it in the share sheet.

Reading long articles in a phone browser is miserable: ads, floating popups, and constant prompts to open an app.

That kind of writing belongs in a reader. WeChat Reading has typesetting and translation. KOReader is what you want on e-ink — fonts and page-turns feel right.

On Android the two sides barely meet. Readers want a local file. The browser only shares a URL. Getting an article into a reader used to mean: copy the link, find a converter, wait, download, then dig through the file manager to open it. By then the reading mood is gone.

I don’t want Pocket. I don’t want this on someone else’s server, and I don’t need a social layer. Both ends are already on the phone. What’s missing is a clean pipe.

This tool does three things:

• Sit in the system share sheet.
• Take a URL, strip it to the article, lay it out as EPUB, PDF, Markdown, or plain text.
• Hand the file to any app that can open it — a reader, or an AI.

It remembers links it has already seen, so it won’t fetch them twice. Set a format and an app, then ignore it.

This page is a test case. If 成书 is installed, share it from the browser and see how it looks in your reader.