Goers: Your Going-out App

Opening the App: Registration and First Look

The installation completes in under a minute. You tap the icon, and the first screen asks for a phone number or email. No guest mode. No social login. You have to register before you can browse any event. The app sends a one-time password via SMS. This is standard for Indonesian apps, but it adds friction for someone who just wants to check if a concert ticket is available. Once you're in, the home screen shows a grid of events: concerts, festivals, workshops, and attractions. The layout is clean. The images load quickly. The search bar sits at the top, but it doesn't auto-suggest as you type. You have to hit enter to see results. For an app that claims thousands of events, the search feels basic.

The app asks for location permission on first launch. This is for the "nearby" feature. If you deny it, the app still works, but you have to manually set your city. The default city is Jakarta. This makes sense for the Indonesian market. The app does not explain why it needs location. It just asks. This is a common pattern in Indonesian apps, but it could be clearer. The registration process takes about two minutes. You enter your name, phone number, and password. No email verification is required. This is convenient, but it also means account recovery relies on the phone number.

The Crowd Feature and Event Ticketing: A Two-Way Interaction

The Crowd feature is the app's social layer. It allows users to create or join meetups around specific events. For example, if a concert is listed, you can see who else is going and start a conversation with them. This is useful for people who don't want to attend events alone. The feature is integrated into the event page. When you view a concert, there's a tab for "Crowd" that shows the number of people interested. You can post a message like "Anyone going to this? Let's meet up." Other users can reply. This creates a community around the event. However, the feature has a limitation: it only works for events that are already listed. You cannot create a meetup for an event that isn't in the app. This means the app controls which events can have social interactions. If an event is not listed, you have to use external platforms like WhatsApp or Telegram to coordinate.

The interaction between Crowd and ticketing is interesting. When you join a meetup, the app does not automatically suggest buying a ticket. You have to navigate back to the event page and purchase separately. This is a missed opportunity. The app could have a "Buy ticket and join meetup" button. Instead, it treats ticketing and social features as separate modules. This creates a workflow where users discover an event, check the crowd, then go to the ticketing tab, and finally return to the crowd tab to confirm plans. This is three steps for what could be two. The app also does not send notifications when a meetup gets more members. You have to manually check the crowd tab. This reduces engagement.

Real-World Performance: Crashes and Customer Support

The app runs smoothly on most modern Android devices. Scrolling through events is responsive. Images load within a second on a 4G connection. However, there are occasional freezes when switching between tabs. The cart sometimes takes an extra second to update. These are minor annoyances. The bigger issue is the crash rate. User reviews on Chrome-Stats mention app crashes and technical difficulties. The app has a 3.20 rating out of 5 based on 2,932 reviews. This is not terrible, but it indicates room for improvement. The crashes seem to occur during peak times, such as when high-demand tickets go on sale. The app has a "waiting room" feature to handle traffic, but some users still report errors during checkout.

Customer support is available via WhatsApp and email. The app claims a response time of 2 to 5 minutes during operating hours. User reviews confirm that the support team is responsive. However, there are complaints about the refund policy. Some users report difficulty getting refunds for cancelled events. The app's refund process is not clearly documented. You have to contact support and provide proof of purchase. This is a common pain point for ticketing apps. The app also does not have a live chat feature. You have to use WhatsApp, which requires adding a contact. This adds friction for users who prefer in-app support.

Storage Permission and Offline Behavior

The app requests storage permission on Android. This is for caching event images and ticket QR codes. Without this permission, the app still works, but images reload every time you open a category. This uses more data. The app also caches ticket QR codes so you can access them offline. This is useful for entry at venues with poor signal. However, the app does not have a full offline mode. You cannot browse events or view details without an internet connection. The app shows a "No internet connection" error message. The storage permission is the only explicit permission requested during installation. The app does not ask for contacts, camera, or microphone. This is a privacy win. The app's size is around 141 MB on iOS and 52 MB on Android. This is large for a lifestyle app, likely due to image assets and the framework used. The app requires Android 7.0 (Nougat, API 24) or higher. Older devices are not supported. The app also does not have a light version for low-end devices, which are common in Indonesia.