Web Summit

How the Recommendation Engine Feeds the Networking Loop

The Web Summit app starts with a feed. It shows you talks, speakers, and companies based on what you have looked at or saved. This is not a static list. It updates as you interact. When you save a session, the app suggests similar speakers. When you view a company profile, it recommends related startups. The feed is the entry point for everything else. From there, you can message other attendees, schedule meetings, or add sessions to your calendar. The recommendation engine does not just suggest content. It suggests people. This is where the networking loop begins. You see a recommended speaker. You tap their profile. You send a message. They reply. A meeting is set. The app has turned a passive viewing experience into an active connection. This workflow is not described in the Play Store listing. The listing mentions personalized recommendations and networking separately, but it does not explain how they feed into each other. In practice, the feed is the engine that drives the entire networking experience.

This loop has a practical limitation. The recommendations are based on your activity. If you do not engage with the app early, the feed stays generic. You get broad suggestions that may not match your interests. To make the app work for you, you need to spend time saving sessions and viewing profiles before the event starts. This is not a flaw. It is a design choice. But it means the app rewards early adopters. Attendees who download the app weeks in advance get a tailored experience. Those who download it the day of the event get a generic feed and miss out on the networking opportunities. The app's support page confirms that you need your ticket reference to log in. If you do not have your ticket handy, you cannot even start the personalization process. This creates a barrier for last-minute attendees.

Comparing the Web Summit App to Slush

Slush is a similar tech conference in Helsinki. Its app also provides scheduling, networking, and a feed. But the Web Summit app differs in one key area: the digital ticket. Web Summit requires you to use the app as your ticket to enter the venue. Slush does not. This is a significant difference. At Web Summit, if the app crashes or your phone dies, you cannot get in. One reviewer noted that the app crashed during a main stage event with 30,000 people watching. Imagine that happening at the entrance. The dependency on the app for venue access is a risk that Slush avoids by using physical badges or separate ticketing. Another difference is the recommendation engine. Slush's app focuses more on matchmaking between startups and investors. Web Summit's app casts a wider net, recommending talks, speakers, companies, and experiences. This makes the Web Summit app more of a discovery tool, while Slush's app is more of a networking tool. However, the Web Summit app's broader scope means it has more moving parts. More features mean more points of failure. The complaints about bugs, crashes, and slow performance suggest that the app struggles to handle its own complexity.

What the Changelog Does Not Say

The current version's changelog reads: "Small improvements and bug fixes". This is the same phrase used in previous versions. The developer, WEB SUMMIT SERVICES LIMITED, has not published specific details about what actually changed. This lack of transparency is a pattern. Reviewers have noted that the app has had stability issues for years. One reviewer said the app "used to crash way too often" and that "there was too little improvement in ux". Another noted that the app "used to crash way too often" and that "it's still very slow". The changelog does not acknowledge these issues. It does not say "fixed the crash after scanning tags" or "improved streaming stability." It just says "small improvements." This is not helpful for users. It does not build trust. It suggests that the developer is not being transparent about the app's problems. The app has been available since at least 2013. Over a decade later, it still has fundamental stability issues. The changelog's vagueness is a symptom of a larger problem: the app is not being actively improved in meaningful ways. The "small improvements" are likely minor tweaks that do not address the core complaints.

The Scanning Feature That Brings the App Down

The app has a feature that lets you scan tags to exchange contact information with other attendees. This is a crucial function for networking. However, multiple reviews have noted that the app crashes after scanning tags for a few hours. One reviewer said the app crashed during a main stage event with 30,000 people watching, and they could not get it back up. This is a serious failure. The scanning feature is not a peripheral tool. It is central to the app's purpose. If it crashes, you lose the ability to connect with people you just met. The app also has a known issue where it logs you out automatically. If you are logged out during the event, you have to go through the registration process again. This is a frustrating experience, especially when you are in a crowded venue with limited time. The app's support page acknowledges login issues. They suggest checking your ticket reference and email. But they do not offer a solution for the crashes. The scanning feature is a clear example of a feature that sounds useful on paper but fails in practice.