|
|
|
|
|
|
by nickcharlton
5630 days ago
|
|
|
It seems to me to be a very bad business decision to decide to write a framework first, before delivering on your core product. As the deadlines have ended up slipping, they have ended up with a set of very defensive posts about why they haven't yet delivered. I don't see why you would jeopardize (that might be a bit of a strong word, but I'm sure they haven't done amazingly in sales in the last few months compared to what they had been) your business by attempting something far more complex when your product was already behind others in the marketplace. There's no reason why they couldn't have gotten cloud syncing working just for them, then rolling out the code into a framework later on. That seems to be the smarter way to go about doing it - not writing a series of defensive posts saying that it's so hard. |
|
|
But they have delivered on their core product (Things.app)...and an expansion of it (Things for iPhone, etc.).
Don't get me wrong...they could be overengineering it (I don't know their user base that well), but it seems that they might be taking the Blizzard approach to things (we're not giving a release date...it'll be done when it's done).
edit: Learning HN's syntax...sorry