Collaboration and Social Software
- 1 Readings
- 2 Reading Responses
- 2.1 Brian Chang - 4/13/2013 14:43:24
- 2.2 Monica To - 4/13/2013 15:56:12
- 2.3 Timothy Wu - 4/13/2013 16:04:18
- 2.4 Jeffery Butler - 4/13/2013 18:37:24
- 2.5 Alice Huynh - 4/13/2013 23:34:47
- 2.6 Lauren Fratamico - 4/14/2013 13:26:14
- 2.7 Mukul Murthy - 4/14/2013 15:20:57
- 2.8 Colin Chang - 4/14/2013 16:31:40
- 2.9 Eric Wishart - 4/14/2013 21:42:04
- 2.10 Yuliang Guan - 4/14/2013 23:22:26
- 2.11 Elise McCallum - 4/14/2013 23:27:35
- 2.12 Brent Batas - 4/14/2013 23:27:55
- 2.13 yunrui zhang - 4/14/2013 23:36:28
- 2.14 Linda Cai - 4/14/2013 23:59:32
- 2.15 Timothy Ko - 4/15/2013 0:39:58
- 2.16 Zeeshan Javed - 4/15/2013 0:55:36
- 2.17 Cong Chen - 4/15/2013 0:58:48
- 2.18 Erika Delk - 4/15/2013 1:06:35
- 2.19 Ben Goldberg - 4/15/2013 1:06:53
- 2.20 Kevin Liang - 4/15/2013 1:33:21
- 2.21 Zhaochen "JJ" Liu - 4/15/2013 2:02:04
- 2.22 Ben Dong - 4/15/2013 2:52:01
- 2.23 Weishu Xu - 4/15/2013 4:24:42
- 2.24 Shujing Zhang - 4/15/2013 4:26:21
- 2.25 Aarthi Ravi - 4/15/2013 7:37:16
- 2.26 Ryan Rho - 4/15/2013 8:48:03
- 2.27 Bryan Pine - 4/15/2013 8:54:28
- 2.28 Tenzin Nyima - 4/15/2013 9:05:58
- 2.29 Scott Stewart - 4/15/2013 10:30:22
- 2.30 Raymond Lin - 4/15/2013 10:50:01
- 2.31 Yong Hoon Lee - 4/15/2013 10:53:58
- 2.32 Cory Chen - 4/15/2013 11:25:18
- 2.33 Christina Hang - 4/15/2013 11:35:10
- 2.34 Sangyoon Park - 4/15/2013 11:37:53
- 2.35 Annie (Eun Sun) Shin - 4/15/2013 11:51:49
- 2.36 Kate Gorman - 4/15/2013 11:56:19
- 2.37 Soo Hyoung (Eric) Cheong - 4/15/2013 12:07:29
- 2.38 Sihyun Park - 4/15/2013 12:15:09
- 2.39 Michael Flater - 4/15/2013 12:22:56
- 2.40 Moshe Leon - 4/15/2013 12:24:59
- 2.41 Arivnd Ramesh - 4/15/2013 12:25:55
- 2.42 Dennis Li - 4/15/2013 12:29:00
- 2.43 Tiffany Jianto - 4/15/2013 12:32:29
- 2.44 Edward Shi - 4/15/2013 12:33:39
- 2.45 Sumer Joshi - 4/15/2013 12:34:20
- 2.46 Claire Tuna - 4/15/2013 12:40:04
- 2.47 Christine Loh - 4/15/2013 12:49:15
- 2.48 Joyce Liu - 4/15/2013 12:59:24
- 2.49 Brett Johnson - 4/15/2013 13:00:20
- 2.50 Glenn Sugden - 4/15/2013 13:07:10
- 2.51 Eric Xiao - 4/15/2013 13:13:55
- 2.52 Tiffany Lee - 4/15/2013 13:15:43
- 2.53 Lishan Zhang - 4/15/2013 13:19:43
- 2.54 kayvan najafzadeh - 4/15/2013 13:21:58
- 2.55 Nadine Salter - 4/15/2013 13:31:09
- 2.56 Andrew Gealy - 4/15/2013 13:42:14
- 2.57 Avneesh Kohli - 4/15/2013 13:58:12
- 2.58 Matthew Chang - 4/15/2013 14:01:46
- 2.59 Oulun Zhao - 4/15/2013 14:01:49
- 2.60 Kimberly White - 4/15/2013 14:06:49
- 2.61 Alvin Yuan - 4/15/2013 14:09:03
- 2.62 David Seeto - 4/15/2013 14:14:54
- 2.63 André Crabb - 4/15/2013 14:15:12
- 2.64 Brian Wong - 4/15/2013 14:20:22
- 2.65 Minhaj khan - 4/15/2013 14:20:42
- 2.66 Juntao Mao - 4/15/2013 14:23:05
- 2.67 Eric Leung - 4/15/2013 14:24:24
- 2.68 Derek Lau - 4/15/2013 14:29:42
- 2.69 Tananun Songdechakraiwut - 4/15/2013 14:29:43
- 2.70 Jin Ryu - 4/15/2013 14:29:55
- 2.71 Alysha Jivani - 4/15/2013 14:30:25
- 2.72 Lemuel Daniel Wu - 4/15/2013 14:32:33
- 2.73 Achal - 4/15/2013 14:59:50
- 2.74 Soyeon Kim (Summer) - 4/16/2013 1:06:50
- 2.75 Jian-Yang Liu - 4/17/2013 12:55:00
- Shneiderman, Plaisant, Coen, Jacobs. Designing the User Interface. Chapter 9, Collaboration and Social Media Participation.
Brian Chang - 4/13/2013 14:43:24
Yes, our application involves multiple users sharing grocery lists with each other and requesting items. Our app falls into the different time and different place time matrix that involves communication and coordination. Users will need to communicate their needs and coordinate a time to meet. The primary goal of collaboration is to share the burden of getting groceries and to be able to split large quantities of items. Major challenges include how people will coordinate inorder to make things simple. For example, what is the easiest way to designate a pick-up time for the groceries since everyone is running on different schedules. Our app will need to address that issue which involves both how to display that and what users will desire in that social context.
Monica To - 4/13/2013 15:56:12
The mobile application that my group, ACME, is creating is a garage sale app that will centralize the garage sale experience. It is an app that is targeted towards garage sale planners (people who hold garage sales) and garage sale attendees (people who go to garage sales). The applicaiton will allow garage sale planners to list their sale allowing them to write descriptions, provide photos straight from their phones and post to the feed to better advertise their sale. Other users are able to search for sales nearby or by content and they'll be able to favorite sales they're interested in for later viewing. Users will also be able to message the garage sale planners to ask for more information regarding the sale or items shown in posted photos. For the time-space matrix from the reading, I believe that our app, for the most part, falls in the Asynchronous Distributed Interfaces: "Different place, different time" quadrant (Communication + coordination). This is because it does not expect both parties (planners and attendees) to be online and viewing the listing at the same exact time. The planner posts their listing and attendees all around at different times of the day will view the listing. The messaging funtion of the app will also be in this quadrant. It will most likely be something similar to E-mail, where someone sends a message and it goes into their "inbox" and the recipient of the message will check and read it on their own time. I remarked earlier that our app was "for the most part" in the different time, different place quadrant becuase there may be cases where both the planner and the attendee are both online and the messaging may become someone thing more similar to Instant messaging rather than email. But it all depends on when the users decide to use our app. Our primary goal of our app is to centralize the garage sale experience from the garage sale planner advertising their sale to the garage sale attendee searching for sales. Another major goal of our application is to improve the means of communication between both targeted parties. We want to create a messaging system that will allow attendees to ask questions and have planners answer them without violating any of the parties' privacy. We will have some sort of anonymity implemented to protect both parties. We believe that having a platform for communication will ultimately mutually benefit both parties. Attendees may be searching for a specific rare item and are willing to pay for it, while planners really want to sell their item. By giving them a platform to communicate, advertise, and search, we will be making it easier for both parties to achieve their respective goals. As mentioned briefly earlier, one of our main social challenges is the issue surrounding privacy. We need to create a communication system in our app that will protect the privacy of both of our target audiences. Giving the users the option to be anonymous seems to be a potential solution to this challenge. Another potential solution is providing users with usernames (which under the user's discretion could include their name or not). Our group discussed the challenges and social features in our application, Gsale, and we have all agreed that having the messaging platform implemented will vastly improve our applicaiton and our overall concept goal: it will make listing, communicating, and searching for garage sales easy, convenient, and efficient.
Timothy Wu - 4/13/2013 16:04:18
Yes, our application involves some form of collaboration between users. It falls more into the Different Time, Different Place quadrant of the matrix because the interaction is neither directly with each user in the same place, nor is it necessarily at the same time. The interaction between users in our application is primarily between users who submit new information about recyclable items and those who access that information, and also to show statistics about a person's recycling impact in the Berkeley community. The primary goals would be to make recycling easier in the Berkeley area by crowdsourcing almost-instantaneous answers of whether items are recyclable.
One of the main challenges our application has to overcome to succeed socially is to incentivize people to submit information about items in the questionnaire. Because the questionnaire has four screens and takes some time to complete, some users may encounter the screen and then want to close the app. In order to reduce the rate of that occurring, we might have to create some kind of social incentive to motivate people to want to fill out the questionnaire. The reading mentioned four means of motivation: egoism (benefiting oneself), altruism (helping out of genuine desire to help), collectivism (believing in supporting the community), and principalism (being taught principles). In the context of our application, I think we should probably be more explicit about the crowdsourcing aspect of entering information into the questionnaire because it would likely evoke a sense of collectivism in our users. We want to make the users feel like they are benefiting the entire Berkeley community by taking time out of their busy schedules in order to fill out our questionnaire, thereby making the application better and more useful in the future.
As for the community statistics aspect of the social function of our application, it could possibly be used to create a more egoist motivation for using the application. The History screen of our application, which contains the statistics for the user as well as the user in the context of the community, could also contain a leader board that ranks the top contributors to the application's database of recyclable items. Seeing their name on the top of the leader board would give them a sense of pride and well-being, as well as giving them the collectivist feeling that they have benefited the community.
Technical-wise, the first feature could simply be done using alerts or on-screen text. As for the second possible feature that I described, it may be more difficult to implement. Creating a community leader board would require having a field in the user model that increments each time a user completes the questionnaire. For the leader board itself on the History page, we would need to do a database query over the users table with the top 10 people with highest questionnaire completions. The backend for our application is probably going to be our biggest technical challenge going forward.
Jeffery Butler - 4/13/2013 18:37:24
Our current project does not have a social media participation implementation. For our project we could add in a component where sprayers comment on the particular house they are spraying. Then sprayers in the future can look at the pervious sprayer's comments about the location and know exactly how to act. Having this extra dimension of social media allows sprayers to collaborate and remember distinctive components regarding locations. This particular addition to the mSpray application would be in the asynchronous quadrant 'Same Place Different Time'. Because the sprayers are recording information about a particular area but they are acting on the area in different times. Also, having the social media implementation can assist 'collaboratories' in reference to the researchers. The researchers located around the world who need this sprayer data can have it enriched it by the sprayers reporting unique observations about the current gps coordinate/house. However, this application is directed towards individuals who are not smartphones users. Having these extra social media features will over complicate the application and ruin the simplicity of it. (Some of these users are not even able to read map let alone navigate through a complex smartphone UI). Will the sprayers be able to leave credible observations that will be beneficial to the researchers? Probably not, but they might be able to assist one another in properly spraying different homes effectively. In addition, this application is made specifically for enriching the data on malaria from South Africa. Researchers already communicate through social media means of EMAIL 'Asynchronous Different Place Different Time' and are already satisfied with the current means of retrieving data. Therefore, adding the social media component to our application will probably not be suitable for the problem that we are solving.
Alice Huynh - 4/13/2013 23:34:47
Yes, our application does involve a form of collaboration between users and social media. In the reading, our application is a bit of a crossover between collaboration and social media. According to the time-space matrix our application falls under “Communication + coordination” because users can interact with GroceryBuddy at different times in different places. Users can be in completely different places, but come together to help other users by inputting prices for items at the grocery store together.
The primary goal that GroceryBuddy is trying to achieve is for large grocery store companies to give us the information that we want: costs for groceries. If these companies are unwilling to share this information then it is up to users to collaborate together to get a better understanding of what the prices are for similar items from different grocery store locations.
The largest problem that GroceryBuddy has to face is the willingness for grocery shoppers to want to input prices into our application. Grocery shopping is already such a hectic experience that by having to create a lot of new items from the grocery store is time-consuming. The challenge will be finding the motivation to keep our application up-to-date with the users’ help. A technical challenge that we have to overcome is the correctness of grocery store items. It’s not going to be easy to always get the most up-to-date prices from all of the different grocery stores. It is also up to the grocery store companies themselves whether they want to output an API or a place for GroceryBuddy to access price data.
Lauren Fratamico - 4/14/2013 13:26:14
Currently our app does not have any form of collaboration between users or social media participation. As Bjoern mentioned during our presentation, we could add a component that does this in the form of sharing a date with the one we are going on it with, so that she can approve it and/or make modifications or suggestions to make the date great. I will evaluate this for this reading response.
The primary goal of this app is to help you plan a great date, and te primary goal of making it social would be to crowdsource the great date planning. This social change would enhance our app in that if would allow for more inputs on the date. If shared even more broadly than with just your date (eg on facebook), you could get more opinions on the places you are going. People might know of cool things to do in the area that would enhance your date or have other suggestions of better things to do. And if just sharing with your date, she could make similar suggestions, or note that, for example, you planned dinner at a seafood place and be able to remind you ahead of time that she hates seafood.
This would fall under the different place, different time quadrant on the matrix as users could edit the date from anywhere at any time via their mobil device (or make suggestions via email or facebook). The major challenges that we would face are: disruption of social process and the adoption process. People would have to be okay with sharing their date with their friends - this is somewhat socially taboo especially in some friend groups. I feel like females would be more likely to feel free to take friends help in planning a date more than men would. Our app would also have to figure out a way to actually share the information. It would probably be easier to share via facebook or email rather than require that all people have the app and can actually comment on/edit the date at the same time. This way we would not have to deal with synchronization details.
Mukul Murthy - 4/14/2013 15:20:57
Our application, FoodStuffs, involves collaboration between users. The intended use is to share shopping lists and current ingredients owned with roommates, so this involves the users updating their shared fridge and shopping list. This falls into the asynchronous, remote quadrant of the time-space matrix because different users eat groceries, add groceries, go shopping, or request groceries at different times, and each user uses their own device. The we plan to implement this is to have every fridge's current stock info stored in a database online, and have a user's device save a local copy every time they open the app. The goals of this collaboration is to enable roommates to always have certain items in stock, prevent items from going bad, and notify others when out of a certain food. However, there are a couple of challenges we still need to overcome. For one, different people can be part of different "fridge" groups. An example of this would be someone that lives with his roommates but spends a lot of time and shares groceries with his girlfriend at her place; ideally, this person would be able to contribute to both fridges but keep them separate from each other. Another issue we have run into is that while our group is all familiar with how databases work and how to use them, we don't have a database currently set up, so we would need to get some server to do that on and then set up a database.
Colin Chang - 4/14/2013 16:31:40
Think about your class project in light of the reading from Shneiderman & Plaisant's book chapter:
Does your application involve any form of collaboration between users or social media participation? If so, describe it briefly in light of the following questions: Which quadrant of the time-space matrix does the application fall into? What are the primary goals of collaboration or participation in your app? What are the major challenges (both technical and social) your application has to overcome to succeed? Our application does not involve collaboration between users or social media participation. Betternote is meant for personal use. If your class project does not involve any multi-user aspects, discuss how you could enhance your application by adding such support. Then answer the same questions for your hypothetical enhanced application. Social support could be added for peer review purposes (e.g. if you are writing of which you want early peer review). This would fall into the remote asynchronous quadrent (you write a outline draft, then request review). The primary goals of collaboration would be peer review. Challenges would be handling peer comments correctly. UX-wise, allowing reviewers to suggest changes and for the writer to accept/deny them and for reviews to offer more general comments. Though, this is not paralizingly difficult technically. You do not have to agree with your group members on your answers; in fact, disagreements can be productive. If you disagree, state so and have a conversation with your group to reconcile your different perspectives. Our app was not intended for sharing purposes, and the above social feature I listed is not being planned for implementation ever. I stipulated it for exercise purposes.
Eric Wishart - 4/14/2013 21:42:04
Our application falls into the different place and different time category. Our users must give information to others who will then review it at a potentially later time, and then respond back.
The primary goal of collaboration is to let people share information about what they would like to purchase, and then having these people respond with whether or not they would also like to get any of those items as well.
The major challenge technically will be setting up a server that can coordinate these messages that must be sent to different people who are connected to the internet a different times. The major social challenge will be getting people to want to coordinate shopping with one another to save big on bulk.
Yuliang Guan - 4/14/2013 23:22:26
(1) Our application is called “Splist” which is a grocery sharing application. People can use our app to coordinate buying in bulks with friends, share with friends, and save money and time. It does involve collaboration between users. It falls into the different place and different time quadrant of the time-space matrix, which different users can communicate and collaborate with each others in different time and places.
(2) In our app, the primary goals of collaboration or participation is as follows: Online communities--our app is for users who live in nearby communities to share groceries and split costs. These people come online to post and share information with each other; Meeting support--for the user who’s going to pick up stuffs from the sharer, they can contact through our app to make sure when and where to meet for the trade; In addition, another goal for our app is to make electronic commerce--users can search for what they would like to get from others or share with others, contact the sharer, confirm to meet, pay and pick up. It is a little bit similar with Craiglist but more focuses on sharing and splitting.
(3) A major challenge that our app face is to build a server to save the database. No matter what different users do to the app, it requests the server to make updates. So that all users can access to information in the database and share information. And also, we need to think about the exception handling. Our app has a wide range of users, which means a wide range of exception handling. Therefore, we need to make our interface as simple and clear as possible so as to meet the expectations of different users.
Elise McCallum - 4/14/2013 23:27:35
As of now, our application does not involve any form of collaboration between users/social media participation.
This application falls into the quadrant of communication + coordination (different time, different place), as it hopes to track and assist the recycling of users at different times in different physical places (all while within the constraint of Berkeley as a location). Integrating a social aspect would ideally increase increase use of the application without shifting into one of the other quadrants, such as requiring users to interact with each other in the present time.
One potential way we could add such support is to have a leader board of sorts for people who have contributed the most novel information (i.e. completed the greatest number of surveys). We have also considered adding the option to correct data input by other users which, if implemented, could be added to tabulate who should be on the leaderboard. A second way we could add such support but may be beyond the reaches of our application would be to allow users to build a profile and friend other people on the app so they can see how they stack up against their friends in terms of their recycling goals and gains. This could also be done with Facebook integration, but would be constrained to ensuring that only friends using the app were pulled from Facebook. The major technical challenge would be learning how to integrate with Facebook and also parse friends to isolate only those in the Berkeley area who use the app. The social challenge would be finding a way or incentive for people to use the collaborative tools on the app as well as reaching new users.
The primary goal of collaboration would be to encourage users to recycle more and be motivated by their peers to become more sustainable and environmentally-aware in the process.
Brent Batas - 4/14/2013 23:27:55
My class project, mSpray, is an app for spray workers to record usage of anti-malaria chemicals in South Africa. The users themselves do not collaborate with each other directly (they just record what they themselves do), but since their data is sent to the same server, they are collectively building up the same database of spray information.
Since social media is not prevalent among our target users—most do not own computers or mobile phones—it does not make sense to incorporate social media in our application since we would get limited participation, if any at all.
However, where we can incorporate collaboration is if we expand our project scope to target other areas other than the specific region in South Africa that we are currently targeting. Secondly, we would also expand our project scope to provide tools for researchers to analyze the data we gather. With various mSpray deployments for different regions, we could have a giant database that aggregates information from those different regions, and makes it accessible for research teams. This would allow various regions to cooperate in building knowledge of DDT, which is great since all of them are trying to achieve the same goal of figuring out how DDT affects ecosystems to determine if DDT is safe enough to use.
This type of collaboration would fall under the remote & asynchronous (aka different place, different time) part of the matrix. Sprays are done in different places and at different times.
A challenge to implementing this new functionality would be coming up with a way to aggregate data from different regions in a way that makes sense. For our mSpray application, we hardcode in the fact that sprayers are sent in teams of two (which they are, in our target user group), as well as the fact that sprayers use either DDT or Pyrethroid. However, in another area, they might actually use more than two sprayers, or they might use different chemicals. Additionally, some technical problems are figuring out how to identify bogus data (i.e., users just entered things in wrong), and remove it, so that the rest of the data can still be valid. Finally, another challenge is that since it is governments who would likely be using our application, we have to deal with the possibility that they do not want to share their information with other outside parties. In dealing with our customer, we have had to take some hefty precautions when it comes to privacy and politics, so it would be a challenge especially if we wanted multiple customers to collaborate.
yunrui zhang - 4/14/2013 23:36:28
Our application is BetaPro, which involves collaboration between users and social media participation. It may fall into all four quadrant of the time-space matrix, since a developer can be a single person, a group of friends, a project team, or even a small company. They may choose to collaborate face-to-fact, via emails, version controls, video/voice communications, or other social medias. The primary goals of collaboration is monetary/career awards that may come with emotional/personal fulfillment that comes with a successful developed application. There are some major challenges that our application has to overcome to succeed. First of all, it does not support multi-user communication as of now. This might be solved if each user in one project team signs in with a single account. But then this makes editing, rating, reviewing, paying not synchronized. Secondly, users in one project team may not agree on certain aspects of the review, and therefore differ in opinion of rating and paying the reviews, and there are no current solution that I have think of on to solve this problem on our side, other than letting the users to solve the problem themselves. Finally, developers may wish to change their applications according to the reviews, and a functionality of agreeing to what should be changed might be helpful. But as of now, it requires major code additions to our existing project to add this functionality.
Linda Cai - 4/14/2013 23:59:32
Our app allows users to discuss bills on the city council agendas. The application falls into the different-time, different-space quadrant. The goals are to express one's opinion about a bill and be heard in the environment that the app provides. Another goal is to attract more people to be involved in local by sharing bill information and showing one's support, which is done by sharing the bill and whether you support it on social networking websites such as Facebook. We also want users to be able to discover and read about other bills. A major challenge is getting people to participate in discussion, since many users involved in local politics are an older audience who are less likely to use smartphones and apps. Also, it well be difficult to start discussions on the bills if there is not a thriving community, which will likely be the case in new applications. People may be confused about what the bills entail and thus may not post about an issue they do not understand. Technically, it will be difficult to retrieve bill information and representative information since each city council has their own website with a different layout, so we will have to retrieve the information manually for now.
Timothy Ko - 4/15/2013 0:39:58
Our project currently does not involve any multi-user functionality, nor did we think to include any at the start of the project. While we do plan to include a feature that will send text messages out to other contacts, these contacts do not have to be other users of the application.
However, we could add a sharing functionality, where users can register each other as friends, and then see each other’s recorded drinking habits. This way, they can get a more detailed account of how their friends are doing in terms of alcohol consumption. The application would then fall into the quadrant of different time and different place, so it would involve communication and coordination. The communication comes from how users can look at other users’ statistics. The coordination comes from outside the application, where users encourage each other to modify their drinking habits, if needed.
The primary goal of collaboration would be for users to regulate the drinking habits of each other if any of them ever drink too much. A major social challenge for this application would be to ensure that users actually do regulate each other’s drinking habit. Otherwise this the feature has no purpose. We also need to somehow make sure this feature doesn’t encourage competition to drink more than your friends. ON the technical side, we need to figure out how we want users to access each other’s statistics. The most straightforward approach would be to use a database, but then we have to figure out where to store this database.
Zeeshan Javed - 4/15/2013 0:55:36
Our application does not involve exhaustive collaboration between users or social media. It could potentially feature a social network or email login, but as far as dedicated social networking, the application is more geared torward the indvidaul user and is in fact quite personal since it takes sensitive data (such as height and weight) into account.
However if the project is put into a variant stage where social networking is a more profuse focus than it would most likely focus on asynchronous remote communication. For quadrants, it would be under the communication/coordination category. The use of email, bulletin boards, blogs, work flow, and wikis would be useful in communicating ways to lose weight, recipes, and gluten-free life style tips. The major challenges that would have to be overcome would primarily be the lack of community in the inception of the application’s social feature. Technically the challenge would not be very difficult and would simply be a matter of paying for server space.
Cong Chen - 4/15/2013 0:58:48
Our application does involve collaboration between users. The quadrant of the time-space matrix that our application falls under is the Communication + Coordination quadrant. Our interaction is asynchronous and can be from different places/remote. Our application is Photo Focus, one that helps amateur photographers find cool locations to take pictures at from other photographers. With respect to the social aspect of it, users can post pictures that they have taken from certain locations so other users can use. Users can tag information to their pictures and other users can comment on it. Essentially, we are creating a community for amateur photographers to help each other learn and grow as photographers. Thus, our quadrant is Communication + Coordination because the events are async; people can post comments whenever. Likewise, the time zone does not matter as real time does not apply for us.
The primary goals of participants on our app is to find other cool locations to take pictures and learn from other amateur photographers. Thus, it makes sense that our platform is a community based one because users who may not know each other can still give comments to help each other learn about photography.
Some major challenges our app must overcome is making the community active and also linking it with flickr or 500px, existing photography social communities online. Because our app is small, we want users to be active in it so that other users can learn and the community can grow. To accomplish this, maybe consider small incentives for users. Another challenge is that our app helps users get information for photo shoots and link this information with their actual flickr or 500px account. Thus, a challenge for us would be to draw the line between what information goes to flickr and 500px and what stays on our social community and also what information should be on both social platforms. This is a difficult one as we do not want to make it confusing and a hassle for the user to upload twice or things like that.
Erika Delk - 4/15/2013 1:06:35
Yes, my class project does involve collaboration between users. We are designing the TV show tracker, and one of our features is being able to recommend shows to facebook friends. Because the different users would collaborate at different times and in different spaces, this would fall into the Communication + coordination or asynchronous and remote quadrant. The goal of this communication would be "decision support." Users would be motivated to check what friends have recommended to them because there would be a higher likely hood they would enjoy it; this makes the decision process easier. Furthermore, a user would be motivated to recommend a show to others out of friendliness and a willingness to contribute. The challenges of this are that firstly, we need to figure out a way to plug into the Facebook API, and secondly, we need to somehow convince users to view television watching as a social activity--which is somewhat different from the way most people tend to view TV.
Ben Goldberg - 4/15/2013 1:06:53
Yes, our app syncs to other users that use the same fridge, that way they can all view and update what is in the fridge. It falls into the different time/different place quadrant since users can update at any time from any place.
I would say that our primary goal for collaboration and participation is conferences. We want our users to be able to communicate with each other about the fridge they share. By inserting food entries, our app automatically generates the correct communication between users of the fridge.
Our major technical challenge is accurately storing and syncing data between users to ensure that they are all viewing updated and accurate information. If our app isn't accurate, users will learn to distrust it and won't use it. Although we haven't implemented these syncing features yet, these technical challenges will be an important consideration when we do.
As for social challenges, our main one is getting people to consistently use the app. The quicker and easier it is to use, the more reliably people will use it. But if people don't use the app much, the information stored in it will be outdated and will be of little use. We must take great care in making our app as convenient as possible to use. This will minimize the social challenge we are facing.
I believe our group members agree that the communication aspect of our app is an important one, although some might argue that it's not the main focus of it.
Kevin Liang - 4/15/2013 1:33:21
Our app that we are working on indeed does involve collaboration between users. Our app connects developers with reviewers to beta test applications. Keeping that in mind, I would believe that we fall in the category of communication + coordination on the time-space matrix. The primary goals of collaboration is to have a diverse amount of reviews in order to produce a decent application. There are many challenges for our application to succeed. One of the technical challenges is implementing the APK uploader with the auto generated code. On the social side, we need a large enough user-base of reviewers in order for the developers to even find our application worth using for beta testing. It may be pointless to upload an apk if there will only be a few reviewers.
Zhaochen "JJ" Liu - 4/15/2013 2:02:04
'Does your application involve any form of collaboration between users or social media participation?
Which quadrant of the time-space matrix does the application fall into?
Different time: our application is mainly asynchronous because it first requires a user to post a deal after he finds it. Then, other people who share the same interest may search the existing deals to find this one.
Different place & same place: the users usually use the system at different locations, but within the same region (same neighborhood). For example, it is more likely someone who live in Oakland to find the local deals posted by users in the Oakland or SF area. However, after the users ‘meet’ online, they may want to meet face-to-face to buy the products together (e.g. movie tickets, clothes) so it can be co-located as well.
What are the primary goals of collaboration or participation in your app?
Achieve common interests: all the users have the opportunity to share the good deals he knew around him to the community so that they can finally purchase the goods together at a lower cost. Aware of outside communities: the users may also use our app as a deal discovery tool so that he can know what is on sale or the general market trends. Avoid social awkwardness: users are usually shy to ask some strangers to see if they want to share a deal. So they can use this application to ask for them. Internet can hide the users’ identity well.
What are the major challenges (both technical and social) your application has to overcome to succeed?
- Takes some effort to learn social network APIs and integrate them into Android app
- Needs to add some notification features so that the user will get notified when a deal is posted under his categories of interests.
- Hard to deal spam and duplicated deals
- GPS do not work well in-door (inside a shopping mall)
- People don’t have the habit yet to post a deal after he saw it as this is a new way of shopping experience
- Users who said they wanted to share a deal may end up break his promise
- Users may not like to share a deal or handle money transactions with strangers
Ben Dong - 4/15/2013 2:52:01
Our application involves collaboration and social media participation in the different place / different time quadrant of the time-space matrix. Users manage their own profiles and photos, and they can leave notes on their photos. They can also comment on other users' photos and privately message other users. In order for our app to be effective, we need users to leave helpful notes on their photos and give back to the photo-sharing community. Comments and messages further this goal of collaboration by allowing users to interact with each other. Without user interaction, our app isn't nearly as effective, since we need users to share their photos and information. The major social challenge we need to overcome is to ensure that users participate in the community. We need them to upload photos, leave notes, and actively engage with other users. The major technical challenges generally involve making this participation possible. We need to create the system to track user's photo sessions and automatically sync their photos with location information. We also need to support the community and make sure that all of our features are implemented.
Weishu Xu - 4/15/2013 4:24:42
Our application does involve collaboration between users. The primary goal of collaboration is to allow users to share grocery lists in order to consolidate shopping trips, which would fall under the example of a "Focused Partnership." Our project falls into the "Different Time, Different Place" (Asynchronous Distributed Interface) quadrant and is most similar to the example of "version control." Each user is allowed to make edits to a communal shopping list that should reflect each individual's needs. The major challenges that our application needs to overcome in order to succeed include the idea of communication being too loose among participants. For example, an individual may make edits on a grocery list, and another individual may feel the need to disagree due to a different understanding of the need. If someone adds a carton of eggs, but someone else is planning on hosting brunch and requires an extra carton, the first user (who may be the designated shopper of the week) may be confused at why there is a necessary addition of a second box and may dismiss it as an input error. A way to overcome this could include an optional "note" section for each list input that another user can reference in the event of confusion.
Shujing Zhang - 4/15/2013 4:26:21
Yes. Our application involves form of social media participation. The application falls into both Remote Interaction (same time, different place) and Communication + Coordination (different time, different place) quadrant. For our Chat function, our app can be categorize into Remote Interaction – users who agree on the same deal can chat online in a chat room at same time but in different places to agree to meet at some place to close the deal. For our posting the deal function, it falls into Communication + Coordination – users can post his/her deal just like bulletin boards. The goal is to notify the app users about the new deals and ask for who may want to share the deal.
The major challenge is that for chat function, our original intention was to build a simple one to one chat interface. But it is too much of work to do that, so we decided to use a chat room which is available online. Another challenge is that we need to record the comments for users posting the deal. Very few strangers may want to leave their comments, which is why we want to add new features to connect facebook friends to initiate the interaction.
Aarthi Ravi - 4/15/2013 7:37:16
My team is working on a social deal sharing application called Divide By N. Our application is solely dependent on collaboration between users and social media. It primarily falls into the Same time- Different Place quadrant of the time-space matrix. It involves remote interactions such as instant messaging/chat room features. Primary Goals of collaboration or participation include:sharing details about your deal with other App users and your Facebook friends, communicating with participants interested in sharing the deal with you and finally meeting the participants in person to complete the deal. Technical challenges include having multiple ways to communicate in order to not exclude anyone just because they are not a FB member and can't use the fb chat service. Social challenge includes getting participants to share personal information with strangers/sharing deals with strangers.
Ryan Rho - 4/15/2013 8:48:03
Does your application involve any form of collaboration between users or social media participation? Yes. Users can post their deals on Divide-by-N and communicate through messaging system with the participants of selected deals. In addition, the users can share their created or selected deals on Facebook so that their friends can join them for the deals.
Which quadrant of the time-space matrix does the application fall into? Due to the nature of the application, Divide-by-N falls into all the quadrants except for the same place & same time. Here are descriptions why all other quadrants are relevant: same place & different time: When it comes to the location of the deal, all the deals are sorted by the distance from the user. Thus, it is highly likely that users in the same location are highly likely to meet each other by selecting the same deal from a near distance. Once the users select the deal, they chat to share information and meet together. different place & same time: Once users select a deal, they chat each other in order to share information and meet together. Instant messaging is done at the same time. different place & different time: Once feature is that users can post their selected deals on Facebook. Their friends can also select the deal later.
What are the primary goals of collaboration or participation in your app? The primary goal of collaboration in Divide-by-N is to share information among the participants of a deal so that they gain trust each other and share detailed information of the deal such as when to meet up or the specific location to meet.
What are the major challenges (both technical and social) your application has to overcome to succeed? Since it involves a regular person posting a deal that costs money, gaining trust of the dealer and participants is important. In this sense, the business is similar to Airbnb where the host share his or her enough personal information so that the users can safely book a room, but without sharing detailed personal information such as contact number. Likewise, sharing enough personal information of a dealer is crucial.
To overcome this issue, the dealers should either provide enough information on their accounts or sign in with Facebook so that the application automatically grab the information. In addition, to promptly communicate without their actually contact numbers or email addresses, instant messaging is provided in each deal.
Bryan Pine - 4/15/2013 8:54:28
My team is the T-Team, and our app is Berkeley ParkAssist. The only thing we have that approaches collaboration between users is the feature that allows users to submit "bug reports" of incorrect information. This feature is collaborative in that it allows users to work together to make the app more useful by ensuring correct information. If I had to choose, this would fall into the "Same Place, Different Time" quadrant of the time-space matrix because a report submission only affects the place that it was submitted from. Future users would only benefit if they happened to be in the same location (and at a later time, after we have processed the request). In this case, the primary goal of collaboration is to improve the platform itself and help the app provide the best information that it can. It falls into the Wikipedia category where users work together to create something that other contributors and non-contributing users can benefit from. Of course, in our case the information is mostly already there, so the collaborative component is much smaller than with Wikipedia. One major challenge to overcome with this approach is motivating users to make contributions. Because of the nature of the app (no profile, etc.) it is difficult to give users credit for their contributions. We do our best to make the report submission process as quick and easy as possible, but this is a problem we still need to solve.
If we had more time and tools, we could take the social aspect a step further and use and aggregate the automatically provided information about where our users park to direct other users to available spots. This interaction would move towards the "Same Time, Different Place" quadrant, and would have a different goal: to provide a feature that would otherwise be unavailable. However this approach would have its own problems. It would not be very useful without a critical mass of users, and that critical mass would have to be high enough to make it likely that a spot we show as open is actually open and not just parked in by a non-user. It could also raise privacy issues, since we would be storing and using location information.
Tenzin Nyima - 4/15/2013 9:05:58
As of now, our class project does not involve any multi-user aspects. But we believe that ,given more time, we can definitely take advantage of multi-user aspects. The same suggestion came from the class after our prototype presentation. Our app, DateMate, could use email notifications so that when one of the partners create a date, it notifies the other partner. This way, the other partner can make sure whether the date plan also works for him/her or not. With this feature, our app will fall into “Communication + Coordination” quadrant of the Time/Space Matrix. The main goal of collaboration or participation in our app is to make sure the created date plan also works well with the other partner. And also the other user can send his/her feedback and make the date plan even better. As Shneiderman & Plaisant writes, one of the challenges our app has to overcome is that of to recognize the appropriate role of shared control of computing and presentation tools so that participants can be more active, while preserving the leadership role of the meeting organizer.
Scott Stewart - 4/15/2013 10:30:22
My application falls into the remote/asynchronous space of the time-space matrix. Users do not have to be in the same place to use the social features. They will be closely linked in time, as each bill will only be relevant for a couple of weeks, but they are still asynchronous. The primary goal of collaboration within the app is to allow users to learn more about a specific bill by discussing it with other users and by seeing other peoples' opinions. The main challenge is that the user collaboration is a discussion board, and users may not always contribute meaningful or helpful information. Allowing users to flag inappropriate posts may help this problem, but the main challenge is that users must contribute and moderate the discussion board. A secondary goal of the app is to help build a networked community. People using this app will most likely participate in city council meetings, so this app will help these people get more involved and bring more people into this community. The main technical challenge is updating every user with new posts. The asynchronous nature of discussion boards makes this somewhat easier, since the updates do not necessarily have to be immediate, but can happen periodically or when a user refreshes a page.
Raymond Lin - 4/15/2013 10:50:01
The app that I am a part of, MetaApp, does require collaboration between users, as it is integral to the task-centered design cycle. I mean what's the point of a prototype, if there are no users to give feed back? Anyways, the quadrant this kind of interaction falls under would be the "face-to-face interactions," where time is synchronous and the place is co-located. The primary goal of collaboration is user feedback that the prototype'er of an app requires to expand and improve upon their app with. Creating mental model of how are app works and limiting the scope has been the primary challenges we've faced so far. We want to strike the right balance between a low-fi easy/quick to create prototype and nicely designed interactive prototype. In addition, there are plenty of features we could add for luxury, but we need to narrow down the tasks to find exactly what users really want.
Yong Hoon Lee - 4/15/2013 10:53:58
Our application could be enhanced by adding some social features, including collaboration on a canvas by multiple users. They can add ideas to the same canvas, and participate in the brainstorming process together. This would be useful especially for collaborative novels or stories, or just to toss ideas back and forth between a small collective of writers.
This hypothetical application falls in the communication and coordination portion of the matrix, as it involves users interacting remotely in an asynchronous fashion. The primary goals of collaboration in the app are to assist groups of writers in producing shared works or provide a common space for creative minds to brainstorm and organize their ideas. By utilizing collaboration, the hope is that the creative works become more vibrant, or the artists get more inspiration. The major challenge for the feature would be to encourage social use. We have designed our application with spatial memory in mind, and it is unclear how much of that will carry over to a group setting, where different people may have different preferred ways of organizing notes spatially. Furthermore, brainstorming tends to be a personal activity (at least in a creative writing setting), and I am not sure how many users will want to brainstorm in groups. Further testing must be done in order to ascertain its usefulness. Technically, we must implement a storage system for the application, which may involve rewriting the entire application to be more suited for cloud storage. As of now, each user's canvas is only stored locally, so there must be a method devised in order to save and load changes to a canvas from a database.
Cory Chen - 4/15/2013 11:25:18
Our application (Gsale) currently has two main forms of social media participation, and both are "asynchronous distributed interfaces". Garage sale planners and attendees are able to message each other after an attendee follows a sale, so that they are able to talk about any finer details of the garage sale such as the price or availability of certain items. This functionality is a lot like email, and is a 1 on 1 task. The second area of social media participation is in the main functionality of the application, the ability to publicize and search for garage sales. The closest corollary seems to a blog or a message board, since the garage sale planner posts the information up for others to see. The attendees can also "follow" garage sales and save them, which is similar to subscribing or following to a blog. The primary goals of participation in our application are to ease the process of selling and buying garage sale items. Since the application has a clear and focused purpose, the individuals using it should have a strong incentive to use the multi-user aspects. Attendees will want to quickly message holders to find out if they need to make the trip to the garage sale or not, so there should not be many social barriers to the multi-user functionality. On the technical side, our application needs to be able to store their messages and send them to the correct people in a timely manner.
Christina Hang - 4/15/2013 11:35:10
In our application, one of our main goals is to have users share their ideas about the bills and other political decisions in discussion. We would like to use Facebook to connect the users so that people can see what their friends are passionate about and what they had to say in regards to a specific bill topic. Since political issues can often times involve heated debates, we may have to incorporate a system of removing inappropriate posts and keeping genuine responses. As for technical challenges, we will have to find a way to allow users to connect to their Facebook accounts and allow our application to have certain access to their information and possibly post their opinions on their wall.
Sangyoon Park - 4/15/2013 11:37:53
We currently do not have any multi-user aspects, but we had an idea about this earlier. So, for now, this is an idea that could enhance our application by adding this such support. In our application, Produce Almanac, we initially had an idea about a notification service to users. The sender would be an administrator or a manager who manages what produce is in-and-out of current season, and the content may include information about what store has the item. This should be the 4th quadrant of the time-space matrix since it is a notification like email service (it is easy if we think it as a LISTSERV system). The primary goal is to give the right information to users, so the app allows a user to try/buy a certain produce before it is out of season by the notification from the app (manager). Challenges: 1- it could be hard to select what's in-and-out of the season properly. 2 - providing store information that sells a specific produce could be hard too. 3 - if there's too many produces that are in-and-out of the season, users would be annoyed from the notification, and they might end up with turning off the app/notification or ultimately not using the app.
Annie (Eun Sun) Shin - 4/15/2013 11:51:49
My group's mSpray application does not involve collaboration between users or social media participation. The main goal of our application is to log data (such as chemicals sprayed or which houses were (not) sprayed) and send them to the government. Because only researchers and government officials will need and want access to information logged by our application, creating collaboration between users or social media participation will only add unnecessary features and confusion to our app. Our app is also used in South Africa where social media does not play a large role. If we were to add multi-user aspects, then I would add a feature that allows different foremen (users) to communicate with each other. Foremen can alert each other if, for example, one group of sprayers skipped a house because home owners weren't home at the time. By telling each other such information, a different group of sprayers under another foreman can head over to the house at another time in the day when the home owner may be home. If such an enhancement were added to mSpray, then the app would fall into the remote interactions quadrant of the time-space matrix because users would be using the app in different places at the same time. The app could also fall into the communication and coordination quadrant because some foremen may use the app at a different time in the day than other foremen. Collaboration allows users to more effectively cover an area with sprayers and keep each other aware with more information. In order for this enhancement to succeed, a challenge we would have to overcome is the culture of South Africa. While it is common in America to be frequently checking phones, the foremen in South Africa cannot always have access to their phones. Even when they have access to phones during their work shift, they will not be used to having to consistently check alerts and updates while constantly moving around and working. If the foremen in South Africa are used to communication via text through cellphones, they may also feel more comfortable talking to each other through a group text as opposed to a feature on the app. Adding such a feature on the app may also kill battery life. Overall, mSpray does not need collaboration among users or social media participation to work efficiently and effectively.
Kate Gorman - 4/15/2013 11:56:19
Yes, our application is actually centered arounding building a community for photographers. Most tasks fall into the "Continuous task" quadrant--- where users are in the same place or are looking to travel to the same place at different times. Some instances where users look at photos in a location where they are currently not would fall into communication and coordination (slightly) . The primary goals of collaboration are to help others explore and become better photographers through aiding others find photographic locations and share notes about how and where they took specific photos. The challenges here are surfacing the social interactions and encouraging the social loops, where users are able to fully engage and help one another, and avoid a 1:many flow which occurs when users just browse and do not contribute. Technically, the integration with 500px or Flickr might be the most difficult.
Soo Hyoung (Eric) Cheong - 4/15/2013 12:07:29
Our app does not involve any form of collaboration between users or social media participation. However, if we were to add feature that require collaboration between users or social media participation, we would incorporate something that would allow users to add to the list of exercises to make the list more extensive, or have a forum that users could utilize to share their experiences to help each other in having better gym workout experience. The feature would fall under the Communication + coordination quadrant of the Time/Space Quadrant since it would be creating a user-input system for people all over the places collaborating to build a list/forum that everyone else can access and benefit from. The primary goals of the collaboration would be to share information to help other users of the app, or to improve the quality of the app. The main challenges would be making sure that, for the collaborative exercise list feature, the inputted data is reliable and not inappropriate, since it would be difficult to draw lines in terms of who can add to the list or something. Technically, we would need a way for people to synchronously add to the list and making sure everyone can access updated list immediately. For the forum, the challenge would be to incorporate system that would encourage users to utilize the forum, and also to make sure reliable information/comments are posted to improve the quality of the web space.
Sihyun Park - 4/15/2013 12:15:09
My class project, Gfree, does not involve any multi-user aspects, but a possible social feature would greatly enhance the application. A key problem that we are facing is data - how can we get all the data of food, products, and ingredients to present the users with the nutritional information? By crowd-sourcing the data by allowing users to add the information for others to see, we can: 1. have much wider range of data of ingredients, products, and meals 2. have up-to-date information for latest products ex. a new spam product. Another feature that can benefit with social integration is Meal Plan. Users can share their meal plans with other users to: 1. learn from other users' diet 2. be motivated by other users' diet. For our Helpful Tips section, users can post articles that they find interesting and helpful with other users.
Gfree's collaboration belongs to remote time & space quadrant (Communication + Coordination), as users contribute information in different place & time. Through collaboration, users can share helpful information and their daily activities with other users. It also contributes to making Gfree a better application by adding more and better data without the need for constant update from the creator. (A possible collaboratory) A challenge for the social feature in Gfree, as with almost any other user-driven application, is that the value from social features is negligible until there are enough users. This is why most applications that rely 100% on users have trouble scaling in the beginning. Gfree, on the other hand, has social features as a supporting tool, and its main features - food search, barcode scan, and meal plan - runs independently. As a result, it can get users without relying on crowd-sourced data.
Michael Flater - 4/15/2013 12:22:56
Our project does, indeed, fall into a category of social media participation. We use crowd sourcing to constantly add to our application as well as updating information that might have been false or is no longer relevant. Our app falls into the remote, asynchronous quadrant of the time-space matrix. It is remote for obvious reasons and is also asynchronous because users need not participate in any particular order to benefit from the application. Our primary goals are to allow users to form a network throught Berkeley to increase awareness and efficiency in their community's recycling goals. This participation includes updating the database with any new information as well as allowing competition through a social network in order to increase participation and overall recycling level within the city of Berkeley. The major challenge with our form of crowd sourcing is accuracy within the system. While we will try to make the entering of data as easy as possible for our users, it is always a challenge to verify and update information in a timely manor.
Moshe Leon - 4/15/2013 12:24:59
Just as a reminder, our app is a gym application, which allows experienced gym-goers to quickly build training plans, reuse favorite plans, and observe their history. At the moment, our app does not involve any form of collaboration between users or social media participation, however, I came up with a few good ideas which might give it a more social aspect and fun features. The first one is phone tapping to share a favorite or current plan with a friend. After this unique feature will be added, the app would fall into the face-to-face interactions, since users now have to be in the same place, at the same time in order to share their favorite or current plans with other app users. The primary goals of collaboration or participation associated with this new feature are not amongst the extensive list Shneiderman presents in his article, although he does acknowledge that his list is “just a starting point”, and that “there are undoubtedly other collaborative processes and strategies, such as for entertainment, multiperson games, challenging contests, theatrical experiences, or playful social encounters.” The feature clearly falls into the zone of “playful social encounters”, although one can also benefit and learn from other more experienced gym-goers whom are willing to share their plans with him. As Shneiderman explains, “designing for collaboration is a challenge because of the numerous and subtle questions of etiquette, trust, and responsibility.” Fortunately, the collaborative feature would not face such problems, since no harm can be inflicted by this type of information sharing. There could not be any abusive behavior or destructive competitive behavior. Shneiderman also discusses how communities of certain collaborative instruments/apps must deal appropriately with rude behavior, off-topic comments, commercial notices, and enforce proper policies by moderators. This feature does not have any apparent potential of abuse or harm from these kinds of behaviors, unless someone “injects” a virus, Trojan, or any other form of commercial “worm” into your phone when you think you are only tapping phones to exchange/share plans. An extremely hard challenge that we might face is to try and keep the app interesting and appealing to the users, so they don’t abandon us for other, similar apps, and if we don’t keep up with technology, even more sophisticated and richer apps. I do believe that such a feature would create a unique, entertaining experience for our app users and thus the “trust-building and motivational aspects of face-to-face encounters” would be preserved.
Arivnd Ramesh - 4/15/2013 12:25:55
Our app, KungFood, relies heavily on user participation and feedback. In fact, a good portion app is just a way in which users are able to communicate with each other. This communication is accomplished by users reviewing food at a restaurant so other people can see how good the various menu items are. This feature falls into the top-right quadrant of the time-space matrix, because users are at the same location (a given restaurant) when they rate a menu item, but often give their ratings at different times. Our app aggregates all these ratings across time, and displays an average for future users to see. In addition, the restaurant owner/manager is given feedback from his customers in order to improve upon his menu.The primary goal of our app is therefore to allow customers at a restaurant to order the best possible meal and get the most for their money.
The biggest technical challenge we had to overcome while making our app was finding a way to get all the user input and store in a database that was easily accessed.
The biggest social challenge will be to get enough users to use the app to generate reviews for a meaningful number of menu items. We must reach a 'critical mass' of reviews before the app becomes useful to the general public.
Dennis Li - 4/15/2013 12:29:00
For our application, we want to make it possible for multiple people to view shared food. This means that when someone buys or eats group food, the remaining people should be notified immediately. They would then be able to go to the store to replace the missing items, or know that their fridge has been restocked. Because of this functionality, our application falls under the different place same time quadrant of the matrix. The challenges we face with implementing this functionality on the technical side is finding a live syncing database. On the social side, we need to make a convenient way for users to differentiate between shared and non shared items.
Tiffany Jianto - 4/15/2013 12:32:29
Our application, FoodStuffs, does involve collaboration between users and social media participation. Our application falls into the “Communication + coordination” quadrant since it will be a way for people who are at the apartment, who use the fridge space, or who go grocery shopping at different times and places to coordinate what is needed and what is left in the apartment. People can update the space and different times, but everyone who shares the fridge space can see the updates. The primary goals of collaboration and participation are for people to organize their fridge space and easily see, share, and purchase groceries for themselves and roommates with the application; this way, they can easily keep track of food they have, food that is expiring, and food they need to buy, etc. This application serves as a point of coordination for people to keep track of various food spaces and to collaborate with others. The primary challenge of collaboration or participation is that everyone needs to actively participate in order to make this application successful; people need to remember to update the fridge space in the application so that others can see the updates and act accordingly. Thus, everyone needs to be willing to participate and have either a smartphone or tablet device in order to participate.
Edward Shi - 4/15/2013 12:33:39
Our application Gsale involves both collaboration and social media participation. Our application aims to provide a messaging system between our garage sale planners and our garage sale attendees. This messaging system in a way works like a hybrid between text messages and essentially an email. This is collaboration on our users part as they will be sending private messages to inquire about details in the garage sale such as prices, dimensions, or other basic information. Our application also involves social media participation in the sense of posting pictures for their garage sale. This is much like picasa where users are essentially uploading a bunch of photos to a place like an album, but in this case their garage sale and sharing it with people to see. Potential attendees or even other garage sale planners who may want to use this as reference can look at these photos. Also there may be crossover between both collaboration and social media participation as we intend for our planners to be able to contact all followed attendees updates or information. This acts as a list serv. Most of these interactions fall into the Communication + Coordination , different time and different place quadrant. This is because most planners will update or post their garage sale and attendees simply look at garage sales on their own time. Even communication, they are located at different places and generally will be responding to messages at their own times and not immediately. The goal of our collaboration in a sense supports Electronic commerce. It may not allow users to directly purchase online such as from nordstrom.com, but it encourages sharing of prices, viewing of potential merchandise, and asking for more detailed information of merchandise. Hopefully, our app can also be a sort of online community because we want this to be the main hub for all garage sale planners and attendees. Here, people can look at all garage sales, talk about it, look at other examples, and search for sales that are interesting. Technical challenges would be how we would want to code the interface design and what we want to provide in terms of functionality. We would need a server and be able to support privacy and not let users account be breached. Socially, we would be competing with any other platform through which current garage sale participants use such as Craigslist. We want them to eventually all congregate into this application. Furthermore, we always have to watch out for delinquents who want to spam our users, hack accounts, or other ways that destroy our functionality. Ultimately, for our application to succeed, we need users to actively participate and need a large online community. If only a few users use this application, there would be no publicity generated for the sale, garage sale planners would then not use our application, and without garage sales,attendees will also leave the application.
Sumer Joshi - 4/15/2013 12:34:20
Our application falls into the different time same space category because it is a continuous task among user to figure out what fruit or vegetable they might want, as well as picking up more than just one item in the grocery market. The primary goal of the application is to inform the user what fruit/vegetable is in season. The major challenges that we need to overcome is figuring out a good way to display search and filtering as well as calendars.
To add multi-user support, maybe we could have recent locations of which friends have visited the supermarket and gotten a fruit or vegetable that's in season and you may want that one as well. It's interesting because in the Bay Area, there are only a few supermarkets that sell organic produce.
Claire Tuna - 4/15/2013 12:40:04
Our application, the Produce Almanac, does not involve any form of collaboration between users/social media. One of our biggest issues is that we aren’t sure where our data (about which fruits/vegetables are in season when) is coming from : our current solution is to draw from a static source such as the Bay Area Food Wheel or the CUESA (http://cuesa.org/page/seasonality-chart-vegetables), even though this information is nuanced and changes every year. Perhaps a better solution would be to crowdsource contributions from registered farmers. Farmers, who could be verified by someone on our end before registering, could information about what they have to offer that week. That information could be analyzed to find out what is in season. The more farmers have item X, the more “in season” that item would be. This would also give our application a notion of continuous seasonality, rather than binary “in/out”. So if it was the first week we had seen farmers having item X, we could say “beginning of season”. We could graph the number of farmers reporting that they had item X, and one would expect to see a parabola over time. The peak of this parabola would be the “heart of the season”, and once it reached the point at which it starts decreasing after the maximum, it would indicate that item X was “on its way out”.
This collaborative model would serve to provide more accurate, detailed and dynamic data. If the farmers were already contributing, they could also state where they sell their produce, so for each fruit, you could have a list of possible locations. The farmer model is a “Communication + coordination” interaction, because it is asynchronous and the farmers are not collocated with each other or with the customers. One major challenge would be motivating the farmer to contribute data. Though the farmer would likely be in favor of the application’s mission statement, farmers are notoriously busy and may not be used to or fond of using mobile technology such as this application.
Another step we could take, if farmers were listing their fruits/vegetables and vending locations, would be to have all users able to rate/write reviews of that fruit/vegetable from that farmer at that location. This is sort of stepping into Yelp/wiki territory and would also fall into the category of “Communication + coordination”. This would be helpful because it could help guide users toward a concrete place to find this fruit/vegetable, which is more practical than just knowing its characteristics. (What good is the info if you can’t find the fruit?). An obvious challenge is reliability of data--how to keep one competing farmer from flaming another’s produce, etc. However, democratic systems like Yelp and Wikipedia have proven that this model works if enough people contribute data.
Christine Loh - 4/15/2013 12:49:15
My class project is the Booze Hounds project. It involves very light collaboration between users in that it adds certain contacts that you choose in your friends to be notified when you pass a certain BAC level. It falls into the Communication & Coordination quadrant of the time-space matrix because users will not necessarily be located in the same place or be notified at the same time as the other. The primary goal of collaboration in the application is to notify others when the user is at a dangerous BAC level, and the application has to overcome social challenges of friends not enjoying constant texts if someone is constantly going over their BAC.
Though I already wrote about the collaboration between users in the current app, we could enhance our application by having a messaging system built into the app, or a way to add/accept friends to see their statistics as well, so other friends can track how you are doing each day to limit your alcohol levels.
Joyce Liu - 4/15/2013 12:59:24
Our application is Splist, the bulk-buying sharing app. In terms of the Time/Space Groupware Matrix, Splist fits in the quadrant of Different Time (asynchronous) and Different Place (remote). It is an app that facilitates communication and coordination. The primary goals of collaboration and participation in our app is to share bulk items so that people can get things that they want but in a smaller quantity than what one normally gets when buying in bulk and still save money, since buying in bulk usually means that the unit price is lower. The major social challenges our application has to overcome to succeed include we need people to have a good number of friends who also use the app, as otherwise it would simply be a normal shopping list. We need people AND their friends to adopt our app. We also need people to be comfortable with sharing the stuff that they buy with others. There needs to be a level of trust involved as well as people being responsible and paying their friends. The major technical challenges is figuring out when an item cannot be split anymore. For example, if I were to get a pack of toilet paper, but if 10 of my friends also want it, I probably can't split it with all of them—I could probably only split it with 2 or 3 of them. Another challenge is whether or not we want to bring back selective share—originally we had it in our design because if people want a particular item but won't get it unless someone splits it with them, it doesn't really matter whom that "someone" is. However, it also seems like people sometimes just want to share with their roommates, so in that case having a selective share option would be beneficial.
Brett Johnson - 4/15/2013 13:00:20
Yes, our application involves collaboration between users, falling in the different place(remote)/different time (asynchronous) category of the time/space matrix. Users are choosing different food dishes to eat in response to the reviews and tags that other users are posting. While in our app's current iteration, users are not directly interacting with one another, the information that they are entering into the app directly affects what other users see. The entire point of getting users to communicate with the application is to provide information that others can use to make decisions.
I think that one of the main challenges of this application will be the varying levels of food allergies that people have. Some people with very serious allergies may try to avoid the app in order to continue with their usual process of just asking waiters, which is safe and familiar to them. On the other end of the spectrum, people with minor allergies may not want to take the time to use an app when the consequences are not very severe. So, I think that something we need to think about is to make sure that we are letting people know that this app serves as a guideline, not a definitive index of allergy free foods. And for people with minor allergies, we may want to market to them as being more about finding tasty food that also guides them toward dishes that will likely be safe for their allergy.
Glenn Sugden - 4/15/2013 13:07:10
Our project intentionally minimizes the amount of different time / sometimes-same, sometimes-different location interactions between users by greatly simplifying recommendation systems that already exist. Our group agrees that those existing rating systems, such as Yelp, are filled with overly effusive or hyperbolic rants and raves for both good and bad ratings. The general public seems to either post 5-star ratings for places that they have had a fabulous experience with, or 1-star ratings for a place that didn't treat them as the special snowflake that they believe to be. The amount of "rating site" burnout that we've found to be is high, so we are actually trying to streamline (or do away with) the socially interactive aspects of our application's functionality.
Our application tries to solve these problems by: minimizing the time delay from experience to rating, making the rating system quick and painless, and minimizing the amount of data collected and presented to other users. We are crowdsourcing the data (ratings), but only make a limited number of data points available - and certainly not making available a way to leave comments that tend to be more abusive than helpful.
While our application might appear to be isolationist and self-serving at first glace, we are carefully balancing the information gathered with the (rating) information presented. We require very little of the user, while aggregating and presenting crowdsourced, useful information from the "social" database.
The toughest challenge is designing a clean, helpful interface - useful to the general public - that is collaborative without actually appearing (requiring) to be collaborative. We want our experience to be personalized, based on social ratings, without subjecting the user to the cesspool known as the greater internet. We have purposefully chosen test-users to be those that are sick of generic rating sights on the web, but still desire to have an informed choice when deciding what to eat from the restaurants around them.
Eric Xiao - 4/15/2013 13:13:55
Our application is very focused on social media participation, inviting lots of discussion from our users about different political issues in their local area, falling under the asynchronous and remote time/space quadrant. The primary goals for participation are to see the general trend as to what people think are important locally as well as to see individual sentiment about different issues in local politics. Major challenges will be to bring users to the platform and encourage them to be a contributor, as most users are consumers of content, not participants or creators of content.
Technical challenges will be to design the application to encourage this participation as well as adding value to the platform without any user interactions at all. If the mobile application builds a community and it's defined as the place to be to find out more about local politics, the social challenges can be overcome and the network effects will take place.
Tiffany Lee - 4/15/2013 13:15:43
Our app Transportion does involve a form of social media participation by allowing users to share/compare their travel statistics with their friends. This kind of participation is in the lower right quadrant (Coomunication + coordination) because the users are asynchronously comparing/sharing their data and the users do not have to be in the same space to do so.
The primary goals of social participation is to use it as a means of motivating to change their travel habits and educating users on how to do so. It allows for the arising of competition between friends on how much less carbon they can emit compared to their friends. Or if the user has friends that have great travel habits, users can learn how to copy them by seeing which modes of transportation they use to get to places.
One major challenge is the fact that some people do not care enough about their travel habits to want to change them. Therefore, our primary goal in using this social feature in our app to spur change would be defunct. Another major challenge is security. We are using the Facebook API for our login and friend features of our app; we have to make sure that private Facebook information can't be easily obtained though hacking - this is a requirement by Facebook if we are to use their API. Another challenge we have is in deciding what information will be compared amongst friends and how to present such data so that it is easy to understand and useful to the users.
Lishan Zhang - 4/15/2013 13:19:43
Our class project is an application to share deals with people nearby or friends. It involved collaboration between users and social media participation because users need to interact with others to share the deals and they can also login in with Facebook account to see what their friends want to share.
Our application falls into different place and different time in four-quadrant of the time-space matrix. The app allows users to post the deal first and finds the others to share later. And people can also use it in different places as long as they have the app installed in their mobile device.
The primary goals of collaboration in my app is to post a deal and find people to share the deal with you or directly search for deals around you. It requires users to collaborate with each other to accomplish.
The first challenge we need to overcome is to make people get used to split the deal rather than buying too much. There are not similar applications in the market so people should take time to find out the benefits. Besides, there will be some credibility problem because people may agree to share the deal but won’t come eventually. The technical challenge is to build a chat system that allows users to communicate directly through the app.
kayvan najafzadeh - 4/15/2013 13:21:58
On our project we use both Face-to-Face interaction and communication + coordination quadrants of the time-space matrix. we were all connected through Google Dive share folder and files as well as GitHub for file sharing and version control. We also got together for many hours to work face-to-face because first of all its faster and secondly we pushed each other to work.
Nadine Salter - 4/15/2013 13:31:09
My group's project ("Betternote", the spatial idea organiser) involves neither collaboration nor social media participation.
Multi-user functionality could be added to Betternote, though it would have to be tasteful and unobtrusive for it to be considered an enhancement. All too many developers go the route of littering their products with "social" functionality simply because such integration is currently in vogue; in the case of a private notebook used for personal creativity, sharing can be anathema. This is not to rule out the possibility of sharing — some are intensely private in their creativity and have no desire to share anything less than a completely finished product, if even that, but many people can be motivated to complete a project by the knowledge that their progress is being watched by others. This does, however, mean that any such additions should be carefully thought-out.
A reasonable first step, providing an essential feature without drowning the app in social nonsense, is an export function: exporting the contents of the entire canvas, possibly as a zoomable PDF or a linearised word processor document, can be used by an individual to access their own ideas on a different device, but can also be used to send ideas to others. This falls in the "different time"/"different place" quadrant of the time-space matrix, and could even be implemented via email (one of the examples listed under that quadrant).
Andrew Gealy - 4/15/2013 13:42:14
Our application does not currently involve any collaboration or social media participation.
If we want to use a proprietary recipe database to our gluten-free app, adding user reviews and user contributions could be useful. On the diet tracking side of things, social participation could take the form of comparisons between friends/users, adding an element of competition to their weight loss. Finally, the app could benefit from user contributions in the form of creative gluten-free alternatives that could eventually be built into the search function.
The application falls into the "Communication and Coordination" quadrant of the time/space matrix. Goals of participation are to create an associated community and contribute to the quality of the app experience by bettering the recipe or substutitions functions (through contributions and reviews) and adding an element of competition and ability to express pride in the weight loss function.
Using a proprietary database that would take reviews and contributions is going to be inherently more complicated and would take time to build, making the initial release somewhat trickier. Using a premade database probably makes more sense, and social features could still be build on top of it. The scale of participation would also have to reach a certain level for it to be useful. A system where reviews are sparse is probably more annoying than one without reviews at all.
Avneesh Kohli - 4/15/2013 13:58:12
Our group's class project revolves around being able to track and discover new televisions shows. While in its current iteration it does not have support for social features, there are certainly social elements to the app that we are planning. In particular, we want to be able to allow users to recommend shows to their friends, see what they're friends are watching, and get automatic recommendations based on ratings for shows submitted by the entire user base for the app. Because users don't need to be in the same place to take advantage of these social features, and because their use of social features can occur asynchronously, I'd classify our application as falling under the communication+coordination quadrant of the matrix. Certainly, the app also reflects some of the properties of a large public display, which would fall under the continuous task quadrant. The primary goals of incorporating collaboration and participation features into our app is to help create a community of television watchers. A community would have the key component of giving feedback and suggestions. The major challenges for implementing this would likely be interfacing with the Facebook/Twitter API's so that people could incorporate their existing social network into our application without having to re-build it. Additionally, building a recommendation engine that would take friend's ratings as input and output shows that a user is most likely to enjoy will not be a trivial task. This is low on our priority list as far as implementation, but certainly something we designed from a user-perspective.
Matthew Chang - 4/15/2013 14:01:46
Our class project has a small amount of social media participation in its planned ability to view/make ratings for a given show as well as sharing of a given show to a friend. Both of these forms are asynchronous in nature, with things occurring at different times and places. This places it within the Communication and Coordination quadrant that is figure 9.1 of the reading.
For the rating system, we plan on leveraging the ratings API present for Trakt.tv. The advantage we have here is the ability to pull information from an enthusiast userbase. This abstracts away the problems associated with verifying accounts and ratings. The problem with this is the need for each user to have an account with Trakt.tv, which increases the barrier to entry for our app.
For sharing a show with a friend, we plan to add Facebook integration, allowing us to easily provide a means for users to share with their friends as well as better guarantee that their friends see the sharing link. From a social perspective, Facebook has already cornered most of the social networking market and tapping into this will allow us a more broad reach.
Oulun Zhao - 4/15/2013 14:01:49
Yes, our application involves collaboration between users and social media participation is actually vital to your application.
In my opinion, our application actually falls into both the Remote Interactions (Different Place, Same Time) and the Communication + Coordination (Different Place Different Time). Because the recommendation feature (share show to a friend) is different place but same time (user receive push notification from friends) and the view feedbacks and comments part is different place and different time.
The major challenges socially, is that we need to get a good amount of users to start using our application so that we can have enough user generated contents that attract more users. Therefore the threshold could be one of our major challenges.
Kimberly White - 4/15/2013 14:06:49
Our app, TryDish, lets users rate/review foods, and search for good food safe for their allergies. This collaboration would fall into the category of asynchronous distributed interfaces (different time, different place). The model of interaction between users is similar to the interactions they may have on something like a wiki, where users upload content/information for others to find and use later. The entire function of the app is based around crowd-sourced food data and reviews.
The biggest challenge for our app is a social one, getting enough people (with allergies, for the current scope of the project) to use the app. We need to find some incentive for users to rate dishes, as without data being entered the app would be useless. Another challenge of our app is the possibility of malicious users, who may input false information about food allergies. In terms of technical challenges, the only problem related to users/collaboration is going to be setting up a database and correctly managing data.
Alvin Yuan - 4/15/2013 14:09:03
My group's app is the garage sale app. It does involve considerable collaboration between users. In fact, we've defined our target users into two groups, planners and attendees, that must in some sense collaborate in order for either group to gain benefit from using our app. Although the end goal is for the planner and attendee to conduct business at the garage sale (same place, same time, face-to-face), our app actually is focused on the communication and coordination aspect of holding garage sales (different place, different time). The primary goals of collaboration include allowing the planner to disperse garage sale information to interested attendees and allowing attendees to contact the planner to gain further information (ex: ask for dimensions of a furniture) or to make a request (ex: hold an item). Major technical challenges include making sure the structure of planning sales and searching for sales fits both of the user group's expectations and ensuring communication happens within time before the sale. Social concerns include privacy/anonymity (particularly the planner may not want to make some personal information publicly visible) and honesty/integrity (planners use the app as intended and only create listings for actual garage sales and attendees do not try to game the system by asking the planner to hold too many items that the attendee is not committed to buying).
David Seeto - 4/15/2013 14:14:54
Purple Platypus' Transportion application falls into the Different Place, Different Time quadrant of the time-space matrix. Users will log in and compare with friends (who might not necessarily close geographically) their various transportation habits to better understand their own habits and have a point of reference when trying to add meaning to the data points.
In this sense, we aim to create a community of interest, connecting environmentally conscious commuters who can spur each other to make more environmentally friendly choices. Knowing and comparing between friends is the first step; it is the catalyst that will facilitate more discussion and "one-upping" each other in the real-world setting.
One challenge we must overcome is designing a meaningful way to present the data when comparing between users. If users find it difficult to use this feature, our application will lose all the social media leverage this feature affords us. Another challenge is to get friends who do not have the application involve. Getting not only users who are already environmentally conscious, but also users who might be willing but never having the motivation or outlet to start will actually create a big impact on our environmental problem.
André Crabb - 4/15/2013 14:15:12
Our project does not involve multi-user aspects at this time. Since our app is an app-prototyping app, multi-user aspects could be added for a developer to share his project with a team of others.
If this were to be implemented: - I think our app would fall under the "Remote Interactions" quadrant. However,
I could also imagine it in others, depending on how users decide to work with our app. For example, a developer could create a prototye alone then send it to someone. Or, a developer may want to collaborate real time with someone else while designing his app. Another possiblitily is for a dev to share just a testing version of his app, for others to play with, but not edit.
- The primary goals, as I envision it, would be similar to the 'Structured Work
Processes' collaborative interface described in the reading, though maybe not so structured. I would imagine a developer might want to collaborate with someone else real time while designing an app. This would essentially mean 'screen sharing', or real-time updating of project files across multiple devices. Or, a developer may want to periodically send new versions of the project to a friend for feedback.
- Major challenges for multi-user MetaApp to succeed would be of ownership,
trust, and same-time collaberation. As creators, we would have to make sure than any shared project remains editable only by the original developer, unless otherwise specified. If real-time collaberation was implemented, it would be up to us to properly handle multiple concurrent edits to a file. A more social challenge would be trust, where the developer would have to trust the perseon he's sharing with that his idea won't be stolen.
Brian Wong - 4/15/2013 14:20:22
Our app, Photo Focus, falls in the 'Same Place'-'Different Time' quadrant. This is because our application curates photo data (pictures, weather, etc.) over time and displays this visually in a map view (same place). The main collaboration goal of our app is definitely 'Online Communities', as described by the reading. The subdivision would be 'Communities of Interest' where we are allowing amateur photographers from localized areas, known as networked communities, to add to the pool of photographs, as well as discuss about any of the photos. Technically, the most difficult aspect will be seamlessly integrating the API's of many photo sharing websites such as 500px and Flickr. Socially, the most difficult aspect will be getting users to further add data (by logging photo excursions), since this currently requires a little extra effort than just checking the app for the community's current contributions.
Minhaj khan - 4/15/2013 14:20:42
Our app has a minor social media function in which only a few users are involved as a 'friends' in the app who would be notified when the user is goin over his drinking limit. The primary goal of this function is to add support to the primary user throug auxiliary users who don't use the app but act as references used by the app for text message notifications.
The main social challenge for the app would be for the user to find friends who's be willing to collaborate with him to receive notifications and help the user in decreasing his drinking. The main technical challenge the app needs to overcome is to figure out how to communicate with the friends of the user. Doing it through automatic text messages is the primary option but implementing this may be a challenge, as we have yet to see if android sdk allows auto text messages to a few contacts.
Juntao Mao - 4/15/2013 14:23:05
Our app relies heavily on collaboration between users, since in our app, the main function to to get reviews for the developers' apps, which is a communicative process between the developers and the users. While our goal is to reach a large population, the number of people involved in one review process is very limited, and it definitely is "typically goal-directed and has a time frame for completion... purposeful and often business related". Our app's collaboration interface would be one of "Structured work processes" where the interaction process has a set flow and steps, and also one of "Online Communities" in the sense that it is like-minded people interested in Android app development or testing coming together to discuss. Our app would fall into "Communication + coordination" quadrant of the time-space matrix. The primary goals of collaboration in our app is for developers to find users who they did not know before, who may be from a far distance away, and may or may not have significant testing experience (based on developers choice). Some major challenges our app has to overcome to succeed includes: general acceptance by the developers as a good platform for testing, finding enough tests of varied backgrounds, ensuring that the communication are worth while for beta testing.
Eric Leung - 4/15/2013 14:24:24
Our application, TryDish (still deciding on stylizing) definitely has strong forms of collaboration in order to get quality ratings with correct allergy information. While definitely it falls inside the different-time column, it arguably spans across both remote and co-located rows. The primary goals of the app is to be able to review and rate dishes and tag those dishes as allergen-safe. In order to do that, it is essential that users are able to collaborate with each other to make sure that reviews are accurate. A major challenge we will have to overcome is to incentivize users to spend time to rate and review a dish, and technical problems include storing these reviews and scaling data as more reviews come in (not a problem in the scope of this class). Thoughts on our incentive program include imaginary "internet points", or additional perks when a user has reviewed enough dishes.
Derek Lau - 4/15/2013 14:29:42
My group's application involves a little bit of collaboration between users in the form of crowdsourced reporting of app/real-life information discrepancies. The application falls into the Continuous Task time-space matrix, because users are reporting inaccuracies in information about a certain place, where users can later retrieve updated and correct information about the same place, when they visit the site.
Collaboration is used in the app as a form of information retrieval/updating. Crowdsourcing is the route that our team chose to keep information up-to-date because it allows for the farthest reach along with minimal work on the developers' end. Participation in the multi-user features of the app can be incentivized through prizes and achievements, such as badges and recognition. This leads into one of the major challenges needed to be overcome for the app to succeed, which is accurate data collection. If the parking data is not correct, the app becomes completely useless. Part of this hinges on how well users can crowdsource mistakes and errors and also how we as the developers can input data accurately and efficiently to cover a large area.
Tananun Songdechakraiwut - 4/15/2013 14:29:43
Communication + coordination quadrant of the time-space matrix in which our application falls in
Our app focuses on street parking in Berkeley. In particular, it allows users to verify if their spots are legally parked or not, locate legal parking area, and also do GPS routing.
Our application has a feature which lets users report errors of our database. If, somehow, it reports an incorrect information about relevant legality, fee, and law, a user will be able to report that error to administrator/server for its correction. The feature includes attaching evidence such as photo, and description of the error.
Note that the users are not directly collaborating among themselves, but indirectly through the server via e-mail. Essentially, the server will distribute the information to the entire users in the sense that, using an app next time, the users can be sure that the app will retrieve the correct data and the users benefit from it as a whole. This is a form of collaboration among users and improving the application concurrently.
Major challenges There is none in the case of technical since, if we, are serious about real complete app(ready to sell!), can simply set up our server to receive reports, and take good care of them. However, in the case of the social challenge, we need users' collaboration. If there are no users, then this feature won't work. So we need to make sure there are enough users, or we can start from hiring someone to do so.
In the future, we will possibly implement a feature integrating the app and social media such as Facebook. In particular, users will be able to share their experiences about parked spots, surrounding environment, and review/recommending of the parking area... etc
Jin Ryu - 4/15/2013 14:29:55
Our application is GitFit, which is a personal training application that helps a person formulate a workout plan for themselves and also track their physical exercise statistics. It currently does not involve any multi-user aspects but it can be enhanced by adding a few multiple user components such as allowing the user to share their favorite workout plans with others - which allows them to connect with others and get a variety of different plans created by friends - or even sharing and comparing their workout stats with other app users as well. This can allow the user to gage their level of physical activity and how they are doing with a community.
The quadrant of the time-space matrix is different place and different time for the workout plan sharing aspect. When a user gets a friend's favorite work out plan, they do not have to be in the same place or at the same time when their friend is using the same plan. They can try their friend's shared workout plan whenever they want at their own preferred gym or even at home.
Primary goals of collaboration in a shared plan implementation can be:
- Focused partnerships: Perhaps the user is working with a trainer and the trainer would like to share how they work out or see if the plan is right for their client. Allowing sharing of plans would ease this process and make communication of a schedule a trainer might have made for the client to do much easier.
- Collaboratories: each person who made their workout plan are sharing their ideas about which workout is the best for what muscle and etcetera. Ideas are being communicated and resourced, and GitFit users may even work together to formulate a good plan for themselves or their friends by sharing their workout strategies as well as getting their friend's formula and being able to modify those plans to fit their needs better.
- We would have to figure out the implementation and in which method the user will share their plans. The ease of sharing is also important. One implementation could be to have the users who are interacting (sharing plans) be in the same place and same time in order to share and link their phones, but there may be some situations when the users do not have the time to meet (but would like to share) or are currently in different cities or places. Our app may have to use an online database system to share and host plans so users can send and retrieve even if they are at different places and time.
Alysha Jivani - 4/15/2013 14:30:25
Currently, our project does not really involve any aspects of collaboration. We do have a user-testing mode, which engages 2 different types of users (the developer and the developer’s target user who is currently testing the prototype), but I wouldn’t think of it as really a form of collaboration or social media participation since the prototype is only accessible on one mobile device and there is only one person either prototyping or testing it at a time.
I think two ways in which we could incorporate more of a collaboration aspect to our app (which we discussed early on in our assignment) are: (1) allowing developers to collaborate on a single app project together (some sort of hybrid between myBalsamiq and Google Docs would be ideal, and it would also have a brainstorm/comments section); (2) allowing for the prototype-testing-mode to be sent to/deployed on multiple devices and creating a user feedback/data collection portion of the testing process, so that testers/users can actively participate in the iteration cycle.
I think the primary goals of collaboration and participation for these options would be something like a “focused partnership” (for developers working together) or a “structured work process” (the developer designs an app, users test it and provide feedback, the developer uses the feedback for the next iteration, etc.). For option 1, I think the new and improved app could occupy all 4 quadrants of the time-space matrix. Collaborating developers could work on the app while in the same room or in different locations, and (ideally) they could collaborate in real-time, or make updates and leave comments for their team to look at afterwards. (Thus, any of the four combinations of synchronous/asynchronous and on-location/remote seem viable for the app.) As for option 2, with the user-testing mode, I would say that the collaboration is mainly between all the testers (probably not within the testers, though) and the developers. That means that it could occupy the on-location and asynchronous (ideally – so that we could observe their comments/reactions/difficulties) or remote and asynchronous (if we had a way of collecting other data to help us uncover confusions or mistakes; this would also help provide more external validity) quadrants. It would have to be asynchronous between a developer and a user since the developer has to design the app, wait for the user to test it, and then make appropriate changes after collecting data and observations.
I think the main challenges for option 1 (real-time collaboration with co-developers) would be difficult because we’d have to figure out a clean, version-control system and how to not overwrite changes. I don’t think creating a brainstorming or chat aspect would be that difficult (though it’s not exactly feasible in a semester to integrate that into our current application) but I think the hardest part would be figuring out how to support real-time editing of screens (especially since we’re currently storing them as Screen objects which are saved in a hashmap within the current project file). The main challenges with option 2 would involve figuring out how to send the file to other devices and how we’d save the file-type. Also, we’d have to add in functionality for collecting user feedback and data (such as whether they pressed, when, how often, etc.) and figure out how to group, evaluate, display, and send it back to the developer team easily.
Lemuel Daniel Wu - 4/15/2013 14:32:33
Our class project does not seem to have any real user communication, because the users mostly are not literate enough to use the application to interact with others. And though there may be multiple users at the same time, they do not share the same physical space, and their work will not conflict with each other (the Google Doc servers will take care of any concurrency issues). As a result, each user can act like he is the only person using the application, and that others cannot affect the result of his use of the application.
That said, there is some user participation in shared media. It isn't shared media, but it is a shared repository of data that they all push data into.
Could we enhance our application, then, by adding in support for user communication? Not really, actually. The point of the project is to enhance the recording of individuals' work in spraying medicine, and the users' work itself had no communication between foremen. As a result, adding user communication might not be helpful to the foremen. And because foremen also are very unused to social media (and aren't used to a lot of the social media cues and paradigms that we use in applications), adding such functionality would not enhance the user experience.
Achal - 4/15/2013 14:59:50
Currently, our application (MetaApp) doesn't really have much collaboration between users. However, there is a lot of room to involve some collaboration and interaction between users.
In terms of the quadrants, our application should ideally involve remote users working asynchronously (communication + coordination) to prototype an app. The primary goals are to sketch out a simple design for the UX/UI of an app, and particularly, the goal of collaboration is to bring together various ideas that a team may have. Technologically, it's hard to figure out merging changes, versioning, and figuring out how to show what someone has changed recently. Socially, there isn't too huge a challenge since most users would have worked together before (as they are likely in a team); the main challenge would be if a team wanted to publish their prototype to testers in their social network, which may require some friction in getting people to use it.
Soyeon Kim (Summer) - 4/16/2013 1:06:50
Which quadrant of the time-space matrix does the application fall into? Our team’s application, Kung-Food which allows users to fill out the ratings of particular dish of the nearby restaurants. It belongs to the asynchronous and remote in the time/space four-quadrant matrix model.
What are the primary goals of collaboration or participation in your app? To bring cumulative effort of dish ratings so that users can benefit from these information.
What are the major challenges (both technical and social) your application has to overcome to succeed? Since our app heavily relies on the ratings from the users, we need to make sure there exist quantity of ratings contributed into the application. To encourage ratings, we give out coupons for nearby restaurants according to the frequency of contribution.
Jian-Yang Liu - 4/17/2013 12:55:00
Does your application involve any form of collaboration between users or social media participation? If so, describe it briefly in light of the following questions: Which quadrant of the time-space matrix does the application fall into? What are the primary goals of collaboration or participation in your app? What are the major challenges (both technical and social) your application has to overcome to succeed?
Our application does involve collaboration between users and even social media participation, at its final form. It mostly involves remote interactions, whether in the form of bug reporting or in mapping the area. Since our application is based on parking in Berkeley, there may be a lot of problems that come from either inadequate information (not completely mapping out areas where there's free parking, or metered spots, and so on) or wrong information. As such, our goals of collaboration/participation in our app involves the user checking whether the information in our app is correct or not, and if it isn't, send us a bug report. Also, there could be cases where there isn't any information in an area because we haven't mapped it yet. In that case, the user can also communicate with us as to the layout of the area with respect for parking, so that we can put the information into the device. The major challenges we must surpass include wrong information from the user, or that the user does not have any incentive to support our app through active testing and bug reporting.