3 ms·
Fabric had it coming. Twitter sold it because they no longer wanted to focus on it. When Google bought it, it felt a lot like buying the market. What Fabric to
by nevi-me 8y ago
Fabric had it coming. Twitter sold it because they no longer wanted to focus on it.
When Google bought it, it felt a lot like buying the market. What Fabric tools are you going to miss, which Firebase does not have/support?
It doesn't make sense for Google to maintain two platforms that do the same thing indefinitely.
Twitter didn't have viable alternatives. They could have sold it to someone else, but who?
- Apple? Forget about Android support
- Facebook? Not interested, they killed Parse
- Google? Made sense, because the value of Fabric was the number of devs using it.
Fabric Crash Analytics was a strong product, why not bring in the team that developed it to gradually bring its features into Firebase?
Fabric is not a good example; it wasn't "abandoned" as developers were given alternatives. It also works better for us developers, because now I don't have to bundle a Fabric SDK and a Firebase SDK.
Lastly, given that Twitter is shutting down access to third-parties to their API, the value of Fabric's integration with Twitter might have dwindled for some people.