Concept

The final full-scale project of the term will combine several issues we’ve discussed over the term, and will also attempt to shed light on future applications of your design. We have been exploring issues of the printed page in the form of booklets and packaging, but in this case, we will start to think about how to design for screen-based environments. This project is “self-reflexive” in that it asks you to re-think the very nature of the software itself.

IMPORTANT! Note that the overarching concept of this project will be to take the aesthetics of one “body of knowledge” and map it onto another. In other words, you’ll use the “look and feel” of an existing analog field as the basis of your software design.

The Project

Like most projects, there are a number of facets to address—many of these facets might strategically overlap. The overall idea is to generate a hypothetical software application, or computer program which will be designed around the artist, architect, or designer of your choice (Note: no games!).

Of course, the first challenge is to choose who you will investigate! Then you will need to determine the “conceptual” and “aesthetic” elements you will adapt for your design. Oh, but there’s one catch (there’s always a catch!), the individual you choose cannot be someone living! Please clear your choice with me before proceeding.

Keep in mind that, as you see below, you will also be designing “tools” which somehow relate to this individual. A major part of the project is based on your ability to conceptualize and translate your chosen artist/architect/designer to the screen. What will the tools be? Will they be image-related? Text-based? Will they go beyond the tired limitations of Photoshop and Adobe? What would a program called “Monet 1.1” actually do? How about “Kandinskyshop”? You’ll need to do more than just create pretty images—research and get into the PHILOSOPHY of this person! If you need help in choosing your individual, feel free to ask…

Time to use Behance!

Milestones:

(Subject to change)

// M01_Concept Approval and Initial Elements

04/22
A discussion of your work. I will clear the artist chosen. Be ready to show progress on the screen-based elements of your work.  

• About Artist (research) and 
• Software name
• What will the software do?
• Show progress on the screen-based elements of your work (splash/wordmark?)

// M02_Concept Presentation

04/24
Conceptualize your project and begin to develop the look and feel. Develop the following elements (which will be added to a nicely designed presentation/proposal. Details forthcoming):

• a name,
• the Logotype,
• what the software/application will do
• and the beginnings of the official Splash Screen that will display when your program first opens.

// M03_Additional Elements

04/29

• Build the interface, look, and feel, window layout, menus, etc.
• Design AND conceptualize three (or more) “tools” and a bin or palette to house these tools
• Design two “windows” that somehow prompt user interaction
• Create a desktop icon for the program

// M04_Draft Image for Breakout Groups Critique

05/06

All elements on a single “staging” image

• Splash Screen 
• Logotype
• Desktop icon for the program
• Three (or more) “tools” and a bin or palette to house these tools
• Two “windows” that somehow prompt user interaction
• Workspace (where creation will take place)

// FINAL!

05/08

All elements are due on 05/08
NOTE: Presentations Part 2 is on Thursday, 05/15 from 1–3 PM

+ Final presentation. Using InDesign, create an “interactive” PDF file that will allow you to navigate through the software as a demo for the final presentation.