...
While Subject B did not really understand much about viral content, her model usage scenario is representative of a large population of users and we believe that our final procedure should be as close to her model as possible.
Task Analysis
...
1. Obtaining source of humor (photo, video, or sound, or
...
other data)
Reasoning: All great internet memes come from some source of inspiration. However, this inspiration can strike at any time. As a result. , it seems that mobile technology is perfectly suited for capturing sources of humor. Mobile devices tend to have access to several ways of capturing this data, including taking pictures and recording video.
Goal: Record or take a photo, video or sound.
Subtasks:
- User opens the interface
- User aligns the frame (or onion skin)
- User records or takes the target source
- User must send data to some other device or service for processing
Preconditions:
- User must own a video recording device, camera, or microphone
Spatial Constraints:
- Whatever recording instrumentation must be integrated with the latter tasks in one device, which is why we are choosing iOS and iPhone for our device
- methods of capturing data
- Frequency of use:
- There isn't really a way to predict the occurrence of meme-worthy content
2. Processing data
Reasoning: Processing this data (cropping, clipping, etc.) is equally important in the initial construction of viral internet content. It must be done in order to make the important humorous aspects of a photo stand out. In order for users to effectively process their data, they need to know what their goal is in utilizing these images or videos. Traditionally, this task is done using a picture editor on the user's computer. The biggest limiting factor of this is the lack of mobility.
- cropping
- clipping
- etc
Goal: Reformat data into a more presentable way
Subtasks:
- Cropping
- Clipping
- Changing bitrate
- Changing resolution
- Image filters
- Backgrounds
- User input (custom crops)
Preconditions:
- User must own software that can do the necessary changes (Photoshop, Audacity, etc)
Time Constraints:
- Processing algorithms can't take unreasonably long
Spatial Constraints:
- Should not take up unreasonable amounts of memory
Frequency of use:
- Constant relative to Task 1
3. Labeling/categorizing humor
*Reasoning: *What makes an meme humorous and reusable is its recurring theme. When creating a completely new meme, the user needs to know what this unifying source of humor is going to be. On the other hand, when creating another instance of an already popular meme, the user must understand what sort of humor the creator was going for. Again, the most traditional way of creating memes or gifs is to use a picture editor, and/or site dedicated to meme generation. Like processing data, it seems like the biggest limiting factor is a lack of mobility.
- captioning
- creating gif
- etc other labeling
Publishing
Goal: Figure out what sort of internet population to appeal to and write text on it
Subtasks:
- User must choose positions to annotate
- User must come up with appropriate text
- User must actually enter text
- User must save the file
Preconditions:
- Must have a grasp of internet humor
Time Constraints:
- Text editing must not take unreasonably long
Frequency of use:
- Constant relative to Task 1
4. Publishing
*Reasoning: *What separates viral content from a joke between friends is the ability to effectively share your content with the online world. Without any sort or assistance, a user would have to effectively utilize social networking. An effective application would increase efficiency by doing this for the user in any number of specified ways. The downside to automatic content sharing is that it can lead to unwanted situations.
- Social networks
- Account management
- Syncronization
- Tagging
Viewing ( optional )
- view your uploads in one feed online
...
...
...
...
...
...
...
...
Goal: Publish edited content to different social networks
Subtasks: Divided by social network
- If user hasn't authorized accounts before, then they must authorize the application first
- User must select which social networks to communicate with
- Actually publish
Preconditions:
- User must use social networks in the first place
Time Constraints:
- Publishing must not take unreasonably long
Frequency of use:
- Constant relative to Task 1
5. Viewing ( optional )
Reasoning: Sometimes users will want to see a history of the content they've published, as well as content of other users. They should be able to view a feed of a user's content publications in some centralized location. Therefore we will need to design a web app corresponding to the iPhone app. This, however, is dependent on how much time we have.
Goal: View content from one user in a centralized location
Subtasks:
- User must sign up for a recording service
- User must use their username or another's to access the personal feed
Preconditions:
- User must have content to view
- User must have signed up
Time Constraints:
- Web application should not take unreasonably long to load or display
Frequency of use:
- Whenever anyone wants to view anyone else's feed
...