A developer with a small software company, I’ve had an idea for a Twitter feature that seems to have withstood the test of time - after a few years I still see the problem to be solved but I don’t see other solutions. I don’t mind paying Twitter for services, posting ads provided by Twitter, or anything else to help Twitter monetize or promote the brand in the best light possible. I’m just afraid of getting shutdown as soon as the app gets popular.
In short, I want to create a new client similar to TweetDeck but much more focused, allow user-defined filtering and aggregation of user-relevant content. The functionality will be accessible via a website, desktop, and popular mobile platforms. Transactions will get posted from the app to my servers and processed into Twitter API queries, with responses then filtered and passed back up to the client app. (If twitter prefers we can also tweet directly from client app to Twitter, with only metadata going back and forth from our servers. Per API guidelines, responses will be cached and API search calls will be minimized, though of course with people tweeting from the apps there will still be whatever number of transactions are require to support the user base.
The app is not intended to mask or re-brand Twitter but to profile it highly as the supporting platform. The whole idea is to allow people to make better use of Twitter in a responsible way that I’m sure Twitter would appreciate. I want to proudly build upon the platform, not in any way subvert it.
But there’s always that threat of getting shutdown for having too many transactions or if Twitter decides they want to do their own app that duplicates the functionality. From what I’ve read over the years, it’s not good to have a Twitter app that’s too popular - and Twitter isn’t fond of alternative client apps.
So what can I do to get prior confirmation that the model is sound - and that assuming we implement with full respect for policies, etc, that we won’t get shutdown? Who can we work with there to walk through the functionality and get approval before moving forward - and without the concept getting turned into the next big feature from the company?
Or is it “you just need to take your chances”? That’s what I’m feeling now and it’s neither developer-friendly nor good for business for anyone.