A taxi sharing application that I'm working on as part of a university project has a "request seat" option. I've spent the afternoon working on the interface (arguably the most important UI element of the app), but I have the feeling that what I have produced so far is clunky and leaves a lot to be desired for.
The top section of the screen shows the current journey that the user would be requesting the seat for, and any pickups (via) that will be made.
The middle section of the screen shows the route being taken.
The bottom section allows the user to enter a pickup address (no destination address is taken because it is implied that the user requesting a seat on the journey is going to the same place), specify a pickup time (once again within a predefined range) and specify their fare contribution (using the +/-). As the user enters their address, the estimated fare value is updated along with the map in real-time.
What I think
The top/middle section of the screen seem alright, but the bottom section can be simplified. Hence, I have the following UI-related questions:
Is there a better way to position the pickup address/time, fare contribution fields? Are the +/- controls necessary? How could I streamline this screen's design to make it better?
The user is currently able to specify a fare contribution of their own but this seems rather unfair, is there anyway to enforce a principle wherein the software provides a minimum fare in view of what everyone else is paying to make it as accurate and fair as possible. How could this be implemented into the existing UI? I've included the "journey" screen (which appears prior to the "request seat" screen - the user clicks on the request seat button to move onto the "request seat" screen above).
Please share your thoughts.