Thread: FRC Spyder
View Single Post
  #8   Spotlight this post!  
Unread 24-02-2016, 11:34
Dave Flowerday Dave Flowerday is offline
Software Engineer
VRC #0111 (Wildstang)
Team Role: Engineer
 
Join Date: Feb 2002
Rookie Year: 1995
Location: North Barrington, IL
Posts: 1,366
Dave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond repute
Re: FRC Spyder

Quote:
Originally Posted by markmcgary View Post
This site may provide some insight. We find it to be pretty accurate.
Yes, I use http://appreviewtimes.com/ regularly (it's the same site, different URL). It provides trends and averages, but it doesn't provide any insight into your specific app review time. It's generally accurate (and showing very fast review times right now), but I've had more than one occasion where my review inexplicably took 2x-3x as long as what everyone else was seeing on that site. There's horror stories out there of apps taking months to be reviewed, too. Obviously whatever process Apple uses for reviews, it's not as simple as a FIFO queue.

Also, we've followed Apple's direction to move everything to HTTPS, but that of course causes an additional review step of Export Compliance for Apple to review our encryption export authorization obtained from the government. It's not clear to me if this happens in parallel while waiting for a review or if our app is only moved to the review queue after export compliance has passed (FRC Spyder has already passed Export Compliance and is Waiting for Review), so I'm not sure if that added an extra delay for us or not.

Side note in case anyone is wondering why we'd care about HTTPS in FRC Spyder when all the data is publicly available anyway: among other things, we've seen some bad cases in the past few years where crummy WiFi portals at hotels, restaurants, etc. (unfortunately common in this case since a lot of FRC participants are obviously traveling) answer requests that were intended for our API with an HTML login page. That could end up causing our event data in the app to be screwed up as the app wasn't expecting an HTML response. HTTPS protects against that as it is not possible for these intermediaries to interject anything in our API calls since its encrypted.
Reply With Quote