605.686.81 - Mobile Application Development for the Android Platform

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:

• The Java or Kotlin language, especially
  • Class and interface inheritance
  • Properties (fields with getters and setters)
  • Inner classes (including anonymous inner classes [Java] or objects [Kotlin])
  • Using callbacks/listeners/observer pattern
  • Using threads [Java] or coroutines [Kotlin] in your application
  • Debugging by reading exception stack traces
    
• Writing basic XML files in an editor
• Simple SQL database statements (some basics are covered in the course, but having some database experience will help greatly)
  
• Basic data structures in Java or Kotlin (lists, maps)
  

Course Structure

For online sections, modules are available at https://androidbyexample.com. Modules may be textual, video, or a combination. Note that this content is available for all sections, online or virtual-live, but for virtual-live sections, this material is considered supplementary. The material taught in the virtual-live sessions is considered the material you must use for the course.

For virtual-live sections, I will video record the lectures 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 applications.

Textbooks

No textbooks are required for this class.

Other Materials & Online Resources

Required Software

Android Studio: https://developer.android.com/studio

(instructions provided in course materials)

Student Coursework Requirements

This course is graded on 6-10 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).

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

Grading Policy

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

Note: Percentages for coursework map back to letters as follows:

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).

All assignments must be your own work. Working together or other academic integrity violations will result in a minimum penalty of 0.0 for the assignment in question.

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

Course Evaluation

I frequently update this course and appreciate any and all feedback. Please complete the course evaluations (midterm and final). If you have other thoughts on the course, what you liked, disliked, topics you wanted to see or any other feedback, please send me an email or post on the Course Feedback discussion forum.

Course Policies

Using Open Source Content and My Code Examples

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 (linked below).

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.

The minimum penalty for academic misconduct is a 0.0 on the assignment in question, but can be more severe depending on the circumstances.

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.