Eventtia On-Site

Checking in attendees at a conference with spotty Wi-Fi

The venue's internet drops. The registration desk has a line of 50 people. The event staff are frantically trying to get the system back online. This is the exact moment the Eventtia On-Site app proves its worth. It doesn't need a live connection to scan a QR code and log an attendee. The scan happens, the data stores locally, and the system syncs automatically when the network returns. That single feature — offline QR scanning — separates this tool from a basic registration form.

Eventtia On-Site is the mobile arm of a larger event management platform. It handles two core jobs: registering new attendees on the spot and checking in people who already registered. The app combines these into one workflow. A staff member opens the app, logs in with Eventtia credentials, and sees the list of events. Selecting an event brings up the attendee list, the check-in interface, and the QR scanner. The interface is straightforward — no unnecessary menus or confusing icons. The focus is on speed. Every second saved at the door reduces the wait time for everyone else.

The QR scanner is the primary tool. It reads codes from printed badges or mobile tickets. The app validates the code in real-time when online. It shows the attendee's name, registration type, and any session-specific details. The staff member confirms the check-in with one tap. A green checkmark appears. The system logs the time and location. For multi-day events or events with multiple sessions, the app tracks attendance per activity. This is where the "checkpoints" feature comes in. An organizer can set up multiple checkpoints — one at the main entrance, one at the workshop room, one at the VIP lounge. Each checkpoint has its own QR code. Attendees scan at each point, and the app records their movement through the event.

The offline sync and QR code interaction

The offline mode is not a backup plan. It is the primary mode for many venues. Event spaces like convention centers, hotels, and outdoor locations often have unreliable internet. The Eventtia On-Site app stores all attendee data locally after the initial sync. When a staff member scans a QR code offline, the app records the check-in and stores it in a local queue. The moment the device reconnects, the app pushes all pending check-ins to the central database. This means no data is lost. No duplicate scans occur because the app tracks which codes it has already processed, even offline. The system also handles the scenario where an attendee has already checked in at one checkpoint and tries to check in at another. The app prevents duplicate entries, ensuring accurate attendance counts.

The sync process is automatic. The staff does not need to press a "sync" button. The app detects the network change and handles the upload in the background. This design choice is critical. During a busy check-in period, staff members cannot afford to manage manual syncs. They need to focus on the attendee in front of them. The app's auto-sync feature removes that distraction. It also reduces the risk of human error. A staff member might forget to press sync, but the app never forgets.

This workflow — offline scanning with auto-sync — is not described on the Play Store page in detail. The Play Store mentions "real-time validation" but does not explain what happens when real-time is not available. The help documentation confirms that the app "can also be used offline if you don't have an Internet connection" and that it "sync data seamlessly" with the platform. The combination of these two features creates a reliable system that works in the most challenging environments.

What the changelog reveals about real-world use

The version history shows a pattern of fixes that reveal how people actually use the app. One fix addressed a permission bug that allowed users to update participant information without proper permissions. This suggests that event staff often need to edit attendee data on the fly — correcting a misspelled name, updating a session choice, or adding a note. The app originally allowed this without checking if the user had the right role. The fix tightened the permission system, ensuring only authorized staff can make changes.

Another fix corrected an issue where workshops displayed in the wrong order on the app. For a multi-track event, the order of workshops matters. Attendees need to see the correct schedule. If the app shows workshop B before workshop A, confusion follows. The fix ensures the app matches the order set in the backend. This is a small detail, but it shows that the app is used for complex events with multiple simultaneous sessions.

A third fix addressed multiple scans of the same QR code and duplicate system calls. This is a common problem with QR code systems. An attendee might present their code multiple times — at the door, at a session, at a networking event. The app needs to distinguish between a legitimate second scan (e.g., checking into a different session) and an accidental duplicate. The fix improved the logic, reducing the number of duplicate entries and the associated system load.

The changelog also mentions improvements to QR code scanning and a fix for an SSO login crash. These updates point to a product that is actively maintained and responsive to user feedback. The fixes are not generic "performance improvements." They are specific to how the app is used in the field.

The real-world performance of the check-in flow

The app's performance depends on the device and the network, but the core scanning speed is consistent. A staff member points the camera at a QR code, and the app responds within a second. The validation — checking if the code is valid, if the attendee is registered, if the session is correct — happens almost instantly when online. Offline, the validation is limited to what is stored locally. The app cannot check real-time changes to the attendee list if it is offline. But for most events, the attendee list is finalized before the event starts. The offline mode works with that static list.

The app handles last-minute registrations. A person walks up to the desk without a ticket. The staff member selects the "register" option, enters the person's name, email, and any other required fields, and the app creates a new attendee record. This new record is added to the local database and synced later. The process takes about 30 seconds. It is not as fast as scanning a QR code, but it is faster than using a separate registration system.

The app also supports badge printing. When integrated with a Zebra printer, the app can print a badge automatically after scanning a QR code. This feature must be activated by Eventtia support for each event. The setup requires contacting [email protected] and providing the event ID. Once enabled, the printing is seamless. The staff member scans the code, the app validates, and the printer produces the badge. This reduces the need for a separate badge-printing station.

The app has limitations. The user interface, while functional, is not visually polished. It prioritizes speed over aesthetics. The attendee list shows names and email addresses, but the search function only works by name or email. There is no advanced filtering. The app also lacks a built-in analytics dashboard. All reporting is done through the web platform. For a staff member who only needs to check people in, this is fine. For an organizer who wants to see real-time attendance numbers, the app is not the right tool.

Permission handling and access control

The app uses a role-based access system. Organizers can assign roles to staff members. A "check-in agent" can only scan QR codes and check people in. A "registration agent" can also register new attendees. An "administrator" has full access, including the ability to edit attendee data and change event settings. The app enforces these roles strictly. The permission bug fix mentioned earlier closed a loophole where a user without proper permissions could still edit participant information. The fix ensures that the role assigned in the backend matches the permissions in the app.

The login process uses email and an access token. The user does not need a password for the app. They enter their email, and the system sends a token to that address. The user enters the token, and they are logged in. This is faster than a password-based system, especially for temporary staff who might not remember a complex password. The token expires after a set time, adding a layer of security.

The app does not request many device permissions. It needs camera access for QR scanning. It may need storage access for caching data. It does not request location, contacts, or phone permissions. This is a positive for privacy-conscious organizations. The app's data security is handled at the platform level. Data is encrypted in transit, and the platform uses standard security practices.

The app is available on both Android and iOS. The iOS version requires iOS 15.1 or later. The Android version supports a wide range of devices. The app size is around 11.5 MB, making it a lightweight download. This is important for event staff who might need to install the app on multiple devices quickly. The small size also means the app does not take up much storage space, which is useful for devices with limited capacity.