Madden 25 Companion App Bugs
First off, just wanted to thank EA for updating the Madden Companion App quickly this year! However, there are several bugs that are causing frustrations for Franchise users. 1. "OOPS, SOMETHING WEN...
Forum Discussion
+1
API access would make Madden crazy sticky, as folks would develop all kinds of awesome tools and community around the APIs, increasing the enjoyment and engagement of the community.
The APIs already exist internally. Making them publicly accessible is a one-time lift that is likely lower cost to maintain than the app.
Heck, I'm friends with many folks who already know your export schema by heart, I'm friends with guys who know how to parse and compose your arcane binary roster format (from PS2 era!), I currently manage APIs professionally on a much larger scale than Madden--just bring us in and give us the go-ahead.
- @KeyLimeSoda I agree completely. I get they might not want to spend time on the Franchise side of the app, but that’s where the community can come in. Why not open the API and let us do all the work?
There's some work to open up the APIs. You'd need to fuzz them and harden them against potential DDOS attacks--neither of which are that challenging.
You'd also still have the issue of authentication. For example, how would the Neon service be able to call the EA servers to get my data? You'd need to have an auth system that allows folks to login directly to EA and then returns an access token to Neon to be able to make calls to the APIs on their behalf. And there's some risk in there that scammers would try to get folks to login to their site instead of EA.
You'd also need to document the APIs and notify folks of changes, but this isn't a commercial application so you're not looking at any serious kinds of SLAs.
All told, it's not without challenges, but the whole project could be done with 3-6 months of a senior dev or less, depending on which pieces are already in place.
