Expect changes in dates and topics as the course will change to meet our needs as they develop.
- Activities lists the general activities for the day in the context of the topics.
- HW (i.e. homework) is the thinking or activities to be done in preparation for the following day(s), and
- PB (i.e. process book) are some prompts to consider in documenting your process.
Denotes a coding topic, roughly speaking.
Daily slides are posted to Basecamp.
Note that some days display two tracks (Design and Dev) for activities and homework to indicate role differences.
Objectives: Get us up and running as a design office. Cover the logistics and necessary course details. Kickoff the project.
8/26 M Day 1 Introductions - who are we and what is this class about?, Course logistics
- Activities: Apples-to-Apples; Get to know our collective skills
- HW: Write your bio and brainstorm ideas for our office “self representations”
- HW: Tool invites, don't be afraid. Kyle will be sending you invites to: * Basecamp * Campfire * KanbanFlow * GitHub (see email from Kyle) * Google Docs (see email from Kyle)
8/27 TU Day 2 What will we be doing? - Collaboration, Project Management, Process documentation; Course Progression, Topics, Schedule;
- What is an iPad technically speaking?; What is an app?;
- Activities:Muddy point; Setup laptops; Review tools; Intro to Project Management; Process Documentation; * Review HW
- HW/PB: Consider your personal experience at ‘Iolani. * What are some of your pet peeves? * What are some things you love? * Have a discussion about this with someone else (family, friend, faculty, etc.). * What did you learn from the exchange? about them? about you? about the topics?
- PB: * What are your personal values? * How do you feel about the introduction of this technology? Fears? Desires? Unknowns?
8/28 W No class meeting
8/29 TH Day 3 Project Kickoff! Ethics; Goals; Constraints; What are our assumptions?
- Activities: * Discuss HW (Review pet peeves & what you love); * Defining ‘Iolani and Community - 5Ws & H; * Mind-maps
- HW: Fill in your part of the ‘Iolani Who, What, When, Where, Why, & How shared document.
- PB: How do you want an app to make you/others feel? What do you want to put out in the world?
8/30 F Day 4 What are our opportunities? - identify areas of interest; Project scope
- Activities: SWOT analysis; Brainstorming
- HW/PB: What do you think you want to create? What are your assumptions about what you can or cannot create? * Download an app and evaluate your experience * Review our various insights based on research to date. Who do you think you would want to build an app for? Are there any specific opportunities of interest to you? Pick two "directions". * Find a laptop case, cover, or carrying solution. If you think you might be interested in doing some of the design work, you might end up switching to a 15" Macbook Pro. So, it might be best to find something that fits either computer.
Objective: Introduction to research in the context of business and design considerations
9/2 M No class meeting
9/3 TU Day 5 What is the iPad? What is an app?
- Activities: Share out app reviews; Discuss some of the technical details of iPads and apps.
- HW: LAB 1: Building your first iPad app in the Simulator
- HW: Hear what Steve Job's has to say about life in this video (< 2min) * Have you had an experience like this? * Is it possible to think of what that might be like if you haven't? * Could this class help? Is this related to the "agency" idea we mentioned on day 1?
- HW: Listen to Steve Job's Commencement Address to Stanford in 2005 (~15min) * Why is this talk ironic? * How far will school take you? Does your own initiative play a role in success? * Steve Jobs had opinions. Strong opinions. You don't have to agree with him. But, you can't argue with his ability to figure out what he wanted and then create it. * Think about what Jobs says about "time." This is a short class, every class period counts. Don't waste it.
- HW: As you continue your day. Write down the first thing that bothers you about your iPad. Also, the first thing that bothers you about ‘Iolani. Report back tomorrow.
- HW: Share a goal of yours with someone you know. Anyone. Report back tomorrow. You chose the format of sharing.
- PB: Any ideas that come to mind after discussing various apps?
9/4 W Day 6 Building your first iPad app
- Activities: Let's figure out how this Xcode things works. And, what are all the steps in building an app with it?
- HW: LAB 2: Complete the setup process for your developer certificate and deploy an app to your iPad.
- HW: Review the research we've done so far and consider whether there are two audiences, topics, issues that are of interest to you? (Ex. Tardies/Attendance Office and Students) Have them ready so we can just share and determine if we want to focus our field work at this point. How you choose is up to you. What do you want to work on this semester? Who do you want to help? What school processes do you want to learn more about?
- HW: Think about the qualities that you want in your teachers. I will give you time to talk together and start creating a rubric for Kyle & me (and potentially for teachers in general).
- HW: Write up your "typical Iolani day." Everyone please create your own Google Doc and share it with the class. What do you do and when (approximate time/durations) from when you wake up through till you go to bed. I don't need explicit details (what you ate for lunch) unless it's part of the "typical" decisions of you make. I would want to know things like whether you walked to your locker to get your lunch, carried it around with you all day, or went to buy it from somewhere (and where). If it helps, just write down what you did on Tuesday of this week. It'll just help us to understand things like personal process flows and we can do more to look for patterns. Step through it like you're talking to someone who hasn't ever gone to school before (has no assumptions about your routine).
- HW-ish: You don't need your laptop Thursday or Friday. I'll extend the app LAB on Friday, based on feedback between now and then.
- HW-ish: Bring a digital camera/iphone/ipad in case we have time to start our field research.
- PB: Whenever we ask you to "think about" something. Or, share something. Put it in your process book, unless you want to email it, post it, Muddy Point it, or talk about it in person.
9/5 TH Day 7 Ethnographic methods - observe, listen, and ask questions
- Activities: Review typical days and discuss patterns, example walk around campus, take notes & photos (finishing up 5Ws & H)
- HW: Start taking photos to help illustrate your typical day write-up. Look for physical traces.
- HW/PB: Start writing some possible survey questions for your selected audience and topic. Do you have any assumptions about what you expect to see/hear out in "the field" (interviews, photo ethnography)? Write them down as well.
9/6 F Day 8 Field research
- Activities: Split up and create process maps and formulate questions for research next steps
- HW: Continue creating process map (try creating digital version), writing up survey/interview questions, taking photos of artifacts/processes.
- HW: LAB 3: Continue learning about Storyboard fundamentals, by adding segues.
- HW: Create teacher assessment rubric (class to collaborate on your own doc).
- PB: What do you hope to learn from the interview? Hypotheses on what some the problems/challenges might be?
Objectives: Continue with deeper research. Synthesize findings to date. Introduce basic coding concepts.
9/9 M Day 9 Storyboarding
- Activities: Live Coding: Review Lab 3 (Navigation Controllers with Segues) and extend with Actions and Outlets
- HW: LAB 4 - Storyboarding: Actions
- HW: Finish first draft of survey and interview questions.
- PB: Checkpoint: How do you think things are going so far?
- PB: Bring your process book to class on Tuesday. We would like to review them.
9/10 TU Day 10 Stakeholders, Surveys, Interviews
- Activities: Purpose of research; Writing Surveys & Interviews
- HW: LAB 5 - Storyboarding: Outlets
- HW: Review survey and interview questions, Start a Google Form if necessary
9/11 W Day 11 Surveys, Interviews
- Activities: Work day - Small group writing of surveys and interviews (Collect process books)
- HW: Finish survey and interview questions.
9/12 TH Day 12 Surveys, Interviews
- Activities: Work day - Finalize surveys, Schedule interviews (Collect process books)
- HW: Finish survey and interview questions.
9/13 F Day 13 Coding Basics - Models of OO
- Activities: Review homework via Live Coding. Begin descent into Object-Oriented programming.
- HW: LAB 6 - Moving that ball we were talking about. This is step 1 in a larger mission to build our learning framework. It starts difficult, but gets easier, I promise. Really.
- HW: Finish up interview questions. Sending our surveys. All research due 9/20.
- PB: Start taking notes on your own processes (for secheduling, assignment organization, collaboration activities).
Objectives: Extract design implications and begin to clarify solution space. Introduce basic programming concepts.
9/16 M Day 14 Core coding concepts - Objects
- Activities: Review of bouncing ball demo (part 1) via Live Coding in pairs.
- HW: LAB 7 - Bouncing ball demo, part 2 of 2 Finish it up.
- HW: Finish up interviews (due 9/18)
- PB: Checkpoint: how is this process going for you?
9/17 TU No class meeting
9/18 W Day 15 FIELD TRIP
- Activities: Share out interview key insights; Brainstorming
- HW/PB: Possible concepts/solutions?
9/19 TH Day 16 Competitive Analysis (may use class time for scheduling interviews)
- Activities: Start assembling all research to date (pictures, text, etc.)
- HW/PB: Continue working on personas
9/20 F Day 17 Close-out research activities - What are we improving?
- Activities: Mind-map solution space; Create vision statements
- HW/PB: Finish vision statements and personas
Objectives: Begin looking for inspiration and start ideation in solution space. Start of ideation phase. Explore the user’s experience of the potential solution spaces and consider appropriateness of interventions. Start Objective-C programming. Choose roles.
Note that there are two tracks (Design and Dev) for activities and homework to indicate role differences.
9/23 M Day 18 Design and development roles; Group brainstorming guidelines; Logistics
- Activities: Checkpoint: where are we in our process. Get organized.
- HW/PB: Review research. Draw 5 patterns, themes, insights. *What do you want your role to be? Be ready to choose.
9/24 TU Day 19 Personas - a better picture of our audience; Use Cases; Critiques - how to give and receive constructive feedback; Storyboarding; Task Analysis;
- Activities: Telestrations; Practice critiquing
Design
- HW/PB: * What is the current experience? * How can you tell the story of the user (emotion)? * Draw/write something that will help to trigger your own emotional connection to our users and their experience
Dev
- HW/PB: * What are the content and context that shape the experience? * What are the limitations of the current process? * Are there limitations based on available data?
9/25 W Day 20 Vision Statements - what are our goals for the solution?; Group Ideation
- Activities: Share out thinking; Review solution ideas to date; Affinity map; Brain writing
- HW/PB: 3+ ideas
9/26 TH Day 21 Group ideation; Selection criteria
- Activities: Share out ideas; Open brainstorming; Create rubric for selection
- HW/PB: Which ideas do you like best? Does the rubric capture all the qualitative aspects of decision making?
9/27 F Day 22 Product Pitch; Mood/Inspiration Boards, Controls
Design
- Topics: Mood Boards; Typography
- Activities: Start looking for inspiration, Begin to articulate desired experience
Dev
- Topics: Controls (Table Table Views, Image Views, Labels)
- Activities: Discussion & Live Coding
Both
- HW/PB: Write up product pitches. Use images or words from research to create a compelling story.
Objectives: Close of ideation phase. Select projects. Start focused research and exploration of concept.
9/30 M Day 23 Project selection; Use Cases; Features; Content; Ethics
- Activities: Share out pitches; Vote; Discuss what to build
- HW/PB: Brainstorm: * What features do we want? * What is the hierarchy? * What are the use cases?
10/1 TU Day 24 Task analysis - What is the desired app workflow?; Points for intervention
- Activities: Share out thoughts; Roleplay “new” process for some use cases; Discuss/document
- HW/PB: Document observations, insights from task analysis
10/2 W Day 25 Core concept; Feature selection and hierarchy; Future considerations; Design elements and principles; Design Patterns
Design
- Topics: Design elements and principles
- Activities: Continue work on mood/inspiration boards; What imagery, themes, treatments, layouts do we like?
Dev
- Topics: Simple Design Patterns: Delegates, MVC, Singleton
- Activities: Discussion & Live Coding
Both
- HW/PB: Look at any other apps that deal with similar features. * Can we apply any of these ideas? * Are there things we want to avoid? * What works/doesn’t work? * Draw 1 screen for what you think we might be building.
10/3 TH Day 26 Review current assessment (participation), OPEN HOUSE, Content: what are we building around?, Presenting concepts
Design
- Activities: Discussion/Group work: Review content and consider variations (groupings, voice, display format, etc.)
Dev
- Activities: Discussion: * Where is the content coming from? * What is the format? * How will we handle it? * Validation necessary? etc.
Both
- HW/PB: Determine what the content will be and begin “cleaning it up” for use in next stage of prototyping.
10/4 F Day 27 Design Persona - Capturing the experience; DEV: feature specific topics
Design
- Topics: Design Persona
- Activities: Group Work: Create design persona
Dev
- Topics: Contingent upon projects
- Activities: Discussion & Live Coding
Both
- HW/PB: * What do you think we’re building? * Where is it fuzzy? * What questions do I have?
I'll transfer this part over later. In the meantime, here's a Wikipedia article on the Design-Build concept as applies to architecture.