Collaboration and Social Software

From CS160 Spring 2014
Jump to: navigation, search


Reading Respones

Myra Haqqi - 4/12/2014 22:15:10

No, my class project application does not involve any form of collaboration between users or social media participation. There are no multi-user aspects in my application because the purpose of my application is to allow a user to take a survey hands-free via voice. In our application, a pre-recorded survey is spoken out loud to the user, and the user speaks back his answers. Our application uses voice recognition to interpret the user’s answers and collect the necessary information for the survey results. This allows the user to complete surveys hands-free, leaving their hands free to perform boring household chores. Therefore, users can be productive and gain the opportunity to earn rewards for their survey answers.

In order to enhance my application by adding such support, I would allow users to interact with one another by having the option to post comments about surveys. They will be able to rank surveys they have taken based on how much they liked the survey or the reward earned from that survey. I do not want the users to be able to post specific comments about the surveys so that the survey results are accurate, and not influenced by others’ opinions; however, with a simple 5-star rating system, users will be able to determine which surveys are worth taking and which ones have not been popular.

The quadrant of the time-space matrix that the application falls into is different time, same place. This is asynchronous and remote. This is because it is similar to a large public display. All users will be able to see how other users ranked surveys. Although each user may select a rating for a survey taken at a different time, and they may all view these rankings at different times, they will all access the same place in order to receive this information. There will be a page of surveys with their respective rankings, and all users can view this same page, implying the same place.

The four quadrants of the time-space matrix are same time, same place; same time, different place; different time, same place; and different time, different place. Examples of same time, same place are when users have face-to-face interactions, e.g. in shared “rooms” of interaction. Examples of same time, different place are remote interactions, e.g. when users have video-chats or instant messaging chat conversations. Examples of different time, same place are continuous tasks, such as when there is one place where users can access data at different times or project management software. Examples of different time, different place are when communicating at different times and in different spaces, such as when users send each other emails, use wikis, or employ version control softwares.

The primary goals of collaboration or participation in my app are to allow users to give feedback on surveys they have taken. They can rate a survey based on how much they enjoyed taking it, or how useful and valuable they found it. This provides information for other users who are deciding whether or not to take a certain survey. By allowing collaboration of users who collectively rank surveys based on their opinions of the surveys taken, they will help other users by giving them information about how good some survey is.

Furthermore, this encourages participation of users because users will rank surveys and their feedback will help other users. In summary, the goal of allowing users to rank surveys and allowing all users to view these rankings is to give users more information about specific surveys. The aspects of collaboration and participation that come into play are when multiple users rank surveys collectively, giving all of the users multiple points of feedback. Furthermore, users who rank surveys highly will encourage the participation of other users to take that survey. This fosters productivity by allowing users to make better use of their time by choosing surveys that have been recommended. This is especially useful because the characteristics of our target user groups include people who seek to make valuable use of their time.

In general, there are many goals of incorporating collaboration and participation. Namely, collaboration fosters satisfaction and productivity. There are several different ways in which people can interact with one another, including, but not limited to, focused partnerships, lecture or demo formats, conferences, and online communities.

The major challenges (both technical and social) my application has to overcome to succeed are to incorporate the back-end implementation of allowing users to dynamically update their ranking of some survey taken. Technically, this implies that we would have to program some way to constantly let users rank a survey, and to continuously reflect updated rankings whenever a user rates a survey. Socially, it will be difficult for my app to ensure that rankings are accurate.

Examples of adversities that applications have to circumvent are issues of anxiety, deceit, the desire for power, and any detrimental harm. Designers must consider the effects of trust and responsibility, because allowing users to interact with one another requires some amount of proper etiquette in order to avoid malicious behaviors. In particular, for online communities in which a large group of people interact, some challenges that arise are to ensure that all users have free will to do as they desire, but also minimize any harm that users may cause among themselves. Technical challenges that arise include storing large amounts of data and processing information, while also transferring data, but also maintaining a sense of trust among the users. Furthermore, in scenarios in which there are many people gathered in a meeting with a single person as the meeting organizer, a challenge arises in allowing people to share the control of the presentation while still maintaining the distinctive role of the meeting authority figure.

Andrew Fang - 4/12/2014 21:09:11

Our class project does not currently involve multi-user aspects. However, one feature we could add would be to connect our users (bikers) to other users (bikers) around the area. I imagine that this would look like some sort of push-to-talk feature where all the bikers who are currently logged in to our app would be able to talk to each other while they are biking. It would be built completely hands free, and would be meant to improve the biking experience. This would fall into the Remote Interactions time-space matrix, because users would be able to communicate with others who are using the app at the same time, but they could all be at different physical locations.

The primary goals for this collaborative feature of our app would be to connect bikers to each other and allow them to engage in friendly banter. Perhaps one user wants to look for a group of people to bike with. He or she could log in to the app and send out a broadcast to everyone else, to see if anyone is around the area and would also be interested in starting a biking adventure. Then, our app would allow these bikers to meet up and enjoy a fun bike ride together.

A major technical challenge would be to set up this push-to-talk walkie-talkie system. First, we would have to find a good way for people to indicate to the app that they want to start talking, without using their hands. Then we would have to have a server through which people could connect and converse. One social challenge might be that at certain points of the day, not everyone would be using the app. and at other times, too many people could all be crowding the line. The user would have to open up the app and listen in to see how many others are currently logged into our app.

Michelle Nguyen - 4/13/2014 0:21:50

Our class project, SpeechTutor, is an application created for users to practice their speeches. As they record their speeches, the application will count the number of filler words ("um"s, "uh"s, etc.) in their speech. The user can also view their "filler word" statistics and see their improvement over time. However, besides simply allowing users to share their recorded audio to others using a share intent, there is no multi-user aspect. From our interviews with users from our contextual inquiry, we learned that a crucial aspect of a speech (besides sounding good and having few filler words), is a speech's structure and content. With current technology, this is an impossible task to analyze since it is subjective and unpredictable. For example, how can a program be able to analyze how interesting a speech will be or if it will be able to touch the listeners? Thus, it will be interesting to be able to add something similar to a forum where users can their recorded speeches to others and receive critiques and advice on the aspects that computers can't help with. If a user chooses to, they can share only with their friends or a designated group of people, or they can share to the public. These users can then post their thoughts on the submitted recording. This falls into the communication + coordination part of the time-space matrix, since the users do not have to be in the same place, and do not have to answer at the same time as the user has posted the speech. The primary goal of collaboration is to provide users with a community that will foster their speaking/presenting ability and help them improve. The forum will allow people to get feedback from others on their speeches without actually having to be in front of the person. This will help them get much more feedback, with a variety of opinions, with less time and effort. From listening to others and giving advice, a user will be able to learn from the mistakes of others. However, there are many major challenges with this feature, many of which are described in the section on "Online and networked communities" from the reading. It will be difficult to stop users from providing rude or off-topic comments in response to the speeches. An easy way to stop this is to allow users to only send their recordings to friends that they know and trust. Unfortunately, users will not be able to get a wide variety of opinions as before, and may miss out from helpful advice from speech experts that they would have no contact with otherwise. Another solution is to have set rules and have moderators constantly removing messages that are against the rules, but this does not scale well. A major challenge of a brand new application is to find a userbase who is willing to actively use and respond on the forum. If there are more users who are posting up their recordings than those who respond, the forum is useless. Users will not be able to receive feedback for their recordings since no one is willing to give it. The more active users there are, the more feedback a person can receive, and the faster they will receive it. There must be incentive for people to help others or a way to establish what the article calls “generalized reciprocity", which is a willingness to help and trust others in the community.

Ziran Shang - 4/12/2014 23:01:31

Our project does not currently involve any social media participation, but we may implement a feature that allows users to share workouts to social media. User collaboration could also be added by allowing users to follow each other within the application, thereby allowing them to directly view the followed user's workouts. This feature would work similarly to Strava and other similar applications.

The primary goal of collaboration and participation would be an online community with a shared interest in health. Having a social feature could serve as motivation for users to workout. The application falls into the different time, different space quadrant of the time-space matrix as communication and coordination, as users will be in different places and using the application at different times. There are no major social challenges since applications with similar functionality are commonplace. The technical implementation should not be too difficult either since it just involves storage and display of user data.

Daniel Haas - 4/13/2014 11:56:30

Our application (CookEase), has a social collaboration feature that allows one user to set an alert to notify a friend via text or email when a kitchen event such as water boiling occurs.

Notifying friends in our app lies in the 'asynchronous, remote' quadrant of the time-space matrix, because the time when one user sets an alert is different from the time another user receives it, and because users need not be in the same place when the alerts are set/received.

This interaction takes the form of what Shneiderman & Plaisant call a 'focused partnership': two people who need each other to complete a task (preparing a meal), using technology to collaborate. The goal is therefore to streamline this partnership--to make it as simple and efficient as possible to enable friends to share tasks while cooking. Since users aren't interacting with a large community, and the interaction isn't public-facing, we needn't be concerned with moderation or enforcing privacy in our interaction.

The technical challenges for the application's social component are all around usability--can alerts be configured and sent to friends easily and intuitively? Can alerts be received and used to link friends to the app quickly? We don't foresee these challenges as being insurmountable, and our initial user testing has shown that users are happy with the interaction. In terms of social challenges, we will need to make sure that the social flow of the app matches the way that friends actually interact when cooking together and sharing a kitchen.

Emily Reinhold - 4/14/2014 9:15:29

App: Stat That! - an app that allows stat keepers to record real-time stats audibly.

Currently, our application does not involve collaboration or social media participation. However, there are two ways in which I think our app could be extended to enhance the experience of our target users:

1) Allow 2 different stat keepers using 2 different devices to "collaborate" on one game. They would each record their own type of stats on their own device (for example, one would record offensive stats, and the other would record defensive stats), and then our application would provide a "share with" feature. Stat keeper 1 would share the game with stat keeper 2, and stat keeper 2 could import the stats that stat keeper 1 took into his game. This would provide a consolidated report that included both offensive and defensive stats. This improvement would be between the same-time/same-place quadrant and the same-time/different-place quadrant. The stat keepers would be at the same game at the same time, but they are sort of in different places in that they use different devices to record the stats. The goal of this collaboration is to enhance accuracy of stats by offloading some of the stats to a second stat-keeper, while still providing full, detailed reports of each game. This improvement poses a challenge that would require us to verify the identity (in some form of username/password) of users, so when an individual user opts to use the "share with" feature, the data gets send to the proper recipient. This would require implementing a backend database shared across all users, which we probably will not have time to implement. Currently we are using an on-device database, which is sufficient for our prototypes.

2) Allow stat-keepers/coaches to make a "team", where they invite all of the players and team affiliates to be able to view their statistics. This is more of a social media improvement -- each player would have their own Stat That! account, and the head stat keeper would invite each of the players to view the reports produced by Stat That!. Players would be able to comment on the stats, perhaps correcting errors. The goals of this improvement would be to enhance accuracy of the stats taken (if the player knows he scored 2 goals but the report only says 1, he could comment on this and the stat keeper could fix it) and to provide concrete details of the game to each player so they can track their improvement or see what they need to work on. This improvement lies in the different-time/different-place quadrant, since the players can look at the reports wherever/whenever they want. This feature poses a social challenge -- when a player views a report that he believes has a mistake, he will comment on the report. However, how does the stat keeper know he is telling the truth and not just trying to boost his stats? We hope this would be mitigated by the fact that most stat keepers also have a video recording of the game, and could go back and check to see if there was actually a mistake made.

Zack Mayeda - 4/13/2014 15:16:21

Our current application doesn't involve collaboration, but we have two possible extensions to our project that would involve collaboration. First, we could take basketball game statistics that were recorded on a phone and make them available online. This task falls into the communication and coordination quadrant of the time-space matrix. Various players and coaches may want to view the stats in different times and places. The main goal of this collaboration task is to share the stat information for a player, team, or certain game with the whole team or the general public. One of the major challenges would be to maintain consistent information on the website and mobile app, especially if the stat keeper makes corrections on their phone. Another challenge would be to design a simple web interface that displays the large amount of information in a simple format.

A second form of collaboration for our app would be to allow two stat keepers to simultaneously track stats for a game. This would fall into the Face-to-face interaction quadrant. The goal would be to have multiple stat keepers record stats for a single game in order to enhance correctness of the stats. The major challenges would be to syncronize the game clocks of record sets and to merge the two sets of stats and resolve conflicting stats.

Shana Hu - 4/13/2014 19:14:24

Our application allows communication and coordination (the bottom right quadrant of the time-space matrix) because we aim to connect users in remote locations, but not necessarily in real-time. Our application targets foreign language learners across the globe, so that people from different countries can help each other improve their pronunciation and fluency. This way, the physical distance between remote locations no longer becomes a barrier to gaining feedback from native speakers. Since we decided to forgo our private messaging feature, our users will most likely not be communicating in real time. This frees users to respond at their leisure, accounts for time differences across the world, and promotes the efficiency of crowdsourcing rather than relying on one-to-one direct contact. In terms of challenges, our application heavily relies on user interaction. Users must be eager and willing to respond to others' questions in order to build a community which thrives off of a shared love of language and learning.

Tien Chang - 4/13/2014 21:54:19

Our application does involve users' participation. We require an instructor to actively start the listening portion of our app. We also require students to actively speak and participate in class to generate our data. We have not brainstormed a feature for the app that involves social media yet.

Our application requires students and instructors to be in the same place (in a classroom) at the same time (during class). This allows for face-to-face interactions that technology helps and not hinders the general flow of learning. Our app aims to help and not replace the job of engaging students to participate.

Our primary goals of collaboration and participation in our app are to have lecture/demo discussions where the professor speaks and students engage in discussions with the professor and with their peers and for meeting and discussion support for the professor to initiate topics and students commenting on such topics.

The major technical challenge is to control how the sound recognition will perceive the difference between actual participation and sneezes/coughs/remarks to nearby students. Another issue, which is partly technical and partly social, is that our application must not take much battery and our application must not be distracting to our students. These are very important concerns we must address while developing our app.

Anju Thomas - 4/13/2014 23:09:40

Does your application involve any form of collaboration between users or social media participation?

Our application currently does not include multi-user collaboration. The main purpose of our group application is to promote biker safety by allowing bikers to perform three tasks while on the go : hear surrounding loud noises while listening to music, enable greater voice amplification to help users better hear people close by, and enable caller id to allow bikers to prioritize and decide whether to pick up a call while on the go. The tasks currently implemented in the application are mainly for personal uses.

If your class project does not involve any multi-user aspects, discuss how you could enhance your application by adding such support. Describe it briefly in light of the following questions: Which quadrant of the time-space matrix does the application fall into?

We could include multi-user aspects and enhance our application by creating a forum for bikers, where they can collaborate and share their experiences and likes of biking, ideas on how to improve safety help new users with the application features. The bikers could also share their experiences with their application, describe how it improved their safety and discuss possible improvements in the application that would increase their safety. The addition would fall into the Communication and Coordination quadrant of the time-space matrix, as the bikers could share their ideas at different times and in different places. The biker could collaborate on ideas and application ratings during their free time, any time or any location they choose. The improvement would also fall into remote interactions quadrant presented by Shneiderman & Plaisant in the time space matrix, where bikers at different places could post and reply to other users during the same time.

What are the primary goals of collaboration or participation in your app?

The primary goals of collaboration or participation in the application would be to increase user participation and use of the app not only while on the go, but also during other activities or free time. It can also help create a platform and opportunity where enthusiast bikers from different regions could come together into one space and join people who share the same interest. This multi-user aspect would allow the bikers to not only share their biking experiences and insight on safety but will also provide the application designer with reviews and ideas on how to improve safety features of the application according to user ideas and preferences. The designers could also get a good feedback from different bikers in both the pros and cons of the design and make changes accordingly.

What are the major challenges (both technical and social) your application has to overcome to succeed?

Some major challenges that the application has to overcome to succeed include the user’s generosity in helping beginner users with the application features. Also, the application has to accurately work to provide the bikers with immediate awareness of surrounding noises without any lag, smooth integration of loud noise with music while enabling them to distinguish the music from the noise, and good quality in voice amplification to truly improve the safety. Only if the application features accurately assess the noises and provide user with instant and clear feedback will the application satisfy the user’s safety needs. Without the effectiveness in the functionality of the application, the bikers might not be as interested in the application, in sharing feedback, or safety tips in the application. Without a large user population for the application, the forum would fail to provide fast and effective user collaboration. The user also has to be willing to spend some time and effort to provide feedback and suggestions to the application designers for its improvement.

Though not originally designed for multi-user interaction due to focus on individual user safety, this new addition could potentially improve user safety by not only relying on the limited features available i the application but also through the knowledge and tips gained through discussion with other people of the same background.

lisa li - 4/14/2014 0:37:45

Our group project is SurveyParrot, which is an application that enables users to take surveys hands-free and redeem rewards from companies.

There is definitely collaborations between users but I think they are not collaborations in the traditional sense. The collaboration within SurveyParrot is more of a crossover between collaboration and social media participation. Just like Wikipedia, a large number of participants contributes to one company's market research with little contact with other users. However, different from Wikipedia, the collaborative result of market research is not shared with the community but is accessible exclusively by the company who conducts the research. Therefore, within one company's market research department, there are collaborations. They know each other in person and share the same statistics in order to retrieve valuable marketing information from it.

Jay Kong - 4/14/2014 0:49:38

Our class project, the sound listener for deaf people, does not currently involve any multi-user aspects. However, it could be enhanced in that regard by adding in a sound signature sharing system. The sharing system would allow deaf users to share pre-recorded sounds. This makes it possible to create a "home bundle" of sounds which new users will find very helpful. To expand on that, new users won't have to take the time to record every sound in their house; they can simply get on the ground and start running.

With the enhanced feature, the application will fall into the "communication + coordination" quadrant of the time/space matrix. The collaborative aspect of the application is asynchronous and remote. Users don't have to be together in order to take advantage of the sharing feature of the application.

As mentioned previously, the primary goals of collaboration would be to help user minimize the set-up time of listening to a sound. By allowing the sharing of a sound, users could simply download the particular signature for a sound they're listening for without having to manually record the sound.

There are different challenges the application would have to overcome. First of all, users would have to be comfortable with sharing the sounds that they listen to. For deaf users, this could potentially be a problem as they don't trust people outside of their community (other people could also download the application). Another challenge would be that the sound signature for one person might not be useful for another person. It might be very difficult to generalize a sound signature so that different users can use it.

Ian Birnam - 4/14/2014 10:44:30

Our app doesn't currently have any multi-user aspects to it. We could add multi-user aspects by integrating social media to the statistics page so that people could share their progress with their friends.

This falls into the communication and coordination quadrant, as people will be sharing and posting their progress to some kind of forum or e-bulletin board. Perhaps they could even coordinate times to exercise together through the use of group calendars.

The primary goals would be to get people to motivate and encourage each other. By posting their progress and communicating with other users of the app, users can get a form of support group where they can gain recognition of their achievements, encouragement if they're not meeting their goals, or workout buddies for real life interaction and motivation.

On the technical side, the most challenging part of our app will be getting the dynamic time warping algorithm implemented for changing the tempo of songs. This is also the main focus of our app, so most of our effort will be going into implementing this.

As for social challenges, assuming we implemented the features described above, we would have to actually create a database of users and build some sort of platform for them to use to communicate and share with each other. The challenge would be to get people to actually want to use this, sine if we force it on them, it may deter users since its just another app they have to sign up for using social media. It could always be optional though, which would probably be the preferred route.

Nicholas Dueber - 4/14/2014 11:02:53

Our application does not involved collaborations between users or social media participation. Our app, is for speech development and the detection for filler words. A way to improve our app could possibly be to add a public recordings where friends can listen to your recordings and then give you feedback. This would be remote interactions for the time-space matrix. This fits logically into this quadrant because it alleviates the need for people to work in the same room or even at the same time. The primary goals for collaboration and participation would be that people would post their recordings of their speeches and would illicit constructive criticism. Then the speech givers could go back and either read comments on their speech, or possibly listen to verbal feedback on their speech from a friend or colleague. The major challenges that we would face from a social stand point would be initially to have users post recordings as public so that others could listen to them. This is originally a daunting task. The main reason that these participants are using our app is because they are not comfortable giving presentations and talking in front of people. It may be even more stress inducing if they are now posting a recording for anyone of their friends to listen to. However, if we market it as a constructive interactive, hopefully we could alleviate this fear. Another social problem that could arise would be that we were not getting people to listen to other people and give feedback. People may be hesitant to give feedback because they do not imaging that they have the expertise on speaking to really criticize; however, that isn't the point. We want people to listen to others and how they give presentations because that is a great method of getting better. You have to listen to other people, and then adapt styles of speaking that you like. A technical challenge that we would need to overcome to make our app successful, would be to have the recordings in a public space. We would have to have a server that could host the recordings, and then give people access to the recordings when they wanted to listen to their friends. We would want them to be on a remote server, so that when our friend's phone is off, their friends can still listen and give constructive criticism. If both of the social problems and this technical problem could be overcome, I am certain that our app would be successful.

Ryan Yu - 4/14/2014 11:29:21

Currently, LaZe (group Honeycomb) does not have any significant forms of collaboration between users or social media participation. Perhaps the only thing that could possibly qualify under such a label is the ability to email generated snippets of LaTeX code to others, but this doesn't really count as a real "form of collaboration" between users.

We could, however, enhance our application in many different ways by adding such support. For one, we could implement some sort of collaborative editing on LaTeX documents (voice generated of course.) This would function similarly to a Google Doc; in fact, some top-tier existing Android applications already have this feature implemented, and I think it is a great way to improve efficiency and encourage participation from other users. Another possible link between users could be the ability to "friend request" people on your Facebook/LinkedIn friends list, which would then enable some sort of "document view" sharing and messaging. In this sense, users would be able to message each other for help and documentation instead of just relying on the application's built-in help activity. In terms of other social media, we could also provide some sort of real-time uplink to Dropbox/Box, and other portals (such as BSpace or BCourses.)

In terms of the Time/Space Groupware Matrix, I believe that our application, LaZe, fits into the "Communication + coordination" quadrant. The description of this quadrant indicates that "E-mail, bulletin board,s blogs, workflow, ..." are its primary characteristics. Because our application primarily focuses on the sole work of individuals (who can then distribute their generated code accordingly with others), "Communication + coordination" is the best-fit quadrant to describe it. The primary goals of collaboration or participation in our application essentially, at this time, involve just emailing of short snippets of code to yourself and others. In this sense, for example, you can imagine a group of students working on some problem set that requires typesetting (think CS170). One of the students in the group could suddenly get a brilliant idea about the problem, type up the series of equations that have to do with his/her solution, and then want to send it to the group. Well, with LaZe, he could simply specify his/her group's emails, and the fully typeset code (i.e. the solution!) would be fully sent to his group members instantly and painlessly.

In terms of challenges, the hardest (and primary) technical challenge we have is actually getting the LaTeX to be interpreted and compiled. (We are thinking of using a third party LaTeX Java library to achieve this.) Furthermore, since speaking aloud math expressions and notations can be obscure, speech-to-text software may frequently interpret with error, which is another problem we have to overcome (we have looked at hardcoding and other speech-to-text libraries for this.) Socially, the collaborative emailing was extremely easy to implement; however, if we decided to implement real-time collaborative editing, this could get very difficult, so we might want to look at how Google Docs/online programming language interpreters (i.e. Codility) implement this feature.

Charles Park - 4/14/2014 12:10:33

Our project allows for collaboration between users in that it allows the user to share their work with others via mail, Dropbox, Evernote, Skype, and etc. However, the original intent of our project is to use these sharing functions to send the product to the user themselves. Nevertheless it still contains the sharing function.

Our application falls under the Difference Place-Different Time quadrant because it falls under the remote & asynchronous part of the matrix.

While the original intent behind the application does not pertain to a collaboration in our app, it allows for the users to share information as well as their projects with other people so that multiple people can work off the base product and create something from the generated LaTeX code.

One of the major challenges for this product would be that the generated LaTeX code at the moment are simple as well as suited for individual work. There is not an implemented means of multiple people generating the LaTeX code at once and therefore if it was a group project, it may be difficult for the different users to know what parts of the project are complete. One way to overcome this may be to have the pre-existing history page be a feed that's shared amongst multiple users so that everyone involved in the project can see exactly what LaTeX codes are generated for everyone on that project.

Gregory Quan - 4/14/2014 12:18:55

Our application, ListenUp!, can be used collaboration. One of the goals of our app is to allow cyclists to communicate with each other, which is a same place/same time form of collaboration. There are no real social challenges to overcome for our app to accomplish this, since cyclists already want to talk to each other. In terms of technical challenges, our app must be able to amplify voices being picked up by the phone microphone and play them through the headphones. This technique might not be very effective if the cyclists are far away from each other or there is a lot of ambient noise. Once we have results of our pilot user tests, we can decide whether our implementation is sufficient or if we need to explore other communication methods such as push-to-talk.

One way to further enhance our app with multi-user support would be to track cyclists’ rides and allow them to share them with each other, similiar to the Map My Run app. However, cyclists can already use Map My Run to map their rides, since Map My Run does not differentiate between biking and running.

Nahush Bhanage - 4/14/2014 12:29:42

Our application (Confluence) extensively involves collaboration between users. It falls into the 'different time-different space' quadrant of the time-space matrix model (it would support multiple users at the same time, but that is not a requirement). Confluence enables language learners to practice their pronunciation, improve their fluency, and receive feedback from native speakers. We aim to facilitate a conversation-based education which would be more natural and intuitive in comparison with the formal textbook education that emphasizes heavily on reading and grammar skills. Our application works on crowd-sourcing pronunciation questions to real native speakers of the language. Due to its social form, users can collaborate and help each other irrespective of their geographical locations.

Our application will have to overcome certain technical and social challenges in order to succeed. We have determined (from contextual inquiries) that there is definitely a need for such an application. But since it heavily depends on crowd-sourcing, it will need a substantial time and effort to gain momentum. Language learners need to be made aware that such an application exists. It would require a minimum number of users to be practically useful. Our aim is to develop a "Stack Overflow" for language learners and getting a large number of users is crucial for it to succeed. We have also determined a couple of technical challenges that we would certainly face in case the application becomes popular and gains substantial participation. We need to design the application keeping scalability in mind. Most pronunciation questions would be in the form of recorded audio. Each question might get multiple answers, some of which would include recorded audio attachments as well. We need to maintain a server that can store all these audio attachments in real time. An estimation of required disk space and bandwidth would be crucial. A large number of users should be able to use it simultaneously without overwhelming the server. These issues need to be handled before launching the application on a social platform.

Everardo Barriga - 4/14/2014 12:31:03

I think by adding users the ability to record themselves and then be able to share that recording with other users you could really enhance the piano practicing experience. It would behave similarly to a review based interaction but rather users will be able to provide feedback on other users piano playing and could potentially get together to collaborate on a piece together.

I think this interaction lies in the communication + coordination quadrant of the time/space matrix because it is similar to a bulletin board or a blog in that you post your content which in this case would be your piano piece and then people can come and look at the piece or comment to help you make it even better.

The primary goal of this multi-user interaction is that users will be able to comment and perhaps give advice to other users on how to make their piece better which would further enhance the “practicing” experience.

A major challenge will be quality control and the validity of the user and their respective comment. Also a nice feature would be to let users comment only if they themselves have posted a piece and so that having that structure could be challenging to implement.

Lauren Speers - 4/14/2014 12:45:07

In the current design, our Melodious app does to support any form of collaboration between users within the app. However, it is designed to facilitate collaboration outside the app by allowing users to save their projects (music sheets) as PDFs, which can then be attached and shared via email. In our contextual inquiry, all composers expressed a desire to share their compositions with other musicians so that someone else could play their composition, either in a performance setting or for instructional purposes. Because our app is designed to facilitate creating and editing music sheets, not reading them, supporting sharing within the app would not add much useful functionality since the receiving user still have to save the sheet as a PDF before playing.

However, we could enhance our application by allowing groups of composers to work on the same project. This type of multi-user interaction falls into the co-located synchronous quadrant, and ideally it would allow users to create music sheets for different players or components of the same composition. Supporting this type of interaction would pose many technical challenges since it would be hard to separate the different components of the sound input, a task our group specifically chose not to tackle given the time constraints of the project.

Opal Kale - 4/14/2014 13:28:50

At the moment, out app does not involve any multi-user aspects. Our app does have a function that allows a person to share their stats on Facebook. However, if we added some multi-user aspects, we could enhance our application. For example, we could add collaboration between users in the same place at the same time (potentially through friends on Facebook) to see if people are at the same gym so they can meet up and work together. We could also add a functionality that allows people who are in a different time/ different place look at their friends’ stats on their workouts and comment/give recommendations on their workout. If we implemented more multi-user collaboration, it could lead to more people using our app for much more time than before, because it’ll have more features to keep people engaged!

Christopher Schechter - 4/14/2014 13:10:00

Our application (the presentation recorder app for entrepreneurs) currently does not support any collaboration or social media elements, but we have already been considering how we could implement it to improve the app. Our idea would be to allow people who have recording a run-through of a presentation to share it with friends or contacts within the app, who can then listen to the recording and comment on it to give extra feedback. This feature would inhabit the "communication + collaboration" quadrant of the time-space matrix, since users could asynchronously communicate their thoughts on a recording.

The goal of this would be to allow users to receive feedback on their presentations that the app itself couldn't automatically give--the app can analyze the presentation in terms of words per minute and counting certain words, but can't give any indication of whether the presentation's content is on-topic, or if a story's emotional impact is valuable, etc. In this way, a collaborative sharing feature would cover some shortcomings our app has.

The most major challenge of adding this feature would be how to handle the logistics of sharing with multiple people. The most simple use case would be if a person records a presentation and shares it with one other person, so they could have an easy two-way conversation about it in a manner similar to texting or instant messaging. Something more complex would be if the user shared the presentation with two or more people, and they would then communicate in a chat room-like environment all together. The most challenging case is if the user wants to share their recording with multiple people, but doesn't want to communicate with them all in the same messaging thread. So ideally the app would be able to handle a situation in which the person sharing a recording with a single friend and the two of them having a simple two-person conversation about it, but also the user shares the same recording with another group of three other people, and their four-person conversation is isolated from the earlier two-person conversation. This would ensure some privacy, since pitching early stage startups can include some sensitive information, but also allow for group collaboration, since that's how they could get the best feedback and results.

Andrea Campos - 4/14/2014 13:40:56

We plan to implement collaboration between users in our app. It would fall in the quadrant of different time(asynchronous)-different place(remote) because these are the exact conditions our target users face, and that would be presumably ameliorated by our app. Our target users who must deliver pitches for their companies don't often have the ability to practice in front of an audience or receive immediate feedback. Therefore, our form of collaboration would allow users to share their practice recordings with their colleagues very easily within the app, and allow others to add comments to those recordings. This way users can gain valuable feedback on their pitches from others even while at a remote location, and even when live practices cannot be scheduled.

Major challenges might be technical ones of how we are to go about sharing recordings and comments between users, as this would likely require databases. Social challenges might include users forgetting to review their colleague's recordings or time coordination issues, which could be overcome with notifications or giving recordings a deadline for feedback.

Seth Anderson - 4/14/2014 13:41:00

Currently our class project, Knock Knock, does not have any multi-user aspects. However, if we were to add multi-user support, we could do so by having users be able to send sounds they had recorded to a larger database that could be used to speed up the machine learning process. For example, multiple microwave alerts would be used as data to further improve the accuracy of detection for that type of alert. Certain noises could also be sent between users, such as a specific brand of microwave, so that users do not have to record a new noise and just download one that has already been recorded.

In the space-time matrix, this would be a Different-Time/Different-Place interaction. This is because there is no live communication between users, they are uploading and downloading sounds whenever is convenient for them, and doing it at separate locations from one another.

The primary goals here are not to bring users together as is mentioned in the reading so often, but to speed up the process for each individual user, as well as increase the accuracy with which the app operates.

One of the major challenges the application will have to overcome will be the categorization of certain sounds. This will take a very expansive machine learning system which will take time to build. Another challenge it will have to overcome will be storing up to thousands of sounds on the server-side and having them be quickly accessible to app users.

Brian Yin - 4/14/2014 13:43:05

Our group's application's main feature utilizes collaboration between many different users. The application works in the different time/different place quadrant by posting questions to a forum where any user around the world can answer at any time. The primary goal for this sort of collaboration is to connect users to experts in their language of interest. These experts will be able to critique and correct others on their pronunciation.

While the crowd-sourced content has its advantages of providing expert knowledge, there are also many problems which may arise from this approach. First of all, an application whose content is crowd-sourced must have a crowd to gather than information from. Without a large user base, the application will be useless. Additionally, another problem would be the scalability of the application. In the case where there are a large number of users posting to a single application, we'll need to find ways to effectively store all the posts.

Christina Guo - 4/14/2014 13:55:15

Our class project, which involves recognizing everyday sounds and alerting deaf people through vibration and visual notifications, does not add any multi-user aspects. One way in which it could be enhanced would be take the existing ability to train the app to recognize certain sounds, and allow the user to upload those sounds to a common forum. This could be useful so that a user would not have to set off their fire alarm or car alarm or anything else in order to train their app--they could just look to see if anyone with the same brand of fire alarm or same model of car has already uploaded the sound signature.

This would fall under the different time/different place quadrant of the time-space matrix because people are uploading sound signatures for the future use of other people in unknown locations. The primary goals of participation in this app would be similar to a one-sided focused partnership or a collaboratory, where uploading sounds would help other users use the app more easily, without having to go through the extra trouble of recording sounds. To add incentives to upload sounds, and to make the partnership more balanced, we could add a point feature in which users get points for uploading sounds and can use points to "buy" other sound signatures.

The major challenges the application needs to overcome is the quality and precision of sound recognition, because it would be a disaster if someone relied on our app to alert them to a serious issue such as a fire, and we failed to alert them to the situation. A social challenge would be gaining acceptance of it's usage within the deaf community, since the phone might need to be left out and running during social situations.

Rico Ardisyah - 4/14/2014 13:57:13

Currently, our application, Beat x Beat, does not involve any of collaboration between user of social media participation. In order to supporting multi-user aspect, we can enhance our application by adding multi-user project. This feature allows users to share their project with other users, and all of them can record a clip. Hence, they can collaborate to create a new rhythm. Therefore, the application fall into different time different place quadrant. Indeed, the users and their project partners can record clips in different place and different time, but they can still save the project and continue working on it anytime. The main goals of collaboration in our app is to create a better rhythm from the collaboration of some users. The technical challenges that we face is to keep the data live for the other project partners. For the social challenges, only a few users want to collaborate in composing a rhythm. They tend to create it alone.

Emily Sheng - 4/14/2014 13:58:22

Our app has the feature where one person can start a task (listen for water boiling) and then set the app to alert another person when the first task is finished. This is in the same place-different time quadrant of the time-space matrix, because the two users must operate in the same space (kitchen) but at different times. The primary goals of collaboration of our app is to promote a more efficient use of time for all users and to help facilitate the goal of cooking in the same space (though at different times for more efficiency, ex: if the kitchen space is small or if both users are not needed at the same time). In terms of technical challenges, our app must be able to correctly identify the sound patterns of specific kitchen tasks and successfully alert and remind users that their kitchen tasks have completed. In terms of social challenges, people must remember and set our app to listen for the completion of specific kitchen tasks and notify themselves/other people. People must be willing to part with their phone and leave it on the kitchen counter while they go off to work somewhere else in the house. Although this social challenge may be difficult for users to get used to, we assume that if users need our app functionality, they would be willing to deal with this social inconvenience instead of alternatives such as purchasing new hardware or using just a normal kitchen timer.

Shaina Krevat - 4/14/2014 14:00:40

My class project (LaZe, the speech to LaTeX interpreter) does not involve any form of collaboration between users or social media. However, it would be possible to add collaboration if users wanted to share equations generated for the same project or homework they were working on. While the emailing function we have implemented does this already, it could be improved by making the sharing in-app.

On the time/space matrix, this would fall in the different time/different place, where the users working on the same project would be able to contribute to the project’s list of equations from wherever they were (with an internet signal) and whenever they had time to do so. The primary goals of collaboration would be the ability to share the information for a single project among many people, which without the app would take another sharing platform, such as github which students use for lab write ups or other projects. The technical challenged would be similar to any other collaboration application: databases of users and their projects, necessary internet connection, etc, but because of the frequency of applications that use these features, it would be possible to find common fixes if we were to implement a collaborative feature. One major social challenge would be using the collaboration for ethical means. If one class put together a “project” that they could share, then it could be counted as cheating or plagiarism by the staff, and students who only got equations and didn’t contribute would be learning nothing. This might require moderators for projects, or invitations to join groups would be required to see what was in a project file, or a limit on the number of people that could contribute to a single file.

Overall, I believe leaving the choice of collaboration platform (i.e. email, dropbox) up to the user would be the best method for this specific application.

Juan Pablo Hurtado - 4/14/2014 14:02:39

Because right now we have the export to PDF functionality with the idea of sharing the composition, we can say it does have a form of collaboration between a user and other people even if they aren't users (it could be any kind of musician).

That said, our project would be in the 4th quadrant, different place and different time. Different time because if the user wants to share the PDF it would need to email it or post it somewhere. Different place because usually the user composes alone in a room and then they share their composition.

The primary goals are for the user can have feedback about their creations and that other musicians can play their creations. So this kind of interaction would fall in what the text calls "focused partnership" and "lecture or demo". Focused partnership, because it allows, for example, a band create a piece and work on it and Lecture or Demo, because you can share it with others to receive feedback and/or others can use for learn from it.

In the more technical aspect the app must have a robust real-time note recognizer and also a good playback feature, these couple of the things are the major challenge because those are the core functionalities of the app. And social, because of how we designed the app, is not a essential part of the app, even though it can be used as a collaborative composition tool (sharing the PDFs), so our app has stronger technical challenges than social. So, speaking of social challenge, would be more like creating a community where the users can easily share their compositions with other musicians.

Brenton Dano - 4/14/2014 14:04:43

Does your application involve any form of collaboration between users or social media participation?

The current version of our application doesn't involve collaboration but I can describe a theoretical version which could implement social media participation. This version would give users the ability to create "troops" where they can share their scripts with other actors in their play. It also has the option for directors to edit their actors scripts and do push notifications for changes to the scripts. It also allows records to be scored for high scores on good performances and also statistics to track practice time that are made publicly available so you can see how well students are practicing their lines.

Which quadrant of the time-space matrix does the application fall into?

It falls into the quadrant of Communication + coordination (different time different place). Users are able to check in on each others progress at different times since the progress occurred and are also able to this from different physical locations (since they will be on their smart phones).

What are the primary goals of collaboration or participation in your app?

To keep actors in the same play connected and directors up to date on the progress of their actors. Also lets the director know if students who struggle during rehearsal need more practice and the director can send SMS messages through the app to alert lagging actors to pick up the pace.

What are the major challenges (both technical and social) your application has to overcome to succeed?

A social challenge would be to get everyone in a play to start religiously using the app. With any social media type thing you need a large user base otherwise it's no fun. Facebook wouldn't be a good site without any users and content!  :)

Technical challenges are scalability (what happens when we get million actors using the app), figuring out how to send SMS messages from an application, getting the database set up etc. We also need to write APIs to implement all the unique features of our applications and spend time make the UI look nice for our users. We also have to deal with copyright issues in case people are recording scripts that they don't have the rights to. Lots of work ahead of us for team QWERTY! :D

Sang Ho Lee - 4/14/2014 14:36:04

My group's application, Spartito, currently does not involve any form of collaboration between users or social media participation. However, it could be augmented with the collaborative aspect of sharing sheet music annotations between users. The implementation of annotation sharing would be an asynchronous distributed interface. Much like the back and forth communication through e-mail, the sharing of annotations would be between multiple devices separated by varying physical distances and time. A situation where annotation sharing would be useful is if an instructor wants to send his or her student sheet music with helpful annotations for practice purposes. While with printed sheet music, hand-written annotations are enclosed within one copy of the sheet music and is not easily transferrable between users, because Spartito's annotations are digital, they can be changed, viewed, and transferred an unlimited number of times between users. In essence, users could create multiple version of annotations for a single piece and share the appropriate versions with other users for their practice purposes. As for technical challenges, Spartito no longer functions as a fully stand-alone application. The implementation of sharing between users requires that data be saved and transferred to a intermediate online server, unless built-in short range transmission technologies such as Bluetooth or Wi-Fi Direct is employed. This means that the users would require connectivity to the Internet, and also that users sign up for an account or ID that uniquely identifies their device. As for social challenges, users must remain private. Any leak of user ID information could lead to spamming of unwanted annotation files. Because annotation data is at its base an image overlay, malicious attackers could spam unwanted images or text to Spartito users who only want to share annotations with known friends. This could lead to a disastrous exodus of users who see the spam as disruptive to their practice routine.

Jeffrey DeFond - 4/14/2014 14:41:37

Our app currently does not involve any collaboration between users. However, I could envision adding a "bulletin board" style system where users could post the templates of the sounds they have trained into the app. This would require a user name a nd login. Informationally this would be essentially sharing a the name and feature matrix of the sound they have trained along with searching and posting features. This would occupy the bottom left of the time-space matrix, as users would post whatever sound they wanted, whenever, from whichever device they were signed in to. So it is not con-current and remote like a bulletin board. As far as challenges, this app would need enter into the deaf community in order to succeed.

Conan Cai - 4/14/2014 14:50:52

Our app is used while running and part of the functionality of the app involves recording basic data on a user's run - things like distance and pace. These stats, while useful for personal use, can also be shared among friends to provide the app a social media aspect. Since users post their individual stats at their own convenience, the app's social aspect falls under the different time/different place quadrant of the time-space matrix. This run stat sharing can provide and extra motivational boost to users. Sharing stats allows there to be an element of competitiveness between friends. Sharing also allows friends to see a recent run and provide feedback and additional motivation. In order for the social part to successful, users must actually be willing to share stats with friends. If people are embarrassed of sharing run stats, then obviously there is no social participation or content available. As far as technical difficulties, the social aspect part is not an integral part of the app, so only very basic functionality of sharing is needed.

Albert Luo - 4/14/2014 14:55:11

We don't currently have collaboration between users. But, it could definitely benefit from adding support for social media participation, by posting to Facebook or Twitter, or even allowing multiple users to work together on a single musical piece. The form of collaboration in our application would fall under the Communication + coordination quadrant of the time-space matrix. The primary goal would be to share the creation of their music and to collaborate in creating music. The major challenges faced would be figuring out what happens when users try to modify the tracks simultaneously, as well as possibly how credit will be shared among multiple users when the piece is finally complete.

Dalton Stout - 4/14/2014 15:05:25

Our application is called "Knock Knock" and is used by the deaf/hard of hearing community to detect particular noises around the house, with the added ability of training the app to learn new sounds. Currently it does not support any social media platform. If I were to enhance our application in that sense, i imagine adding the ability to share recorded sounds with your friends so that they can use the app to detect the same sounds that you have trained, even if they haven't been near the sound and trained it themselves.

This Enhanced Knock Knock application would fall into the bottom right of the time-space matrix, communication and coordination, a different time at a different place. This is because the core functionality of social media platform is the ability to share sounds with friends that they do not yet have. These sounds could be recorded at any number of places at anytime, and then shared remotely with a list of friends who also use our app. I believe that text refers to this as an asynchronous distributed interface.

The goal of the sharing functionality would be to open our user base up to a wider range of noise detection that they may not have access to in seclusion. For example, perhaps a user wants our app to detect a smoke alarm, but doesn't want to set their smoke alarm off. Another user who has a good recorded sample of a smoke alarm could share that training sample with the first user. It gives our app more utility.

The major social challenges we would face is first building up a user base that is large enough that our social functionality becomes useful. If they are very few users, then not many users will be inclined to use the new service. Also, we would need to give the user some motivation to WANT to share their recordings, perhaps some sort of reward system. On the technical side, our team would need to decide the best way to implement the sharing feature, like what protocol would be used to share the recordings. Also we would need to ensure confidentiality in our sharing so that no user recordings are vulnerable to theft or eavesdropping.

Armando Mota - 4/14/2014 15:06:10

Which quadrant of the time-space matrix does the application fall into? The quadrant that our app, CookEase, falls into is “Continuous task”. The collaborative element in our app is the ability to split up cooking tasks between multiple people in the same location - because our users are often going to be working or spending time on tasks, this means that the two users might not actually interact with each other until after the cooking is done and they are eating. That is to say that they are in the same place (kitchen) at different times throughout the cooking process (and in general, the use of this app).

What are the primary goals of collaboration or participation in your app? The primary goal of collaboration and participation in our app is having focused partnerships. The participants need each other to complete the cooking task (technically they wouldn’t need each other if they chose to do the task by themselves, which they certainly could do, however when they’re using this portion of our app it is assumed that they have explicitly chosen to work together to reach their goal). Structured work processes are also involved in this app - for example, the first person sets the water on the range and turns the heat on, sets the alert to email his roommate when the task is done, and the action of turning the heat off and continuing the cooking is performed by the roommate (because that’s his specific task). There is an explicit structuring and differentiating of tasks between participants.

What are the major challenges (both technical and social) your application has to overcome to succeed? As the paper mentions, “researchers are starting to understand the reasons people participate in these activities and how to motivate higher levels of participation”. I think participation, and the want to participate in a collaborative cooking effort, is something our app will have to generate. While some households and roommate relationships might already be consistently using collaboration to achieve their cooking goals, for those who aren’t, hopefully we can find a way to design this app in a way that spurs them to use these features. The notification methods must also be designed so that they are perceived as a notification from a friend, rather than a business. There is a distinct difference between getting a text/email from a business or organization and getting one from your friend - in day to day life, one is certainly more annoying/cumbersome than the other. If the email/text features of the app are to be used, people need to feel as if their friend is notifying them that it is their turn to participate in the activity. The last technical challenge we have to overcome is being able to recognize multiple sounds at once - this is something we will have to do a lot of testing on to achieve.

Kaleong Kong - 4/14/2014 15:07:39

Our project doesn't support multi-users aspects although we design the app in order to increase parent children interaction but they will all share one device. Our current app is designed to let user to make custom card by adding picture and vocabulary to the database, and parents can use those cards to teach their children new vocabs. I think we can extend the idea to let different users share pictures and vocabs on the internet. They can even rate each other custom cards and leave comments on them. I think this will fall into the different time and different place time matrix that involves communication and coordination, since they can give suggestions to other people's cards and try to make a better card to share in the internet. The primary goal would be letting parents make a better card for their children by communicating with each other and sharing resources(cards) in the internet. The major challenges would be how to control the quality of the card so that no one can upload cards with unappropriated pictures to the online gallery.

Sijia - 4/14/2014 15:07:46

Our application (Cook Buddy) involves multi-users participation. It enables and invites users to post their own cooking experience, for example successful recipes they created and used before. Users will be able to see recipes posted by their friends from their phone book or Facebook friends.

The application falls under the asynchronous (different time) and remote (different place) time/space quadrant (page 366, Designing the User Interface). It requires communication + coordination. Basically, a user can communicate with another user by making comments under his or her recipe posts; they are able to communicate each other because they know each other (Phone book) and/or they are friends somewhere like Facebook.

The primary goals of participation in our application are to let users enjoy cooking, love cooking and share cooking experience as well as to promote people's connections through cooking experience. We are aim at making people love cooking again!

Major challenges (social) will be to bring users to our application platform and encourage users to post their recipes. How to encourage users to become contributors of recipes is a main social challenge we will have to face and solve, since we know that most users are consumers of contents, but not the creators or participants of contents.

Major technical challenges will be to design the application in such a way that attracts users to frequently use it as well as to come up with an algorithm which will automatically expand and enlarge the "cook buddy" community. The algorithm will rank the recipes and introduce top-ranking recipe creator to users so that they can make connections. As the community become larger, the above social challenges will be overcome and the community will grow on itself.

Munim Ali - 4/14/2014 15:11:15

Our final project does involve collaboration between users/ social media participation. The application falls within the same place - Different time quadrant (people can listen to audio tags at any time but have to be around the tag location to be able to access it). The primary goals of collaboration/participation in our application as far as the primary target group (geocachers) is concerned is trying to make geocaching more sociable, by connecting geocachers. The rating system for audio tags enhances participation as it provides users with encouragement to use the application to create more tags. We also intend to implement a comment section for each tag, allowing users to express their opinions to each other. The major social challenge for the application would be misuse of the application as users could create 'spam tags' (say companies using the platform to advertise); we hope the rating system will alleviate this problem. The major technical challenge involves scaling the application for a large user base.

Aayush Dawra - 4/14/2014 15:12:03

Yes, our application involves multiple users from the users phonebook sharing recipes with each other. This sharing aspect 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 collaboration in our application, CookBuddy, is mainly between users who submit their own recipes and their phonebook contacts, who can view that recipe and ask them for help.

The primary goal for this collaboration in our application would be twofold: first, users will have a set of recipes available that are more relevant since they are the recipes that their contacts have come up with and hence are more useful to the user than a large, general set of recipes and second, users will be able to seek help from the recipe author himself/herself since the recipes are linked to the author's phone number.

The main social challenge will be to incentivize people to actually submit the initial set of recipes, since the application is going to be truly useful if there are enough recipes for the user to choose from since the recipes are only submitted by other users. The main technical challenge will be to parse every step of the user submitted recipes, since our application allows to set an automatic timer at eery step, for which the step text needs to be parsed and analyzed for any time input into the recipe, apart from linking the user phonebook contacts to the recipe contacts. Another challenge will be scalability, especially taking into account how the application behaves once a user has a substantial number of contacts in his/her phonebook.

Cory McDowell - 4/14/2014 15:19:32

In my application, SurveyParrot, companies will post surveys and consumers will fill them out. Because companies can upload surveys whenever and users can take them when convenient, out application falls in the “Communication + coordination” quadrant of the time-space matrix.

The primary goal of collaboration is so companies can gain information about their customers and their preferences. However, it is difficult to get users to willingly provide their purchasing preferences to companies.

The biggest challenge my application has to overcome to succeed is getting users to take the surveys posted by companies. Taking surveys requires time and thought by the users, so we have decided to create an incentives program for our application. When a user takes a survey, he or she will be assigned points. Once he or she accumulates enough points, he or she will be able to redeem these points. We are hoping this will motivate users to take surveys provided by companies.

Sol Park - 4/14/2014 15:27:16

Our class project application involves collaboration between users. The application falls into face-to-face interactions since all the users have to be in the same place at the same time. The primary goal of participation in our app is to help instructors to grade participations of students in his/her class. The major challenges are catching only individual's voice excluding other students' voice and counting number of individual's participation as they participate.

Erik Bartlett - 4/14/2014 15:27:45

Yes our application does. (Bearly a Group - Confluence)

It rests in the bottom right corner - of different time and different place. Answers to questions are not guaranteed, as it is a forum, and there is no need for user's to be anywhere near each other.

The primary goal of collaboration in our app is to allow users to provide meaningful feedback to other users about their pronunciation of words or phrases. We want this to be crowd sourced to decrease response time, along with increasing the accuracy and availability of answers.

Socially the most difficult part of our application is going to be getting a critical mass of users such that questions get answered in a timely manner, along with verification of answers. Technically the most difficult problem we face, as of now, is getting the backend to run smoothly - processing requests for tons of questions and answers that we would receive if we reached the size we would need to be very useful.

Gavin Chu - 4/14/2014 15:33:26

SurveyParrot just as a survey taking app currently does not involve any form of collaboration between users. Although many users will contribute to the same surveys, there's is no interaction between the survey takers. Once a survey is completed, the user will never have to see it again.

One functionality that we could add to our app is allowing the users to view the survey results. The goal of this option is to give the users the sense of contributing to a group, or knowing that they participated. Since viewing survey results can be done at different time and different places, this task falls into the remote asynchronous communication and coordination quadrant of the time-space matrix. The technical challenge is to keep track of all the surveys each user has completed and organize the results in a meaningful way. The app also needs to decide when is it appropriate to share the survey statistics because we wouldn't want to mislead the user with results that only reflected on the opinions of a few users. The social challenge will really depend on the contents of the survey questions. Some people may be offended by the results of a specific question. However, this will only be a problem between the user and the company that provided the survey, not between the users. Sharing survey results may also run into the issue of confidentiality, which means we should give the user the option to share their results or not. If the user rejects, then he or she should suffer a trade off of not being able to view the statistics.

Another functionality that can add collaborative support is the option to find surveys that a user's friends had taken. This also falls into the remote asynchronous communication and coordination quadrant because the user can do this anytime and anywhere. The goal is to help users find surveys they want to take. People are more inclined to take a survey if their friends have also taken it due to group effect. The problem is that some people might not qualify for their friends' surveys, so our app must carefully determine what surveys to share.

If the app were to include the company aspect of creating surveys and analyzing surveys, then there would also be a collaborative environment in the form of one-to-many question and feedback. This is the backbone of any survey, but our app focuses on the users taking the survey.

Jeffrey Butterfield - 4/14/2014 15:40:22

Our app tracks student participation in a classroom by having each student’s device listen for when that student talks for a sufficient period of time to be considered a participation event. While this involves a form of interaction between people that might not traditionally be considered an example of “collaboration” between users, the app does depend on different people for it to be functional, so those parts that do involve multiple people can be considered collaboration. The “work” in this case is to track participation, and this requires all students being tracked to be involved to accurately accomplish this task.

This application falls into the same-time/same-place quadrant of the matrix model for group-supported work. The same-place row is appropriate for describing the interactions involved because it assumes the classroom setting is traditional and not one that uses remote conference technology to teach many students in disparate locations (though the app could theoretically be expanded to work for same-time/different place). The same-time row is necessary because the vocal participation our app tracks (which comes in the form of asking or answering questions or otherwise contributing to a real-time discussion) could never be effectively carried out in an asynchronous fashion.

The primary goals of collaboration are to allow all students to participate as they normally would (free from the distraction of recording participation events themselves) while creating accurate statistics on who is participating. We have aimed for the app to be an invisible aid for the teacher to better understand who is participating in the classroom, so any extra social media component would probably work against this goal.

The technical challenges of documenting this collaboration of students to discussion is achieving accurate results. Classrooms can get loud, students might talk at the same time, and one student’s participation might be detected by multiple devices. To account for all these factors, we must implement algorithms for comparing the readings of different devices in order to give the actual participant credit for his or her participation. The major social challenges are making students and teachers comfortable with the inclusion of technology in the classroom and the fact that devices are “listening” to students speak. While our app does not write any of the auditory information to disk or send it over a network, the device’s microphone is indeed activated and processing the surrounding noise for participation events.

Jimmy Bao - 4/14/2014 15:43:54

My group's application, Curtain Call, does not intend to involve any multi-user aspects. We originally intended to allow users to share scripts or even have director/actors settings where a director can make changes to the main script and all actors that are involved in the play will see the director's changes. However, after our contextual inquiry assignment, we found that script sharing would not be beneficial. We originally thought we'd make the actor's life a bit easier by allowing every actor to record *just* his or her lines and then share those with the other actors, but the actors we interviewed said that reading other people's lines was actually part of the learning process. They said that every actor pretty much should and does come to know basically every line and every cue. That's what makes the actual performance so smooth since they know everything and not just their own.

As of right now, we're not currently intending to support any collaboration between users or social media participation as we feel it isn't very necessary for the application we plan on developing. It's meant to be a really robust replacement for the voice memos that actors currently use.

Everardo Barriga - 4/14/2014 15:44:16

I think by adding users the ability to record themselves and then be able to share that recording with other users you could really enhance the piano practicing experience. It would behave similarly to a review based interaction but rather users will be able to provide feedback on other users piano playing and could potentially get together to collaborate on a piece together.

I think this interaction lies in the communication + coordination quadrant of the time/space matrix because it is similar to a bulletin board or a blog in that you post your content which in this case would be your piano piece and then people can come and look at the piece or comment to help you make it even better.

The primary goal of this multi-user interaction is that users will be able to comment and perhaps give advice to other users on how to make their piece better which would further enhance the “practicing” experience.

A major challenge will be quality control and the validity of the user and their respective comment. Also a nice feature would be to let users comment only if they themselves have posted a piece and so that having that structure could be challenging to implement.

Sangeetha Alagappan - 4/14/2014 15:58:37

Currently, our application doesn’t have any functionality for multi-user collaboration or social media participation. While we have plans to implement a share intent so that users can share their compositions and projects on several social media platforms and text messaging, it would entail a user merely sharing his/her work with others with no collaboration. As our application is geared towards amateur musicians who like to compose their own music, it can greatly benefit from incorporating multi-user collaboration (by allowing multiple users to work on a single project, allowing remixes of tracks by other users, allow messaging between users, allowing users to share tracks with other musicians to incorporate into their own music). Music composition is often enhanced with input from a variety of sources and making the beat composition process collaborative would make our application a great learning experience and could produce incredible experiments and techniques, and great music.

As a music composition application, we aren’t focused on real-time results and would much rather enhance collaboration irrespective of time and location. So our application would be performing an asynchronous distributed task, falling into the asynchronous, remote quadrant of communication and coordination. We would like users to share music with each other, collaborate on projects, create remixes from any place at any time.

The primary goal of collaboration would be to form an online learning community to help our users (who are amateur musicians) make better music (by themselves as well as with other users). As the reading highlights, a collaborative community can help increase performance and knowledge as has been seen with learning communities at schools and universities. Another primary goal would be increasing creativity - collaboration fosters discussion and novel ideas (as has been seen with sites like YouTube).

If we were to develop our application to support multi-user collaboration, we would be faced with a number of challenges. One technical challenge would be with sharing music files quickly and effectively without loss of quality in the compression process. Sharing and collaborating on music has always been a bit of a grey area in terms of intellectual property rights as well and might pose a challenge to open collaboration on tracks. We will also face the challenge of version control when it comes to allowing remixes and multiple users working on the same project. Allowing users to send messages to each other come with a variety of social challenges - avoiding spam, predators and unwanted communication.

Stephanie Ku - 4/14/2014 16:00:21

For our application Spartito, the music assistant for piano players, we currently have no plans to integrate social media or any form of collaboration between users. However, if we were to do so, I believe that there can be a few social features that enhance a user’s experience.

Firstly, Spartito allows users to annotate their sheet music with the option of displaying or not displaying their annotations while playing their music. To enhance user experience, we can allow multiple users (other users that the main user has ‘friend’ed) to annotate the same piece of sheet music. We can then give the user the option to show certain annotations by only a particular user, or show annotations by all users. For the latter, the annotations can be colorized by user such that each user’s annotations can be easily distinguished. This feature would fall under the Same Place/Different Time quadrant, as users are able to annotate the same sheet in their own time.

The primary goal would be for the user to learn about how to play the particular sheet of music. By being able to see how other users’ interpret the piece, the current user can then make artistic choices as to how they want to play their music. Similarly, if the user has shared this piece of music with their piano teacher, the piano teacher can edit, change, or suggest further annotations. This way, the user can learn and be easily informed in the same space (the music sheet), but both the user and teacher can annotate in their own time without having to both be physically present.

The main technical challenge of our application has more to do with our music-tracking algorithm. While this new feature of social annotation will be difficult, I believe that is implementable within our time frame. Technically, I think that we can implement this by simply saving each user’s annotations as a jpg (which it is currently implemented as for single user). We can then ‘connect’ each user through the music sheet, and display the other user’s annotations if chosen (or if all selected, we just overlay all the jpgs on top of one another). I think it will be challenging to create incentive for users to help one another out with annotations. However, if we can overcome this, I believe this feature will be very successful.

Justin Chan - 4/14/2014 16:02:54

The Team Awesome application (as it stands) allows you to share your recordings with your friends, presumably so they can listen and evaluate your speech for you. This sharing can be done through Facebook, messaging, and any other relevant social media applications. We anticipate these collaborations to be remote – after all, the whole point of social media is that they take place in virtual networks. We also anticipate these collaborations to be asynchronous – this will allow for better quality and quantity in feedback because others can listen to the speech on their own time and make comments. As I said before, the main goal of collaboration in this app is to give your friends a chance to listen and evaluate your speech for you. In the context of public speaking, it is uniquely very difficult to evaluate yourself – hence, giving others the opportunity to can only serve to help.

In terms of challenges our application faces, we anticipate that the actual sharing on social media might be a challenge. People may not be willing to share on Facebook a recording of their speech, especially if they perceive that their speech is subpar. There is a tendency for people to “curate” their social media profiles, making sure only the “best” stories make it. Sure, they might agree to post a video of them doing a decent cover of a song, one where they’ll probably heap tons of likes and praise from their friends (free ego boost to boot!). But a speech in which they are inherently looking for improvements? Might have to think twice…

A good way to get around this is to have these “speech shares” through private messages – hence, you still get to “share” with your friends, but you just do it individually instead.

Sol Han - 4/14/2014 16:07:40

Our application, Curtain Call, does not currently involve any form of collaboration between users or social media participation. That said, however, it is easy to see ways in which we can incorporate multi-user aspects into our app. An obvious method of collaboration would involve allowing co-actors to share a script over the app, so that they can each record their own lines for others to listen to and rehearse with.

The above example would fall into the different-time/different-space quadrant in the time-space matrix; this is because the script and its associated audio recordings would be shared remotely, and users would be adding new recordings for their character at their convenience (though our app could theoretically fit any of the other quadrants, depending on our implementation of the collaboration feature). Because our app revolves around scripts, which will often involve multiple people, it follows that the primary goal of collaboration in our app is to enhance the rehearsal process by allowing different actors to practice together even in different times and spaces; being able to hear one's co-actors recorded voices can make rehearsal more faithful to the actual performance.

Implementing a script-sharing feature would pose some technical and social challenges. On the technical side, we will need to consider the size of the audio recording files and whether our app is scalable enough to handle the sharing of these files to other users. Because our current design for Curtain Call only makes a distinction between the user's (Me) lines and other (Them) lines, we would additionally have to modify the design so that the app can recognize multiple characters. In terms of social challenges, we'd have to consider the responsibility of users to record their characters' lines so others can practice. For example, who is responsible for recording a particular character's line if that character's actor is unable to access the app? It may prove beneficial to include communication methods within the app (such as chat boxes or annotations) so collaboration among actors is more streamlined.

Justin MacMillin - 4/14/2014 16:12:57

1. Our application, Cook Buddy, does involve interaction between users. Cook Buddy is a cooking application that helps users go through a recipe hands free. The user to user interaction comes from sharing recipes with others. Our application allows the user to call or text the recipe author in case they have questions while cooking. They are able to do this because Cook Buddy only grabs recipes from people in the user’s phone book. This interaction is in the bottom right quadrant of the time-space matrix - “Communication + coordination.” Users are not directly interacting with each other while using the majority of the application, unless they need to call/text for help. The primary goals of collaboration in our application is so that users have a wide range of recipes varying significantly by preparation time. The more people that contribute, the better the app helps everyone else because everyone has more options. There are not significant technical problems our application would face, it is easy to add a recipe and the sharing happens automatically. Our application will face some social struggles because it is not easy to get users to contribute to the overall success of the application by adding recipes. At the end of the day, there is little incentive for them to post their own recipes except for if they want to keep them all on the app (instead of using multiple cookbooks) or, of course, use voice commands.

2. Our application could be improved by adding support for multi-user collaborations on certain recipes. For example, there would be a generic recipe like spaghetti with meatballs and from there various users could suggest to each other various spices/meats/sauces to use to make the recipe taste better or just for the sake of variety. In addition there might be a chat room or something similar for a specific recipe for people who would like to communicate with more than their friends. This type of social interaction lies in the bottom left quadrant of the time-space matrix - “Remote interactions.” This idea would create more diversity in foods that people could make on the app. It also would encourage interaction through collaboration, especially for those who become interested in cooking as a result of using the app (or of course those who already are interested in cooking, although those are not our target users). The main issue with this would be technical problems we would experience editing the same page over multiple users. Another idea we had was to have ranked recipes from people all over the world. There would be a section of the application where people can post their recipes (possibly by type of food) and other people could rank/vote on them from there (similar to reddit). This feature would also be in the lower left quadrant of the time-space matrix called “Remote interactions.” There would be few issues with this feature beyond the technical implementations of the feature itself. Our application would have to become popular for people to decide to use this feature of the application. Voting features always require a large user base and large user participation. It would be difficult to encourage people to check the voting pages often. Even though they might use the app whenever they cook, participation will be a different beast.

Allison Leong - 4/14/2014 16:22:40

Our project (CookBuddy recipe sharing app) involves collaboration between users and social media participation. The application falls into the "different time, different place" quadrant of the time-space matrix. Users upload personal recipes at their own convenience and these recipes are accessed by friends and family at a later time. In instances where a recipe includes an unclear instruction, a user may make a phone call to the recipe creator in order to clarify the meaning of the instruction. It is only in this instance that our app falls into the "different place, same time" quadrant of the time-space matrix. The primary goal of the collaboration is to foster an online community where members can share recipes that are tried and true with one another. Most likely, the online community will be of like-minded novice cooks, who are eager to learn new simple recipes from their peers. The technical challenges are relatively straightforward. The application must store the data that is uploaded by users so that other users may access the data at a later point in time. Some of the social challenges include privacy and determining who the appropriate audience is for each recipe. Our recipes include call-the-author functionality, but we do not want to overwhelm recipe authors with phone calls, especially not at dinner time. For these issues of privacy, we hope that our users will abide by every day guidelines of social interaction.

Anthony Sutardja - 4/14/2014 16:26:34

Our application does not involve any collaboration between users and does not utilize social media participation. The purpose of our application is to help pianists improve their musical abilities relying on themselves and computer-assisted software to determine accuracy and maintaining practice time. I can think of two ways how we could expand this to collaboration and social participation.

For collaboration, the practicing pianist may find it useful to collaborate with other pianists on their past practice sessions. A user should be able to share a particular practice session that has been recorded for other pianists to listen and give feedback. This would fit into the "asynchronous distributed interfaces" quadrant (communication and coordination) because the task of giving feedback to the user can take place from anywhere and at anytime. The ultimate goal of collaborating about an individual's practice session would be to get different perspectives on improving the individual's practice efforts. A major social challenge to this is getting the right type of feedback. Some pianists may be just beginning and may get feedback from advanced musicians that have a more developed set of jargon, which would be rather unhelpful to a beginner. Likewise, a professional musician seeking professional feedback may get feedback from a novice that he/she may not want to hear about. A major technological challenge would be handling how this feedback system would scale. If 1000 piano players gave feedback on a single practice session, this would overwhelm the user with feedback. Rather, the server should only make some practice sessions visible to potential commenters to limit the number of people who provide feedback.

For social participation, we could possibly game-ify our application such that the number of hours spent practicing can be correlated to a local leaderboard ranking. This again would fit into the "asynchronous distributed interfaces" quadrant where the users do not necessarily have to be engaging at the same time or place. Rather, the users are trying to achieve ranking on their own time. A major social challenge would to limit cheating. Some users may just log practice sessions for the sake of being at the top of the leaderboards. This could be mitigated by analyzing if the practice session actually took place with the microphone. A major technological challenge would be scaling (again). The amount of users that might participate on a global leaderboard may overwhelm tracking statistics (as well as make the user seem insignificant).

Haley Rowland - 4/14/2014 16:33:00

My group's application, Curtain Call, does not currently involve collaboration or communication between users; the app is to be used exclusively by one user. While it might be nice to be able to share recordings of scripts between users, the purpose of the app is to help actors memorize their lines. Speaking the script aloud (while recording it) is considered a productive part of the process of memorization. Because of the "My line" and "Their line" recording methods, sharing recordings wouldn't be feasible because two actors would most likely not have the same lines. However, we could imagine a situation in which there is an understudy for a certain role, so two actors would have the same lines. If they wish to be able to share the script, changes made by any participating party should be reflected across all the copies of the recording, if a user chooses to accept those changes. This would be a remote and asynchronous interaction, so it would fall under the “Communication and Coordination” quadrant.

Another potential collaboration between users might look like an interaction between a director and an actor. Say the director wanted to change the text of the script, they could potentially send out notifications to their actors through the app, and users could edit their recording to reflect that change. This director-actor interaction would again fall under the "Communication and Coordination" quadrant because this interaction would be remote and asynchronous.

Vinit Nayak - 4/14/2014 16:33:09

No, our application does not involve any form of collaboration. It is meant to optimize time an individual spends on their own when they have to memorize lines.

We could integrate social media such as Facebook or file sharing applications such as dropbox to share what the users create in their individual applications or to publicly display achievements regarding how much of a certain piece they have memorized so far. File sharing could be helpful so only one user will need to record the speech or play and then can share it w/ others.

If our application had this feature, then it would fall into "Different Place/Different Time" category (bottom right). The collaboration between the users of the app would not need to be face-to-face since the material transferred would be for individual use only. There is not much incentive to do this for our application, since many of the users want to record the files themselves to help w/ the memorization.

There are not many technical challenges, since it would simply require integration with already present and developed SDKs/APIs.

Seyedshahin Ashrafzadeh - 4/14/2014 16:38:40

My group's project for the class is to make a music journal app for piano players that keeps track of the user's practices and give him/her live feedback on his/her tempo. At this point, the app does not have any multi-user aspect to it. However, with the success and growth of our app, I can imagine to add the social networking aspect to it. Based on the main functionality of our app (journaling and live feedback), two users do not necessarily have to be at the same time and place to practice. As a result, our app corresponds to Different Time/Different Place (remote asynchronous) quadrant. Within the scope of this social media participation, users are able to connect with their friends and community of interest (or community of practice) to share their achievements and get feedback from them on a song that they practiced. They can create competition among themselves based on the scores that they get practicing songs or they can share the history of their practice routines to get a sense of achievement from their peers. This model of collaboration is called online communities. However, according to the article, developing successful online communities and networks are not easy. This community must deal with rude behaviors, off topic comments, and provide members with norms of behavior. Some threats to this community are disruptive behaviors, illegal activities, and invasion of privacy. Therefore, the policies of this online community should address these issues. From the technical side, it should be simple so a large number of users be able to participate. It should be easily scalable to large number of participants. In case of rapid expansion, the moderator of the community has to be able to split the community into more focused groups to avoid overwhelming the participants with many detail. It needs to be able to direct the participants to the right content.

Robin Sylvan - 4/14/2014 16:46:05

Our application currently is only designed to help a user play music matching the pace of their run, and track their individual running progress – we don't plan on implementing a social media interface during this semester. A multi-user aspect we could add in the future would be the ability to share information about their runs and progress over time with their friends through an asynchronious distributed interface – different time, different place on the time-space matrix. The primary goals of collaboration would be for friends working as a community: supporting and congratulating each other on their progress in a health-positive environment. Other friends may also be competing with each other to see who has been running the most or the fastest. One of the first challenges we would face in social involvement would be deciding how we moved to social media – creating our own platform for viewing others stats with our own account system, or trying to work with other forms of social integration (i.e. Facebook posts). If we were to use a social media method such as Facebook posts, we would need to balance the number of posts to not make users feel spammed, while at the same time providing helpful information to their friends. Another issue we may run into with the social aspect might be users readiness to share their fitness information with their peers. Many people just getting into exercise may feel ashamed at some of their initial statistics. Also, people may not want to share their stats as to not try to brag about their level of fitness, something like an achievement system based on improvement instead of sharing run specifics could help these users feel more comfortable.

Hao-Wei Lin - 4/14/2014 16:48:25

My class project (Melodious Minds) doesn't really involve any form of collaboration between users or social media participation. However, it is possible to implement such features into our application, say, through allowing users of the application to post and share their music creations on a platform. If that were the case, the application would fall into the "different time, different space" of the time-space matrix, since a common platform is shared with users' creation at different place and at different times.

If we do have the above features, the primary goal of participation in our app would be to have users benefit from learning the music creation of other users and from gaining recognition through his/her own creation (even better if we have the "like" feature implemented). To have these features succeed, we do have to overcome the issue of copyright. How do one preserve his/her originality once the music is created? How do we even know if one is copying his/her "creation" from an existing piece that was not widely recognized? These are all social challenges we need to consider. Technically, we also need to figure out whether or not we want to create an internal storage whenever the user creates something.

Matthew Deng - 4/14/2014 16:49:48

Our application does not particularly use multi-user collaboration (I am assuming that sharing the final product of the app between users does not count). I believe that we could enhance our application by adding a feature to intake different people simultaneously and interpret them as different beat, separating them and transcribing them separately. This would fall under the same place, same time quadrant in the time-space matrix, in a conference manner such that multiple users are contributing to the creation of the beat. The primary goal of this group interaction is to allow for multiple people to create a more complicated beat than what just an individual could, much like how the different drums contribute to a drum set. The major challenges that our app has to face when dealing with this group participation is 1) to differentiate one person's tapping from another's, and 2) to be able to filter overlapping beats. After dealing with these issues, the rest of the app should not differ too much from our original application.

Will Tang - 4/14/2014 16:50:35

While not currently a definite plan in our application design, social media integration does fit in very well with the information generated by our app. As was mentioned by one of our classmates during our interactive prototype presentation, some users may appreciate the ability to share their workout statistics on Facebook or Twitter, or even send them as an email attachment to a personal trainer. User interaction for our application would occur in the different-time/different-place quadrant of the time-space matrix. Users would first log information during their workouts, and choose to share their workout information on social media platforms upon completion of their workout. An additional feature that we could support would be feedback, where others can comment on workouts and the user would receive these comments within the app. The goal of this feature would be to provide feedback to the user about their workout habits and practices, or simply to provide motivation. A major challenge of sharing workout information on social media would be privacy. A user may not want specific people to know what their workout habits are, or how they can only bench the bar. In addition, some users may spam their Facebook/Twitter feeds with their workout statistics, which may be annoying for others. These are not hard problems to fix, however, as most social media platforms support private sharing and blocking. Ultimately, these problems and their solutions already exist. If a Facebook user decides that he's tired of seeing the same guy who post selfies at the gym on his Facebook feed every day, he can simply unsubscribe.

Max Dougherty - 4/14/2014 16:51:59

StatThat is an application which allows a single user to record and manage statistics for a team. Currently the application does not support any cross-user or cross-team actions. However, the application could feasibly allow shared sport statistic recording between users. In such a situation, the application would fall under “Communication + Coordination”, as recording of events for a single shared team may occur at different times and locations. This collaborative stat recording could be used to increase the fidelity of the found statistics and fill in gaps where one may have missed an event. It would also allow anyone with the stat taking app to record stats for a team and have it shared to a common resource. An immediate challenge to consider is the security of information with multiple collaborators. The application must appropriately aggregate information from multiple sources, but have the ability to remove committed stats (much like git). Additionally, the ability to share a team between users must be protected and would likely function like permissions on google docs.

Bryan Sieber - 4/14/2014 16:52:20

Our application, Cluz, is a geocaching app that helps friends and strangers in their struggles to locate a cache; users are allowed to place audio tags at their exact location for other individuals to hear in the future. In the Time/Space Matrix, our application mainly falls into the category of Different Time (asynchronous) and Same Place (co-located) and therefore is Continuous Task. Geocaching is when individuals place caches (containers) and then inform other individuals of the cache with its GPS coordinates. Inside the caches is usually a “Log” to see who has been there and at what times, and there could also be “white elephant” trades. In Cluz, the primary purpose is to aid other users in their search for geocaches. Sometimes geocaching can be super difficult and caches can be well hidden. We want to make geocaching fun and easy for everyone. The tags will be placed publically or privately at GPS coordinates and can only be viewed at those coordinates. The clues from the tags could be puzzles, directions, motivational, or anything that the user wants to say. The major challenges to making this a possibility is dealing with the “locked” element based on the GPS coordinates. If the cache is in a location without Wi-Fi or 3G/4G how could one place, or hear a tag? Potentially, a work around would be allowing the user to use the app offline and allow tags to be viewable offline, but still keep track of the GPS coordinates from the system; also, a way to work around the placement would be to allow the tags to be queued onto a system and saved onto the local machine until the user regains an internet connection where the information would be sent out to a DB and known to others (if this does happen it would also be beneficial to inform the users that there was no connection so the tag would have a warning in advance to allow it to be downloaded). Another technical challenge would be the database and storing all the tags and user information. One social challenge could be that we are entrusting the users to be helpful with these audio tags, there is the possibility of potentially targeted bullying, slurs, and other unjust sayings. These sayings would be impossible for us to find, unless we implemented a rating or moderator approval.

Doug Cook - 4/14/2014 16:53:29

Our application (Group Melodious Minds) facilitates collaboration in the form of shared music compositions. This is accomplished by outputting PDFs of sheet music to be shared through email and Android messages. Production of sheet music in groups would be asynchronous because our app currently has no real-time collaboration tools. The app falls into the lower right quadrant of the time-space matrix (different time, different place). In terms of Schneiderman and Plaisant’s chapter, our app’s primary goals fall into the “lecture and demo” and “collaboratories” categories. The “lecture and demo” case arises from our app’s ability to generate content at a time and place different from where it’s needed. The “collaboratory” use-case occurs when users share and contribute to unique scores and arrangements by simply playing their instrument(s) and emailing the results.

To succeed in the social domain, users must actually find one another and set up communication in an environment outside of our app. It has no built-in social network or communication functionality so this is a heavy burden to finding collaborators. Challenges in the technical domain include formatting and protocol issues. Our app must overcome the issue of sharing projects between distinct devices in a way that preserves the music. PDFs are great for print and read-only applications but we need other formats to support further editing. Sticking with email as the only protocol for sharing is also bound to slow down collaboration. In the future we might incorporate a means of signing in to the same workspace on multiple devices so that it’s no longer necessary to leave our app and wait on mail services.

Alexander Chen - 4/14/2014 16:53:38

Yes, I do have some collaboration between users. The users will be able to share music in the different time, different place quadrant. This appears to be the least restrictive quadrant. Users don’t need to arrange for them to work together at the same time, nor do they have to be in the same vicinity to collaborate. Instead, they can choose a time which is convenient to look at updates from their friends. The place in which they do so is irrelevant.

At this moment our application seeks to allow users to share pdfs of beats that are generated during the music making process. These pdfs of the transcription can then be emailed to the author’s friends and family for review and feedback. This is the chosen method because email is the most widely used asynchronous distributed interface.

Some obstacles that we have to deal with include the ability to integrate with the email application- or at least create an intent to pass the pdf to the email client on the phone. Another obstacle is catering to many different screen sizes. We envision that the pdf generation algorithm would output something that looks good on a mid size tablet, but not so much on a smaller smartphone. Perhaps we could offer many different output sizes, or perhaps email a file containing the project to let the recipient generate the pdf on their own device.

In addition to the device, we also have platform compatibility issues with users who might be using an iProduct, Windows Phone, or Blackberry. This is before we consider users with desktop or laptops running other operating systems. Unfortunately, these people will be unable to use the application.

In the future, perhaps we could let users share their beats and projects instead of just the transcriptions. This would still be different time, different place. Users don’t need to collaborate on the beats at the same time for this to work. Another feature would be live beat remix sessions where the users would have to work at the same time, but different place. The users would communicate via chat and could set “record” sessions where both of their beats are recorded into one track.

Prashan Dharmasena - 4/14/2014 16:56:28

Our application, CookBuddy, encourages users to share their recipes with their friends and allows you to view recipes posted by other people in your contact list. It falls into the Communication + Coordination quadrant, as it is essentially a bulletin board for recipes. The goal of collaboration in our app is to help encourage novice cooks to actively cook and get better by trying out recipes that they know are good (ex: family recipes). We also want to encourage users to try out new recipes and share them with their friends. Through our "call the author" feature, we want novices to feel comfortable trying new recipes out and calling the author if they need help. Some challenges we must overcome is making the creation of a recipe easy enough that a user will want to do it. If the process is too long or too complicated, users won't feel compelled to share their recipes. Some people might also feel too shy or ashamed to call for help if they need it. Others might be intimidated by the quality of other recipes and not want to post their own recipes.

Steven Wu - 4/14/2014 17:05:32

Our application, CookEase, notifies the user and his friends to increase his productivity while food in the kitchen is cooking. In terms of the time/space grouping, CookEase fits in the quadrant of different-time and different-place. The application takes into the account of communicating with your roommates and coordination of who does what. The premise behind collaboration and participation in the application is to figure out which roommate does what in the cooking process. This requires a pipelining structure where person A begins something and person B finishes the activity in which person A has started. As for social challenges of our application we had originally considered ways of communicating with your friends and roommates who can pick up the cooking activity but this largely is dependent on whether or not they had the smartphone application. But instead, we decided to work around this by pulling contacts directly out the user's phone to circumvent the issue of having many users needing to adopt the application. We find it that the text message notification system works better as this would seamlessly integrate into a tech-savvy household. A technical challenge we must overcome is the machine learning algorithms that would learn how to pick up kitchen sounds and properly detect when an activity has finished since that is the main idea behind our application.

Tristan Jones - 4/14/2014 17:06:21

Our app currently does not involve any multi-user aspects, since practicing music has strong individual components. We are targeting the audience that practices alone since it is much easier to analyze sound from a technical side. Musicians have mastered their pieces alone for many years so we don't see a strong incentive to add or create a social aspect to our application.

One way we could add a "social" feature is to add a leaderboard of who practices the most. It could include a users facebook friends and a global leaderboard. This would fall into the "different-time, different-place" part of the spacetime matrix. The primary goal of collaboration is to let users see how they rank among their peers and motivate them to practice harder. This is known as gamification. Some major challenges we have to overcome is to encourage people to share their practice history with their friends, implement facebook login, and find a way to prevent cheaters from posting fake high scores. We most likely aren't adding social features to a piano practice app so this discussion is unnecessary.

Patrick Lin - 4/14/2014 17:07:59

Our application, Wordtastic, a children’s vocabulary building game, currently does not involve social media but does require some form of collaboration between parents and children. The primary feature of our app, aside from the use of flashcard-esque gameplay, is the ability to customize a curriculum by allowing users to create their own cards and pick their own words. Since we are targeting young (around 5 years old) children, it is expected that parents will be the ones responsible for creating these custom decks in advance before they are played, at a different time and place (coordination). Younger children may also require parental assistance to set up and facilitate gameplay (e.g. press the mic button, prompt the child for a response to the picture) during a round, which requires side-by-side synchronous action (same time, same place).

The goal of implementing these features is to encourage parent-child interaction throughout the educational process. Allowing the games to be flexible means parents can prioritize teaching words they feel their children should know or are interested in. This requires our app to integrate with Android’s image gallery and the phone camera to allow for custom flashcard creation, as well as back-end database support to hold custom cards and decks. Social challenges would be incentivizing parents to play an active role and actually make use of the feature to create custom cards rather than just playing default decks. There is also a chance that parents would prefer to use the app as a distraction and hand off the device to the child rather than playing with him or her. Some factors are simply parenting styles and beyond our control, but we could consider adding more features to flesh out some sort of two-player gameplay. Our main focus should be on keeping the app accessible for both young children and parents for the portions they use.

Insuk Lee - 4/14/2014 17:08:28

Our current application does not involve any collaboration between users or social media participation. However, we can add this social component by creating a community of piano players who want to encourage each other to get better. By expanding the music journaling aspect of our application and sharing the individual goals to be met with the community, the users will be more motivated to practice harder and meet their goals. We can also create a mobile forum where the users can share tips and insights with others to create a more collaborative environment.

This would fall into "Communication and Collaboration" (different time, different location) quadrant of the time-space matrix because users all over the world, with different time constraints, will be logging into our virtual social community. As talked about in the previous paragraph, the primary goal of collaboration in our app would be to foster friendly competition by sharing their practice goals and progress and to encourage a collaborative spirit by discussing helpful tips and insights amongst all individuals of our community. The first challenge our application faces is to garner the user base. A prosperous community can only come about if there were a lot of contributing members in it, and therefore we would have to make the application as user-friendly as possible and market our application well to achieve the number of downloads we want. Technically, as emerging Android developers, it would take us some time to figure out how to make this a user-friendly social app - more complex development is required for us to aggregate and direct all the data that would come out of users' usage, in addition to making it scalable in the future.

Christopher Echanique - 4/14/2014 17:09:45

At the moment, our app does not support collaboration between users or social media participation. However, we do have a feature that involves users exporting music sheets with the intention of sharing them with other musicians outside of the mobile application. Hypothetically, we could create user profiles that sync to social media platforms like Facebook and Twitter in order to allow the users to share and edit music sheets with other musicians both through the app and on these platforms. This task would fall under the communication and coordination quadrant since participation between users is both asynchronous and remote. The main challenge in implementing this is in the editing feature. Since the collaboration is asynchronous, there is a possibility of users editing the music sheets simultaneously. This can cause conflicts to the document. A way to mitigate this issue is to lock the document during editing so that other users don’t edit it at the same time.

Meghana Seshadri - 4/14/2014 17:10:35

Our application, Wordtastic, is an educational gaming application that focuses on giving young children a more enriching and entertaining educational tool. While, our process flows focus on increasing parent-child interaction, this application can act as a stand-alone interface that solely the child or parent is interacts with.

(a) The quadrant of the time-space matrix that our application falls into is primarily same time, same place, or “Face-To-Face Interactions”, but it can also fall into the different time, different place, or “Communication + Coordination”, quadrant. Because our application primarily focuses on increasing interaction between parents and their children, it falls mainly in the same time, same place quadrant. However, for the cases where the parent or child are solely using the application, then it would fall into the different time, different place quadrant.

(b) Some primary goals of collaboration or participation that are visible in our application are focused partnerships, as well as some entertainment focused goals such as challenging contests and playful and theatrical experiences. Focused partnerships are collaborations between two or three people who need each other to complete a task. In order to get the most out of our application’s gameplay processes, a parent and a child need each other to complete them. Because our application is a game in its inherent sense, we also focus on making sure that the game provides challenging contests for the child as well as an entertaining and playful experience so that they don’t grow bored of the application.

(c) In the process of building our application, there are a few major challenges, both technical and social that our application must overcome to succeed. The technical major challenges include: (1) building a stable and efficient database that will contain the already existing flash cards and decks that come pre-installed in the application; (2) building a robust voice recognition system that will work even in the presence of other external noises. The social challenges include: (1) finding ways to maintain interaction between parents and their children all throughout using the application and making sure that connection doesn’t break at any point during gameplay; (2) encouraging parents to maintain an active role in creating and customizing card decks; (c) supervising younger children throughout gameplay, especially in regards to prompting responses and knowledge of which buttons to press.

Daphne Hsu - 4/14/2014 17:11:41

Our application (Stat That) doesn't involve collaboration between users or social media participation other than the user being able to share stats after a game. We could enhance our application to having more than one stat keeper per game. If there are 3 stat keepers, each can record stats for a game. If there are at least 2 users recording the same stat, then the stat is "verified" and recorded. The goal of this approach is for stats to be more accurate. Another thing we can do is have one user record offensive stats, and one user record defensive stats. These stats are then displayed on the same page in the order in which they were recorded. The goal of this is to lessen the work load of one stats keeper, allowing for each stats keeper to track stats better and not miss anything. I think these two scenarios can take place under either the same place/ same time quadrant. All users must be present at the same basketball game at the same time. The major challenges the app has to overcome to succeed is if 10 people want to help record stats for one game. It would be hard to determine who is recording what.

Diana Lu - 4/14/2014 17:16:02

Our application does involve collaboration between users, but so far doesn't incorporate any social media participation. For the most part, our application falls into the quadrant of the time-space matrix that is "Different place, Different time" that requires communication and coordination. I believe it falls into this quadrant because there is a disconnect between the time one user leaves a tag at a specified location and when another user can view the tag. The primary goals in terms of collaboration in our application is to allow users to leave private sound tags for just a subset of friends, rather than making the tag public for anyone to be able to view. One of the major challenges we face with regards to this is incentivizing people to utilize sound clues while geocaching instead of leaving texts for friends or using existing geocaching applications. We want to eventually be able to integrate our application with existing geocaching applications so users can search for existing geocaching options, while also using our application as a means of making geocaching a more social activity.

Zhiyuan Xu - 4/14/2014 17:16:55

Currently, because TreadTracks is an application which focuses on the individual runner on a treadmill, our application does not involve any multi-user aspects. However, there are ways of improving the experience of our application by including such applications such as being able to share run results with friends, or being able to find treadmill running buddies. A online support community can also be created to encourage users to run more often and be healthier. These features will most likely be in the communication and coordination time quadrant, as users will be able to interact with and see messages from the past. The main goal of participation with this application will probably be to establish an online community for support. In terms of major challenges for creating a form of communication, if results were to be shared with Facebook, individuals may complain that they accidentally press the share button when they do not want it to be shared, so there must be a way of disabling the button. If some sort of internal communication platform was established, the application will have to worry about the way in which messages are passed and displayed to each user.

Peter Wysinski - 4/14/2014 17:19:28

Our current application does not have any multi-user facets. We can enhance our application by implementing the ability for users to share their practice sessions with friends. If there are two aspiring virtuosos who make a pact, the ability for them to share stats with one another would encourage them to stay on track by being accountable with one another. Such gamification of practicing would serve to motivate players to stick to their goals. When evaluating such a feature in view of the temporospatial matrix presented in Shneiderman & Plaisant the proposed feature would fall in the bottom right quadrant: Communication and Coordination. The users playing stats would be uploaded to a server and made visible to colleagues; there would also be no-need for this process to occur in real time as the stats could be uploaded and compared anytime after the practicing has occurred. The major social challenges in implementing such a stats sharing feature are that users are often hesitant to share their personal data with online services and might begin to feel discouraged once they fall behind practicing. While implementing such a feature would not be too challenging from a technical perspective, user accounts and syncing may prove to be cumbersome. Since most of the piano practice rooms we have seen are underground and lack cellular reception, we’d have to implement the ability to cache stats locally on the phone and upload them when a connection is established.

Andrew Dorsett - 4/14/2014 17:19:34

Our project currently doesn't have any collaboration between users and social media participation. We could add in an element where users are able to upload the stats they've taken to a shared site. There they could compare, analyze, and sync stats. For the most part this would fall into "Different Time, Different Place" corner of the Time/Space matrix. Our goal would most likely fall under collaboratories. It may not be possible for all stat keepers to make every game and having a central place means you can pool and combine your data. We could even expand the app to include the online community goal. It wouldn't be unreasonable to think there's interesting in having a place were fans could see stats of the players. Stats that were recorded, parsed, and uploaded by our program. A challenge I see is authentication. Making sure the people who are posting are official stat keepers. Also making sure users actually upload their stats once they've been verified.

Andrew Lee - 4/14/2014 17:25:30

Our application doesn't inherently have a multi-user component. We could augment it to allow tasks such as sharing sheet music and users' annotations for them. For example, a piano student can share their annotations for a particular piece with their piano teacher, who can in turn add their own on top.

This would fall into the "communication and coordination" quadrant, since the users are not interacting with each other in real-time and can be anywhere in the world. The primary goal would be to let users share their interpretations of pieces and learn from others as well. The main challenge is fairly straightforward: building a server to facilitate all this. This would be where users can upload/download sheet music as well as annotations. Of course, these items should be searchable as well and whatnot. In terms of social challenges, perhaps a feature to share files with only a particular set of users (like between a student and teacher) would be desired.

Another potential feature that could have social benefit is having the app track how much the user practices each section of the piece. This data could be uploaded to the server as well, which could analyze multiple users' data to determine which sections are more difficult.

Emon Motamedi - 4/14/2014 17:25:39

Our application does involve some form of collaboration between users, this collaboration is nuanced. As way of background, my application is Particip8, which allows instructors to track participation in the classroom by utilizing the microphones on the phones' of students to listen for students voices and send a participation even to the instructor's phone. From there, the instructor can view participation statistics of his students.

It is through this interaction that our application involves collaboration between users. The phones of the users are collaborating with that of the instructor to send across the necessary participation data. The instructor then likely will wait until another time and place to view the data and the additional statistics. As such, our application falls into the bottom right quadrant of the application: different time and place/remote and asynchronous. There is a chance that the instructor chooses to view the statistics from inside the same classroom but I feel it is more likely for him to do so on his own time at other location.

As the application is designed to track participation, a major goal is that the phones monitor the voices of students accurately. To this extent, a technical challenge is ensuring that the mechanism behind tracking participation is strong enough to ensure that phones do not accidentally pick up participation events of other students or just chatter among students that is not intended to be participation. The social challenge is communicating participation events to the instructor's phone and achieving support for the application among students, the first of which we have achieved and the second we have yet to address.

Aman Sufi - 4/14/2014 17:26:42

Yes, our application (Team Pesto Pasta) not only involves but relies on user interaction and participation. It falls into the quadrant of ‘Same Place, Different Time’, which is a rare trait in software, seeing as there is no section dedicated to it in the chapter. In our application, users asynchronously leave messages and tags for others to view as they approach the same area where the tags were left. Sound recordings are utilized as the medium for communication, and they can be targeted towards a specific group of friends or to all users of the application in the same area. In this way, people can create ‘social media’ type content intended for their friends to view and react to, as well as create general content for a broader audience to consume as well, such as information about locations, such as clues to the location of geocaches.

The primary goals of participation in the app in our initial product vision is to enable geocachers to find geocaches in a more social environment, where friends who have visited those areas can leave helpful clues, stories, or other information relating to the geocache via voice recording, personalized for their friends. People who wish to leave more general information may also leave public recordings, in the same way that a wiki can be updated by multiple people to reflect the information about a topic, except using voice as the medium.

Some of the major applications of our app, technically, are to allow users to preload voice recordings in areas where they will not have reception, which can sometimes be the case with geocaches, as well as to create a continuous experience, with new sound tags in the location of a user automatically alerting users as to their existence. Socially, the difficult challenges we address in our app are the ability to create personalized social content so as to engage people together on a more personal level and give them the ability to leave context (location) aware messages for the people they know so as to form a type of ‘smart’ messaging.

Namkyu Chang - 4/14/2014 17:28:19

No, our class project does not involve any form of collaboration between users and social media participation, but we could add a functionality where the user could share their last cooking statistics on social media.

This means that this interactions occurs at a different place (remote) and different time (asynchronous), meaning it's in the Communications+coordination quadrant.

By sharing their statistics, the primary goal is "lecture or demo" because it involves one person (our user) sharing information with many users at remote sites.

Some challenges that could potentially arise from this method of social media participation is etiquette and responsibility. How often should the user share their data on the social media platform so that other followers get a good grasp on the user's cooking, but isn't overwhelmed by it? Similarly, where is/isn't an appropriate place to share these information (e.g. on Facebook or LinkedIn?).

All these challenges are some that are shared by other collaboration goals, but they apply to our project as well.

Romi Phadte - 4/14/2014 18:05:27

Our project does have some user interaction by giving the user of the app the ability to send an email of his or her latex. This give the user the ability to interact with others in a group setting for collaboration purposes. However, the application doesn't have any interactions in social media or within users emulating social media. Our application would be in the different time different place quadrant in the time-space matrix. The primary interface is Collaboratories. Our app allows users to share the limited resource of our speech to equation algorithms. In order for the application to succeed we must implement a robust speech to equation algorithm that is worth sharing. Additionally, we must make sure the email interface is friction free.

The class project might allow users to record or take pictures of really complicated equations that are not recognizable or translatable by the application. Then, it can share with all users of the application and use their help to figure out what the latex is. From there the application could use that information to learn more about what the equation actually is.

This application would have collaboration and social media participation. It would still be different place different time on the matrix. The primary interface would still be Collaboratories but there would also be an online community of friends and app users to ask regarding latex to help just in case something goes wrong. Major challenges include making the speech to equation robust, getting enough users to provide for a vibrant community, ensuring that users provide useful and valuable feedback, and that the users are engaged enough to participate in online discussions. Despite such challenges these features will definitely provide for a more valuable feature set for the end consumer.

Chirag Mahapatra - 4/14/2014 20:51:26

Yes. It does involve collaboration between users. I am in the Pesto Pasta team and we are working on geo-tagging voice messages. These messages can be accessed by people by locating it on the map. Our app would fall in the different place different time part of the quadrant. There is a feature on our app which can let people access messages only if they are in the vicinity. However, this does not fit the conventional sense of same place different time quadrant.

The primary goal of the app is to help people geocache. Geocaching is a treasure hunt where you follow clues and coordinates to find a treasure. It has natural collaboration with the cache creator and the geocachers. Furthermore, if people who do find the cache may leave messages for future cachers as clues. Hence there is collaboration between past and present cachers.

The major technical challenges are: - Creating user profiles and linking it to the map interface. - Scaling the app where it can be used by thousands of people. This will be a big challenge because we aim to have public and private messages. Hence, a user might have access to a large number of messages.

The major social challenges are: - Being accepted by the geocacher community. The geocacher community is a large group which consists of over 3 million people. They are generally used to text based clues and it is unknown on how they would react to voice based clues.

Eric Hong - 4/14/2014 18:48:32

Our proposed class project - helping users listen to songs following their pace while running on the treadmill - does not involve multi-user aspects due to the time constraints in development. However, we can add multi-user interactions to enhance the app, such as sharing run results and interactive competition to match your pace to the song beat or another user's pace.

The sharing of run results would fall under the different place, different time quadrant, since a user can access the shared run results at any time after they are shared. The primary goal of this function will be to share your accomplishments with others or ask for running tips. The function can also be used in training classes to help the instructor keep track of improvements or give running homework. The major challenge of the above function is to send and receive data between phones reliably, since users might not want anyone to have access to their personal run information.

The interactive competition function would fall under the different place, same time quadrant, since users will need to have access to the app at the same time in order to compete. The primary goal of this function will be to provide a more exciting workout for the users. The major challenge of the above function is to update the app in real-time without major pauses or glitches. The interactive game will only work well if all participating parties hear the same beats at the same time.