-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wait times are totally off #41
Comments
Hi, thank you for your feedback. The goal of the project is to make an estimate based on previous data (Google data). I know that the app may be not accurate and this is why I also added the user feedback feature. This feature is very useful because, as in your case, an user can update the wait time by giving a very similar real wait time. By doing this, the app will be more accurate. |
I understand that these are estimates, but if they're off by 30 minutes, then they're useless. The whole point of the app is to give me an idea of how long I can expect to wait. If you want to make it a crowd-sourcing app, where the times are based on user submissions, then fine. It might work, it might not work (depending on whether there are enough submissions). |
Crowdsourcing data is always based on information. Look at Waze. Garbage in, garbage out. I don't think we can blame the developers here. However, the sluggishness of the application et al has put many people off. Some other developers, programmers have created their own similar applications which have gained a heckuva lot more traction. Take this application for example https://howbsy.com/ It's very basic, but effective AND ridiculously popular. If the geniuses here would implement some of the features including a very nice and clean interface similar to howsby and fix the terrible mapping UI, covid19-waiting time the join tech might be a success. |
It seems that in order to come up with your wait times, you're taking the time range that's given by Google, do some math, using popularity and historical values, to then come up with a single number. (So, basically guessing...)
Unfortunately, the result is nowhere close to reality.
I just went to a store that had a 35 MINUTE wait time listed, but, once I was there, there was absolutely NOBODY in line at all. ZERO wait time...
When I got home I checked again, and it still gave me 35 minutes, so, I'm afraid your algorithm isn't really working for quickly changing situations (as we have right now).
The text was updated successfully, but these errors were encountered: