This is the CSE340-SP19 final website.

Welcome to Interaction Programming!

Interactive technology is changing society. Some of today’s interfaces are used by a billion people at a time. Almost everything we create is created for people to use, through user interfaces. We will learn about interactive systems, including programming paradigms and design of event handling, layout, undo, accessibility and context awareness.

For quick links to key things, check out the navbar above and the table of contents here:

Class Instructors, time and date

CSE 340 will be held on M/W/F at 10:30am Labs will be Thursday morning

CSE 340 is taught by Jennifer Mankoff. Ryan Rowe is Head TA.

Instructor Role Office Hour Time/Location
Jennifer Mankoff Instructor 2:30pm to 4pm, Wednesdays, Gates 211
Ryan Rowe Head TA Fridays 1:30-3pm, Gates 150
Saidutt Nimmagadda TA Mondays 12-1pm, Allen Center 021
Adam Towers TA Tuesdays 5pm-6pm, Gates 131
Harshitha Akkaraju TA Thursdays 5:30 - 7:30pm Allen Center 021

Should I take this class?

Yes! Some of today’s interfaces are being used by a billion people at a time. Almost everything we create is created for people to use, and user interfaces are how people interact with anything else you do (whether it is a new machine learning algorithm or a database system). User interfaces are incredibly important, but they also represent a different programming paradigm than you may have learned before. This class will teach you

Taking a class is a big commitment, and you will work hard in this class. So we want to help you make sure this is the right class for you. Below is some information about prerequisites and expectations.

Prereqs and expectations

The only requirement for this class is that you have taken CS 142 and 143 or an equivalent class, meaning you are comfortable programming in Java, and have some experience with data structures. However, if you are not comfortable working in an IDE environment, using version control, and picking up and working with someone else’s library code, you will likely need to plan for extra time with TAs, and possibly attend extra tutoring sessions, to keep up with the class. A good plan is to take 391 just before or concurrently with 340 to learn some of these things.

The specific platform and language for this class are Java on Android phones (or simulators); using the IntelliJ IDE (Android Studio). While Google is switching over to Kotlin, there are good reasons to start learning Android with Java first.

Note that this class is designed for CS majors, and other students who work regularly with information technology and are strong programmers. While we will consider applications from outside the major, in its first year, financial and room restrictions may limit space for such students.

Other relevant classes to know about

There are a number of classes on campus that teach related concepts which you may wish to consider in addition to this one. As of summer, 2018, here are the ones we are aware of:

Resources

Course Structure

Many of the goals in this class center around learning by doing. This means that hands on time trying out everything from implementation to evaluation is critical to learning. An educational approach that can support this is active learning. To support this, readings and videos will be available ahead of class, while class time will be used as much as possible for activities, discussion, review, and homework. This means you’ll be getting information at home and doing problem sets in lecture, rather than the reverse. We will help to support and guide your learning, but your preparation outside of class is essential.

Why break the mold of standard lecture classes? I believe that this will improve your learning.I also value the chance to support you while you do work on assignments and practice material. However this requires you to be independent and accountable for your own learning, stay on top of course materials, bring your questions to class and seek help if there are problems.

Workload

This is a challenging, four credit class, meaning you should expect 8 hours of homework a week. We hope make the workload as predictable as possible. You can expect your weeks to look look something like this:

Homework takes two forms – exercises and assignments. Exercises are assigned on Thursdays and due on Mondays. Assignments typically have two weekends to be completed.

Class Coordination

We want you to succeed in this class, and an important way that you do that is by asking questions and discussing course issues with your peers and teaching staff. Some ways to do that include:

Class Expectations

The class is a shared learning environment, and it is important that you treat everyone in the class with respect. Some specific things we will do to try to make the class a welcoming environment:

Grading

Grades will be assigned approximately as follows:

To estimate your final GPA, multiply your current overall grade (from 0 to 100) by 4 and divide by 100.

Late Days

Each homework will allow late days with a 10% penalty per day. Partial days may not be used (i.e., 12 hours late is a 10% deduction, not 5%). You are allowed to use up to 2 late days on each assignment, after which turn-ins will be given a zero.

For the quarter, two penalty-free late days are provided which can be used on assignments by filling out the late day request form posted on Piazza.