FreemiumProBusinessEnterprise

What Works Without Internet

Why Offline Mode Matters

Events often take place in locations with unreliable internet: basement-level conference halls, outdoor venues, remote locations. tikento ensures organizers can work fully even without a network connection.

Offline mode activates automatically when connectivity is lost. No special settings or actions are required.

What Works Offline

Participant Check-in

The primary offline scenario. You can:

  • Scan ticket QR codes
  • Search for a participant by name or registration number
  • Mark a participant as arrived
  • View check-in status (checked in / not checked in)

All check-in marks are saved locally and synchronized with the server once internet becomes available.

Viewing the Participant List

The full list of registered participants is available offline:

  • Name, email, phone
  • Ticket type
  • Registration and payment status
  • Additional fields from the registration form

Data is cached each time you visit the participants page while online.

Viewing Event Information

Key information about your events is available offline:

  • Title, description, dates
  • Venue
  • Ticket types and prices
  • Current registration count

Viewing Payments

The list of payments for an event can be viewed offline:

  • Amount and status
  • Payment method
  • Payment date

Manual Payment Marking

If a participant pays on-site (cash or bank transfer), you can mark the payment manually. The mark will be saved locally and synchronized later.

What Does NOT Work Offline

Some operations require a server connection and are unavailable without internet:

  • Creating new events -- slug generation and uniqueness checks require the server
  • Processing online payments -- the payment gateway is unavailable without a network
  • Sending notifications -- email and Telegram require connectivity
  • Editing the registration form -- form versioning requires the server
  • Managing the team -- invitations and roles require server-side validation
  • Financial reports -- calculations are performed on the server

When you attempt an unavailable action, the system will display a notification explaining that an internet connection is required.

Data Storage

IndexedDB and Dexie.js

Local data is stored in the browser's IndexedDB database via the Dexie.js library. Main tables:

TableContents
eventsEvent information
registrationsParticipant list and statuses
paymentsPayments and transactions
syncQueueQueue of changes awaiting synchronization
metaSync metadata (last sync timestamp)

Encryption

All data in IndexedDB is encrypted to protect participants' personal information:

  • Algorithm: AES-GCM (256-bit)
  • Key: derived from the user's credentials via PBKDF2 (100,000 iterations)
  • Encryption/decryption is performed via the Web Crypto API on the client side

Data cannot be read without being authorized in the system. When you log out, local data is cleared.

Preparing for Offline Work

Although offline mode activates automatically, for reliable operation we recommend:

  1. Open the event in advance. Navigate to the event page and open the participant list while you have internet. Data will be cached automatically.
  2. Check the sync indicator. Make sure all data is loaded -- the indicator should be green.
  3. Install the PWA. Install tikento on your device's home screen for more reliable offline operation.

Compatibility

Offline mode works:

  • In the PWA (installed on the home screen) -- best experience
  • In mobile browsers (Chrome, Safari, Firefox)
  • In desktop browsers
  • In the Telegram Mini App (with limitations depending on the Telegram client)

For stable offline operation, using the PWA is recommended.

Frequently asked questions

Do I need to configure anything special for offline mode?
No. Data is automatically cached in IndexedDB every time you visit a page. Simply open the event and participant list at least once while online -- after that, the data will be available offline.
Is it safe to store participant data locally?
Yes. All data in IndexedDB is encrypted using AES-GCM. The encryption key is derived from the user's credentials via PBKDF2 (100,000 iterations). Without authorization, the data cannot be read.
What happens to changes made offline when the internet returns?
All changes are automatically synchronized with the server when connectivity is restored. The order of changes is preserved -- they are sent in chronological order by timestamp.