Technical concept
With Looksyk I want to create a local platform to collect information.
Currently, the backend renders all content in Markdown, which is displayed with Marked in the frontend. This makes Looksyk relatively close to the Markdown standard. Code highlighting is done with highlightjs and emojis with openmoji. The application is wrapped in an electron app (with electron forge). If you want to synchronize your graph, you can use the integrated Git interface. Since the data is stored in Markdown files on disk, you can also use your own sync tool.
Even if the project is currently a pure web project, I would not deploy it publicly because the project in its current state has not paid much attention to security (for example Injection-Attacks or Path-Traversal-Attacks).
Currently, the backend is very fast, my Logseq graph (~900 pages and 900kb text) is scanned and indexed in milliseconds (~80ms on a 3-year-old Laptop). That's why Looksyk does not have a database, reading new data into RAM is fast enough. Look at the Benchmarks.
The frontend still has some challenges, especially when it comes to the overall design and the mobile user experience, but I am working on it.
Tested browsers:
| Browser | Compatibility |
|---|---|
| application-wrapper (Electron) | works |
| Chromium / Chrome | works |
| Firefox | works on nightly (Jan 2025), contenteditable=plaintext-only required |
| WebView | works, but copy-pasting files has issues |
Tested operating systems
| OS | Compatibility |
|---|---|
| Arch Linux (AUR) | works, preferred (AUR package: looksyk-desktop) |
| Linux (any) | works, e.g. AppImage (download from Releases) |
| docker (linux, windows, mac) | works. If no environemnt variable for the key location is provided, only system-git support is available for sync |
| Android (at least arm64) | works, no system-git available, but git with PAT-Auth is compiled into the app |
| Windows | Portable windows build exists (download from Releases). Sync is tested and a version of git is already packaged into the portable-build. |
| MacOs | Not tested. Keyboard shortcuts are currently only designed for a Windows keyboard layout, but this can be changed via a pull request. There are also likely to be challenges in the build script. Otherwise, Looksyk is programmed to be platform-independent. |
Project work and future
The project is a little hobby of mine, and I program a few lines sometimes when I feel like it and have the time.
I am happy about every contribution, but I cannot guarantee that I will implement every feature request.
If you have any changes or suggestions, please send me a pull request. For feature requests and bugs, you can submit an issue (or a pull request if you can).
Current status of the Android app (Tauri V2)
An Android app based on Tauri has been under development since August 2026. The app is stable, but some features aren't yet perfectly adapted for mobile view. This applies not only to the Android version but also to the Docker version. I welcome your feedback. In addition, some actions may cause the app to freeze briefly while data is being processed. After processing, the app works as usual.
The following functions have not yet been fully implemented:
- Mobile-specific behavior: Content assist / code completion does not open when using software keyboards. Improvements are planned but have not yet been implemented.
Replacing the Electron version with a Tauri version for the desktop
I would love to replace the Electron version with a Tauri version for the desktop, but unfortunately, there are still a few challenges for which solutions have not yet been finalized.
- Inserting files via copy-paste has not yet been implemented.
Roadmap
The simple and quick answer: There is currently no roadmap.
Looksyk currently includes all the features I urgently need. Of course, many smaller changes would be desirable, such as improving the mobile user experience, making the query language more flexible (e.g., through default parameters or by breaking the strict parameter order), improving the Kanban view, supporting additional file types in documents, enabling the editing of text-based assets, or moving Markdown rendering from the frontend to the backend.
When I have time, I will continue working on one or two of these topics. If you have any suggestions, ideas, or even pull requests, please let me know.