App
The Cicero product substrate. Two sides — what we ship to the agency (platforms, app integration, websites) and what we ship to the traveler (the consumer app + its backoffice).
Cosa stiamo costruendo
Recap delle spec consumer dalla docs repo. Click per il dettaglio.
sunday-docs sia disponibile (in dev: come sibling del repo; in prod: GITHUB_TOKEN configurato).Cose da fare
Mock board con drag & drop. Stato locale, non persistito.
TA-side
Three surfaces, each with the same three-layer stack underneath: CMS · Data layer · Backoffice.
Internal operating tools we ship to the travel agency itself. One platform stack, one tenant per agency.
The TA-side surface of the consumer app — codes, branded views, cohort dashboards, per-agency styling.
Public-facing storefronts per travel agency. Multi-tenant catalog inheritance, drop-in WP-compatible markup where required.
Consumer-side
The mobile app + its backoffice — different sprint cadence from the TA-side stack.
The mobile experience travelers hold during the trip — code-unlock, museum content, group-trip mode. From now on labeled 'consumer app' to distinguish it from the TA-side app integration.
UI/UX in FigmaOperations console for the consumer app. Surfaces what's shipping, what just broke, and what's running where — all in one place.
- GitHub — commits, branches, PRs feeding the build queue
- Codemagic — CI/CD pipeline for TestFlight + App Store + Play Store deploys
- Flows — user click-paths to key actions (commit, play, etc.) with friction counts
- Destinations — what museums / cities / experiences we currently cover, with per-destination depth
Consumer app · UI/UX (Figma)
Canonical source of truth for the consumer-app design. Anything that ships to the traveler is reconciled against this file first.