Travel & Bookingモバイルアプリテンプレート
Travel screens run in a line. Search, a list of results, one option, and a confirmation the user can find the next day. Search should ask for the facts that change the results, usually where and when, and leave the rest for later. Results are a list someone can scan: a name, a price, and the one fact that decides it. A time, a number of stops, a distance, a rating.
The detail screen answers the practical questions for that object. A room needs the dates and the nightly price. A flight needs times and stops. A car or a parking spot needs where it is and until when. The confirmation is a ticket: a code, the time, and where to go. If a banner covers the code, move the banner.
Use a map when the user has to reach a place. A trip planner can lead with the itinerary instead of a map. Pick one primary object, a stay, a ride, a flight, or a spot, and remove the modules from the other templates. A hotel home screen that also offers a flight search and a parking map is three products.
The row on the results list should be tappable as a whole, with the price in the same position every time. That consistency matters more than a unique card style. People are comparing, and comparison fails when each row hides the price in a different corner.