Prerequisite: CSC 221

Course Description

This project-based course presents the fundamental concepts and techniques of mobile application development. The course will focus on the iOS platform, developing apps using Apple's XCode IDE and the Swift programming language. An overview of other platforms and development tools will be included, and best practices in the design and implementation of mobile content will be studied. Specific topics include the iOS architecture, the Apple UIKit, views, workflows, tables, data persistence, and Web integration.

The specific goals of this course are:

• To apply existing programming skills to the mobile domain, addressing challenges such as memory restrictions, touch-based interfaces, and rapidly evolving architectures.
• To appreciate the wide range of tools and platforms available for mobile development, and be able to identify appropriate tools for various tasks.
• To be proficient with the XCode development environment and the Swift programming language.
• To design and implement apps that address real-world needs, using best practices in design and software engineering.

Required Work

Much of the course time will be spent in hands-on learning activities, working through interactive tutorials and developing apps in structured exercises. At the end of each unit, each student will complete a larger assignment, which applies the concepts and skills learned in that unit. A late penalty of 25% will be applied to any late assignment - assignments will not be accepted more than a week late. In the second half of the course, students (working individually or oin a team of two) will propose and implement an app of their own design. This app should address a real-world need and demonstrate good design and programming practices. In the last week of the semester, students will present their apps to the class.

Mixed into the semester will be discussion days, where students discuss assigned articles concerning mobile technology, design principles, and project management. Discussion questions will be assigned and students must submit their answers before class on that day. In addition, there will be one 75-minute midterm exam and a cumulative final exam (see the schedule below for exam dates).

There is no specific attendance policy for the course, although it is expected that absences will leave the student unprepared for tests and assignments. Tests will not be rescheduled except in extreme circumstances. The final grade for the course will be based on the following weightings:

At the minimum, departmental grading cutoffs for the final average will apply. That is, 92-100% guarantees an A, 87-91% a B+, 82-86% a B, 77-81% a C+, 71-76% a C, and 60-70% a D. Depending on class performance, some shifting of grades (in an upward direction only) may occur as final letter grades are assigned.

It is expected that all students check their Creighton email accounts regularly. Official announcements, such as assignment revisions or class cancellations, will be distributed through Creighton email.

Policy on Collaboration

Creighton's policy on cheating and plagiarism is spelled out in the Student Handbook, with college procedures available online. When completing exercises in class, students are encouraged to work in teams or small groups. Unless otherwise specified, unit assignments should be the sole work of each student. Semester projects may be completed individually or with a partner.

Violations of this collaboration policy will be dealt with severely, with possible outcomes including failure in the course. In the case of unit assignments, you are encouraged to start early so that there is time to seek help from the instructor as the need arises.

Daily Schedule (check regularly for updates)

Sample code from class