I would assume that its in the works, but they already slapped developers in the face yesterday with new restrictions, if they added pricing plans on top of that, that would be inhumane and too much for developers to handle in on gulp.
Additionally with the pricing, its hard to get right. They won't be able to modify prices as they see fit after they announce them. So it seems like a logical progression: 1 restrict amount of data. 2 next, determine pricing
Personally, I think I'd find pricing tiers as a relief. It might be a hard pill to swallow at first, but in the long run it aligns third party API developers and Twitter's interests. Twitter would have a reason to provide quality support to developers, and in turn developers would have a stronger sense of security in developing using the Twitter API, since they're paying for it.
Pricing is hard to get right. But they have years of data, a billion dollars, and 140 employees. I think they have the resources to give it a good first estimate.
Comments
I would assume that its in the works, but they already slapped developers in the face yesterday with new restrictions, if they added pricing plans on top of that, that would be inhumane and too much for developers to handle in on gulp.
Additionally with the pricing, its hard to get right. They won't be able to modify prices as they see fit after they announce them. So it seems like a logical progression: 1 restrict amount of data. 2 next, determine pricing
Personally, I think I'd find pricing tiers as a relief. It might be a hard pill to swallow at first, but in the long run it aligns third party API developers and Twitter's interests. Twitter would have a reason to provide quality support to developers, and in turn developers would have a stronger sense of security in developing using the Twitter API, since they're paying for it.
Pricing is hard to get right. But they have years of data, a billion dollars, and 140 employees. I think they have the resources to give it a good first estimate.