Hi John,
It’s great to hear you have some contributors supporting the launch of twitter4j-ads for version 3, and do really appreciate your involvement in this release as you have already done in the past with previous versions.
But honestly, in my modest opinion, the greatest news would be Twitter assumed the ownership of the different languages SDKs, the same way Google, Microsoft and Facebook have always done with theirs respective APIs. This way the community of developers could start working with the latest SDKs versions about the same time the new API versions are communicated and launched. This could really make the life of the developer ecosystem a lot easier:
- They could perfectly schedule the required upgrade activities.
- They could avoid the uncertainty around whether there would be continuity for the SDKs library every time a new version is launched.
- They could avoid the uncertainty around when the new SDK version will be available and if it will be available before the deadline.
- They could rely on the quality of the released SDKs, an skip unpleasant last minute problems like the namespace conflict between twitter4j-core and twitter4j-ads, that was recently solved.
It is clear to me that the “community supported” approach hasn’t been your decision, but wanted to take this opportunity to express my opinion about it. This really makes a big difference between Twitter and the rest. Advertising is key part of the game, and providing the best tools to analyze and justify the investments in advertising should also be treated as a key part of the game too.
Many thanks,
Luis
