Hi Sean, just checking to see if you can give us any idea of how everything went tonight. My app has now been downloaded by 2,000+ Palm webOS users and I bet a decent amount of them used the app tonight. I saw about 10 seconds more delay than normal on some calls at the start of the game and the start of the 3rd quarter, but otherwise the app ran beautifully! I was very pleased with the service.
I've really been working on how much API calling I do. In my latest version, it takes two API calls to get to the main app and three to make a roster move (one for the move, one to check and one to refresh the team page where the player was listed). I'm still trying to get roster moves down to two, but I'm struggling with reading the XML returned by the PUT. The only other call I make is if a user taps the refresh button.
I was also watching Yahoo!'s iPhone app, and it was struggling. Some of the scores in my webOS app we're not showing on the iPhone app and the iPhone app was showing timeout errors occasionally. Does it use the same API?
I'd really love it if you guys could share some of our stats with us individually.
Yep, the iPhone app uses the same API, but there were some goofy scoring issues that they're working through today. I'm not even sure why they're trying to mess with scores on their side at all, as we provide all the views they need? Whatever... :P