Let me get this straight. You want to focus on developing your product, but you want your customers to focus on migrating to another provider so that you can focus on your product. This is a pretty shitty way to treat a paying customer. A two and a half month notice is basically a fuck you, I'd be surprised if you kept any of those customers.
So would I, considering they're shutting down the product...
Roughly three months warning, plus free service during that time, plus free Urban Airship Pro for six months seems pretty reasonable to me. What length of time would you have considered fair?
This isn't about users being too lazy to switch to option B, this is about SimpleGeo building an innovative service and then abandoning its paying users.
I like that phrasing, "The decision was made." Like it was an unstoppable edict from God himself. I can't speak for anyone else but I never support the future endeavours of a dev that treats me like that.
I'm your customer, and if you sell me to another organization you better make damn sure that organization has my interests at heart, or you'll never see me as a customer again. YOU dropped the ball. Passing the buck only makes you feel temporarily better, it doesn't actually make anything better.
SimpleGeo building an innovative service and then abandoning its paying users
Without working at Urban Airship or SimpleGeo (or being close to someone who does), how would one know that when Urban Airship said they were excited to acquire SimpleGeo to continue improving the service that it was BS, and that the search for a replacement should have been started?
More to the point, a more trustworthy company would comport in such a way that its paying customers don't need to know the difference. In this case, that might mean open sourcing components or giving enough notice that their customers could reasonably transition. A link to the R-Tree wikipedia page is not what I'd expect from a reliable vendor.
Anyone with half a clue could have seen this coming a mile away.
Why would you spend time and effort developing a failed product you didn't create when your highly successful product is your main focus?
Move along, nothing to see here.
Essentially they've punched a hole in the SimpleGeo life raft & are offering parachutes & life raft building instructions to the now drowning customers. Some will be hostile to these actions.
As a reader of HN, one would expect that acquired products are almost always shuttered within a year. Customers that didn't have year-ahead contracts are exposed to that high-probability risk.
This is such fantastic logo and identity design work: http://softfacade.com/simplegeo.html
Though I guess now it's a very different story to tell, compared to less then a year ago when I was hanging out with the SimpleGeo guys, it still going full speed ahead.
I don't get it...
Edit: Here is a great list of alternatives https://support.urbanairship.com/customer/portal/articles/31...
Antics like this make me distrust all web services in the future. They've got to have a really strong income stream and most definitely not a target of a talent acquisition, if I'm to rely on them.
One poster said most companies that get acquired are shut down within the year (http://news.ycombinator.com/item?id=3458414). This appears ridiculous on its face (or there needs to be a mass migration from Heroku), but what other symptoms should folks have been looking for here? I'm interested in objective measures that one might reasonably use in evaluating vendors. I'm specifically not interested in things like how many/few job postings they run on Stack Overflow, the chatter at the last San Jose Ruby Meetup, VC blog posts, etc.
SimpleGeo has rewritten its platform several times (project GISele, then project Penelope), it was done by people who thought they knew how to do geosearch, but they really had no idea, for example they never offered polygon search, they also only offered tag search a few weeks prior to being acquired, and it was done by a girl who left the company like a week after her feature went live.
This company was probably a scam from day one, it only got money because its founders were reknown.
The company was acquired because it has real, defensible technology. If you're going to talk shit, at least get your facts straight.
Edit: here is the link http://www.zillow.com/howto/api/neighborhood-boundaries.htm
Although perhaps they've gotten better, I'll give them a look.
It appears that Factual might be picking up some of the slack. I'm also looking into Google Maps API again. Oh well -- no sense worrying about it; just need to learn and move on.
1. You could mean "to dwindle, pass, or die away". To this definition, I would say that no, in fact, SimpleGeo did not die, as it's going to be thriving at Urban Airship, working towards a larger goal of building a powerful mobile infrastructure company." - Matt Galligan, SimpleGeo Co-Founder
With SpacialDB, we wanted the best of both worlds, traditional GIS and Web, RT & Mobile-Centric APIs.
The way we did this was to let users provision databases, then import any geodata (points,lines,polygons 2 or 3D) into SpacialDB and either use a raw PostgreSQL connection (from a pool) or our REST API (http://devcenter.spacialdb.com/Layers-API-v1-Documentation.h...) to query it - its super useful for building geo-apps quickly.
In fact, initially that's why we built it; we need a quick way to get going for a lot of the disaster response work we do at nomad-labs (geospatial.nomad-labs.com)
Sorry for the shameless plug, but it's mutually beneficial if time is tight.