However, my comment is specifically in regards to the app challenge. The Pebble team should've planned the timing of the challenge and the last iOS update better, so that voters are able to try out these apps that have been submitted to the challenge. It's not fair to the app submitters if voters like myself won't be voting for their apps as we are unable to try them out.
Interesting, I was under the impression that "pure watchapps" (C only) would be immediately available, even on iOS. Yet another thing that I didn't know about the user experience on the other side of the fence!
You're right that this could probably have been accounted for by the Pebble team. But this is their first app challenge. Hopefully things like this will inform the structure of future challenges. We can't expect it to be perfect the first time around.
I too am bothered by this. Unlike most people who already had an app done before the challenge began, I wrote my first line of code the day the challenge started and bundled, submitted, and made a video with 20 minutes to spare before the deadline. But now my iOS version can't even be downloaded!
I reached out to someone at Pebble and their response was,
"We just didn't foresee the delay in getting the iOS apps for public download. Unfortunately the deadline has been hard set for some time now and it won't be extended."
Oh well, I guess all we can do is hope that most of the reviewers are Android users, and hope that Pebble learns from this before their next challenge.