Syllabus
Hello and welcome to the class! We are your instructors for this course, Sophie and Zach, and we’re incredibly excited to help you learn how to make Android apps this semester. It wasn't too long ago that we were learning the intricacies of Android ourselves, and now we wish to pass on the knowledge we've learned to you. It’s going to be a great semester and we can’t wait to get started!
Name | Role |
Sophie Meng | Course Instructor |
Zach Seidner | Course Instructor |
Emily Hu | TA |
Ram Peddu | TA |
Justin Guo | TA |
If you have a question for the course staff, ask a private question on Ed Discussion or schedule a meeting during office hours.
This schedule is tentative and subject to changes to Cornell's Spring 2023 academic calendar.
Lectures will be held in Gates 114 at 8:35-9:25pm every Monday and Wednesday.
Lectures will be held on Mondays whereas discussions will be held on Wednesdays. Discussions are meant to supplement what is being learned in lecture that week but will not introduce anything "new" in the sense that what's learned is an integral part to Android development.
Towards the end of the course, you'll be participating in the 2-week Hack Challenge alongside students from other AppDev courses, to create a full-fledged mobile application.
Outlined below is a schedule of our lectures, discussions, and projects (with their due dates).
Class Dates | Lecture Topic | Prepare for: | Project | Project Due Date |
10/4 | Intro to Kotlin & Android Studio | Creating a project & views | None | None |
10/9 | Cancelled, October break | | P1 | 10/17 |
10/11 | User input & documentation | Seekbars, in-class coding | P1 | 10/17 |
10/16 | Intents and Permissions | Demo & code-along | P2 | 10/23 |
10/18 | Coding Together | Intent & Logic Flow activity | P2 | 10/23 |
10/23 | RecyclerViews | Code-along | P3 | 10/29 |
10/25 | RecyclerView demo | Code-along, start project | P3 | 10/29 |
10/30 | Navigation & Fragments, Hack Challenge Intro | Code-along | P4, Hack Challenge Teams | 11/5 |
11/1 | Navigation demo | Code-along, start project | P4, Hack Challenge | 11/5 |
11/6 | Networking & Persistent Storage | Code-along | P5, Hack Challenge | 11/15 |
11/8 | Networking demo | Code-along, start project | P5, Hack Challenge | 11/15 |
11/13 | In-class coding | | P5, Hack Challenge | 11/15 |
11/15 | Bonus Lecture | | Hack Challenge | |
11/20 | Bonus Lecture | | Hack Challenge | |
Note: for Fall 23, you can take this course for up to 2 credits, in the event of credit overload. However, regardless of the number of credits you're signed up for, you are still expected to complete 2 credits worth of work.
This is a 2 credit S/U course and grading will be determined by all projects, with more emphasis on the Hack Challenge final project.
Each project is worth 10-12 points, and the final project is worth 20 points: 10 points for the midpoint submission and 10 points for the final submission. Each project (with the exception of the first) will have extra credit opportunities for you to challenge yourself and dive deeper into Android development.
To pass this course, you will need >= 70 points by the end of the semester.
Assignments | Weight |
P1 - Trichromatic | 15 |
P2 - Trochromatic Extended | 12 |
P3 - Spotify Playlist | 12 |
P4 - Wallpaper Gallery | 13 |
P5 - Notes App | 13 |
| |
Hack Challenge | 20 |
Participation | 15 |
Total | 100 |
Passing Score | 70 |
Attendance is required for all students of the course for the lectures, and are permitted at most 1 absence (not including bonus lectures which do not require attendance). This is subject to change based on the status of Cornell's campus and COVID guidelines. Attendance will be taken through a Google Form, a QR code for which will be displayed only to students during lecture.
For the discussions, we ask that you make it to 4 out of the 6 of the discussions slated to receive full credit for attendance.
You are given 6 slip days that you can use on any of the assignments aside from the Hack Challenge project. Each assignment will be opened for late submissions for an extra 2 days after the regular deadline. If you submit an assignment late and run out of slip days, assignments will be automatically docked 2 points.
If you are unable to finish the project as a result of an error, please add a note in a README.txt file explaining:
- 1.the error that you are encountering
- 2.the suspected cause of the error (doesn't have to be correct!)
- 3.the solutions you have attempted to resolve the error
This helps out the grader quickly find and debug errors and give partial points for effort!
It is also helpful to leave broken code in your project (but have it commented out). This will allow us to better understand your thought process and give you partial points for missing features.
- If you ever need help, you can always post on the course Ed Discussion. We will be monitoring the class feed to be helping you! For more complicated questions, try to attend office hours if at all possible.
- Office hours are held at multiple times throughout the week by instructors and TAs. See the schedule below for details.
We are here to help you succeed! Our number one goal is for you to LEARN Android development and we will be with you each step of the way to make sure that happens 👏.
Name | Hours | Location |
Justin Guo | Sunday 3-4 PM | Hollister 312 |
Sophie Meng | Monday 6-7 | Hollister 362 |
Maxwell Pang + Zach Seidner | Tuesday 3-4 PM | Hollister 206 |
Emily Hu | Wednesday 7:15-8:15 PM | Upson 225 |
Aarushi Singh | Thursday 5:45-6:45 PM | Hollister 368 |
Corwin Zhang + Ram Peddu | Friday 5-6 PM | Hollister 312 |
At the end of the course, you and up to three other members of AppDev courses (Intro to Digital Product Design, Intro to Backend Engineering, Intro to iOS) will have the chance to work in a group and apply all that you’ve learned in the course to create a functional, polished app.
Participation in the Hack Challenge is required as the final project for this course. The course staff will judge the best apps and there will be sponsored prizes! Last semester’s winners won Google Homes, bluetooth speakers, Echo Dots, or Chromecasts. This could be you this semester, so start brainstorming ideas!
As with any other course at Cornell, the code of academic integrity will be enforced in this class. All individual projects must be done by yourself. All University-standard Academic Integrity guidelines should be followed. This includes proper attribution of any resources found online, including anything that may be open-sourced by AppDev. The University guidelines for Academic Integrity can be found here.
We encourage using the internet to learn more about Android development, but again, any code you submit must be written by you!
Last modified 24d ago