Skip to content
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

Timer sometimes goes off less than the set interval #146

Open
dougli1sqrd opened this issue Mar 16, 2018 · 0 comments
Open

Timer sometimes goes off less than the set interval #146

dougli1sqrd opened this issue Mar 16, 2018 · 0 comments

Comments

@dougli1sqrd
Copy link

Love love the app! I use it every day in SF!

Sometimes when I set the timer for a bus, say for when the bus is 5 minutes away, the timer will not go off until later, say the bus is 3 minutes away. That's not so bad, but if the timer is 3 minutes, I'm in much greater danger of missing the bus I'm waiting for.

Expected behavior would be for the timer to be a little more conservative, and definitely not go off later than set.

Possible proposal: I imagine the timer is requesting whatever agency API for how close the bus is to the given stop, and then going off when it's closer than the timer value. One thing that could be done is set a real time countdown, so that if the network is down or the API is inaccurate for a brief period, you still get a time based on the last known bus position. Then the countdown could be updated every time quicky asks the agency for the new real time data. For example, if the timer is set for 3 minutes, and the bus is 5 minutes away, set a real time timer for 2 minutes, and if not updated in that time, set off the quicky timer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant