astendo Event

The self-check-in workflow

You open the app and see a list of events you are registered for. Each event shows its name, date, location, and a small logo. Tap on an event, and the screen changes to show the event overview. At the bottom, there is a button labeled "Ticket." Tap it, and a QR code appears. This code is your entry pass. The organizer can scan it at the venue, or you can use the self-check-in feature. Self-check-in means you scan your own QR code at a designated terminal. The app does not generate the code — it displays what the organizer has configured in the astendo eventManager backend. This is a critical distinction. The app is a viewer, not a generator. If the organizer has not set up the event correctly in the eventManager, the QR code may not work. The self-check-in feature then becomes useless. The app provides no error message for this scenario. You simply see a code that does nothing when scanned.

Notifications are another key function. The app can receive push notifications from the organizer. These might be venue changes, schedule updates, or cancellations. The notification system works reliably, according to the changelog, which mentions fixes for notification symbols and self-check-in bugs. However, the app does not have a notification history. If you dismiss a notification, it is gone. There is no way to retrieve it later. This is a limitation for events where multiple updates are sent over several days. The live chat feature partially compensates for this. You can message the organizer directly through the app. The chat is real-time, but it requires the organizer to be actively monitoring it. If the organizer is busy with on-site tasks, your message may sit unanswered. The app does not indicate whether the organizer has seen your message. This is a common frustration in event apps, and this one is no exception.

Comparing the ticket system with a competitor

The ticket system in astendo Event is basic but functional. It shows a booking number, your name, and a QR code. That is it. There is no barcode, no PDF download, no Apple Wallet integration. Compare this with the "Eventbrite" app, which offers multiple ticket formats, including Apple Wallet passes and PDF tickets that can be shared via email. Eventbrite also allows ticket transfers and waitlist management. astendo Event does none of these. The ticket is locked to your account. You cannot transfer it to another person. You cannot print it. You cannot save it offline — the QR code requires an internet connection to load. This is a significant limitation for venues with poor connectivity. If the network is down, you cannot access your ticket. The app does not cache tickets for offline use. The competitor "Sweap" offers offline ticket caching, according to user reviews. astendo Event does not.

The event overview screen shows basic information: name, date, logo, location. There is no agenda, no speaker list, no floor plan. The organizer can configure additional content in the eventManager, but this is limited to website content. The app does not have a built-in agenda view or session scheduler. For multi-day conferences, this is a noticeable gap. The app is designed for single-day events or simple check-in scenarios. The self-check-in feature is the main value proposition. It reduces waiting time at the entrance. But the trade-off is a stripped-down feature set. You get check-in and notifications, and little else. The app does not have a feedback form, a survey tool, or a networking feature. These are common in competing event apps. The developer has chosen to keep the app focused on the core check-in workflow. This works for simple events but feels incomplete for complex ones.

What the changelog reveals about the development cycle

The most recent changelog lists several improvements: French language support, disabling events in non-active status, better feedback for user actions, hiding the event's language when no translations are available, and UI improvements for different display and font sizes. Bug fixes include notification symbols and self-check-in without a code. This is a detailed changelog for a minor update. It suggests the developer is actively maintaining the app. The addition of French language support indicates expansion beyond the German market. The UI improvements for different font sizes show attention to accessibility. The self-check-in bug fix is critical — checking in without a code would be a security hole. The changelog does not mention any new features, only fixes and small improvements. This suggests the app is in a maintenance phase rather than active development. The version number on APK mirror sites is 1.4.0, but the Play Store shows a different version number. This inconsistency is confusing for users. The app has not received a major update in several months, based on the available data.

The developer, astendo GmbH, is based in Berlin. The company has been in the event management space for years. Their primary product is the eventManager platform, which starts at €1,200 per license. The app is a free add-on for event participants. This explains the limited feature set — the app is not a standalone product. It is a companion to the paid platform. The revenue model is indirect. The app drives value to the eventManager by making the check-in process smoother. The app itself has no ads and no in-app purchases. This is a positive for users. But it also means the app will never be a priority for the developer. The platform is where the money is. The app will receive updates only when they are needed to support the platform. This is a realistic assessment based on the available information.

Notification behavior and language settings

The notification system supports push messages from the organizer. The app does not allow users to customize notification preferences. You get all notifications or none. There is no setting to mute certain types of updates. The app also does not group notifications by event. If you are attending multiple events, all notifications appear in the same list. This can be confusing. The language setting is tied to the device's system language. The app supports German, English, and French. If your device is set to a language not supported, the app defaults to English. This is a reasonable fallback. The "hide event's language if there are no available translations" feature prevents empty or broken UI elements. This is a thoughtful touch. The app does not have an in-app language switcher. You must change your device's language to switch the app's language. This is a limitation for multilingual users.

The self-check-in feature requires the participant to scan their own QR code at a terminal. The app does not have a built-in scanner for this — the terminal does the scanning. This is different from some competitors where the app scans a QR code displayed by the organizer. Here, the app displays the code, and the terminal reads it. This is a simpler implementation but requires the venue to have the necessary hardware. The terminal must be connected to the eventManager backend to validate the code. If the network is down, the terminal cannot validate codes, and check-in fails. The app itself does not store any check-in data. All validation happens on the server. This is a point of failure that the app cannot mitigate. The changelog mentions a fix for self-check-in without a code, which suggests there was a bug where participants could check in without scanning anything. This has been fixed, but it raises questions about the security of the check-in process.