Documents and notes decision
GoodLinks
A technically capable developer can reproduce the core read-and-annotate workflow and export features in about a week, but matching GoodLinks' deep OS integrations, polish, iCloud reliability, and multi-language support would take more effort—so building a useful subset is realistic, full parity is not.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Save a URL -> fetch & extract article text -> store article, tags and highlights -> open in reader UI and annotate -> export highlights
What it still won’t have
- Deep Shortcuts integration
- AppleScript automation on macOS
- Widgets and home-screen quick actions
- Built-in iCloud sync across devices (unless implemented)
- Localized translations provided by the vendor
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 6 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal universal iOS/macOS read-it-later app using SwiftUI + Combine + Core Data (or SQLite) and an open-source Readability HTML-to-text library. In scope: a share extension to save URLs, background fetch and article extraction, a reader view with font/spacing/theme controls, highlight and note attachments saved to the local DB, tags and starred state, Markdown export of highlights, full-text search, and optional CloudKit-based iCloud sync toggle. Out of scope: App Store submission, offline installer, advanced UI polish, multi-account cloud servers, and proprietary macOS AppleScript shortcuts (provide basic URL schemes instead). Include error handling for network and parsing failures, unit tests for extraction/storage/search, and a small e2e UI test covering save -> view -> highlight -> export.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 7 cited sources+3
- Evidence score60
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 7
Every page the run actually retrieved.
- official productGoodLinks — The Better Way to Save and Read Articles
- official productGoodLinks features list
- official productGoodLinks platform & integrations
- official productGoodLinks automations & OS support
- official productGoodLinks desktop automation
- open sourceomnivore-app/omnivore
- open sourcewallabag/wallabag
Integrity checks
What held up, and what did not.
