| Gallery |
|---|
| include | 1-1.png, 1-2.png, 1-3.png, 1-4.png |
|---|
| title | Efficiency Design |
|---|
|
This design 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.
| Gallery |
|---|
| include | 2-1.png, 2-2.png, 2-3.png, 2-4.png, 2-5.png, 2-6.png |
|---|
| title | Mobile Design |
|---|
|
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.
| Gallery |
|---|
| title | Usability Design=3-1.png, 3-2.png, 3-3.png, 3-4.png, 3-5.png |
|---|
|
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 heads.