You hit the nail on the head. Twitter built an empire on the backs of devs using their API, then left them to rot or actively burned them directly as soon as the money got real.
As they say: fool me once, shame on you. Fool me twice, shame on me.
Exactly my thoughts. There are so many dev tools out there but I can never figure out what they actually do by reading the info on their landing pages. All I get is a bunch of buzzwords and empty promises.
Somewhere buried deep in this "experience" is a way to add twitter sign in to my iOS app. Can you just give me a link to the darn framework so I can download it and drag it into my XCode project like EVERY OTHER FRAMEWORK I EVER USE HAS? Why must I install some toolbar client and inject some script into my Xcode build process. Somehow these things are talking to each other. It got me into this state where it broke my iOS app build. And now im stuck.
Yeah, using "platform" for just a bunch of libraries that are vaguely related is quite linkbaitish. This doesn't solve any of the issues a 'platform' or framework would solve. It just gives you an easy way to link said libraries to your project.
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 met the executive driving this project earlier this year. He explained to me that Twitter only cares about one metric: growth.
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.
I find this choice of name particularly egregious. It's not just the existence of current projects [1] and common use in technology prior [2], but the source.
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.
WTF. I click the link "Get started with fabric" and start the signup process, and then it says "we'll be in touch" like this was a beta invite-only thing? Seriously false advertising. I doubt I'll look at it, even if I ever do get confirmed now.
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.
Agreed. It was pretty disappointing to sign up on a "Try it now" form and then be told I'm on a waiting list without mentioning that before. Was looking forward to trying the Crashlytics Beta offering, but I suppose I'll look elsewhere for beta distribution.
Wonder if sign in tokens are still limited. There are so many horror stories about popular hitting the user limit and being unable to grow any more. Don't really trust Twitter enough to invest the time to read to find out after they've auto-banned some of my games for being able to Tweet scores and "being too much like a Twitter client".
This is all quite confusing. I decided to try it out: so I downloaded Fabric.app (OSX), and signed up for a trial account. Somehow I was put in a pre-existing group when I signed up, with 8 other members whose email address I didn't recognize. Then, when I fired up Fabric.app, it goes into the menu bar and sits there. Does nothing. Asks me to select an XCode project (only lists my existing XCode projects) and doesn't really go further until I login. That's very unfriendly so I decided to quit until I learn more about it - oh, there's no quit option in the menu. Seems like Fabric.app has installed itself and wants to sit there .. forever .. doing .. something? I see no need for that in an developer platform, so 'kill `pidof Fabric`' it is, for me .. until I at least RTFM and find out what all the fuss is about.
Hey there! Hmm seems strange -- I'm from the Fabric team and I'd love to chat more about this. Mind dropping me a note at [email protected]? Thanks :-)
Seems like it's a collection of independent SDKs for iOS and Android. Some of the back-end services that you can use with these SDKs are new, such as "Digits".
For Android, they also have an IDE plugin for configuring the libraries, which is nice... But does not quite make this a "platform" IMO.
I thought this was going to be more like Parse or Angular/Ionic but it's not even close. I can't envision a single usage scenario even remotely similar to the high level description.
This actually really bugs me as a Crashlytics user. I'd much rather they stop trying to bundle it themselves and just list these so they can be used by the already established package management out there - Gradle/Maven and Cocoapods. Having to install an IDE plugin just to get a library feels like the dark ages.
Releasing libraries tied to IDEs sound like an absolute nightmare to have to maintain over time. Package managers exist for exactly this reason - I have no idea how anyone at Twitter could have ever thought this was a good idea.
So this is unrelated to the Fabric tools for managing devices? There is zero information on the website before asking to agree to rather long legal agreement and give you permission to spam my email. You have an opportunity to improve your on-boarding.
[+] [-] untog|11 years ago|reply
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.
[+] [-] catkin|11 years ago|reply
[+] [-] egfx|11 years ago|reply
[+] [-] unknown|11 years ago|reply
[deleted]
[+] [-] wmeredith|11 years ago|reply
As they say: fool me once, shame on you. Fool me twice, shame on me.
[+] [-] skrebbel|11 years ago|reply
In what language will I code? Can I reuse code across platforms? Is all this trouble Solved. when I use Fabric?
[+] [-] PhoenixWright|11 years ago|reply
[+] [-] enos_feedler|11 years ago|reply
[+] [-] dguaraglia|11 years ago|reply
In other words, this is just native advertising.
[+] [-] andypiper|11 years ago|reply
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)
[+] [-] ksherlock|11 years ago|reply
[+] [-] hockeybias|11 years ago|reply
[deleted]
[+] [-] adamfeldman|11 years ago|reply
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.
[+] [-] berdon|11 years ago|reply
I received an invite and installed it. The plugin is Crashlytics + Twitter and MoPub integration.
[+] [-] kolanos|11 years ago|reply
[+] [-] aarondf|11 years ago|reply
http://fabricjs.com/
[+] [-] dypsilon|11 years ago|reply
https://www.twitterflight.com/ and http://flightjs.github.io/
[+] [-] namuol|11 years ago|reply
[+] [-] kornakiewicz|11 years ago|reply
[+] [-] Newky|11 years ago|reply
[+] [-] 0x0|11 years ago|reply
[+] [-] robinhowlett|11 years ago|reply
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.
[+] [-] LiweiZ|11 years ago|reply
[+] [-] incision|11 years ago|reply
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.
1: http://www.fabfile.org/
2: http://en.wikipedia.org/wiki/Switched_fabric
[+] [-] joelrunyon|11 years ago|reply
[+] [-] pbnjay|11 years ago|reply
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.
[+] [-] tylerlh|11 years ago|reply
[+] [-] jarsin|11 years ago|reply
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..
[+] [-] venomsnake|11 years ago|reply
[+] [-] lnanek2|11 years ago|reply
[+] [-] fit2rule|11 years ago|reply
Bad Aji!
[+] [-] growthhack|11 years ago|reply
[+] [-] 0x0|11 years ago|reply
[+] [-] pavlov|11 years ago|reply
For Android, they also have an IDE plugin for configuring the libraries, which is nice... But does not quite make this a "platform" IMO.
[+] [-] nbevans|11 years ago|reply
Is it? I thought it was distributing 140 character messages in an eventually consistent manner.
[+] [-] wldlyinaccurate|11 years ago|reply
[+] [-] verst|11 years ago|reply
@CharlesMerriam2 - more info will be published after the presentations happening right now.
[+] [-] pbreit|11 years ago|reply
[+] [-] bmnick|11 years ago|reply
[+] [-] colbyh|11 years ago|reply
[+] [-] CharlesMerriam2|11 years ago|reply
[+] [-] lfx|11 years ago|reply