This is a genuinely interesting topic, and as we say in the blog post:
> Together, we’re building a comprehensive package registry to serve the Swift community’s evolving needs.
The great thing about a registry is that it doesn't care where the original source is hosted. We will be moving away from that model completely as we work towards this.
> It would be nice to see a final graph of review times across the entire span the data was tracked. Luckily there's Archive.org to fulfill that curiosity in some way. Here's 2018:
Yes, I considered doing that but didn't have time and just needed to get it shut down in the end. The original shutdown plans included this but then having to actually get all of that organised was delaying it from actually getting shut down :)
Yes, it may even be too overwhelming :) If so, those feeds are what I use as my main sources for writing iOS Dev Weekly, here: https://iosdevweekly.com/ which will give you a slightly cut down list of the best of the week in iOS development.
I am (possibly optimistically) hoping that people will be accurate with the data :)
It needs a decent amount of usage to be anything like accurate anyway and so I hope that the occasional bad data point will be hidden by the averages. I will be watching to see how accurate the data "feels" by watching the kind of tweets people are putting through it.
Main reason... I wanted to keep it really simple in terms of implementation and also so people might see the hashtag being used and go investigate what it was :) It was knocked up in a few hours total.
However, I also think it would be easier just add the hash tag to a tweet that you may even already be typing rather than have to go to a separate web page and enter a form. I would certainly prefer to do it this way.
I had forgotten about that, just checked and they do show a percentage of iOS (no Mac) apps which are reviewed within 7 days (currently 75%) but it is kinda tucked away in the middle of a page and not really obvious. It will be interesting to see if the user generated average settles on ~7 days, my feeling is that it probably will be around that mark.
Also, if I get a decent amount of data coming through the system there is the possibility of gathering more data or creating some interesting visualisations of it. We will see.