Web platform
What it is
Section titled “What it is”Syndik8 runs in a modern browser as a single-page web application. The web build is feature-equivalent to the mobile builds except where a capability only exists on a phone (push notifications, the biometric app lock, camera hardware) or only makes sense on desktop (the payment checkout).
The web app is served from app.syndik8.app.
Who can use it
Section titled “Who can use it”Every member. The web app has the same role-based permissions as the mobile apps; see the role capability matrix.
Where to find it
Section titled “Where to find it”- App:
https://app.syndik8.app - Docs site:
https://docs.syndik8.app(you are here).
Fields / options
Section titled “Fields / options”Supported browsers
Section titled “Supported browsers”Syndik8 targets modern evergreen browsers:
| Browser | Support |
|---|---|
| Chrome | supported; primary test target |
| Edge | supported |
| Firefox | supported |
| Safari (macOS, iPadOS) | supported |
Older browsers, in particular Internet Explorer and legacy Safari, are not supported and are not tested.
URL strategy
Section titled “URL strategy”- Production: the web build uses path-based URLs (for example
/syndicates/abc/calendar). - Legacy links: if a user arrives via a hash-fragment URL (
#/path), the router reads the fragment and redirects to the path-based equivalent. New links are always path-based.
Layout
Section titled “Layout”The web build uses the same adaptive layouts as the mobile builds. A browser window narrower than 600 dp renders the mobile compact layout; between 600 and 1199 dp renders a left-hand navigation rail; 1200 dp and above renders an extended rail with labels beside icons. The switch is live; resize the window and the layout follows.
Behaviour rules
Section titled “Behaviour rules”- No push notifications. The web build does not register for push. The Push column is hidden on the notification preferences screen when you open it in a browser. Email delivery still works.
- No app lock. The biometric app lock is mobile-only. The Security → App lock toggle in user settings is not shown on the web at all: the web build substitutes a do-nothing biometric service rather than asking the browser about hardware it does not have, so there is nothing for the toggle to switch on. See iOS and Android for the mobile behaviour.
- Upgrade from free is direct. When a free-tier syndicate hits the 4th-member or 2nd-asset limit on the web, the block dialog offers Cancel / Upgrade Now. Upgrade Now opens the checkout URL in a new tab. There is no email handoff; that is the mobile-specific path. See upgrade prompt.
- Checkout runs on the web only. Even users who do almost everything on mobile complete subscription checkout in a browser. Mobile paths send an automatic email with a link.
- Camera on web is limited. Attaching a photo (a meter photo when logging a flight, or a receipt on an expense) falls back to the browser’s file picker; there is no in-app capture flow. On a phone browser the file picker can offer the camera; on desktop it opens the file system. Uploading the photo needs a connection: the browser has no durable place for an image to wait, so unlike the mobile apps the web build cannot hold one back and upload it later.
- Connection indicator is the Profile tab icon. The person icon on the Profile tab is green when connected, amber while reconnecting, and red when offline. It is always the icon, never your photo, and it is not in the top bar. There is no dedicated full-width banner at launch.
- Offline capability is narrower on the web than on mobile. The web build also syncs reads and writes, but there is no background sync while the tab is closed, and there is no offline cache for document files. Local data stays in the browser’s storage between visits; it is cleared when you choose Clear data while signing out, or when a different person signs in. See offline capabilities.
- Cookies are functional only at launch. No marketing cookies, no third-party analytics cookies. No cookie banner is shown.
- Timezone follows your profile, not the browser, for everything the syndicate shares. Exactly as on iOS and Android: times are stored in UTC and shown in the timezone on your profile (Profile → Timezone), which covers which day a booking is on, when a flight was flown, which month a charge is filed under, and every date on your balance or an exported statement. Signing in from a machine set to another timezone does not move any of those. A few standalone notices — event times on the calendar, and the deadline dates on the closed, restricted and pending-deletion banners — do read the browser’s own timezone.