1. Choose your development path
Match equipment to the real tasks you must perform, not a brand or a presumed diagnosis. You can start with an iPad or other accessible device and still document why a separate workstation is required for certain development work.
| Path | What you need to demonstrate | Equipment approach |
|---|---|---|
| Learning and web coding | Edit code, use source control, preview accessible pages and run basic tests | Browser-based editor or accessible local editor, dependable internet access, keyboard or alternate input, backup and authentication |
| General software development | Run a selected language/toolchain, debugging, automated tests, local services and possibly containers | Choose a compatible local computer, remote workspace, or hybrid setup; measure memory, CPU, storage and access requirements against a representative project |
| Game and media development | Run the chosen engine, edit assets, test performance and input, export builds | Document engine-specific CPU/GPU, RAM, SSD, display, audio/input, backup and testing hardware requirements |
| Xbox console development | Use Microsoft's supported desktop tools and approved console build/test path | Windows x64 workstation and applicable SDK/tools; approved program and development-kit access where required — not merely a retail console |
2. Equipment checklist
- Compute: processor architecture, RAM, GPU and cooling appropriate to the actual language, engine and workload.
- Storage: working SSD space for project files, packages, builds and media; separate backup or versioned recovery strategy.
- Access: readable or magnified display, alternative input, screen reader/keyboard compatibility, usable editor and debugging interfaces.
- Software: operating system, editor/IDE, terminal, Git, SDK, dependencies, test runner, licenses and recurring services.
- Network: reliable internet, secure sign-in, remote access as needed, and wired connectivity only where required by testing or deployment.
- Continuity: power, updates, support, repair, warranty, project restore and recovery if a device becomes unavailable.
3. Compare minimum, preferred and optional
Minimum: the least accessible configuration that can complete and verify real learning or work tasks. Preferred: added capability tied to a specific workflow, accessibility or reliability gain. Optional: conveniences without a demonstrated requirement. Do not equate a faster machine with an eligibility or funding justification.
4. Existing Xbox workstation example
The source curriculum already documents a planning target for comfortable Windows/Xbox-related development: 8-core-class CPU, 32 GB RAM, 1–2 TB NVMe SSD and an engine-appropriate discrete GPU. These are not Microsoft minimum requirements, a universal developer specification or a purchase recommendation. Its September 26, 2026 budget example must be rechecked against current offers.
Read the technical game-development source · View the dated price research
5. Make an evidence-based equipment request
- Identify the career goal and representative project.
- Record software/engine, supported operating system and required tests.
- Document access barriers in terms of tasks, without disclosing unnecessary medical details.
- Test local, cloud and hybrid alternatives against the actual workload.
- Make a minimum, preferred and alternative specification list.
- Collect comparable, dated itemized quotes, including accessible peripherals and recurring costs.
- Ask the responsible counselor, employer or funder to decide; do not presume approval.
Use the technology plan, equipment justification and quote comparison. Keep private records outside public repositories.