605.686.8VL - Mobile Application Development for the Android Platform

Computer Science
Summer 2023

Description

This project-oriented course will investigate application development for the Android mobile platform. We will explore techniques for building well-structured applications, from local and remote data access using databases and REST APIs, through view models that synchronously and asynchronously manage and expose that data, to a Jetpack Compose user interface layer for a simple specification and testing. Assigned projects include demonstrations of full data flow from database to user interface, use of graphics and user-screen interaction, Google Maps, REST API communication and testing. Prerequisites: Strong comfort with Java and its basic APIs. Comfort with concepts such as callbacks, threads, lists, and maps. EN.605.603 Object-Oriented and Functional Programming in Kotlin is recommended but not required. Course Notes: This course is taught using Kotlin, the primary language for Android development (and required for Jetpack Compose). Kotlin knowledge is not required for this course, and its basics will be covered from the assumption that students are very comfortable with Java. Tools for developing and testing Android apps are available free of charge. Note that Android emulators may run slowly on some machines; physical Android devices are strongly recommended, but not required, for this course.

Expanded Course Description

Prerequisites

This course relies on a high comfort level with the Java or Kotlin language and basic APIs. The course moves quite quickly and there is no time to learn Java while taking it.

This course includes a Kotlin primer (which assumes Java knowledge), and will demonstrate other Kotlin constructs in presented examples.

You will need to feel very comfortable with:

If you are not comfortable with these concepts and Java or Kotlin syntax, the assignments in this course can be quite difficult to complete.
The 605.603 Object-Oriented and Functional Programming in Kotlin course is recommended but not required, though after this course piques your interest in the language, you'll likely want to take it...

Instructor

Profile photo of Scott Stanchfield.

Scott Stanchfield

scott.stanchfield@jhu.edu

Course Structure

Course materials are divided into modules. For online sections, the Modules can be accessed by clicking Course Content on the menu in Canvas.

Each week contains one or more modules. Please check the Course Outline for a detailed overview of the course layout.

For online sections, each module contains one or more videos and slides. This content is available for all sections, online or face-to-face, but for face-to-face sections, this material is considered supplementary. The material taught in the face-to-face classroom is considered the material you must use for the course.

For face-to-face sections, I will video record the lectures using Camtasia and post them along with any sample code after the class meeting.

Course Topics

(Order of some topics may vary based on term)

Course Goals

Explore the differences between mobile and desktop application development, and demonstrate these differences through the development of Android phone and tablet applications.

Course Learning Outcomes (CLOs)

Textbooks

No textbooks are required for this class.

Other Materials & Online Resources

Android Developer Site: http://developer.android.com

K
otlin Language:https://kotlinlang.org

I
nstructor Site: http://javadude.com

Required Software

Please see the "Course Hardware and Software" section of the Introduction module for details

Student Coursework Requirements

Introduction

This course is graded on 7-8 programming assignments (may vary per term). There are no tests or graded discussions in this class.

Late submissions will be reduced by one letter grade for each day (or partial day) late (no exceptions without timely prior coordination with the instructors).

Expected Conflicts: If you expect any issues with turning in work on time, please see the instructor as soon as you know. If I know in advance about business travel and expected high workloads, I can work with you. However, letting me know a day or two before an assignment is due is not acceptable (you've had time to work on the assignment prior to the interruption).

Please see "Assignments" and "Grading" section in the Introduction module for more details.

Grading Policy

Grade Scale

Assignments are worth 4 points each, equating to a GPA-style letter.

My grader and I assign letter grades first, then convert them to numbers and apply late penalties. The grading scale from letters to numbers is as follows:

Letter GradeNumerical Equivalent
A4.0
A-3.7
(A/B border)3.5
B+3.3
B3.0
B-2.7
(B/C border)2.5
C+
2.3
C2.0
C-1.7
(C/D border)1.5
D+1.3
D1.0
D-0.7
F0


Note that there is no A+. We had been reserving that for "exemplary" submissions, but some students considered an "A" as lost pointsA+.

Your final grade WILL NOT include +/- designations. A/A- both count as "A" and "4" for University GPA purposes(and similar for other letter grades).

Please see the "Grading" section of the Introduction module for more details.


Course Policies

Using Open Source Content and My Code Examples

Note that you may copy small sections of code and other content you find online **if and only if** you attribute it and the code is freely copyable with a license that says it's ok to copy. Place a comment above the copied section stating where you found it and the license that applies.

You may copy code from my class examples as well. Once again, attribute it. Assume that any code I do not explicitly mark is licensed for your use only in this class and for not other purpose.

Code from the course sample code repository is licensed Apache 2 (see the LICENSE-code.txt file in the repository) and can be used/incorporated into your own projects with attribution.

Code that I write live in face-to-face class or post in a discussion forum are not licensed for any use outside this class. You may not post or distribute any this code.

Your Work in this Class

PLEASE READ THIS SECTION CAREFULLY. I HAVE HAD TO SIGNIFICANTLY REDUCE GRADES AND/OR CONVENE ACADEMIC INTEGRITY HEARINGS BECAUSE OF ISSUES MANY TIMES IN THE PAST.

Please be sure to carefully read the Academic Misconduct Policy.

You are encouraged to discuss the course material with each other as you sort through concepts that may be difficult to comprehend. However, the line between collaboration and cheating needs to be carefully delineated.

Whenever you turn in work with your name on it to be evaluated, graded and included in your record it must represent an individual effort by you alone.

If you include direct quotes or code from any source in your discussions or project submissions, you must provide attribution. Note that you are only allowed to include code when the license for that code is explicitly stated (such as what I mention above for course code samples) and that license is open source.

Note: I have had issues with plagiarism during several terms. I am very good at catching this! Work that you submit as your own must actually be substantially your own. Any code that you borrow must be attributed.

Let me repeat: You cannot discuss what your code or project structure will look like. It's ok to discuss the concepts and code I have demonstrated, but you cannot discuss how to apply those concepts to the homework assignments.

Johns Hopkins Student Assistance Program (JHSAP)

If you are struggling with anxiety, stress, depression, or other wellbeing-related concerns, please consider contacting the Johns Hopkins Student Assistance Program (JHSAP). If you are concerned about a friend, please encourage that person to seek out counseling. JHSAP can be reached at 443-287-7000 or http://jhsap.org.

JHSAP has counselors available at multiple Johns Hopkins campuses: East Baltimore, Eastern, Bayview, Washington, D.C., and Columbia.

Academic Policies

Deadlines for Adding, Dropping and Withdrawing from Courses

Students may add a course up to one week after the start of the term for that particular course. Students may drop courses according to the drop deadlines outlined in the EP academic calendar (https://ep.jhu.edu/student-services/academic-calendar/). Between the 6th week of the class and prior to the final withdrawal deadline, a student may withdraw from a course with a W on their academic record. A record of the course will remain on the academic record with a W appearing in the grade column to indicate that the student registered and withdrew from the course.

Academic Misconduct Policy

All students are required to read, know, and comply with the Johns Hopkins University Krieger School of Arts and Sciences (KSAS) / Whiting School of Engineering (WSE) Procedures for Handling Allegations of Misconduct by Full-Time and Part-Time Graduate Students.

This policy prohibits academic misconduct, including but not limited to the following: cheating or facilitating cheating; plagiarism; reuse of assignments; unauthorized collaboration; alteration of graded assignments; and unfair competition. Course materials (old assignments, texts, or examinations, etc.) should not be shared unless authorized by the course instructor. Any questions related to this policy should be directed to EP’s academic integrity officer at ep-academic-integrity@jhu.edu.

Students with Disabilities - Accommodations and Accessibility

Johns Hopkins University values diversity and inclusion. We are committed to providing welcoming, equitable, and accessible educational experiences for all students. Students with disabilities (including those with psychological conditions, medical conditions and temporary disabilities) can request accommodations for this course by providing an Accommodation Letter issued by Student Disability Services (SDS). Please request accommodations for this course as early as possible to provide time for effective communication and arrangements.

For further information or to start the process of requesting accommodations, please contact Student Disability Services at Engineering for Professionals, ep-disability-svcs@jhu.edu.

Student Conduct Code

The fundamental purpose of the JHU regulation of student conduct is to promote and to protect the health, safety, welfare, property, and rights of all members of the University community as well as to promote the orderly operation of the University and to safeguard its property and facilities. As members of the University community, students accept certain responsibilities which support the educational mission and create an environment in which all students are afforded the same opportunity to succeed academically. 

For a full description of the code please visit the following website: https://studentaffairs.jhu.edu/policies-guidelines/student-code/

Classroom Climate

JHU is committed to creating a classroom environment that values the diversity of experiences and perspectives that all students bring. Everyone has the right to be treated with dignity and respect. Fostering an inclusive climate is important. Research and experience show that students who interact with peers who are different from themselves learn new things and experience tangible educational outcomes. At no time in this learning process should someone be singled out or treated unequally on the basis of any seen or unseen part of their identity. 
 
If you have concerns in this course about harassment, discrimination, or any unequal treatment, or if you seek accommodations or resources, please reach out to the course instructor directly. Reporting will never impact your course grade. You may also share concerns with your program chair, the Assistant Dean for Diversity and Inclusion, or the Office of Institutional Equity. In handling reports, people will protect your privacy as much as possible, but faculty and staff are required to officially report information for some cases (e.g. sexual harassment).

Course Auditing

When a student enrolls in an EP course with “audit” status, the student must reach an understanding with the instructor as to what is required to earn the “audit.” If the student does not meet those expectations, the instructor must notify the EP Registration Team [EP-Registration@exchange.johnshopkins.edu] in order for the student to be retroactively dropped or withdrawn from the course (depending on when the "audit" was requested and in accordance with EP registration deadlines). All lecture content will remain accessible to auditing students, but access to all other course material is left to the discretion of the instructor.