Page History

...

...

This design follows a typical flow in which the user first signs up or signs in.  Then, the user searches for his or her event.  In the next screen, the user selects his or her event from a list of results.  Lastly, the final screen shows the user the details about the event, including other users that have already joined this event in search of a carpooling partner.  This screen also allows the user to add himself or herself to the event.  After doing so, the screen would allow the user to check the boxes next to the other users and contact them.

All-in-one Design

This design differs from the previous one in two fundamental ways:

1. It completely changes the order in which a user signs up for the service.  Instead of forcing the user to sign up immediately, this design allows the user to first search and see that other users are interested in carpooling before creating an account.  By allowing users to search first and then sign up, users are shown the value of the website, which should motivate them to get past the obstacle of signing up.
2. It seeks to compress the various screens needed to meet the user's needs into one screen.  In this design, additional sections of the screen will be made available as the user progresses through the UI.  For example, after the user enters search criteria and presses submit, the next section, "Matching Events", will then appear.

Ultra-Efficient Design

This design seeks ultra-efficiency.  As soon as the person enters the event that they are looking for, the best match is shown.  The user can then enter his or her information and click a button to automatically send a form email to the top two potential partners based on proximity.  With this design, a user could reach out to other potential partners in very few clicks.

focuses on efficiency in the sense that the goal is to have the user have the most control per page, reducing the need to navigate between pages frequently. While there is some crowding on certain images, this would be targeted at web users who are on laptop/desktop computers. This means at a higher resolution we would be able to fit these controls much more easily. Also, many items on each page display multiple pieces of information such as each one of the pointers on the map on the screen labeled "Main Page". The display the time for the next time you will have to go to that location.

This design focuses on the mobile user. This mainly includes interfacing that is much more viable for a touchscreen/smaller screened device. Unlike the efficiency design, not much is tried to be conveyed in each activity. Breaking the same work into more "pages" helps the user have safety because although your fingers are very precise, touchscreens require buttons to have a large hitbox which causes problems if there is a lot going on on every page. The main navigation for this implementation would be either tabbed browsing using an Android Fragment scheme or a dropdown box that contains all relevant activities. This number should be less than 5 or 6 because this would probably be a compliment to a web interface.

This design focuses on usability because our overarching user class ( parents ) may also be older and not as familiar with newer applications or even computers themselves. This implementation focuses on using images and other external contexts that all users would be familiar with in order to make the experience either. The goal of making this more illustrative is that we want parents to have full functionality without having to understand any intermediate/advanced computer browsing methods. One feature is standardized subject heads for messages. This would make sure that messages are clear and to the point based on the other user's request. The message could contain more content in the body, but there is much less need for that with automated subject headsIf the best matched results is not in fact the result that the user wants, he or she can click the button at the top right to go to the results page and select a different event.