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 companion app for working on GitHub itself — triage, review, and quick file edits committed straight to the remote — with no local clone on the device.
| GitHub Desktop | GitHub Mobile | |
|---|---|---|
| Runs on | Your computer | Phone or tablet |
| Core purpose | Local Git operations with a GUI | Triage, review, and quick edits on the go |
| Can you edit code? | Yes (via your local editor) | Yes — any text, code, or Markdown file, including workflow files |
| Can you commit? | Yes, to your local clone, then push | Yes, committed directly to the branch on GitHub |
| Local clone on the device? | Yes — that is the point | No |
| Local Git operations (merge, rebase, stash)? | Yes | No |
⚠️ Exam Trap: Do not assume GitHub Mobile is read-only. It edits files and commits them, and can open and merge pull requests. What it does not do is keep a local clone or run local Git operations — the distinction from Desktop is WHERE the work happens (directly on GitHub versus on a working copy on your machine), not whether you may commit at all.
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?
