The expectations for the product are definitely on target and expected. Planning & design run about 4 months ahead of production release right now and a lot of the roadmap was laid out very early on, so we’re on track with where we expected. One problem (that’s been observed) is that we often are reasonably close to a finished feature/application/product and mention it when it’s suggested publicly even though it may still be a month or two away in order to solve all the tiny glitches, implementation issues, and ensure it meets FlightAware’s standards for interface simplicity.
When I read your original post, I wasn’t sure what to reply because I couldn’t see a distinction between “keep building on the system to accomodate all requests or just run it straight n level for a while concentrating on the much sought after features” although in retrospect perhaps you were referring to infrastructure vs implementation. Either way, it’s definitely a lot of both and everyone can expect to see substantial development and new features regularly.
One thing that I don’t think anyone expected was the phenomenal rate of growth. It definitely led to a major focus on scaling/expansion vs development for a while although realistically, the two go hand in hand on some level. We have the growth rate well under control, expansion is pretty turn-key, and our hardware/datacenter expansions are generally a few weeks ahead of demand, so that’s a good place to be.