Everness

Opening the App: A Festival Companion

The installation completes quickly. You tap the icon, and the first screen greets you with a question: "Fárasztó éved volt?" — "Was your year tiring?" in Hungarian. The app immediately sets a reflective tone. No login screen. No registration. You are dropped straight into the festival information. The home screen shows the Everness Festival logo and a countdown to the next event. Below that, there are tabs: Program, Info, Community, and Settings. The layout is minimal. The font is clean. The background is a gradient of sunset colors, matching the Lake Balaton theme. For a festival app, this is a welcoming start. You can browse the program schedule without creating an account. This is rare for event apps. Most require registration before showing anything useful. Here, you can see the full lineup of workshops, meditations, concerts, and yoga sessions.

The program tab lists events by day. Each entry shows the time, location, and a short description. Tapping on an event opens a detail page with a map pin and a "Add to calendar" button. The map uses Google Maps integration. The app does not have its own map view. This is a practical choice. The "Community" tab shows a feed of posts from organizers and attendees. You can like and comment without an account. This is unusual. Most community features require registration. Here, the app treats everyone as a guest. This lowers the barrier to participation. But it also means there is no way to save your favorite events or create a personalized schedule. The app does not have a user profile system. Every session starts fresh. This is a limitation for repeat users.

The Program and Community Tabs: A Two-Way Interaction

The Program tab and the Community tab are the app's core features. They work together in a specific way. When you view a program entry, there is a "Discuss" button that opens the Community tab with that event pre-selected. This creates a direct link between the schedule and the social feed. You can see what others are saying about a workshop before you decide to attend. This is useful for first-time festival-goers who want to gauge the vibe of a session. However, the "Discuss" button only works if the event has an associated post in the Community tab. Not all events have posts. Some are listed in the schedule but have no discussion thread. This means the app does not automatically create a discussion for every program. The organizers have to manually add posts. This creates a gap. Users might click "Discuss" and see an empty page. This is confusing.

The interaction between the two tabs also has a timing issue. The app does not send notifications when a new post is added to an event you have viewed. You have to manually check the Community tab. This reduces engagement. For a festival that lasts 10 days, this is a missed opportunity. The app could have a "Follow" feature for specific events. It does not. The only way to stay updated is to keep checking the app. This is a common limitation in event apps. But here, it is more noticeable because the app does not have a user account system. Without accounts, there is no way to save preferences or receive alerts. The app treats every visit as a first visit. This is fine for casual users, but it limits the app's utility for regular attendees.

Performance and Privacy: What the Exodus Report Shows

The app runs smoothly on most Android devices. The UI is responsive. Scrolling through the program list is quick. The map loads within two seconds. However, the Exodus Privacy report for version 2.0.7 found one tracker in the code. The report also lists 17 permissions requested by the app. These permissions include storage, network, and phone state. The app does not explain why it needs these permissions. The Play Store page does not list any permissions. This is a transparency issue. For a festival app that handles no personal data, the lack of clear permission explanations is concerning. The app does not collect any data according to the App Store privacy label. But the Exodus report suggests otherwise. The tracker is not identified as running, but its signature is present. This means the code is there, but it might not be active. For a user who values privacy, this is a red flag. The app also does not have a two-factor authentication option. The login is non-existent. This is standard for guest-mode apps, but it is not secure. If a user loses their phone, anyone can open the app and see the festival information.

The app's performance is consistent across versions. Users report no major crashes. The "Hibajavítások" changelog suggests the developer is maintaining the app. But the lack of detailed changelog entries means users do not know what actually changed. The app has only a handful of installs on Google Play. This is a very small number for an app that claims to support a major festival. The low install count could mean the app is not widely adopted, or attendees do not bother to download it. The one review on the App Store gives it a 4+ rating, but no context is given. This is not a representative sample, but it is the only direct feedback available. The app's overall rating is not displayed due to insufficient reviews. This makes it hard for new users to trust the app.

Storage Permission and Offline Access

The app requests storage permission on Android. This is likely for caching images and program data. Without this permission, the app still works, but images reload every time you open a category. This uses more data. The app also caches program data so you can access it offline. This is useful for attendees at the festival grounds, where mobile signal might be weak. However, the app does not have a full offline mode. You cannot view the program schedule or community posts 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 location, camera, or contacts. This is a positive aspect. However, the app's size is around 140 MB on iOS. This is large for a festival app, likely due to image assets and the framework used. On Android, the size varies by version. 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.