Steam API
01. Problem: Decision Paralysis
In a group of busy friends, the "window of opportunity" to play together is often small. We found that a significant portion of our limited free time was being wasted on the same repetitive cycle:
02. Solution: Quick Fix
A web-based comparison engine that automates the audit process by leveraging the Steam Web API:
03. Key Technical Challenges
Challenge: Steam Privacy Settings
If a user hasn't explicitly set their "Game details" to Public, the GetOwnedGames call returns an empty result, even with a valid API key. Implemented a fall back to just inform the user that their profile is private.
Challenge: Interacting with the API
The API is massive but doesn't allow for super selective filtering so it was hard to optimise and limit the amount of requests being sent, ended up just having to brute force at times but ensuring that i was not breaching rate limit.
Technologies Used
- API
- Node.js (API Layer)
- JSON
- Javascript
What I Learned
"I mastered API integration by navigating Steam's data constraints and privacy hurdles. Additionally, I learned to apply set-theory logic to solve a real-world problem, transforming fragmented library data into a streamlined, actionable tool."