The Concert

The first screen after launching The Concert is a registration form. There is no option to browse events as a guest. The app demands a phone number and a password before showing anything else. This is the entry barrier. For someone who just wants to check if their favorite artist is playing nearby, this step can feel unnecessary. But it is also the moment where the app's business model becomes clear: this is a closed ticketing system that requires user identification before any transaction can proceed.

Once logged in, the home screen displays a grid of upcoming events. Thumbnails show artist photos and event dates. A search bar sits at the top. Below it, tabs for "Discover," "Tickets," "Merchandise," and "News" provide navigation. The design is functional but not polished. Text sometimes overflows its containers. Images load slowly on older connections. The overall feel is that of a platform built for utility rather than user experience. But for the core task of finding and buying tickets, the basics are present.

The ticket purchasing flow starts with selecting an event. This opens a seat map. Available seats are shown in green. Taken seats are gray. The user taps a seat, and it turns yellow, indicating a temporary hold. But this hold is not exclusive. Other users can still see the seat and attempt to select it. This is where the first major friction point appears. Unlike other ticketing platforms that lock a seat for a few minutes during checkout, The Concert allows multiple users to compete for the same seat until payment is finalized. This creates a race condition that often ends in disappointment.

The Seat Selection and Payment Race

The seat selection process is tied directly to the real-time reporting system. The app continuously updates the seat map to reflect current availability. This sounds good in theory. In practice, it means that seats can disappear from under a user's finger while they are filling out payment details. The app does not reserve a seat when the user starts the checkout process. It only finalizes the booking when the payment is confirmed. This is a critical design flaw that has been reported by multiple users.

The payment interface itself is a source of additional problems. Users have reported that the system times out frequently, especially during high-traffic periods. One review described being kicked out of the payment screen more than twenty times in a single attempt. The app supports credit and debit cards, but the payment window is tight. Users have only a few minutes to complete the transaction. If they fail, the seat is released back into the pool. This is not mentioned in the Play Store description. It is a real-world limitation that only becomes apparent during the actual purchasing process.

Real-World Performance and System Stability

The app's performance under load is its weakest point. During popular ticket releases, the system slows to a crawl. The app freezes, crashes, or displays endless loading spinners. Users have described the experience as "whack-a-mole" because seats appear and disappear so quickly. The system is not built to handle the surge of traffic that comes with a high-demand concert. This has led to widespread frustration, with some users missing out on tickets entirely due to technical failures.

The stability issues are not new. Reviews from 2023 and 2024 describe the same problems: crashes, freezes, and payment timeouts. The app has received updates over the years, but the core issues remain unresolved. The changelog mentions "improvements to the shopping experience," but users report that the experience has not meaningfully changed. The app also has security concerns. The Exodus Privacy report shows that the app includes three trackers for crash reporting and analytics. It also requests 23 permissions, including access to location, camera, and storage. Some users have reported account theft and scams, raising questions about the platform's overall security posture.

The app is available on both Android and iOS. The Android version requires Android 6.0 or later. The APK size varies between 70 MB and 108 MB depending on the version. The app uses the standard Google Play signing certificate. The developer is THE CONCERT APPLICATION COMPANY LIMITED, a Thai company registered in Bangkok. The company's registered capital is 5,000 THB, which is modest for a ticketing platform of this scale. The company also offers a "Ticket Shield" insurance product in partnership with KPI, which provides coverage for unforeseen events.

The Bot Problem and Consumer Advocacy

One of the most significant issues with the platform is the prevalence of bots. Automated ticket-sniping tools are available on GitHub. These bots can bypass the normal purchasing flow, allowing scalpers to secure large numbers of tickets in seconds. This has led to a situation where genuine fans are locked out of events. The problem has become so severe that the Thai Consumer Council has issued a public statement demanding that The Concert address the issue. A petition has also been circulated, calling for fairer ticketing practices.

The app's response to these problems has been mixed. The company has introduced features like "Presale Event" registration, but this must be done through the website, not the app. The app also offers a "PASSLOCK" feature that adds a layer of security to tickets. However, these measures have not stopped the bot activity. The company's customer support is primarily available through Line OA, a messaging platform popular in Thailand. Users have reported that support is slow and unhelpful.

The app's developer address is in Huai Khwang, Bangkok. The company operates as a marketplace intermediary for ticket sales. This means that the company does not issue the tickets itself but facilitates transactions between sellers and buyers. This structure may limit the company's ability to enforce fair ticketing practices. It also means that the company is not directly responsible for ticket availability or pricing, which can create a disconnect between user expectations and the platform's capabilities.