// startup autopsy
Twitter Fabric
Twitter built the best mobile crash reporting tool — then sold it to Google who folded it into Firebase.
marketfitFire Sale
Distressed acquisition below last-round valuation · Fatal mistake: Sold by Twitter to fund operations — developer platform casualty of parent company financial distress
// the model, blind
Evaluating only Twitter Fabric’s profile at its peak — without knowing the outcome — the model ranked Acquisition gone wrong as the #1 likely cause. Documented cause: No market fit.
Key Events Timeline
FOUNDING
Twitter officially launches Fabric developer platform at Twitter Flight conference, bundling Crashlytics (acquired 2013) with new tools Answers, Beta, and TwitterKit into a unified mobile SDK suite
PRODUCT LAUNCH
Twitter launches Digits as a standalone phone-number-based authentication product within Fabric, reaching over 400 million users across thousands of apps and positioning it as a direct competitor to Facebook Login
ACQUISITION ATTEMPT
Twitter sells Fabric to Google for an undisclosed sum (estimated $100–200M) as Twitter struggles financially and needs to cut costs; Google integrates Crashlytics into Firebase, signaling the end of Fabric as an independent platform
SHUTDOWN
Google officially deprecates Fabric branding and begins shutting down non-Crashlytics components including Digits, TwitterKit, and Fabric Answers, forcing thousands of developers to migrate away from Fabric APIs with a March 2019 sunset deadline
SHUTDOWN
Twitter Fabric ceases all remaining operations; Google completes full migration of Crashlytics into Firebase, permanently retiring the Fabric brand after six years and leaving only Crashlytics alive under Firebase infrastructure