<commit_before>---
layout: assignment
title: Assignment 2 - Application Seminar
---

<br>

{:.table.table-bordered.table-striped.deadline-table}
|Issue date &nbsp;| Monday, 15 August 2016 |
|Groupings due &nbsp;| Friday, 19 August 2016, 23:59 |
|Slides submission &nbsp;| Friday, 26 August 2016, 23:59 |
|Presentation &nbsp;| Monday, 29 August 2016, 18:30 |
|Application critiques &nbsp;| Tuesday, 30 August 2016, 23:59 |
|Mutual critiques &nbsp;| Sunday, 4 September 2016, 23:59 |

## General Overview

In order to build good and original applications, it is important to learn what other people have already done — and think critically about what is good and bad, as well as explore ways to improve and to generate new ideas. In addition, it is important to learn how to articulate one's ideas in a clear and succinct way both orally and in writing. The application seminar is designed to help students both (i) gain a better understanding of existing applications; (ii) learn how to present (or sell one's ideas) and (iii) learn how to articulate their ideas on paper.

You will form groups of 4 people to study one application of choice and make a presentation about it to the rest of the class on 29 Aug 2016. Each team will put up their grouping and propose three choices (in order of preference) by 23:59pm on 19 Aug 2016 on the seminar groupings page on the Course Wiki. Your group can talk about any app that has been released within the **last three years**. The reason why each group is required to submit three choices is to avoid duplications. In case of duplications, we will make the choice at random. We will sort out the assignments of the applications to be studied by 21 Aug 2016 and you will be informed.

## Grading and Admin

The presentations should attempt to cover the following points about the chosen application:

1. Description of the application
2. Why we should care about the application you chose
3. How the application can be implemented if you had to do it (Describe the program organizaion by using high level views like logic flow, identifying technologies used like Flash, FBJS, etc)
4. What is good, bad and ugly about the application
5. Suggested improvements
6. Commercial potential
7. New app(s)/business models/ideas arising from studying the application

From our past experience, students tend to ramble on and on in their presentations. To control this we are using a format called Pecha Kucha. See <http://www.youtube.com/watch?v=9NZOt6BkhUg> for an example. It works like a charm. We will do the same this year.

In particular, each presentation is limited to 20 slides and each slide should have exactly 20 seconds of air time. This means that each presentation should be approximately 7 minutes long. Please stay within this time limit. You can choose to have a single person present or more than one but keep in mind that you have a limited time. The teaching staff WILL cut you off after 7 minutes.
<commit_msg>Fix typo in Assignment 2<commit_after>---
layout: assignment
title: Assignment 2 - Application Seminar
---

<br>

{:.table.table-bordered.table-striped.deadline-table}
|Issue date &nbsp;| Monday, 15 August 2016 |
|Groupings due &nbsp;| Friday, 19 August 2016, 23:59 |
|Slides submission &nbsp;| Friday, 26 August 2016, 23:59 |
|Presentation &nbsp;| Monday, 29 August 2016, 18:30 |
|Application critiques &nbsp;| Tuesday, 30 August 2016, 23:59 |
|Mutual critiques &nbsp;| Sunday, 4 September 2016, 23:59 |

## General Overview

In order to build good and original applications, it is important to learn what other people have already done — and think critically about what is good and bad, as well as explore ways to improve and to generate new ideas. In addition, it is important to learn how to articulate one's ideas in a clear and succinct way both orally and in writing. The application seminar is designed to help students both (i) gain a better understanding of existing applications; (ii) learn how to present (or sell one's ideas) and (iii) learn how to articulate their ideas on paper.

You will form groups of 4 people to study one application of choice and make a presentation about it to the rest of the class on 29 Aug 2016. Each team will put up their grouping and propose three choices (in order of preference) by 23:59pm on 19 Aug 2016 on the seminar groupings page on the Course Wiki. Your group can talk about any app that has been released within the **last three years**. The reason why each group is required to submit three choices is to avoid duplications. In case of duplications, we will make the choice at random. We will sort out the assignments of the applications to be studied by 21 Aug 2016 and you will be informed.

## Grading and Admin

The presentations should attempt to cover the following points about the chosen application:

1. Description of the application
2. Why we should care about the application you chose
3. How the application can be implemented if you had to do it (Describe the program organization by using high level views like logic flow, identifying technologies used like Flash, FBJS, etc)
4. What is good, bad and ugly about the application
5. Suggested improvements
6. Commercial potential
7. New app(s)/business models/ideas arising from studying the application

From our past experience, students tend to ramble on and on in their presentations. To control this we are using a format called Pecha Kucha. See <http://www.youtube.com/watch?v=9NZOt6BkhUg> for an example. It works like a charm. We will do the same this year.

In particular, each presentation is limited to 20 slides and each slide should have exactly 20 seconds of air time. This means that each presentation should be approximately 7 minutes long. Please stay within this time limit. You can choose to have a single person present or more than one but keep in mind that you have a limited time. The teaching staff WILL cut you off after 7 minutes.

{'fraction_non_alphanumeric': 0.04917480633209835, 'fraction_numerical': 0.031828898619063656, 'mean_word_length': 4.404003639672429, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1526016', 'n_tokens_mistral': 1618, 'n_tokens_neox': 1410, 'n_words': 964}