[!NOTE]
Status: public beta. All three apps are now in public beta on Android, iOS, and
Desktop, and anyone can
join the test.
The Web version is still in alpha: usable for trying things out, but some parts
are not settled yet. Development moves quickly right now — expect rough edges,
frequent releases, and the occasional breaking change. Feedback is what the beta is
for: open an
issue or write to
spectacled@techbee.at.
Spectacled
Open, standards-based journals, notes, and tasks — synced over CalDAV, on your own server.
Spectacled is a family of apps for Android, iOS, Web, and Desktop, built on the VJOURNAL and VTODO components of the iCalendar standard and synced over CalDAV. No proprietary backend, no account required — your data lives on whatever CalDAV server you already trust (Nextcloud, Radicale, or anything else that speaks CalDAV), and Spectacled is just the client.
It's one shared Kotlin Multiplatform / Compose Multiplatform codebase, built into three apps:
| App |
Uses |
For |
| Spectacled Journals |
VJOURNAL |
Dated journal entries |
| Spectacled Notes |
VJOURNAL |
Free-form notes |
| Spectacled Tasks |
VTODO |
To-dos, with status/priority/due dates |
📸 Screenshots
Screenshots coming soon.
Why
The iCalendar standard (RFC 5545) has included the VJOURNAL component for journal/note entries since 1998, but almost nothing actually supports it: KOrganizer and GNOME Evolution offer rudimentary support on Linux only, and jtx Board — an earlier project by the same author — was the first mobile app to support it fully, but relies on DAVx5 for sync and only exists on Android.
Spectacled aims to close that gap: a single, standards-based app for journals, notes, and tasks that works the same way on Android, iOS, Web, and Desktop, talks CalDAV directly, and leaves your data exactly where you put it. No vendor lock-in, no proprietary sync protocol — just iCalendar and CalDAV, the same open standards your calendar app probably already uses.
Features
- Connect to any CalDAV server and browse its collections
- Create, edit, and delete journal/note/task entries, with summary, description, categories, and classification
- Search and filter your entries
- Attachments (inline or linked)
- Parent/child relationships between entries (
RELATED-TO)
- Sync runs in the background and locally caches everything, so the app stays usable offline
- Light/dark theme, one consistent UI across every platform
📥 Download
Every available build is listed on the download page:
spectacled.techbee.at/download
🚀 Getting started
New to Spectacled? Connecting your first server takes about five minutes.
📖 Getting started guide — the whole setup in
writing: choosing a provider, connecting your account, creating a folder, and
writing your first entry, plus a troubleshooting table for when a server doesn't
behave.
🎬 Watch the walkthrough — the same thing as
a four-minute video.
One thing worth knowing before you pick a server: notes and journals are stored
as VJOURNAL, which far fewer CalDAV servers implement than the calendar and
task parts of the standard. Nextcloud-based servers handle it; several
CalDAV-capable mail providers don't, and can only be used with Spectacled Tasks.
The app suggests providers that are known to work, and the guide covers this in
more detail.
Support the project
Spectacled is, and will stay, open source. Maintaining it across five platforms (Android, iOS, Web, Desktop, plus the shared backend logic) is ongoing work — if it's useful to you, consider supporting it:
🛠️ Tech Stack
Built with Kotlin Multiplatform and Compose Multiplatform. Local storage and sync use SQLDelight (SQLite everywhere, including a persisted IndexedDB-backed store on Web), networking is Ktor, and dependency injection is Koin.
Exact versions aren't listed here to avoid this file going stale — see gradle/libs.versions.toml for the current pinned versions of everything, including the supported Android SDK range.
⚡ No Java / Gradle installation needed
This project uses the Gradle Wrapper and the Foojay toolchain resolver. The first build downloads Gradle and a JDK automatically — you only need Android Studio (for Android/Desktop/Web) and, for iOS, Xcode.
📁 Project Structure
📦 spectacled/
┣ 📂 shared/ ← Almost everything lives here: UI screens, CalDAV sync,
┃ iCalendar parsing, local database, repositories — used
┃ by every app and every platform
┃
┣ 📂 composeJournalsApp/ ← Platform entry point for the Journals app
┣ 📂 composeNotesApp/ ← Platform entry point for the Notes app
┣ 📂 composeTasksApp/ ← Platform entry point for the Tasks app
┃ (each targets Android, iOS, Desktop/JVM, Web/JS, and Web/Wasm; each is a thin
┃ wrapper that picks a variant and hands off to shared/'s UI)
┃
┣ 📂 androidJournalsApp/ ← Android entry point for Journals
┣ 📂 androidNotesApp/ ← Android entry point for Notes
┣ 📂 androidTasksApp/ ← Android entry point for Tasks
┣ 📂 baselineprofile/ ← Baseline Profile generators for the Android apps
┃
┣ 📂 iosApp/ ← iOS Xcode projects (kept out of the repo root so
┃ ┣ 📂 iosJournalsApp/ Android Studio treats the root as a pure Gradle
┃ ┣ 📂 iosNotesApp/ project; the Kotlin Multiplatform plugin still
┃ ┣ 📂 iosTasksApp/ discovers these for iOS run configurations)
┃ ┗ 📄 spectacled.xcworkspace ← Xcode workspace combining all three iOS apps
┃
┣ 📂 server/ ← Ktor CORS proxy for the Web build (see server/README.md).
┃ Only the browser needs it; native apps talk CalDAV directly.
┃
┗ 📂 gradle/
┗ 📄 libs.versions.toml ← ★ All dependency versions live here
Why three separate apps instead of one with a mode switch? Each is published as its own listing (its own icon, name, and store page), which matches how people actually think about journals vs. notes vs. tasks — but all three share every line of business logic and almost all of their UI, which both live in shared/. compose<Variant>App is just the per-platform entry point: it picks a variant and wires it up for Android/iOS/Desktop/Web. If you're contributing a fix, it almost always belongs in shared/.
✏️ Where to Write Your Code
| What you want to do |
Put code here |
| UI screens, CalDAV sync, iCalendar parsing, database, business logic |
shared/src/commonMain/kotlin/ |
| Platform-specific logic (e.g. credential storage, file access) |
shared/src/<platform>Main/kotlin/ |
| Platform entry-point wiring for one app (rarely needed) |
compose<Variant>App/src/commonMain/kotlin/ |
| Static web assets (favicon, index.html, the sql.js worker) |
compose<Variant>App/src/webMain/resources/ |
| Android-only entry point code |
android<Variant>App/src/main/kotlin/ |
| iOS-only Swift code |
ios<Variant>App/ios<Variant>App/ |
| Shared strings/images (used by all 3 apps) |
shared/src/commonMain/composeResources/ |
🏁 Building & Running Each Platform
Each command below works for any of the three apps — just swap composeJournalsApp / androidJournalsApp / iosJournalsApp for the Notes or Tasks equivalent.
🤖 Android
# Debug build
# Requires Android SDK available on the machine. Simplest way is to setup
# Android Studio. As the installer sets up SDK, note the path.
# Create a local.properties file in the project root directory with the content
# `sdk.dir=<absolute path of SDK location>`
./gradlew :androidJournalsApp:assembleDebug
# APK: androidJournalsApp/build/outputs/apk/debug/
# Or just open the project in Android Studio, select an androidJournalsApp run
# configuration and a device/emulator, and click ▶️ Run.
Baseline Profiles
Each Android app ships a Baseline Profile and a startup profile, which make cold start
and the first interactions faster and let R8 lay out the startup code in the primary DEX
file. They are generated by the baselineprofile<Variant> modules
(baselineprofile/) and committed to android<Variant>App/src/release/generated/baselineProfiles/.
Regenerate them after larger UI or startup changes:
# Needs a connected emulator or device on API 33+ (or rooted API 28+). The profiled
# build is signed like a release build, so the keystore values (ANDROID_KEYSTORE,
# ANDROID_KEYSTORE_PASSWORD, ANDROID_KEY_ALIAS_JOURNALS, ANDROID_KEY_PASSWORD_JOURNALS,
# …) must be set, either as environment variables or in local.properties.
./gradlew :androidJournalsApp:generateReleaseBaselineProfile
🖥️ Desktop (Windows / macOS / Linux)
# Run directly
./gradlew :composeJournalsApp:run
# Native installers
./gradlew :composeJournalsApp:packageMsi # Windows
./gradlew :composeJournalsApp:packageDmg # macOS
./gradlew :composeJournalsApp:packageDeb # Linux
# Output: composeJournalsApp/build/compose/binaries/
🌐 Web (JavaScript)
./gradlew :composeJournalsApp:jsBrowserDevelopmentRun
# Opens http://localhost:8080 with hot reload
# Production bundle:
./gradlew :composeJournalsApp:jsBrowserProductionWebpack
🌐 Web (WebAssembly)
./gradlew :composeJournalsApp:wasmJsBrowserDevelopmentRun
Requires a recent browser (Chrome 119+, Firefox 120+, Safari 18.2+).
⚠️ The Web build needs the CORS proxy. Browsers block cross-origin WebDAV requests, so the
web app routes CalDAV traffic through the small Ktor proxy in server/, which
adds the required CORS headers (native apps talk to CalDAV directly and don't need it). Run it
locally with ./gradlew :server:run and point Settings → Proxy server at
http://localhost:8088. For hosting, self-host your own instance (a shared proxy can see your
credentials in transit) — see server/README.md for Docker/Fly.io setup and
the trust caveats. Users who can't do that can opt into the instance we host, but only after
confirming a dialog that explains what its operator can see.
Local development: run ./gradlew :server:run and choose My own proxy server → Local
development server in the settings. localhost isn't the official origin, so the hosted proxy
isn't offered there and an empty setting means a direct connection.
🗂️ Web app on your own webspace
Every GitHub release also ships the web apps as static bundles:
spectacled-journals-web.zip, spectacled-notes-web.zip and spectacled-tasks-web.zip
(always the newest at https://github.com/TechbeeAT/spectacled/releases/latest/download/spectacled-<app>-web.zip).
They are the same JavaScript build that runs on GitHub Pages, with relative paths only, so any
web server that serves static files works — no server-side code, rewrites or special headers:
- Download the ZIP and unpack it. It contains a single folder, e.g.
spectacled-journals/.
- Upload that folder to your webspace and open its
index.html URL in the browser.
- In Settings → Proxy server, choose how the app reaches your CalDAV server:
- No proxy (direct connection) — works if the app is served from the same origin
(scheme, host and port) as your CalDAV server, e.g. the app at
https://cloud.example.com/spectacled/ and CalDAV at https://cloud.example.com/remote.php/dav,
or if your CalDAV server sends CORS headers that allow the app's origin. A different subdomain
or port is a different origin and needs a proxy.
- My own proxy server — run the proxy and add your webspace's origin
to its
PROXY_ALLOWED_ORIGINS.
The proxy Techbee hosts only accepts the official GitHub Pages origin, so it isn't offered in a
self-hosted copy.
🍎 iOS
Requires macOS + Xcode 16+.
1. Open iosApp/spectacled.xcworkspace (or iosApp/iosJournalsApp/iosJournalsApp.xcodeproj
directly) in Xcode.
2. Select a simulator or device.
3. Click ▶️ Run.
For a physical device, set your Apple Developer Team in ios<Variant>App/Configuration/Config.xcconfig:
DEVELOPMENT_TEAM=YOUR_APPLE_TEAM_ID
📝 Useful Gradle commands
| Command |
What it does |
./gradlew :shared:allTests |
Run the shared module's test suite |
./gradlew :server:run |
Run the Web CORS proxy locally on http://localhost:8088 |
./gradlew :server:test |
Run the proxy's test suite |
./gradlew clean |
Delete all build outputs |
./gradlew --stop |
Stop all Gradle daemons (useful after a bad incremental build) |
💡 Always use ./gradlew (the wrapper), not a system-installed gradle — it pins the exact Gradle version this project needs.
🌍 Translations
Spectacled is translated with Weblate, a libre web-based
translation platform — thanks to Weblate for hosting our translations free of charge for
open-source projects.
Help translate the apps into your language at
hosted.weblate.org/projects/spectacled.
No development setup and no Git knowledge required: sign in, pick your language, and start
translating in the browser. Weblate opens the pull requests against this repository for you.

The source strings live in shared/src/commonMain/composeResources/values/strings.xml
and are shared by all three apps on every platform. Translations land in sibling
values-<lang>/strings.xml directories — please don't edit those by hand, let Weblate
manage them so nothing gets overwritten on the next sync.
Contributing
Issues and pull requests are welcome — this is an open-source project and stays that way. A few starting points:
If you're touching CalDAV sync or iCalendar parsing, start in shared/src/commonMain/kotlin/at/techbee/spectacled/screens/core/ — that's where the platform-independent logic lives, and it's the part every app and every platform depends on.
License
This project is licensed under the Apache License 2.0 — see LICENSE for details.