1. Drop an email to me with the subject line as "Learning Windows 8 Game Development - Review Request" on [email protected]
2. State in your email your choice of websites for posting your book-review (can be your blog or website, Amazon, Goodreads, DZone, Slashdot)
Learning Windows 8 Game Development teaches you how to create exciting games for tablets and PC on the Windows 8 platform. Make a game, learn the techniques, and use them to make the games you want to play. Learn about graphics, multiplayer options, how to use the Proximity + Socket APIs to add local multiplayer, how to sell the game outright, and In-App Purchases.
Subject Line for Review Request: "Learning Windows 8 Game Development - Review Request"
Platforms for Posting Review: You can post your review on your blog or website, Amazon, Goodreads, DZone, or Slashdot. Book Description: "Learning Windows 8 Game Development" teaches you how to create exciting games for tablets and PCs on the Windows 8 platform. The book covers various aspects such as graphics, multiplayer options, using Proximity + Socket APIs for local multiplayer, selling games outright, and implementing in-app purchases. If you're interested in reviewing the book, you can follow the instructions provided in your post. For more detailed information about the book, you can visit the book page: http://www.packtpub.com/learning-windows-8-game-development/book. If you have any specific questions or need further assistance, feel free to ask!
A Windows 8 game development book could still be useful for:
Core game loop design
Asset management
Input handling concepts
Performance thinking
Debugging discipline
Basic graphics pipeline ideas
Those fundamentals age much more slowly than the platform APIs.
Where it will likely feel dated
Windows 8 app model
Store packaging and deployment guidance
UI framework assumptions
Toolchain screenshots and setup steps
Platform-specific monetization or certification details
So the book may still be valuable as a foundations book, but not as a modern workflow manual.
For someone learning today
If the goal is current indie or Windows-focused game development, I’d treat it like this:
Read it for architecture and performance habits.
Double-check any API-specific instructions.
Compare its workflow against modern engines and tools.
Use newer docs for publishing, input APIs, graphics APIs, and deployment.
Practical test for a review
If someone reviews it, I’d suggest scoring it in three parts:
Still useful fundamentals
Outdated platform-specific content
What a 2026 reader should replace with newer tools/docs
If you want, I can help draft a modern review checklist for an older Windows game dev book so people can quickly judge whether it is still worth reading.