2.4. GitHub Desktop and GitHub Mobile
GitHub's web interface isn't the only way in — and the exam tests whether you know when each alternative client actually fits the task at hand.
💡 First Principle: GitHub Desktop and GitHub Mobile extend GitHub's workflow outside the browser, each trading away some capability in exchange for fitting a specific context. Desktop is a graphical Git client for people who want to commit, branch, and push without memorizing Git commands. Mobile is a lightweight companion for reviewing and responding on the go — it's built for triage, not for writing code.
| GitHub Desktop | GitHub Mobile | |
|---|---|---|
| Runs on | Your computer | Phone or tablet |
| Core purpose | Local Git operations with a GUI | Review, triage, notifications on the go |
| Can you edit code? | Yes (via your local editor) | No — read, comment, and merge only |
| Can you commit? | Yes | No |
| Needs a full IDE? | No, but pairs with one | N/A |
⚠️ Exam Trap: GitHub Mobile is built for reviewing and responding to activity — approving pull requests, triaging issues, managing notifications — not for writing or committing code. That capability sits with Desktop, the web editor, or a local Git client.
Reflection Question: A developer wants to approve a pull request from their phone during a commute, with no laptop nearby. Which GitHub client fits, and why wouldn't the other one work here?
