ChronoGrid is intentionally a focused product — Java-first Vaadin Flow with built-in CalDAV. This roadmap reflects that focus: it lists features that strengthen the niche, and it explicitly calls out features that would dilute it.
The prioritisation comes from the competitive analysis against FullCalendar Flow, Scheduler, DHTMLX, Kendo, Bryntum and TOAST UI — see that page for the full reasoning per feature.
Coming next (high priority)
These close real gaps versus production-grade calendar usage. Each one is on the path; the order will be shuffled based on user feedback once 0.x hits public.
| Feature | Why it matters |
|---|---|
| Recurring events / RRULE | Production calendars are mostly recurring meetings. Without RRULE support the component is a demo, not a tool. |
| ICS Import / Export | The data-exchange and migration story. People want to ingest existing calendars and move events out. |
| Agenda / List view | Often more productive than month grid for managing real schedules. The view most users would set as default. |
| Search & filter | Critical once a user has more than 2-3 subscriptions. Without it, multi-source is theoretical only. |
| Read-only mode per subscription | For shared / foreign calendars you don’t own. Currently every subscription is writable. |
Coming after that (medium-high priority)
| Feature | Why it matters |
|---|---|
| Conflict UI | When two clients change the same event, ETag mismatches need a useful merge dialog — not just an exception. |
| Provider presets | One-click connect for Nextcloud, Radicale, Baïkal, mailbox.org. Apple iCloud ships today; the catalogue is a single-list extension point. |
| Offline / cache mode | Robust On-Prem and remote scenarios. Read access without network. Writes queue and sync. |
| Extended event editor | Categories, URL, location, description, attendees. Currently the editor is minimal. |
| Keyboard navigation | Accessibility + power-user productivity. |
| Mobile optimisation | Depends on real-world demand — most CalDAV usage today is desktop. |
What ChronoGrid will deliberately NOT become
Calendar UI is a crowded space. The strategy is to be the best Java + Vaadin
- CalDAV component — not to compete with enterprise schedulers on their turf. The following are explicitly out of scope unless a strong reason emerges:
| Feature | Why we’re not building it |
|---|---|
| Resource planning | Bryntum, Kendo and FullCalendar Scheduler own this segment. Adding it would expand scope and put us in their lane with weaker tools. |
| Timeline view | Beautiful in screenshots, but mostly relevant for resource planning — which we’re not doing. |
| PDF / Excel export | Nice-to-have but not core. CalDAV speaks iCalendar — that’s the export format. |
| Outlook clone | Scope creep. We are not building a groupware suite. |
| Full groupware | Calendar is one piece of groupware; we don’t want to become the others. |
| Custom FullCalendar replacement | FullCalendar is excellent at rendering. We use it. Building a parallel renderer is wasted effort. |
Architecture-level commitments
Less feature-list, more guardrails:
- Headless core stays headless.
chronogrid-coremust remain usable without Vaadin — CLI tools, sync jobs, Spring Boot services. The Vaadin dependency lives only in thechronogridadd-on module. - CalDAV semantics are first-class. ETag-based optimistic concurrency,
If-Match/If-None-Match, the full PROPFIND chain, REPORT with calendar-query — all of these are tested against caldav-testbench on every build. - The seam between UI and Java host stays explicit.
StateStore,i18nand the route layer are extension points. Host applications keep their own security architecture; ChronoGrid does not assume it. - License: EUPL-1.2. Copyleft-style, EU-approved. This is a deliberate choice for an On-Prem / EU-data-privacy positioning.
How to influence the roadmap
ChronoGrid is open source under EUPL-1.2. Three ways to move things up the list:
- Open an issue on GitHub describing a real use case. “We need X for Y” beats “would be nice to have X” by a wide margin.
- Send a pull request. Anything aligned with the architectural commitments above is welcome.
- Sponsor a feature. For commercial users who need a specific item sooner — talk to me. The roadmap order is influenceable for sensible reasons.
See also: Competitor comparison matrix · Main project page
