CSc 317 - Mobile Application Programming

University of Arizona, Spring 2022

Course Description

Students will learn how to develop applications for mobile devices. The course will cover the necessary programming language(s), development environment, and a number of platform-specific APIs commonly used in mobile applications such as maps, location services, notifications, camera, and local storage. Other mobile-specific software development topics will be considered such as programming with limited computational and battery resources, client/server architecture, and cloud synchronization.

Location and Time

This is an in-person class. This class is scheduled M/W in Engineering Rm 318 9:30-10:45am.

Prerequisites & Co-Requisites

CSc 210, or equivalent prior software development experience. Speak with the instructor or a computer science academic advisor to determine if your background will suffice.

Instructor & Teaching Staff

There will also be one or more TAs.

Course Format and Teaching Methods

The course will meet for two 75 minute time slots per week. This course will use active learning, peer-teaching (if possible), and flipped-classroom teaching techniques.

By active learning, I mean that class time won’t be just 75 minutes of me talking. Instead, class meetings will include a number of in-class activities (ICAs) for you to work on individually and/or in a group. Thus, you can spend some time “actively” learn, rather than “passively” listen to the instructor.

By peer-teaching, I mean that you will have opportunities to learn from your classmates, and vice-versa. In many of the in-class activities, you will be able to work on groups and help each-other when necessary.

By flipped-classroom, I mean that you will often be assigned reading or other material to complete before attending each class meeting time. By doing this, you will come to class with (at least some) preparation. This will hopefully result in more class time allocated towards active learning!

Course Objectives

Students will learn how to develop applications for mobile devices. The course will cover how to build applications for the Android platform using Java, XML, and the Android development API. The course will also cover a number of platform-specific APIs commonly used in mobile applications such as maps, location services, camera, and local storage.

Learning Outcomes

A successful CSc 317 student will be able to:

Coursework and Grading Policies

The breakdown of grades in this course is as follows:

There will be a weekly quiz to be taken via gradescope. These quizzes will make up 10% of the student grade. The quizzes may cover topic(s) from a reading, class, or PAs.

There will be approximately 8-10 programming assignments throughout the course, worth 30% of the grade. Many, or perhaps all, will be individual projects.

There will be three exams throughout the course. The first two will be worth 10%, and the final 20%, for a total of 40%. These exams may cover material from class, the programming assignments, the final project, and the readings. Exams will be given in an online modality.

The final project will be worth 20% of the course grade. This will be a large-scale project requiring students to construct a mobile application, from idea to final product. Students will be expected to work on these in groups of 2-3 students, though exceptions may be made if a student has a strong desire to work on a project individually. Groups should be approved by the instructor.

The instructor and teaching staff will do their best to have grades back to students within 1 week. This includes, but is not limited to, grades for exams, projects, programming assignments, attendance, and quizzes. Once a grade has been entered for a particular item on the digital gradebook, students have at most 5 days to dispute the grade. This includes disputes related to excuses such as sickness, personal matters, dean’s excuses, etc. If 5 days pass and there has not been such a request, the grade is final.

The correspondence between percentage grade and numeric grade is as follows:

Late Days

In this class, you are given 2 late days for the semester. What this means is that you are allowed to submit up to two assignments within 24 hours after the due date throughout the semester, without penalty. You should not burn through all of these free late days on the first two assignments though! Consider saving some for later in the semester, when you might be in dire need :). You may only use late days for regular PAs. You cannot use them for quizzes, exams, or the final project. Any late work beyond the due date and or an available late day will result in a zero.

Final Exam

The final exam will be on Thursday May 12th 10:30am-12:30pm. There will be no make-up opportunities for the final exam.


There will be a group project towards the end of the semester. There also might be other groups project(s) during the semester.


Though there will be many required readings (see the class schedule), there is not a textbook that you are required to purchase.

Equipment and Software

For this class you will need daily access to a computer running Windows, MacOS, or Linux. You will also need regular access to reliable internet signal.

You should have a computer, or have regular access to a computer, that can support the Java runtime, Android studio, Android virtual device runner, and other software. If you have a personal computer, you should download and install these software on your machine.

Getting Help

Likely, some (or many) of you will want some help at one or more times throughout the course. The instructor and teaching staff provide a number of opportunities to receive help when you are stuck.

The instructor (Ben) will have several office hours each week. The TA(s) will also have office hours.

If you are unable to make office or lab hours, you can also get help online. You can ask your question(s) on Piazza, and you are welcome to post questions and get help from the TAs, other students, or the instructor. However, you may not publicly post any of your code or solutions to problems. If you are making a public post (visible to the entire class) make sure you do not include this. If you would like to include this, post to the instructors only.

If you are ever stuck, ask for help!


Unless otherwise specified, you may not work in groups on any coursework. This includes quizzes, exams, programming drills, programming assignments, etc. You may not share code, copy/paste code, or look at each-others code. The instructor will be using software to help detect cheating (similar code).

If cheating is detected on your work, penalties may include (but are not limited to):

Course Schedule

See the schedule page on the class website for the topic and reading schedule.

Department of Computer Science Code of Conduct

The Department of Computer Science is committed to providing and maintaining a supportive educational environment for all. We strive to be welcoming and inclusive, respect privacy and confidentiality, behave respectfully and courteously, and practice intellectual honesty. Disruptive behaviors (such as physical or emotional harassment, dismissive attitudes, and abuse of department resources) will not be tolerated. The complete Code of Conduct is available on our department web site. We expect that you will adhere to this code, as well as the UA Student Code of Conduct, while you are a member of this class.

Classroom Behavior Policy

To foster a positive learning environment, students and instructors have a shared responsibility. We want a welcoming environment where we can challenge ourselves to succeed. To that end, our focus is on the tasks at hand and not on extraneous activities (e.g., texting, chatting, reading a newspaper, making phone calls, web surfing, etc.).Students are asked to refrain from disruptive conversations with people sitting around them during lecture. Students observed engaging in disruptive activity will be asked to cease this behavior. Those who continue to disrupt the class will be asked to leave lecture or discussion and may be reported to the Dean of Students.

Threatening Behavior Policy

The UA Threatening Behavior by Students Policy prohibits threats of physical harm to any member of the University community, including to oneself. See

Accessibility and Accommodations

At the University of Arizona we strive to make learning experiences as accessible as possible. If you anticipate or experience physical or academic barriers based on disability or pregnancy, you are welcome to let me know so that we can discuss options. You are also encouraged to contact Disability Resources (520-621-3268) to explore reasonable accommodation. Please be aware that the accessible table and chairs in this room should remain available for students who find that standard classroom seating is not usable.

Code of Academic Integrity

Students are encouraged to share intellectual views and discuss freely the principles and applications of course materials. However, graded work/exercises must be the product of independent effort unless otherwise instructed. Students are expected to adhere to the UA Code of Academic Integrity as described in the UA General Catalog. See

The University Libraries have some excellent tips for avoiding plagiarism, available at

Selling class notes and/or other course materials to other students or to a third party for resale is not permitted without the instructor’s express written consent.

Violations to this and other course rules are subject to the Code of Academic Integrity and may result in course sanctions. Additionally, students who use D2L or UA e-mail to sell or buy these copyrighted materials are subject to Code of Conduct Violations for misuse of student e-mail addresses. This conduct may also constitute copyright infringement.

UA Nondiscrimination and Anti-harassment Policy


Additional Resources for Students

UA Academic policies and procedures are available at Student Assistance and Advocacy information is available at

Obtaining Help

Makeup Policy for Students Who Register Late

Students who register after school has already begun are not guaranteed to be given the opportunity to make up late work.



As we enter the Spring semester, our health and safety remain the university’s highest priority. To protect the health of everyone in this class, students are required to follow the university guidelines on COVID-19 mitigation. Please visit

Absence and Class Participation Policy

The UA’s policy concerning Class Attendance, Participation, and Administrative Drops is available at:

The UA policy regarding absences for any sincerely held religious belief, observance or practice will be accommodated where reasonable:

Absences pre-approved by the UA Dean of Students (or dean’s designee) will be honored. See

Incomplete (I) or Withdrawal (W):

Requests for incomplete (I) or withdrawal (W) must be made in accordance with University policies, which are available at and respectively.

Course Communications

General course communication may happen via in-class announcements, email, and discord.

Subject to Change Statement

Information contained in the course syllabus, other than the grade and absence policy, may be subject to change with advance notice, as deemed appropriate by the instructor.