ControlTickets

ControlTickets is a companion app for the RedTickets event platform. It is not a ticket-selling marketplace. Instead, it is the tool you use at the door. The moment an event is created on RedTickets, a unique event code is generated. You take that code, enter it into ControlTickets, and the attendee list downloads straight to your phone. From that point on, the app acts as your gatekeeper.

The core action is QR scanning. Every ticket sold through RedTickets carries a unique QR code. When a guest arrives, you point the camera at their ticket — printed or on a screen — and the app validates it instantly. The system marks that ticket as used, so the same code cannot be scanned twice. This prevents duplicate entries and fraud. The app also keeps a running tally of how many people have entered. You see that number update in real time as each person walks through the door.

What is not obvious from the Play Store description is how the app behaves when the network drops. The attendee list is downloaded once at the start, so it lives on the device. Scanning works offline. This is a critical detail for venues with poor cellular coverage. The app does not need to phone home for every scan. It only needs the initial code to pull the list. After that, the validation happens locally.

Entering the event code and loading the list

The first screen you see is a single input field. It asks for the event code. That code comes from RedTickets after you publish the event. Type it in, and the app immediately pulls the attendee roster. The download is fast, usually under a few seconds on a standard connection. Once loaded, the list stays on the device until you explicitly refresh or the event ends. You can also refresh manually if ticket sales are still open and the list changes.

A practical issue emerges here. If you are managing a large event with hundreds of attendees, the list can be long. The app does not offer a search function on the main screen. You have to scroll. However, if a guest's QR code fails to scan, you can fall back to searching by name. That search is available, but it is buried in a secondary menu. For a busy door, this extra step can slow things down. The ideal workflow is QR scanning only, but the name search is a useful backup when the camera struggles with glare or a crumpled ticket.

Adding multiple access points with separate devices

One of the more useful features is the ability to install ControlTickets on several smartphones. Each device uses the same event code. This means you can have multiple staff members at different entrances, all scanning tickets simultaneously. The app syncs the attendee count across all devices in real time, provided there is an internet connection. If a device goes offline, it still scans locally, but the count may not reflect on other devices until it reconnects.

This multi-device setup is not explained in detail on the Play Store page. The developer mentions it briefly, but the real-world implication is significant. For a festival with three gates, you can have three phones running the app. Each phone scans independently. The total attended count is shared, so you always know the overall number. This eliminates the need for a central check-in desk and reduces queues. The only requirement is that each device has the camera working and the event code entered correctly.

There is a catch. The app does not have a built-in way to assign roles or differentiate between gates. All devices show the same list and the same count. If you need to track which gate had more traffic, you would need to manually note that separately. The app treats all scanners as equal. For most events, this is fine. For large-scale operations with multiple zones, it may be a limitation.

What the changelog reveals about recent updates

The latest version, 14.14, includes fixes for iOS 26 and later. This is interesting because the Android version also carries the same changelog. The developer is clearly maintaining both platforms with the same codebase. The update also adds guest entry functionality and the ability to read the cancellation reason when scanning a disabled membership QR. This suggests the app is expanding beyond single-event tickets into membership-based access.

Reading the cancellation reason is a specific detail. If a membership is cancelled, scanning its QR code now tells you why. This could be useful for gyms, clubs, or co-working spaces where memberships are suspended for non-payment or policy violations. The app does not just say "invalid" — it gives context. That level of detail is not common in basic ticketing scanners. It indicates the developer is thinking about ongoing access control, not just one-off events.

The guest entry feature is another addition. It allows you to manually add a guest who does not have a ticket. You can enter their name and mark them as admitted. This bypasses the QR scan entirely. It is a practical workaround for situations where a guest forgot their ticket or the QR code is damaged. However, it also introduces a potential loophole. Since there is no verification, a staff member could admit someone who is not on the list. The app trusts the operator.

Handling camera failures and search fallback

The camera is the primary input method. If it fails, the app provides a name-based search. You tap a button, type the attendee's name, and the app shows their ticket status. You can then mark them as entered. This works well for low-volume events. For high-volume events, typing names is impractical. The search is case-sensitive and requires exact matches. A misspelled name will not return a result. This can cause frustration at the door when guests have common names or typos on their tickets.

The app also recommends keeping the ticket about 15 cm from the phone for optimal scanning. This is a specific distance that works best for the camera's focus. Deviating from this can cause blurry scans. The app does not give feedback on why a scan failed — it simply says "invalid" or does nothing. There is no guidance on adjusting the distance or angle. This lack of feedback can be confusing for first-time users.

The offline capability remains the app's strongest technical advantage. Once the list is downloaded, scanning does not require a data connection. This makes it reliable in basements, stadiums, and remote venues. The list is stored locally until the event ends or you manually refresh. If ticket sales continue after the event starts, you need to refresh to get the updated list. That refresh requires a connection. So the app works offline for validation but online for list updates.