# Dollaride Product Feedback ## After initial Browserstack demo * Given that drivers are dealing with a higher volume of pick-ups/drop-offs, the boarding process seems closer to a standard single pick-up ride-sharing experience, which makes it harder to easily have visuals to identify the passanger, ensure they're on-board, and check payment. For example, user profile photos/thumbnails are small. ## Questions * Where are the driver codes displayed? * Would it be faster to have seatback info with the code? * Do the participating drivers have QR codes to drive installs? * Are there any markings on the outside of the vans to help riders identify the van they're meant to get onto? * Is it actually faster to hail a van vs. waving one down? * How does the app fill the roll of the "dispatcher"? * Is the Wadgma Testing Matrix still in progress as an exercise? Who created it? What about the other PM checklist? * Is on-van advertising part of the strategy? * Did you use the questionaire on any users who fit the personas? * Beyond the data point from the email from Renee, has their been research into unlimited passes for a fixed duration of time? ## Comments * If a passenger has card auto-payment setup, the user is charged based on the geofence * There is auto-boarding and auto-charging for stored credit cards * Need to find a way to handle edge cases where the driver and/or passenger decide to circumvent dollaride for payment but still used it for hailing * The static routes aren't given visual emphasis. From a product perspective, I think that perhaps Dollaride is more of an on-demand bus system than a group ride-hailing service. The UX for both the driver and rider seems to support the latter. For example D2D pickup/drop-off makes it feel closer to Lyft Lines/Shared Rides or Via. It seems that Dollaride may require drivers to adjust their behaviors to benefit from the app instead of easing critical painpoints for how they already are running their business. ###### tags: `Dollaride` `feedback`