

Twitter Distances Itself from Developers
At its Flight conference in 2015, Twitter CEO Jack Dorsey proclaimed the company was re-dedicating itself to working with developers. It launched a #HelloWorld campaign in an attempt to engage the developer community on what it felt Twitter should do with Fabric and its other tools, including the Twitter API (which has its own interesting history with developers). We're pretty sure none of the #HelloWorld responses involved selling to Google. Still, the move is a good one for the developer community. Google has a history of supporting developers and acting in their best interest with regard to its suite of tools and APIs. It also has a very good database, something Fabric doesn’t offer natively. In addition, Fabric provides out-of-the-box support for macOS and Unity, two platforms Firebase doesn’t currently support. It remains to be seen if some Fabric kits such as Nuance, which provides a method for developers to add interactive voice to apps, remain. Some other kits (like Mapbox or Stripe) directly compete with existing Google products. Twitter, on the other hand, seems as though it’s priming itself for an acquisition of its own. Time will tell how that pans out, but it’s clear that developer tools are not something most companies are interested in supporting. Jettisoning Fabric (and shutting Vine down) makes Twitter more attractive to potential suitors, and this merger with Firebase suggests Google isn’t interested in Twitter after all. With regard to Twitter, the company's overtures have panned out as a dalliance with the developer community. Whatever happens next for the company, it can never go back to being an entity that expects full-throated support from developers, not after some key missteps over the past few years. Just take a look at this representative Tweet:Hey @jack so now that Twitter ditches @fabric does that mean Twitter is back to hating developers again?
— Jonathan Wight (@schwa) January 18, 2017