Exercise 1: Why Auth Is Cheap Here — Possible Solution
====================================================================

WHAT THE OTHER THREE COURSES WOULD NEED
------------------------------
Adding real user accounts to Food Tracker (FastAPI), Food Tracker (Django), or Food Tracker (React + Express) would require building password hashing, session or token management, and a users table or model - each a genuinely substantial piece of work built from scratch, since none of those three architectures come with an authentication system already provisioned.

WHY THIS COURSE'S VERSION IS CHEAPER
------------------------------
Firebase Authentication was already part of the Firebase project provisioned back in Chapter 1, alongside Firestore and Cloud Functions - it's infrastructure the course already paid for and already set up, not a new subsystem. Enabling the Email/Password provider and wiring up a few SDK calls (createUserWithEmailAndPassword, signInWithEmailAndPassword, onAuthStateChanged) is a genuine extension of what's already there, not new infrastructure that has to be built and secured from the ground up.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies password hashing, session/token management, and a users model as the real work the other three courses would each need to build themselves, and correctly explains that this course avoids that work because Firebase Authentication is already provisioned as part of the same platform used since Chapter 1.