Fabric – Mobile developer platform by Twitter
dev.twitter.com
dev.twitter.com
http://www.wired.com/2014/10/twitter-fabric-sdk/
It's... fine. But given Twitter's history of dev antagonism I am not about to create apps that rely on them as a backend. Sorry.
As they say: fool me once, shame on you. Fool me twice, shame on me.
In what language will I code? Can I reuse code across platforms? Is all this trouble Solved. when I use Fabric?
In other words, this is just native advertising.
The framework's available here as a cocoapod: http://cocoapods.org/?q=crashlytics
There is a lot more information on the developer site http://dev.twitter.com/fabric and there are also now replays of the sessions from Flight available https://twittercommunity.com/t/missed-flight-we-got-you-cove... (YouTube playlist, blog posts and livestream replay linked from there)
Fabric seems to be a brand under which Twitter offers modular 'kits', or SDKs for two of its major acquisitions (Crashlytics, MoPub) and the Sign-in with Twitter product. It's unclear if this is a new wrapper around existing SDKs/APIs, or a new, simplified SDK/API for these products.
I received an invite and installed it. The plugin is Crashlytics + Twitter and MoPub integration.
https://www.twitterflight.com/ and http://flightjs.github.io/
In particular they are hyper-focused on signing up new Twitter users and then "on-boarding" them so that they can follow other users, posts tweets etc. within the first session. That means that products using the Twitter platform need to be focused on that too.
Twitter wanted to position themselves around three core features:
* the feed itself * the platform (recent third-party hooks/features such as voting (World Cup) and payments (Stripe et al) are part of this) * developer tools
It was explained to me that the latter was needed because too often Twitter felt that social/twitter features were "bolted on" too often at the end of projects, meaning that the integration was naturally segregated from the other features.
Twitter felt that for developers to create products that were inherently social, they would need to provide the tools to build those products themselves, and that social integration would be encouraged early in the product development cycle.
Fabric appears to be the first output of this strategy.
Twitter, being Twitter could call this whatever they wanted.
"Yolk" or whatever would make just as many front pages.
I don't see how "Fabric" can do anything but serve someone inside Twitter who likes the name while being inconvenient / irrelevant to everyone else.
I'm sure little old me doesn't matter to them in the grand scheme of things, but I absolutely hate crap like this. Tricking me into registering by pretending to have a product I can try immediately is just plain stupid. I lose all respect for projects that do this as a first impression.
Looks just like a collection of backend services that you can include in your apps today without this framework if you really wanted them.
Hopefully more info will be released because I am not seeing anything here..
Bad Aji!
For Android, they also have an IDE plugin for configuring the libraries, which is nice... But does not quite make this a "platform" IMO.
Is it? I thought it was distributing 140 character messages in an eventually consistent manner.
@CharlesMerriam2 - more info will be published after the presentations happening right now.
Parse gets it, has an awesome cocoapod.
Also does anyone know if you use their Digits login solution if you get the phone number or do they store it? Couldn't tell from the docs.