You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: