Studio 2 Process Diary

Task list

2007-10-16T00:33:00.000+10:00

This evening I gave Long a hand finishing off the task list. He asked me to write code that let users change the name of tasks and tick tasks off when they were finished. It sounds simple but the tasks have a lot of other functionality associated with them, like drag-and-drop re-ordering and dynamic adding and removing, so it became a complicated operation.

There is a plugin for the drag-and-drop functionality, and another plugin for the click-to-edit, and they were interferring with each other. I modified the click-to-edit function so that it deactivates the other function while it is being used.

I had a lot of frustrating moments this evening when things would just not work for no apparent reason, but I've made it through in the end and got the task list completed. It's nice to use in the end. Here's a screenshot:

Error checking

2007-10-15T17:34:00.001+10:00

This morning Long, Justin and I went through the website and created a list of things to fix on the website.

JUSTIN
-------
1) X Duplicate document type icons for .docx, .pptx and .xlsx
2) X Fix little icons on the New Version and New Doc Comment panes
3) X Make the word 'task' and 'project' in the Welcome message detect whether to pluralise or not (copy from Docs page)
4) X Dashboard titles for My Tasks and News Feed aren't there with brand new User
5) X When creating a new user, need to add folder when they choose to add a project
6) X The default task when a new Project is created needs to be assigned to the user creating the project
7) X Sample description needs to be inserted into database when new project is created upon registering a user
8) '0 secs to go' bug with commenting system
9) On Project page, if description = '', then make it 'click here to add project description'
10) Reorder My Projects list on Dashboard to be newest to oldest

LONG
-------
1) X Login page error messages for Incorrect Email/Password
2) Project and Document history and News Feed needs to be truncatable ('Show more' button)
3) Fix commenting on project error
4) Edit tasks
5) Add tasks needs to add without a page refresh
6) Document comments box bug
7) Change powerpoint slide from 'Things to fix' to 'Improvements'
8) Restyle AutoComplete
9) Create New Project styling in IE

KEEGAN
-------
1) X Remove the numbering on document versions
2) Need to be able to select yourself when assigning a task
3) X Skip the second page of the Create Project wizard if no collaborators are added
4) Need to make News Feed recognise items since last login and not just list everything
5) Validation on Create New Document
6) create_project2.php - with collaborators bug (asks for a project name)
7) First file version with a New Document needs the new filename code
8) Update project last updated time throughout

I finished the items I was assigned. Here's what the dashboard looks like now:

Almost finished

2007-10-14T22:31:00.001+10:00

We have finished all of the main functionality of Tabletop. Tomorrow we will go through the website and write a list of things that need to be fixed. There will doubtlessly be many bugs, but we should be able to iron them all out before the presentation on Wednesday.

Javascript problem of the day.. and a solution YAY :-)

2007-10-08T21:08:00.000+10:00

This evening I have been working on the "Add a New Task" section of the project page. I copied across some code from the "Create a New Project" page, because both pages involve selecting person/s, entering a date and time. I got the calendar and time selector to work with no problems, but the autocompleter for the name input exhibited some strange behaviour. It is meant to show suggestions immediately below the input box, but it was showing them in the top corner of the page. See the screenshot below.

There is a lot of functionality on this page, and it has a huge amount of Javascript (including 7 different jQuery utilities). My first thought was that something else was interfering with the autocompleter, probably with its CSS.

But another possibility occured to me. On this page, the form is located in a DIV that is hidden until the user clicks to show it. That is different to the "Create a New Project" page where I have the autocompleter working. Maybe that difference was the reason it wasn't working. To test my theory, I stopped the DIV from being hidden and refreshed the page. Low and behold, the autocomplete suggestions were shown in the correct position:

I had identified what was causing the error. But I didn't have an adequate solution, because we can't leave that ugly form on the page when the user doesn't need to use it. I continued examining the page's behaviour and stepping through my code. I noted that when I clicked "Add a New Task", followed by "Cancel Adding Task", followed by "Add a New Task" again, the autocomplete suggestions were not displayed at all, let alone in the correct position. All the "Cancel Adding Task" link does is hide the DIV that the form is in, so once again, the problem was linked to the DIV being hidden.

That gave me an idea. Maybe I could initialise the autocomplete function whenever the form was shown, rather than when the page was loaded. So I changed this line of code:

$(document).ready(function() {
$("div#addnewtask input.person").autocomplete(...);
});

to this:

$("button#addtask").click(function() {
$("div#addnewtask input.person").autocomplete(...);
});

And it worked! Hoorah!

Uploading new file versions and commenting on them

2007-10-05T18:49:00.000+10:00

I did some work on the Documents page, so that now users can upload new versions of files and leave comments on them. I was worried that I would have difficulty getting the file upload functionality to work. We are letting users upload any type of file, and I though that would be harder than the display picture upload, which is just images. In fact, the opposite was true. We don't need to check what the file type is and so its really easy to upload files.

We have always planned to rename uploaded files in the following format: {file_version_id}.{extension}. In our original database design, we intended to save this filename in the database. But I realised that by including the file version id we are creating redundant data by storing the primary key twice. So I decided to only store the file extension. We will work out file names on the fly when we need them, by joining the file version id with the extension.

Comments on documents

2007-10-03T18:40:00.000+10:00

I wrote a little section for the Project page Long has been working on. Now people can write comments on the page. It follows the same-page AJAX functionality we have used elsewhere. I'm getting the hang of AJAX now.

Making fields autocomplete in the way users expect

2007-09-29T20:03:00.000+10:00

It is a good idea to follow usability conventions in your website, because then people will know how to use it without having to learn anything new. This evening I spent some time modifying our autocomplete function so it behaves in a way similar to other websites, gmail in particular.

The JQuery autocomplete function we are using is for the most part very good, but it had a few little quirks that I wanted to iron out so that it functioned exactly how our users would expect. It used a | as a separator, and it removed spaces in between entries. So a list of email addresses would be entered like this:

email@address.com|email2@address.com|email3@address.com

I changed the separator to a comma, and automatically added one space in between email addresses. This is what gmail does, and I think it is what our users will expect.

email@address.com, email2@address.com, email3@address.com

Bloody cache!

2007-09-28T15:58:00.000+10:00

Argh I am so annoyed. I just spent an hour trying to figure out why some of my Javascript wasn't working, and it was because the page I was working on was being read from cache so none of my changes were even being processed! On a brighter note, users can finally register new projects. I think I will come back to this on another day...

Sending email with PHP is so frustrating

2007-09-28T15:08:00.000+10:00

OK so I got the send mail function working yesterday on my home server, but now when I get to uni it doesn't work! The Uniform Server we are using doesn't let us send emails, and when we upload this website to mytabletop.com, that server will be different again. Its frustrating having to modify things so they work on different servers. I'm going to stop working on the send email function, and do it after everything else is finished and we have the website hosted on the final server. There's no point spending more time on it now.

Solution for sending email with PHP

2007-09-27T14:31:00.000+10:00

I submitted a ticket on the support desk of my web host, MD Webhosting, explaining my problem with the PHP mail() function. They told me to use PEAR:Mail to send the email instead of mail(). I tried this, and it worked. So the problem is fixed.

Problem sending email with PHP mail() function

2007-09-27T12:53:00.000+10:00

Today I have encountered a problem while trying to send emails to people who the user would like to invite to their projects. It seems that I can send emails to some addresses, like ...@keeganstreet.net and ...@readymedia.com.au, but not to gmail or hotmail accounts. I don't know why this is so I am looking into it.

Creating new projects

2007-09-26T12:41:00.000+10:00

Long, Justin and I worked all day at uni today, and got a fair bit done. I worked on the "Create a new project" page. I spent most of my time working on the part that collects data from the user, but I haven't got around to actually storing that data yet!

This page has taken quite a while to develop because I had to make an auto-complete function for the "add people to this project" field, and a clickable calendar for the project's due date. I didn't write these myself, but I had to find them and modify them to work with our product. When a user creates a project, they can invite other people to work on it as well. To do this they can either enter a list of email addresses, or when they start typing characters, suggestions of people they have worked with in the past will be shown. See the screenshot below:

Users also have the option of entering in a due date for their new projects. This is what the due date input field looks like:

The auto-complete function and calendar are both add-ons for the jQuery Javascript Library, so it was a good move by us to use this library. Modifying these pre-made components was much more efficient than trying to create our own from scratch.

Display image distortion on edit profile page

2007-09-16T19:03:00.000+10:00

I noticed that when I upload a rectangular image as a display picture, it is not resized correctly, and is distorted into a square. I stepped through my resizing algorithm, and all seemed to be OK, so I had a look at the HTML page where the image was being displayed. It turns out that the image had been resized correctly when it was uploaded, but we were then squashing it into a square shape in our style sheet:

img.avatar {
border:3px solid #1C8B35;
height:96px;
width:96px;
}

I have removed the size restriction from our CSS, and I will tell Justin and Long on Wednesday.

Not much progress this week

2007-09-12T19:12:00.000+10:00

I missed class this week for a job interview with Eclipse Group. It turned out that my interviewer, Jarrod Dumble, is one of Matt Butler's mates. I haven't made much progress with my Studio this week because of the interview and lots of work in my other subject.

I sent an email to Justin and Long to let them know I wouldn't be coming:

Hi Long & Justin,

I won't be able to come to studio today because of my job interview with Eclipse Group.

Here's my tabletop files. During the last week I have been working on the register section.

Please note that it is not working, because of a database issue. In our schema file, I forgot to make the primary keys AUTO_INCREMENT. We need to change this in our database before it will work. I have attached a new schema file and test data file which *should* work, but they are untested. Compare them with your current schema file and test data file to see what I did.

Good luck!

--
Keegan Street

President
Monash Union of Berwick Students Inc
Phone: 03 9904 7092
Mobile: 0400 188 581
Fax: 03 9904 7134
Email: president@mubs.com.au
Web: www.mubs.com.au

Proprietor
Ready Media
User focused web development
ABN: 19 640 210 286
Phone: 0400 188 581
Email: keegan@readymedia.com.au
Web: www.readymedia.com.au

Using the jQuery Javascript library

2007-09-09T14:53:00.002+10:00

After researching some different Javascript libraries and considering writing our own Javascript, our group has decided to use the jQuery Javascript library for Tabletop. This library will help speed up our development process because we won't have to write functions that other people have already written for us. The library includes things like form validation, visual effects and AJAX functions. It makes writing Javascript a lot easier. I no longer have to write this:

document.getElementById("message").innerHTML="Your changes have been saved.";

Because I can achieve the same thing with this:

$("#message").html("Your changes have been saved.");

To use a Javascript framework?

2007-08-29T11:47:00.000+10:00

I haven't been using a Javascript framework to write my AJAX, so I've been writing everything in raw Javascript. Today Justin Morris (not the Justin in our group), noticed that, and suggested I consider using a Javascript framework because it would make the coding more efficient. However using raw Javascript is a good learning experience. I will discuss this with my group members today.

Justin recommended two good Javascript frameworks:

jQuery
Prototype

AJAX on the Profile and Settings Page

2007-08-29T11:06:00.001+10:00

The Profile and Settings page is almost completely functional now. Users can change their email address, name and password. Later today they should be able to change their display pictures. I have enjoyed learning AJAX over the last few days for this page.

Using AJAX in Tabletop

2007-08-24T17:55:00.000+10:00

Early in the design stage of Tabletop we decided that we wanted it to be fast to use, and that would mean using AJAX to perform functions without loading new pages. Over the last couple of days I have been learning how to use AJAX. The best tutorial I found was at w3schools. I have been working on the "Edit Profile" page. Data is collected on a form and sent to a PHP file, which validates the data before saving it to the database. An appropriate message is shown to the user on the original page.

Combining Long's login system with Justin's timestamp formatter and my news feed

2007-08-22T17:35:00.000+10:00

Today Long, Justin and I combined what we had each been working on over the week. Long had created a login system that verified a username and password and created a session for logged in users. Justin had written a function that took a timestamp as input and gave it back in English (i.e. it turns "1185955434" into "two days ago" and "1185959034" into "next week"). I had created the dashboard page, including a news feed of recent activity and a task list. When we put them all together, here's what we got:

As you can see it is starting to look a bit nicer. We had to tweak a few things to get our work to fit together, but nothing major had to be done.

Dilemma solution

2007-08-18T13:48:00.000+10:00

I will define the difference between the way to-do list items are displayed and ordered on the dashboard and project pages.

Dashboard page

Displays only the to-do list items that are assigned to the logged in user, but for all of their projects.
Items are ordered by due date, and are categorised under the following headings: Overdue, Due Today, Due Monday, Due Tuesday, Due Wednesday, Due Thursday, Due Friday, Due Saturday, Due Sunday and Upcoming Tasks. Items without a due date are put at the bottom under the "Upcoming Tasks" heading.

Project page

Displays all of the to-do list items associated with a project, no matter which person they are assigned to. Doesn't show items from other projects.
Items are by default ordered in the order they were created, and can be re-ordered by clicking and dragging.

Here is a screenshot of the task list on the dashboard.

The dilemma of how to order items in the to-do list

2007-08-18T12:38:00.000+10:00

Due dates are optional for to-do list items in Tabletop. This is because when people work on projects, some of their tasks will have due dates and some won't, and we need to reflect this reality.

However, this introduces a challenge for our development team. If all tasks had due dates, then it would seem intuitive to order them by due date. But how do you order a list by due date when some of the items don't have one?

We have previously discussed this dilemma in our group. We noted that effective people work on important, rather than urgent, tasks first. So we decided that it is important for users to be able to re-order their to-do lists, and move the most important tasks to the top. The default order for to-do lists in Tabletop will be the order in which the items were added, not their due dates. Users will be able to drag and drop tasks into the desired order.

This introduces a problem for me today as I work on the Dashboard page. I need to collect to-do list items from all of a user's projects, and put them into a list so the user can see what to work on. I would like this list to be due-date based, so overdue tasks appear red, today's tasks are bold, etc. But I am wondering if this conflicts with our earlier decision...

Creating the skeleton

2007-08-15T19:04:00.000+10:00

Today Long, Justin and I began working on the PHP for our website. Long was mainly focusing on creating a login system with sessions. I started working on the dashboard page, which gives users an overview of their projects. I got the page to show a list of the user's projects and a News Feed of recent activity. This screen shot shows how much I got done:

I ran into my first problem with the database design today. I forgot to include a variable in the user table for last_login_date and in the to_do_list_item table for created_date. I needed these to be stored for the news feed. So I amended the schema.

Completing Process Diary

2007-08-08T16:11:00.000+10:00

Today we handed in our project proposal. Long had almost finished it, so today I wrote the technical requirements and file naming conventions, and Justin and I added the database plans and project timeline. We proof-read, edited and printed the document, and then handed it in.

Over the next week, I am going to start to write some PHP functions for the website. Justin is going to do some research into PHP and AJAX.

Reviewing the Project Scope as a Group

2007-08-01T21:43:00.000+10:00

In studio today we stepped through the process a user would go through when they used our website. We figured out a few changes I would have to make to the database. They included adding a project_description to the project table.

We also made these decisions:

When a user invites people to a project, the invitees are sent an email and have to click a confirmation link before they are added as a member of the project.
We will use automatically appearing input-text boxes (like on flickr), for users to change text on the website.
Users can drag and drop items in their to-do list to re-order them. We will save their position in the database.
When a project is created, if it has a due date we will automatically create a to-do list item called "Project due" on the due date.
Comments can be deleted NOT edited.

We want to highlight unread comments to users on our website. I think we should store an unread/read value for every user/comment combination, but Long thinks this is too inefficient. I understand that it will create a huge number of entries in our database ([C x U] x P, where C=avr no of comments in a project, U=avr no of users in a project, and P=number of projects in our database). But databases are made to handle heaps of records. Plus we will only be storing two integers and a boolean for each record so it won't be much storage space.

After class I stayed back til 8pm and made the appropriate changes to our database design. I then exported a schema and a test data insert file, and checked them for errors. I eventually got everything ironed out, so we've got a working MySQL database that is propagated with test data. We can now start writing functions as soon as we like.

Long is going to a Microsoft conference on the Gold Coast next week (lucky guy!.. except for the Microsoft part), so he is going to finish all his work by the end of the week, and that will give Justin and I a chance to go over it before the plan is due next Wednesday.

Computer-Aided Database Design

2007-07-28T16:46:00.000+10:00

After designing the database on paper, I used Database Design Studio to redo it on the computer. DDS helps create a schema with proper foreign keys and everything. This is the Entity Relationship Diagram made in DDS:

This is the Data Structure Diagram:

Designing Entity Relationship Diagram

2007-07-27T18:29:00.000+10:00

I designed a draft ERD today:

Defining the Scope of the Project

2007-07-25T18:21:00.000+10:00

In studio today we defined the scope of our project. We explained the idea to Mark and he didn't have any problems with it. I drew this as a map of our ideas:

This is my understanding of the scope of our project:
A user creates, or is invited to be a group member of, a project. The number of users working on a project is not limited. The number of projects a user can be involved in is limited to 3, or unlimited for paying users. Users can leave projects if they no longer want to be involved. If all of the users involved in a project leave the project, the project is deleted. Projects have a name and a last update time.

When a user has write permissions on a project he/she can do the following:

Invite other users to a project. They are automatically added to the project (no approval required).
Add an item to the to-do list of that project.

To-do list items have a name, a due date (optional) and person/s responsible (required for group projects, and automatically set for individual projects).
Users can set items to be either in progress or completed.

Add a document to the project (could be an image, word file, PDF, etc)

Documents must have a name. The name should be editable by any user with write access (using AJAX - similar to the status change feature on Facebook).

Documents must have at least one version, but possibly many versions uploaded by different users. Versions must have a system date. Old versions are still accessible, but can be deleted by any user with write access.

Write a comment in one of two places - on the main page of a project (where the to-do list is located), or on a document page (i.e. "I like that version you just uploaded Fred").

Comments have a time and a body. They are not sorted into threads.

When a user has read permissions on a project he/she can do the following:

View the to-do list, documents and all comments. Nothing is hidden from them, they just can't change anything or write any comments.

When a user is a member of a project (with either write access or read access), here's the added benefits they get:

They will be notified in a 'news feed' whenever a new version of a document is uploaded. The notification will remain in their 'news feed' until they open the document page.
New to-do list items will have a star next to them the first time the user sees them.
They will be notified in a 'news feed' whenever a to-do list item is assigned to them as the person responsible.
They will be notified in a 'news feed' whenever a new comment is added to a document or to the project.
New comments will have a star next to them the first time the user sees them.

Users might have a number of projects on the go at the same time, so when they log in they see a 'dashboard' page with recent info from all their projects. This is what users can do on the 'dashboard':

Create new projects or remove themselves from old projects.
View their 'news feed' containing all notifications.
See a to-do list of items they are responsible for, across all of their projects.
See a visual representation of due dates (i.e. a calendar)

We also brainstormed for names of the project. Here are some of the ideas: projector (or projectr), project now!, chalkboard and tabletop. Some other words that are related to our project that could make up part of a title are: student, schedule, learning, books, time, calendar, project, planner, desk, web, lab and table.

Over the next week I am going to design the database, Justin is going to make a Gantt chart to illustrate our project schedule, and Long is going to work on the project plan documentation.

Review of To-Do Facebook Application

2007-07-24T09:14:00.000+10:00

The description of To-Do in the Facebook Applications Directory includes a "still under development" disclaimer, so I didn't have huge expectations of it.

When you add a to-do list item, you enter a category, description, due date and priority. There is no clickable calendar in the due date field, but users can submit English answers like "tomorrow" or "Friday". A (plus) icon is used to save items, which I think is confusing for the user. To-Do is a one-page application; when the user saves a to-do list item, it is simply printed to the page. There is no calendar to visually represent due dates; dates are formatted like 07-24-07, which doesn't effectively highlight that THIS TASK IS DUE TODAY! To-Do doesn't make use of the social environment Facebook provides at all. It doesn't tell the users friends when they complete a task, or when they need help on a task, and it doesn't let users show off their achievements on their profile.

Don't set your expectations too high when using this application, or you might be disappointed.

Review of Basecamp Project Manager

2007-07-23T12:59:00.000+10:00

Basecamp is an online project manager for small businesses. It helps organisations manage their projects by creating to-do lists keeping track of what needs to be done and who is responsible, sharing files within the organisation and with external clients, recording how much time people spend on different tasks and letting team members talk on message boards.

To review Basecamp, I will set it up to help manage one of MUBS' current projects, a student to student tutoring program.

I am working on this project with the Education Officer, so to begin I clicked a tab called People, and I was able to add him to the project.

I then clicked the messages tab, and added a description of what this project actually is. There were some simple checkboxes on the screen that let me notify the other team members that I had posted the message. One weakness I noticed in the messages section is that the post message form is on a separate page from the view message page. The user experience could have been improved if AJAX had of been used to allow the user to view and edit the message on the same page.

Next, I clicked the to-do tab to create a plan for the project. I gave the to-do list a name, "Set up tutoring program", and then entered in to-do items one by one. I specified who was responsible for completing each item, and was given the option to notify the person by email. I was glad to see that this time Javascript was used, and I didn't have to wait for new pages to load every time I made a change. I was able to drag and drop tasks into the correct order, and edit them where they were published.

Next stop: Milestones. The to-do list doesn't record deadlines - that feature is separated into the Milestones tab. To create a milestone, I was asked to enter a due date, a description and a person responsible. There was a checkbox offering to email the person I specified now and 48 hours before the task is due - a nice touch. A feed was automatically created to import milestones into iCal or Mozilla Calendar. I did have a strange feeling I was double handling the items I had entered in the to-do list though.

The next feature on the tab list is the Writeboard - a basic wiki. When I created a new document, I was forwarded on to the Writeboard website (which is made by the same company as Basecamp). Basecamp and Writeboard have been integrated quite effectively, and most users probably wouldn't notice they are moving between two websites. Unfortunately Writeboard is a very basic wiki; nowhere near the likes of Google Docs.

Being an internet website has both advantages and disadvantages for Basecamp. The file sharing feature is a good example. The fact that Basecamp is online makes it easy to keep colleagues and clients updated on your progress. However, if you are working with large files, it is just not practical to upload them to the internet to share - especially in countries like Australia with slow internet.

The to-do list and milestones were very nice to use, and although there were some problems with the website, I would love to use it in MUBS. I won't though, because I already introduced a wiki this year and I'm having enough trouble getting people to use that!

The start of Studio 2!

2007-07-22T15:43:00.000+10:00

This semester I'll be working with Long Zheng and Justin Tickner. The reason we formed a group is we're all interested in developing a database driven website. We want to make something that we can put on the net so other people can see it and use it. We're all studying double-degrees, so we're a year behind the people we started with and we're among the last cohort to do Studio 2 before it is phased out. Long and Justin worked together in Studio 1 and made a fashion website / CD-ROM. They did a fantastic job with it, so it will be good to work with them this semester.

This week in studio we talked about ideas for our project. Long explained an idea he'd been thinking about over the mid-year break, and that was a project manager for students. It would let students create to-do lists for their assignments, tick things off when they were completed, talk to team members on group projects, and work collaboratively using a wiki. We talked about our experiences of writing to-do lists for assignments, especially when all the assignments come at once, and we agreed that an computer based system could really help. A to-do list for a media essay might look like this:

Research Second Media Age in the library - by July 27;
Compile a list of good references - by July 27;
Work out an essay plan and discuss it with tutor - by August 3;
Write a draft for the body of the essay - by August 16;
Write a draft for the introduction and the conclusion - by August 17;
Proof-read - by August 21;
Write a final copy - by August 24;
Write a reference list - by August 28;
Submit essay - August 31.

At times I've had three or four to-do lists like this on different scraps of paper. We could develop a system that helps students store all their assignment objectives and plan their work schedule. This would be much more effective than keeping to-do lists on scraps of paper. Ticking off completed tasks can also serve as a good motivator. Justing and I both admitted to writing elaborate to-do tasks of things we'd already completed, just so we could tick them off and feel good about our achievements.

I suggested that this idea would be useful for businesses as well as students. I know that in MUBS it can be difficult to make sure everyone has something useful to do, and that they are doing it. The last MUBS board meeting was focused on figuring out our goals for second semester. Throughout the semester I'll be ticking goals off on a white board as we achieve them. However, Long pointed out that a common mistake made by students in studio is to make their project too broad, and there are already really good project managers for businesses out there (such as Basecamp). I think it is a good idea to focus our product on students.

We also discussed the method of distribution for the product. Long suggested we package it as a standalone website that lets students create x number of assignments for free, but then requires payment for continued use. Group licenses could also be sold to schools and universities (if the government funded them adequately that is). I suggested that a good alternative would be to make our product on the Facebook platform so it could be distributed virally from students to their peers. It could have a free number of trials or be ad supported. During the mid-year break I made a Facebook application called Introduce Me, and now there's over 1,500 people using it. After discussing these options we decided to go with the standalone website. We think our product is better suited to be standalone because Facebook is for socialising, and our product is for studying. By putting it into the Facebook environment, there would be too many distractions for our users.

Over the next week, we will research whether our idea has been done before, and if so, how.