CSCI E-65: Mobile Application Development Using Swift and ios

of 5 OFFICIAL 25 Jan 2016 CSCI E-65: Mobile Application Development Using Swift and ios Harvard University Extension School: Spring 2016 Instructor: Daniel Bromberg bromberg@fas.harvard.edu TF: R. Van Simmons rvsrvs@mac.com TF: Mark Sobkowicz mark@evtika.net Location: Science Center Room 309 Lectures: Mondays 5:30-7:30PM Sections: Each TF leads a 60 to 75-minute section; each student assigned to one TF and must attend that section. Students will be notified of section schedules by start of class. Sections will likely run from 7:45-9:00 on the same night of class. LATEST VERSION OF THIS DOCUMENT: http://git.classyswift.com/e65/admin/syllabus-spring-2016.pdf OBJECTIVE: To lay a foundation in the concepts, libraries, and development tools necessary to create and deploy a realistic App (mobile software application) on latest-generation iphones and ipads. We will focus on the fundamentals: the one-year-old Swift programming language; the Xcode IDE; the ios development cycle; the essential Foundation and Cocoa Touch libraries; Apple best practices, especially the Model-View-Controller paradigm; responsive event handling, such as thread-aware task dispatching; the storage and recall of user data to remote & local databases; and deploying apps via itunes Connect. While the ios API is vast, we intend to show enough core material and patterns such that students graduate able to apply their knowledge to uncharted territory and rapidly absorb advanced material on their own. PRE-QUALIFICATIONS: Students must take a pre-qualifying self-assessment test before enrolling: http://git.classyswift.com/e65/self-test (available 12/01/15). The test should take less than an hour. Answers will be available in a sub-directory. It is important before enrolling and investing considerable time & expense in the course that you feel confident in your answers. Please e-mail me individually if you are unsure about any particular answer or the overall difficulty level. READINGS: Readings will come from a combination of: The Apple Developer Library; Chapters from new e-books; and online tutorials. Students must understand that due to the young age of the technology, written documentation is relatively scarce and academic-grade texts do not yet exist. It is essential to be comfortable assembling know-how through a variety of sources, which will vary considerably in style, abstraction level, and intellectual depth. The following introductory material is highly recommended as preparation for the first class and will be due for the 2 nd class: https://developer.apple.com/swift/ One-page promotional background

of 5 https://developer.apple.com/videos/wwdc/2014/#402 Official intro video at WWDC 2014 https://developer.apple.com/videos/play/wwdc2015-106/ What s new in Swift 2.0 https://developer.apple.com/library/ios/documentation/swift/conceptual/swift_programming_lan guage/guidedtour.html Technical introduction to Swift EQUIPMENT: Students must bring their own portable Mac running OSX 10.11, with at least 4GB of RAM, as well as an iphone 5 or later running ios 9.x. For those interested in specializing their work for the ipad, owning one is highly recommended as well. For commercial development and deployment to the App store, students are advised to purchase the $99/year Apple Developer membership. TOOLS: Class assignments (which include readings) and lecture teaching materials (mostly example code, some diagrams) will be hosted at a private Git / web server: http://git.classyswift.com/e65/assignments and http://git.classyswift.com/e65/lecture-notes. Each student will also have an individual repository, with a username and password, into which they will submit all assigned work. The naming conventions will be spelled out so that all submissions have the same directory structure. Online discussion: We will have a moderated discussion forum in Google Groups, with one thread per assignment. This is an essential tool to disseminate information efficiently in a fast-paced environment. All questions about the course material should be directed to this forum for maximum visibility to staff and students. Students are strongly encouraged to use the forum on a daily basis to make their homework time efficient. Show leadership by asking questions. If you have a basic question, so does at least a third of the class. As far as the staff is concerned, a central premise of learning programming is doing some research, trying a few solutions, getting stuck, and asking an informed question no matter how basic you think it is. Participation credit is generously awarded for such efforts. Other contact: E-mail, calls, and texts to the staff should only be used if you feel you need privacy, and in that order. IDE: Xcode 7.2: https://developer.apple.com/xcode/ide/ Online REPL (Read-Eval-Print-Loop): http://swiftstub.com This is a pure Swift simulator that is, nothing ios specific in a simulated terminal. It is good for entering experimental snippets to help learn the core language, such as closures and looping syntax. This is not an official Apple site; however it is quite nice.

of 5 WORKLOAD: This is an intensive course with ambitious goals of teaching a new programming language, an IDE, several frameworks, a variety of UI and design concepts, and practical debugging and deployment knowledge. Assignments will be issued once per week and due the next week. Students must commit to roughly 15 hours per week of homework, 2 hours per week of in-person class/section, and 30-60 minutes of pre-recorded lectures that cover pre-requisites for actual class. ASSIGNMENTS: Timely completion of reading and assignments is absolutely essential. There will not be much time for the staff to help students catch up on missed work or missed classes. Late work will not be accepted except for medical emergency or religious observance (for the latter, prior notification required). Because some answers may be revealed in subsequent lectures, work that s even a little bit late will not be accepted. Rather we will be very inclined towards partial credit as long as you turn in what you have on time, even if it doesn t work or won t compile. If you are having technical difficulties in submission, let us know immediately at the start of class and a TF will help you. Grading: 15% Class participation (includes section); 50% general assignments; 35% final project. In the event of any conflicting or ambiguous information on exactly what s expected from each assignment, whether logistics or content, please let us know immediately. Van is the final authority for all homework related matters. ATTENDANCE: Due to limited interaction time, only 2-3 hours per week, lecture and section attendance is strongly recommended. ACADEMIC HONESTY & INTEGRITY: You are bound by these policies for the entire course: https://www.extension.harvard.edu/resources-policies/student-conduct/academic-integrity There is no flexibility in these rules because they apply to the entire Harvard Extension School. In addition, defining plagiarism in computer code has unique challenges, partly due to the fact that some simple techniques, especially those mandated by the given API or OS, are virtually identical across all programs, whereas deeper designs and algorithms vary as widely as original poems by different authors. We adopt the written policy of Harvard s flagship Computer Science course: https://cdn.cs50.net/2015/spring/lectures/0/w/syllabus/syllabus.html#academic_honesty In particular, when you learn how to do something from code on the Internet, no matter how well the learning process worked, and no matter how short the example, you must cite the source SINGLE LINE SOURCES INCLUDED. They should appear as a comment (usually a valid URL, or complete book title and page) right above the relevant code. The only exception is if we ve already given the source to the entire class. In particular, any snippets in the Apple Technical documentation need not be cited.

of 5 The citation process is not merely busy-work; it helps us learn what students need help with, and to see if they re using good, up-to-date learning tools. There is never a penalty for citing any (or many) sources; in fact it will reflect positively in your participation in the course. Before doing online search for pre-cooked solutions, however, apply some pedagogical sense: for the first assignment especially, many answers are just one or two lines. Think about how best to learn. Learning a language requires writing code from scratch using the fundamentals. It doesn t matter if there are dozens of existing solutions that are just a few search keywords away. Play it safe early on and use official Apple documentation and the help of the staff only. ACCOMODATIONS / DISABILITY SERVICES: In accordance with https://www.extension.harvard.edu/resources-policies/resources/disability-services-accessibility LECTURE SCHEDULE: (Harvard-wide calendar: https://www.extension.harvard.edu/academic-calendar) Lectures will be heavily example-driven. Much of the material will be refined in layers over several classes. Schedule will also be adjusted to prevent average student workload from significantly exceeding aforementioned estimates. Week Date Focus Likely topics 1 1/25 Introduction to Swift and Xcode for ios 2 2/01 App development and Swift essentials 3 2/08 Structuring a larger project Xcode and Swift 4 2/15 NO CLASS: Recorded lecture: The ios API: Cocoa Touch Policies; Student Surveys; Xcode Intro: Demo of a basic ios App & Playgrounds; a look at the Swift language Navigating Xcode to create a real project: StoryBoards, Source files, & wiring them together (References & Outlets); Swift essentials: Arrays, Dictionaries, functions, Optionals, Control Flow Organizational concepts: Coordinating multiple source files; Swift classes & structs; Essential debugging; Basic interactive controls within UIKit UIKit building blocks: Views and View Controllers; important UIKit interactive and display widgets, attribute customization 5 2/22 Layout and Drawing The Xcode Autolayout engine; working with constraints and the Scene hierarchy. Basic custom drawing (2D Quartz library); Touches and Gestures

of 5 6 2/29 Model-View-Controller Neatly separating, then tying together the essential pieces of any GUI App: Protocols, delegation, separate model classes, observed properties, and notifications 7 3/07 Pulling pieces into multiscreen app Application Lifecycle; Multiple views of same data, multi-screen apps: Tabbed Views, Hierarchical (Navigation Controller) Views -- 3/14 NO CLASS / No lecture SPRING BREAK Come up with project idea, write brief proposal 8 3/21 Persistence; structured data display Timers; Property Lists (XML); JSON; NSCoder; Core Data; Table & List views 9 3/28 Tables and data retrieval UITableView; JSON parsing and display 10 4/04 Tables with images & navigation Advanced Tables w/navigation controller Images; background (network-bound) data handling 11 4/11 3 rd party integration Tying App to FaceBook and Parse.com for user authentication, social sharing, and data storage 12 4/18 MapKit & GPS Geotagging, Map annotations, using phone s built-in GPS; Review of other topics as needed 13 4/25 Additional Frameworks, Project feedback Physics (UIDynamics); Other topics, depending on student interest. Possibilities include: Review of previous advanced topics; Accelerometer; Affine Transforms; Font formatting 14 5/01 Presentations Presentation marathon.