Right now for bus stops you have to put in the stop ID which can be somewhat annoying because it's not always readily available to the user. This is a bad user experience and should be improved.
The WMATA API has an endpoint for nearby stops which accepts LAT/LONG coordinates. The proposed flow would be something like this...
> User asks for nearby stop
> Application asks if it can access the users location data.
> User accepts or denies, application then presents the top 3 stops near them if they accept.
> User selects a stop, and the prediction data is presented to them.
This could be improved for assistant devices with a screen as an actual interface could be presented to the user for them to select, for speaker devices (Most Google Homes) the name could be read off to them, or the address.
I'm not sure if this is really needed for trains, or if the tools even exist for the functionality to be mimicked for that service.