A ride is a ride "Single Rider" queues no longer count separately Parks publish the single rider line as if it were a separate ride, and the app believed them. Disneyland Paris counted 39 rides where there are 38, riding via one queue left the other unmarked, and reviews were split into two halves that never reached the minimum to be published. Now it is one ride: riding either queue counts the same, and reviews and ratings belong to the ride. Wait times stay separate, because they are two different queues and both matter. The ride page no longer contradicts itself When a park doesn't measure a ride's queue, the source sends a 0 that isn't a measurement: it means there is no data. The page showed it as "0 min" and warned right below that it couldn't show a wait time. Now it shows a dash and explains why. For the same reason, a closed ride no longer says whether its queue is rising or falling: if it's closed, no queue is moving. And "best time to visit" is no longer calculated from data that doesn't exist. Out with what isn't a ride "Princess Pavilion" and "Meet Mickey Mouse" appeared in the list with a 0 minute wait. They are character meets, and our second source already classified them as shows: the bug was that we only read that classification for rides already matched to it.

A deep pass over the data We went through the entire catalogue, park by park, cross-checking it against official park websites. Here is what came out. Parks showing duplicate rides Parc Astérix listed 82 rides. It has 41. Our data provider had re-indexed the park and kept sending both sets of identifiers at once. Fixed there, and everywhere else it was happening. Rides that exist and were not showing Eight were missing at Parque de Atracciones de Madrid. They are on the park's own website, but the park never publishes their queue times and the app was hiding them. They now show up, and you can mark them as ridden: your progress count for the park was falling short. No wait times is not the same as no data These were two different things under one label. A ride whose queue the park never measures is not the same as one we have no data for today, and the explanation they shared only applied to the second. They are now separate, each with its own reason, and they differ by colour at a glance. Unified names A ride and its Single Rider queue could appear in different languages, so they did not look like the same ride. Some names also carried the park's map number or invisible characters that broke alphabetical order. Steadier ads On iPad the ad slot went blank when no large-format ad was available. It now retries with a smaller one.

Two data sources, and the app no longer takes one at its word Until now WaitDrop relied on a single source. If that source got it wrong, so did the app. And it does get it wrong: at Parque Warner, on an ordinary day, 14 rides were flagged as closed while several were running — one of them with a 60-minute queue. From this version there are two sources, cross-checked. When they disagree for more than half an hour, the app stops trusting the one saying "closed". And only in that direction: if one says open and the other closed, we won't send you to a queue that might not exist. Rides that simply weren't there Parque de Atracciones de Madrid has 8 rides the app never showed — Los Rápidos, Vértigo, Lanzadera, Los Fiordos and four more. A third of the park. The second source brings them in, along with dozens at other parks. Knowing whether the park is open Walk into a park and you now see whether it's open, and until when. With the park closed every ride shows as closed, and without this line the screen looked like a bug. The hours are the ones each park publishes, a month ahead. Getting to each ride New "View on map" on every ride page: it opens Maps at the ride itself, not at the park entrance. WaitDrop is now on iPad The app is now available on iPad too, not just iPhone. Tick off the rides you've already been on In a big park you lose count fast. You can now mark every ride you go on, and marked rides show a green checkmark next to the name. WaitDrop PRO unlocks the full history, grouped by park and dated; marking them is free. Say what each ride is like, and whether you enjoyed it The app knew how long the queue was, but nothing about what the ride is actually like. Whether it's scary, whether it works for kids, whether you get soaked — only someone who's been on it knows that. Every ride page now has "What it's like": eleven tags to pick up to three from, with the most-voted ones shown as percentages. And when you mark a ride as done, three faces appear so you can say whether you enjoyed it — right there, just off the ride, which is when you know. The page then sums up the verdict: "People love it · 82 ratings". Only people who've marked the ride as done can have their say, so what you read comes from people who were actually there. Choose your theme: automatic, light or dark The theme followed your phone, but the switch only toggled between light and dark: touch it once and automatic was gone. Now you pick between all three. Also fixed • Rides are grouped by park area, closed ones included, with a bar showing how many you have ridden. • Ridden, favourite and alert buttons are visible in the list, no swiping. \1: the average sits with the live figure ("35 min · Average 62 min"), with an arrow saying whether the queue is rising or falling. And it loads considerably faster. • Create an alert from the list itself: a strip unfolds with the most-used thresholds, adapted to that ride's queue. • PRO features now show a sample, so you can see what you are buying before paying. \1: cards and rows were painted with a white meant for dark theme. • The Parks header animation flickered if you stopped scrolling halfway, and went haywire when filtering by a country with few parks. • "Out of season" was a lie: of the 57 rides arriving flagged that way, not one was. They go back to their area, marked "No recent data", which is all that can honestly be said. • Restaurants, shops and drinks machines no longer show up among the rides: 140 catalogue entries that weren't rides. • The alert screen's cards now follow the same pattern as the rest of the lists. Thanks for using WaitDrop. If something doesn't work as expected, write to us from Profile > Help: we read every message.

==================== ESPAÑOL (es-ES) ==================== Cuando un parque deja de publicar datos, ahora te lo decimos Los tiempos de espera nos los da el parque, y a veces deja de publicarlos sin avisar. Hasta ahora, esas atracciones aparecían como "Cerradas" aunque estuvieran funcionando con total normalidad. A partir de esta versión, cuando llevamos tres días o más sin recibir una sola lectura de apertura de una atracción, dejamos de afirmar que está cerrada y mostramos "Sin datos recientes", explicando que el parque no está publicando su estado y que conviene confirmarlo al llegar. Es lo único que de verdad sabemos, y preferimos decirlo a inventarlo. Esto también llega a los avisos de cola: antes, un aviso sobre una atracción así no habría saltado nunca y te habrías quedado esperando sin saber por qué. Ahora te avisamos. Las atracciones que cierran de verdad —por horario o por temporada— se siguen viendo exactamente igual que hasta ahora. También hemos arreglado • Al comprar el plan trimestral, el indicador de carga aparecía sobre el botón del plan mensual. La compra funcionaba bien, pero parecía que estabas comprando otra cosa. • Los títulos largos de las pantallas se cortaban a media frase; ahora pueden ocupar dos líneas. • Los títulos quedaban descentrados en las pantallas con botón de volver. • El texto que explica la sección "Sin datos recientes" quedaba pegado al borde de la pantalla, desalineado respecto a las tarjetas que describe. Gracias por usar WaitDrop. Si algo no funciona como esperas, escríbenos desde Perfil > Ayuda: leemos todos los mensajes.