Linkora

Releases

• Jul 29, 2026 0.19.0
  ## What's New - Added a crash handler on Android, you can directly send the report via mail or copy logs from the crash activity - Both the folders and tags page tabs are now shown explicitly in the Collections Screen ## Fixes - web-capture services are initialized as expected after startup on desktop --- **Full Changelog**: https://github.com/LinkoraApp/Linkora/compare/release-v0.18.0...release-v0.19.0
• Jul 21, 2026 0.18.0
  ## What's New - Linkora now supports saving webpages as standalone HTML files locally; all processing happens on-device. - This feature is based on [capture-core](https://github.com/LinkoraApp/capture-core), a [monolith](https://github.com/Y2Z/monolith) fork, and is disabled by default. You can enable it from Data Settings Screen -> Web-page Captures. - A new database will be created at your chosen path to map links to their respective folders. All folder names are random UUIDs, and their mappings are stored in the database at the chosen location. This database is completely portable, so you can manually check the folder mappings if you want. - Linkora supports reading the external database even after reinstalling the app. Linkora will regain ownership of the database file that previously existed on Android. - Since the external database contains all the mappings, deleting it will result in a loss of these mappings, and Linkora will not be able to locate the files when you want to open them. - Upon reinstallation, make sure to choose the folder where the database previously existed. This will avoid creating duplicate folders for the same link. - All processing happens in the background via WorkManager on Android. If you are saving webpages for all links via the app, you can cancel the task and it will be cancelled. However, individual downloads when saved or refreshed aren't tracked. If you want to kill all captures, turn off the web capture feature; this will stop the ongoing process on both Android and desktop. On Android, notifications will be used to show progress, while on desktop, you can see a downloading icon in the navigation rail. - The link text field will no longer be autofocused when sharing links from external apps (by @gycgabriel).

  More…

  ## Fixes - Fixed an issue causing unusual random cancellations when refreshing all links. --- **Full Changelog**: https://github.com/LinkoraApp/Linkora/compare/release-v0.17.2...release-v0.18.0
• Jul 8, 2026 0.17.2
  ## What's New - Security token field in sync-server setup now includes a show/hide toggle (by @linky3754) - Shared intent title will now be used by default when sharing the links via external apps; force-fetching metadata saves fetched info instead (by @linky3754) ## Fixes - App no longer crashes when opening links if no browser is installed; instead, a snackbar notification indicates that the browser is missing. - Desktop target now uses the preferred preferences when refreshing all links.

  More…

  And other minor improvements across the codebase. --- **Full Changelog**: https://github.com/LinkoraApp/Linkora/compare/release-v0.17.1...release-v0.17.2
• Apr 8, 2026 0.17.1
  ## Fixes * Fixed the `field userAgent is required...` messages when importing JSON files.
• Apr 7, 2026 0.17.0
  Linkora now runs on Web via Kotlin/Wasm and is currently experimental, try it out: https://linkora-app.netlify.app/ (scroll to bottom of this release notes for complete info) If you use the sync-server, you must be on the latest version, v0.3.0 (at the time of writing this). Also, [fill out this survey](https://forms.gle/75ww25CLQqZuSSuZ6) if you use sync-server, it'll give me insights on a possible rewrite in Rust with more solid syncing mechanisms and a couple more features beyond saving and syncing links. From this release, all platform-specific artifacts are built via GitHub Actions. ## What's New - A new proxy is available to route all your requests through it, built specifically for the web app and disabled by default on other platforms since there's only one public instance. - You can self-host the proxy, see the [proxy repository](https://github.com/LinkoraApp/proxy) for more info. - You can now resize the list pane in the collection screen (currently restricted to two boundaries) on desktop, web, Android tablets, or any large screen.

  More…

  - Added scrollbar support to Regular (and title-only) and grid layouts. - Replaced the default snackbar with a custom UI. ## Internals - Collections Screen is now completely based on Material 3's adaptive-layout library, and the detail pane now uses its own navigation. I haven't migrated to Nav3 yet. There are a couple of limitations with the current Nav2, it basically binds the backstack with the NavHost and nested navigation becomes a mess. Had to do some workarounds. Once Nav3 is stable for KMP, I'll migrate eventually. - Preferences are now based on UDF principles instead of the global object approach it previously used. There wasn't a strong reason to migrate on its own, but web handles preferences differently than Android and desktop, and forcing it to work the old way would've been a mess. I needed a common ground that keeps things simple, so that's that. - All `expect`/`actual` definitions no longer directly reference the `File` object received from a specific platform since it isn't supported on web. It now uses either `ByteArray` or whatever works in the specific case. Basically, a lot of things are refactored. Again. ## State of the Web App Linkora on web is not stable by any means. It runs fine on web itself, but the core component that handles the database isn't stable, primarily because of OPFS. This is already a known issue (https://sqlite.org/forum/info/58a377083cd24a). If there's any possible workaround, I'll implement it and put out a release.
• Feb 16, 2026 0.16.0
  If you use sync-server, you must use the latest sync-server version, v0.3.0 (at the time of writing this). ### Performance Improvements These benchmarks are based on 100K+ rows collectively across multiple tables, with a JSON file being 11.4 MB and an HTML file being 7.24 MB. Both import operations are stable and take linear time to complete instead of quadratic. These reports are based on OPPO A77S hardware. - Importing via JSON now uses 56.1% less memory (heap) and, on average, 17% more CPU efficiency. - Importing via HTML now uses 58.7% less memory (heap). While it uses 6.2% more processing power on average, this increased throughput allows it to complete successfully without the previous version's crashes. <img width="3600" height="2400" alt="performance_comparison" src="https://github.com/user-attachments/assets/2ff66263-3824-440d-b85a-f7c36c47ba8a" />

  More…

  - Note: The performance gains might actually be higher than what is listed here. In the previous versions, both HTML and JSON imports crashed before finishing, so this comparison is based on the current stable version (0.16.0) against the recorded usage of the old version right before it crashed. - HTML exporting, copying of folders, and a couple of others now run in linear time instead of quadratic. - Pagination is now implemented using a cursor-based approach instead of offset-based. - While this might be overkill for an app like Linkora, this prevents the app from processing thousands of skipped rows just to reach the current page, significantly reducing unnecessary database overhead during deep scrolls. ### What's New - Added an option to force write default internal folder IDs to respective links (in data settings screen) ### Fixes - Fixed the "PROCESS ENDED" crashes that occurred during large data imports. --- **Full Changelog**: https://github.com/LinkoraApp/Linkora/compare/release-v0.15.2...release-v0.16.0
• Feb 6, 2026 0.15.2
  ### Fixes - Sets AMOLED theme based on preference as expected (android-only) (#132) As the desktop version remains unchanged, you can use builds from https://github.com/LinkoraApp/Linkora/releases/tag/release-v0.15.1 as usual. **Full Changelog**: https://github.com/LinkoraApp/Linkora/compare/release-v0.15.1...release-v0.15.2