SPEAKER NOTES: Welcome everyone to CS 3180. Today sets the tone for the entire semester. We have a real client, a real problem, and a real app to build. By the end of this session students will know who Hope Foundation is, why we're building their app, and have Android Studio running on their machines.

SPEAKER NOTES: Before we meet the client, let's do a quick orientation to the course so students know what to expect. Keep this high level — they'll read the syllabus on their own time.

SPEAKER NOTES: Emphasize "project-based" and "real client." This isn't a toy course — by week 15 students will have something in their portfolio. The single-platform focus is intentional: going deep on Android with Kotlin is far more valuable than a surface-level tour of everything.

SPEAKER NOTES: Walk through each component briefly. Stress that the best-10-of-12 quiz policy gives students flexibility — missing two quizzes won't hurt them. The team project is the capstone: they'll present working software to the class and optionally to Hope Foundation.

SPEAKER NOTES: Be direct here: AI is not banned, but submission without understanding is academic dishonesty. Walk through the three-step model. A good test: "Could you explain this code in a live code review?" If yes, great. If not, that's a problem. Copilot and Claude are on the approved tools list in the syllabus.

SPEAKER NOTES: Now the fun part. Students will spend the whole semester building for Hope Foundation. Treat this introduction like a real client kickoff meeting.

SPEAKER NOTES: Give students a moment to appreciate the stakes. This isn't a contrived homework problem — real money for real kids. The scramble format means every player hits on every hole and the team records the single best score. That scoring logic will be central to the app.

SPEAKER NOTES: Paint the picture of tournament day: 20+ teams, 18 holes, scores trickling in on crumpled paper cards. The volunteer at the scoring table is overwhelmed. Disputes happen. The leaderboard isn't live. Students can immediately see how a mobile app fixes all of this.

SPEAKER NOTES: Keep scope expectations realistic. Version 1 is the MVP: score entry, leaderboard, scorecard history. We're not building registration, payment processing, or social features. This focus makes the project achievable in 15 weeks while still being genuinely useful.

SPEAKER NOTES: Now we zoom out before zooming in. Students need context for why we chose Android and Kotlin — not just "because the syllabus said so."

SPEAKER NOTES: This table gives students a mental map of the industry. All three approaches are valid professionally. The choice depends on budget, team, and target audience. Ask: "If you were starting a startup tomorrow, which would you pick?" Expect divided opinions — that's the point.

SPEAKER NOTES: The market share number grounds the decision. For a charity tournament serving a general public, you want the platform most people carry. Kotlin and Compose are explicitly the industry direction — job postings increasingly list Compose experience. This is the right tool for both the client and students' careers.

SPEAKER NOTES: Hands-on time. The goal by end of class: everyone has Android Studio open. The goal by end of the week: everyone has an emulator running their first Compose app.

SPEAKER NOTES: If students have IntelliJ from another course, Android Studio will feel immediately familiar. Mention that it's free — no licenses to manage. If anyone is on a Chromebook, flag that now; there are workarounds but they need to plan ahead.

SPEAKER NOTES: Walk through each item. The SDK Manager is under Tools → SDK Manager. API 34 is Android 14 — current stable target. AVD = Android Virtual Device; creating one takes a few minutes. Gradle sync is the first thing Android Studio does when opening a project — watch for red error banners.

SPEAKER NOTES: If you're live-demoing, do this now. The emulator takes 30–60 seconds to boot the first time. While it's loading, explain that x86_64 is chosen because it runs natively on most laptops (ARM images are for Apple Silicon Macs). Students on Apple Silicon: use the ARM image instead.

SPEAKER NOTES: Walk through this live. Package name convention: reverse domain of your institution. API 26 minimum gives us ~95% device coverage while still using modern APIs. The first build always takes a few minutes while Gradle downloads dependencies — this is normal, not a bug. Students will see "Hello Android!" in Compose.

SPEAKER NOTES: Final section. Keep it brief but don't skip it — students need to know where to get help before they leave.

SPEAKER NOTES: Be explicit that install problems are normal and expected. Students who finish early should help neighbors — this builds community and reinforces the setup steps. The Wednesday deadline is firm because the demo session assumes a working environment.

SPEAKER NOTES: Pull up the channel invite link. Make joining a class activity right now so it actually happens. The "post your setup status" prompt gives quiet students a low-stakes way to participate and gives you a real-time sense of where the class is before Wednesday.

SPEAKER NOTES: Show the exact format expected. The point is not to penalize AI use — it's to ensure students engage with the code. A disclosure like "Copilot wrote everything, I changed nothing" is a problem. A disclosure like "Copilot generated the data class, I added the null-safe score field and wrote all the tests" shows real engagement.

SPEAKER NOTES: Close with the roadmap so students leave with a clear picture of the week. The zyBook chapter covers Android fundamentals — students should read it before Wednesday. If they haven't installed Android Studio yet, that's the priority tonight. Remind them: post in #setup-help if stuck.

SPEAKER NOTES: Leave 5 minutes for questions. Walk around and check on installs in progress. If the room has strong Wi-Fi, some students may get to the "Hello Android!" screen before leaving. Celebrate that when it happens.