I have a bit of a dilemma. The above screenshot shows the UI wireframing I'm doing for a taxi-booking and sharing mobile app.
Now when a user requests a seat in a taxi you've booked, a couple of things happen:
You receive a notification, and you need to act on it (either by accepting it or rejecting it asap, because it is a time-sensitive application, it is important that a decision is made).
Your journey details change, including the price, journey time and distance. Secondly if you had 4 seats available in your taxi, it gets reduced to 3.
My dilemma is as follows:
How do I keep the notifications "alive" if the user has not accepted/declined a sharing request? With the mobile apps I've seen so far, you receive a notification and then once you open it, it is of no use. With taxi share requests, I'd like to keep the notifications "in focus" until the user makes a decision, so that they don't forget
How would I reflect the changes to the journey (which are displayed once the user taps on the share request notification) with a bit more impact? Currently I am using the UI setup above (to the right)... although this is good... it makes it very hard to tell which implications are raised (in terms of cost, journey time and length) when the user decides to a share a taxi. As they need to base their decisions on these implications, its important that I get it correct. In the instance below, I've simply highlighted the changes in a different colour. Would there be a better way of showing a before/after snapshot (i.e. what the journey looks like now and what it would look like afterwards).