>I'd like to be able to rearrange the order so that I can put my local station at the top. EDIT: I guess having location on kinda does this. I just almost never give apps access to my location out of habit, but since this lovely app is open source I can actually confirm that it isn't doing anything with my data! Ty for putting the source up, really appreciate it.
Yeah I could have some sort of manual sorting, but it might get a little complex, and possibly confusing if location overrides it.
​
>The thing at the top that tells you how recently it was updated gives me anxiety - it's animation every second is distracting and feels like a countdown clock even though it is not. I'd appreciate if that was at the bottom of the page or if it only updated every 10s or so.
Haha this is fair, I might have gone a little overboard here. I think moving it to the bottom makes sense and only showing something at the top if there's something wrong. An error bar will already appear here if the latest refresh (every 30s) failed so that's an indication of failure anyway.
​
>There is no need to label the Hoboken layover trains with HOB if they are past Hoboken on either end. For instance, it is confusing to see JSQ HOB in the Grove St box because that train is the same as JSQ: It is only going to Journal Square. Same as 33rd HOB at like Christopher St. I know the trains themselves don't do this, but it would be a little less confusing in the app.
This is a good point. I did keep it for consistency with the trains and the TVs at the stations. I definitely agree with the simplicity here, will need to think if I want that to override the consistency argument.
​
>it would be cool to have an indication of what left/right arrows mean. The path app uses "to NY" / "to NJ" to differentiate, which is helpful. This would also help with the last bullet.
Yeah the arrows aren't immediately obvious, I kind of do expect people to enable the option to only show only the opposite direction, but that is also not super discoverable. My fear with "to NJ/NY" is clutter since that's fairly verbose and not an icon. It'd be nice if either state had an obvious symbol to use. Any ideas here?
​
>it would be nice if I could tap on a train and see its scheduled list of stops. This is really missing from the official PATH app. Bonus points for showing current delay and then propagating that delay to each future stop as an estimate.
Oh that would be cool for new riders! The data is not going to be perfect here since the API from PATH doesn't actually say what a train is, only arrivals, so it would be using heuristics, I think I would be able to guess 95% of the time correctly though. I think the delay is already built in, I will notice that on the NWR-WTC train for example all the ETAs at JSQ, Grove, and Exchange Place, will move in sync, or won't move when a train is stopped.
​
>it would be nice if I could tap on the station name and see an expanded view with more trains.
All the trains that we get from the API are already shown unfortunately, there's no more information to show, for real-time arrivals. I could add on the schedule afterwards, but that might get a little dicey, e.g. if a train is arriving at 4:12 and the schedule says there is a train at 4:10 and 4:15, which train is that?
​
>Unfortunately, PATH is so often broken in some way that I always check the alerts before going anywhere. it might be necessary to put the Path alerts on this app so that users don't have to use two apps every time they travel.
Good idea! I'll have to see if there's an endpoint for this.
NocturnalBeaver OP t1_jaabp0i wrote
Reply to comment by theLRG in PATH Real-Time Arrivals Android App by NocturnalBeaver
Great suggestions!
>I'd like to be able to rearrange the order so that I can put my local station at the top. EDIT: I guess having location on kinda does this. I just almost never give apps access to my location out of habit, but since this lovely app is open source I can actually confirm that it isn't doing anything with my data! Ty for putting the source up, really appreciate it.
Yeah I could have some sort of manual sorting, but it might get a little complex, and possibly confusing if location overrides it.
​
>The thing at the top that tells you how recently it was updated gives me anxiety - it's animation every second is distracting and feels like a countdown clock even though it is not. I'd appreciate if that was at the bottom of the page or if it only updated every 10s or so.
Haha this is fair, I might have gone a little overboard here. I think moving it to the bottom makes sense and only showing something at the top if there's something wrong. An error bar will already appear here if the latest refresh (every 30s) failed so that's an indication of failure anyway.
​
>There is no need to label the Hoboken layover trains with HOB if they are past Hoboken on either end. For instance, it is confusing to see JSQ HOB in the Grove St box because that train is the same as JSQ: It is only going to Journal Square. Same as 33rd HOB at like Christopher St. I know the trains themselves don't do this, but it would be a little less confusing in the app.
This is a good point. I did keep it for consistency with the trains and the TVs at the stations. I definitely agree with the simplicity here, will need to think if I want that to override the consistency argument.
​
>it would be cool to have an indication of what left/right arrows mean. The path app uses "to NY" / "to NJ" to differentiate, which is helpful. This would also help with the last bullet.
Yeah the arrows aren't immediately obvious, I kind of do expect people to enable the option to only show only the opposite direction, but that is also not super discoverable. My fear with "to NJ/NY" is clutter since that's fairly verbose and not an icon. It'd be nice if either state had an obvious symbol to use. Any ideas here?
​
>it would be nice if I could tap on a train and see its scheduled list of stops. This is really missing from the official PATH app. Bonus points for showing current delay and then propagating that delay to each future stop as an estimate.
Oh that would be cool for new riders! The data is not going to be perfect here since the API from PATH doesn't actually say what a train is, only arrivals, so it would be using heuristics, I think I would be able to guess 95% of the time correctly though. I think the delay is already built in, I will notice that on the NWR-WTC train for example all the ETAs at JSQ, Grove, and Exchange Place, will move in sync, or won't move when a train is stopped.
​
>it would be nice if I could tap on the station name and see an expanded view with more trains.
All the trains that we get from the API are already shown unfortunately, there's no more information to show, for real-time arrivals. I could add on the schedule afterwards, but that might get a little dicey, e.g. if a train is arriving at 4:12 and the schedule says there is a train at 4:10 and 4:15, which train is that?
​
>Unfortunately, PATH is so often broken in some way that I always check the alerts before going anywhere. it might be necessary to put the Path alerts on this app so that users don't have to use two apps every time they travel.
Good idea! I'll have to see if there's an endpoint for this.