[Disclaimer: I'm founder of a competitor ( https://circleci.com , which offers CI/CD for iOS and Android as well as web apps, open source, etc).] I don't know why it shut down, but my guess: customers didn't want to use one CI system for their iOS builds and another for their server-side builds. This was one factor in CircleCI acquiring distiller.io (which was a ship.io competitor) last year. The history here is very…
Ship.io says goodbye
31–35 of 35 posts
Re: Ship.io says goodbye
#32Back when we started only a handful of CI services were available for iOS developers. One of them was CISimple which was later aquired and rebranded as ship.io . Our motivation to start our own service was that none of the available hosted services at the time were flexible enough to handle the projects we were working on.
Ship.io did improve a lot, allowing custom scripts to be executed, but, at least for us, they always seemed to be too locked down, too much of a black box.
This is exactly why we recently introduced our [open source CLI](https://github.com/bitrise-io/bitrise), so that you can run your CI and other automation configurations on your own machine if you want to, and of course in the (highly unlikely ;) case we would decide to close the shop you can still export your configuration and run it anywhere you want to.
I remember, just a few months ago, we felt that ship.io had a spy in our team, as they introduced new features almost at the same time we did (Slack support, Deliver support, ...).
It's surprising they closed so quick, they had quite an active marketing team and released new features frequently. I guess this decision was not up to the people who actually worked on the product, most likely they failed to meet the (monetary) expectations of their parent company.
Fairwell old friend, we'll always remember you!
Re: Ship.io says goodbye
#33[Disclaimer: I'm founder of a competitor ( https://circleci.com , which offers CI/CD for iOS and Android as well as web apps, open source, etc).] I don't know why it shut down, but my guess: customers didn't want to use one CI system for their iOS builds and another for their server-side builds. This was one factor in CircleCI acquiring distiller.io (which was a ship.io competitor) last year. The history here is very…
I see the reasoning behind pbiggar's post but I have to say that from our experience (and our target market) there's not that much demand for a unified CI service that can build both server side and mobile apps. We've had this issue come up a couple of times but most of our customers are mobile app dev teams that have separate tooling from their backend teams and using different CI services for different teams isn't generally a deal-breaker.
What killed ship.io? I don't want to speculate and I hope that we'll see a post mortem from them in the near future.
Re: Ship.io says goodbye
#34So apparently they only launched less than 6 months ago: https://ship.io/ship-io-launches-out-of-public-beta/ I'm not in touch with the startup world but does that seem a short time to see if it sticks? Did they just have too short a runway?