§008

Winter 2026
Prereq: EECS 281; Satisfies ULCS/FlexTech

Images: : [1, 2]
Have you built a full-stack mobile app that handles real-time streaming data? Have you created mobile AI agents that can use tools? How do you ensure your UI is not janky? Have you built a mobile app that interacts with the device's camera, mic and speakers, GPS, and biometric sensors?

In this course, EECS 498-008: Mobile Apps with Real-time Updates and Integrated AI (ULCS), we build mobile apps that integrate GenAI/LLM with tooluse to solve user problems. We will build using concurrent coroutines to ensure responsiveness, without heavy OS context switches. If you want to learn fullstack mobile app development with AI integration and reactive handling of streaming data, see you in class!

You have never written a line of mobile or backend code? Don't worry, we will start from how to use a mobile IDE and progress all the way to AI-powered reactive native mobile apps.

Note:

This course has combined lectures with the MDE special-topic course EECS 498-002, Mobile App Design and Development. Only the projects and exams are different between them. The MDE-version of the course (498-002) has a team-defined semester-long project with presentations but no exams. The ULCS version (498-008) has smaller projects throughout the term, with two exams, like other ULCS courses. You can sign up for either, but not both. If you have any questions about either course, please feel free to ask Prof. Sugih Jamin (uniqname: sugih).

Students who have taken EECS 441 Sections 3&4 with Prof. Jamin also cannot take either course for credit.

Room & time  

 
Lecture: 1008 FXB
Discussions: 2505 GGBL
TTh 10:30 - 12:00
F 10:30-11:30

Staff  

Sugih Jamin (sugih)
OH: TTh right after lecture and by appointment
Chenglin Li (lchengl)
OH: MonTue 6-6:30 at BBB Learning Center Table 1

Office hour locations:

Sugih's by-apppointment office hours will be held in 4737 BBB. GSI's office hours will be held in the BBB Learning Center, Table 1. We also have a Discourse discussion forum.

Required readings:

There is no textbook. Instead, the tutorial specs and lecture notes are both required readings. We will post important course-related information and answers to FAQs on Announcement page and on Discourse.

Tutorials (optional)

Preliminaries:
llmChat
Maps
Audio
Images
llmTools
Signin

 ULCS Projects

llmPlay
llmAction

 Course Schedule

 Grading Policy

Letter grades

Letter grades will be posted after the last day of final exams.
There is no "standard" mapping from grade point ranges to letter grades.

Policy on collaboration

Projects, homework, and tutorials may be completed either individually or in teams of at most 2 people. You may partner differently for each assignment.

Acts of cheating and plagiarizing will be reported to the Engineering Honor Council. Cheating is when you copy, with or without modification, someone else's work that is not meant to be publicly accessible. Plagiarizing is when you copy, with or without modification, someone else's work that is publicly available without acknowledging the original author. Please further review the College of Engineering Honor Code.

If you received substantial help from another person or AI/LLM to complete your assignment, you must name and acknowledge them in your work. If you use any published materials (books, papers, or materials found on the Web) in any submitted work, you must give full citation that enable the location of the original materials (for example, the URL of the Web site).

Regrade and late submission

You will have ONE opportunity to fix bugs in each graded tutorial by the assigned office hour following the tutorial's due date. Corrected code can be credited up to 50% of its original grade points. Code not submitted by deadline will be ineligible for regrade. To be eligible for regrade, do not modify the code on your git repo past the due date. Code with commit time past the deadline will not be eligible for regrade.

Other than the tutorials, you have two business days from when a grade is communicated to you to ask for regrade. To ask for regrade, you must submit a written request explaining the technical reasons that would make a regrade necessary. A regrade means regrading your whole work and may result in an overall lower grade.

You will have at least one week to complete each assignment. Extensions will be given only for documented medical and family emergencies.

Cloud services such as compute engine (AWS or GCP), git repo (GitHub), collaborative apps (Trello, Figma), video hosting site (YouTube) have been known to become inaccessible for 24 hours or more. Video encoding and uploading can take longer than expected. Your laptop could crash or you could be locked out by Bitlocker or other security measures on your laptop. CAEN/ITCS computer labs could be full or closed and machines slowed down due to overload. NO extension will be given for any of these reasons. Plan on them happening and have your work done a couple of days before any due dates. Extensions will also not be given for job interview nor any other non-emergency activities.

Keep a backup of your work off-site, for example, on a remote git repo, and keep your backup fresh.

Class participation extra credits

Completing in-lecture code exercises allows you to earn extra credits which can be used to top up your overall course grade. You cannot make up for missed extra-credit opportunities.

 References