Appearance
Trying the current demos
These instructions describe the current source checkout. Building a demo does not update an already hosted website, installed APK or TestFlight build.
The Web demo and handbook were updated for publication on 9 November 2026. The native changes described below are available in the source checkout; no new Android or iOS app version was published as part of this website update.
Calendar: half-day arrival and departure edges
The regular Web, iOS and Android Calendar demos opt all-day events into half-day edges. Open Month or Week on Web, or Week on native platforms. Multi-day bars start halfway through the first occupied day and end halfway through the last. Touching changeovers share a lane. Single-day events and clipped continuations keep their full cell. Timed events retain their original geometry.
This is a presentation convention. Ends remain exclusive and the demo does not reinterpret a date as a real check-in/check-out time. Native Month and Day use lists, so there are no horizontal date-bar edges to change there. The library's consumer default remains full-day; only the demos opt in.
Gantt: paged resources and buffered entries
The Web Gantt demo links to Load resources in pages (pagedRows=1) and Large dataset: 3,000 resources (lazyStress=1). Both retain the selected Vanilla/React/Vue integration. The stress example spans 3,000 day columns and simulates delayed responses. Scroll horizontally and vertically, return to a loaded area, resize the viewport and change scale.
In the iOS and Android Gantt demos, enable Daten nachladen / Load data asynchronously. Resource rows and interval entries use separate providers. The measured viewport determines row demand; entry requests use prefetch margins and a bounded response cache. Native loading indicators and retry/load-more controls keep failures recoverable. The native demos use their own smaller fixtures; they are not a 3,000-by-3,000 performance benchmark.
The iOS demo also provides delay selection and simulated entry-loading failure. The providers in all demos are in-memory examples, not real backend connections.
Resources: lazy Timeline plans
Select Resources, then Timeline. The regular Web, iOS and Android examples load placements asynchronously through the Resources API, while retaining inventory and the configured rows. Move, create, resize or remove a placement, then scroll away and back: the demo's authoritative session store supplies confirmed changes on subsequent reads. Constraints continue to validate proposals.
Inventory and rows are configured up front in these examples. This differs from the separately paged Gantt resource provider. Unloaded intervals are unknown; server-backed consumers must validate global stock/capacity on their server.