Challenge 2: Why Android Studio Isn't Part of This Course's JetBrains Coverage — Solution Walkthrough

Why Android Studio is excluded despite being IntelliJ-based:

Per this chapter's own material, Android Studio: The IDE Itself has
its own dedicated course specifically because its entire focus is
Android development tooling — the Layout Editor, the Profiler, the
AVD Manager, Gradle-aware project structure — not a general survey of
editors and IDEs. The fact that it happens to be built on the
IntelliJ Platform is a genuinely relevant detail (and one this
course's own Chapter 4 cross-references directly), but it doesn't
make that course part of a general editor survey.

What actually determines the boundary:

This course's own scoping principle is about covering general-purpose
editors and IDEs not already owned elsewhere — Android Studio is
excluded not because it's unrelated to the JetBrains platform, but
because its own course already exists and is scoped around a
completely different subject (Android app development) rather than
editor/IDE comparison for its own sake.

Why the cross-reference still matters:

This course's own JetBrains chapters build directly on Android
Studio's own Chapter 1 for the shared-platform architecture, exactly
because that material is relevant and already covered well elsewhere
— reusing it through a cross-reference rather than either duplicating
it or awkwardly folding Android Studio itself into this course's own
JetBrains-family chapters.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the distinction between "shares an
underlying platform" and "belongs in this course's own scope" is
understood clearly — the two are related but genuinely separate
questions.