11–20 of 35 posts
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?
1. Customers don't rely on the service.
2. There are no customers.
Otherwise, why not leave the servers on for another month?
EDIT: 3. The service isn't automated enough to be run without human intervention, even for a month. Which would also likely create failure when it scales.
I'm curious about the shuttering timelines that failed startups use. Three weeks is awfully fast to go from operational to shutdown for a service that customers rely on. I see two options, either could be reasons that a startup would fail: 1. Customers don't rely on the service. 2. There are no customers. Otherwise, why not leave the servers on for another month? EDIT: 3. The service isn't automated enough to be run…
Damn, this was actually a really helpful and easy to use service...
Our builds were failing because even though we could check out our Git submodules fine, they could not. They couldn't resolve it and told us to stop using submodules instead.
Then our builds were failing because they weren't respecting our scheme's settings. First they didn't even understand the problem and told us to restructure our project, then when they did understand it, they didn't treat it as a bug report, but a feature request.
To be honest, it felt like we were just an inconvenience to them. We stopped using their service because they seemed more interested in us doing work to solve their problems than them doing work to solve our problems.
Ship.io apparently never raised money according to CrunchBase, which means this shouldn't be that unusual.
They should be able to get some funds by selling their domain though. I imagine someone would want to pay a good chunk of change for that.