Design 1:

Task 2: View real-time location of social contacts:	Storyboard	Learnability	Efficiency	Safety	Visibility
	Once Bob adds Joe as a contact, Joe can now search for Bob in his social contacts. He sees the screen shown here that indicates Bob’s current location (depending on what Bob allowed him to view). Joe can also choose to view historical locations visited by Bob or Bob’s aggregated information. On the similar screen on Bob’s application, where Bob would be viewing Joe’s profile, Bob would see that the button “View Aggregated Information” would be disabled since Joe did not allow Bob to view his aggregated information. Suppose that a month has passed since Joe added Bob to his contact list. Joe can view Bob’s historical data by clicking on the button called “View Past Locations”. He would then see this screen that shows Bob’s locations using markers on three different maps. These three maps correspond to a daily, weekly and monthly summary of Bob’s locations (based on the permissions that Bob set for Joe).		Have to explicitly search for the contact to be able to view location. Would be better if there was an alphabetical list of contacts that the user could scroll through.	Cannot edit the contact's information, so nothing irreversible can happen.	The most important detail (current location) is visible in an understandable manner in a quick glance.

Task 3: View offers and opt-in to create commercial contacts:	Storyboard	Learnability	Efficiency	Safety	Visibility
	Joe starts from the home screen and clicks  on the tab “Commercial Contacts”. He is then taken to the screen shown here that can be considered the “Home Screen” to handle his commercial contacts. Here, he can view various categories of products on a wheel.  This visual representation helps him view various categories in a quick glance. Tiny numbers enclosed in circles indicate the number of offers by merchants/stores belonging to that category. Since Joe is at a ski resort and wants to buy some gear, he selects the wedge titled “Sporting Goods”. He is then taken to the next screen that shows him the list of stores selling sporting goods and having offers. Here, Rei happens to be the store offering the two discounts in this category. Since the two offers require different location information (either in type or amount), the actual location value is not displayed here. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ca10ba64-84d4-46b3-9d96-72630a71d892"><ac:plain-text-body><![CDATA[[Note: you can view the sketch in the “Home ]]></ac:plain-text-body></ac:structured-macro>  screen” section to see an example of the location information displayed below the store names]. The distance from his current location to Rei is also displayed (0.2 mi). Once he clicks  on the region, he is taken to the next screen where he can see the two offers. Here we see that Rei is offering a 10% off in exchange for raw GPS coordinates. By default this would mean GPS coordinates in that state. We display Joe’s current GPS lat/long coordinates to help him visualize the exact information he will be sharing. The second offer involves a 25% discount in exchange for a weekly aggregate information . This means that LocaShare will aggregate Joe’s information into meaningful chunks and share them with Rei. In both cases, Joe can choose to accept or delete the offer by pressing the “Accept” or “Delete” buttons respectively. If he returns to the previous screen, these offers  do not disappear from the screen and will be  shown to him the next time he views the “Home Screen” for commercial contacts. Suppose that Joe decides to take Rei up on the first offer. He would now see the following screen that summarizes the information that Rei will receive and gives Joe to add Rei to a category (in case he wants it to be displayed in another category, or create a new category  for this merchant/store). He can then save Rei as a contact by pressing the “Save Contact” button or cancel the offer by clicking “Cancel”. If he clicks on “Cancel”, he will be taken back to the “Home Screen” for commercial contacts.	The numbers do not make sense as they are not labeled or defined on the screen.	Have to go through four screens to establish the commercial contact relationship.	If you over-share information, the only way to cancel that is by deleting the contact relationship. Not very efficient in that respect.	Options and controls are clearly visible.

Task 4: View aggregate information of social contacts:	Storyboard	Learnability	Efficiency	Safety	Visibility
	Since Alice wants to view Joe’s aggregate information, she first searches for Joe on her “Home Screen” for social contacts. She then sees Joe’s profile as seen in this sketch. At a glance, she can see that he is near Sunday River and so she is relived that he reached the resort safe and sound. When she clicks on “View Aggregated Information”, she sees the following screen. She can see a summary of Joe’s location on a daily, weekly and monthly basis. Instead of a map view that showed Bob’s locations using markers, in this aggregated view, Alice can see a pie chart/wheel showing the amount of time Joe spent at various places. This data can be collected from Google Places API. Google Places API supports categorizing locations based on their “type” (such as, church, restaurant, store, bank, university, gym). Alice can choose to drill down and get additional details by selecting a wedge from the wheel. Suppose  that she selected the category “Campground” (shown as a shaded region), she can see a list of places related to “Campground” that Joe has been to and the amount of time he spent at each place. Thus, she is able to keep track of her family member using LocaShare.	The user would use the first two screens to view the current location as well, so this task is easy to understand.	Have to go through three screens to view the interested data. May be helpful to have hovering mechanisms.	No irreversible change can be done in this viewing task.	The graphs do not really convey interesting information. May be helpful to show the information on the fourth screen on hover (instead of clicking and going  to another screen).

Task 5: Edit social contacts:	Storyboard	Learnability	Efficiency	Safety	Visibility
	Since Joe wants to modify the location permissions for Bob, he first searches for Bob on the “Home Screen” for social contacts. After he comes to Bob’s profile, he clicks on Bob’s icon/photo and comes to this screen. Here he view the amount and type of information that Bob can view about <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="23dfd21c-1f3d-4a01-a5a0-1f84a5edd239"><ac:plain-text-body><![CDATA[him. [Note: Suppose that during the trip Joe ]]></ac:plain-text-body></ac:structured-macro> allowed Bob to view his aggregated information.] Joe can see that Bob can see his current location as the lat/long in Cambridge, MA (his current location). He also sees the pie chart/wheel that describes the categorization of places that Bob was able to view about him. He can now choose to modify the permissions by clicking on the button called “Modify Permissions” or can choose to return by clicking “Cancel”. Once he clicks “Modify Permissions”, he taken to the permissions sketch described in task 1.	The task is not very easy to learn in these two slides, since the bulk of the editing happens in the permissions screen.	May be helpful to have a "Cancel This Option" button beside the specific/aggregate information display. That way, the user does not have to go to the permissions screen to cancel aggregation option (for example).	No irreversible action possible in these two screens.	The data that the social contact (user's friend, for example) can see is very visible and easy to understand.

Task 6: Edit commercial contacts:	Storyboard	Learnability	Efficiency	Safety	Visibility
	Since this task started with Joe seeing an offer from Rei, he is led to this sketch by clicking on Rei’s icon in the screen described in task 3 (that shows the two offers provided by Rei). In this screen, Joe can view the  current and aggregate information that Rei is able to view about Joe. Since a commercial contact is not editable by Joe (it was tied to the specific offer), he can only choose to continue sharing the information  or delete the contact. If he happens to accept multiple offers from Rei (that require different types and/or amounts of location information), this screen would show a summary of entire information set  that he is sharing with that one store. In that case, clicking on “Delete Contact” will stop Rei from accessing any of the pieces of information it was able to access previously. This is a more intuitive approach since it gives Joe control over the specific types and amount of location  information he wants to share with Rei.	The task is not very easy to learn in these two slides, since the bulk of the editing happens in the permissions screen.	May be helpful to have a "Cancel This Option" button beside the specific/aggregate information display. That way, the user does not have to go to the permissions screen to cancel aggregation option (for example).	What if the user wants to share a subset of information with Rei? This design describes an all-or-nothing approach.	The data that the social contact (Rei, for example) can see is very visible and easy to understand.