Originally Posted by
guisar
I didn't mean to spawn a discussion of SF vice Kansas just to note that losing more or less the whole development team basically right after the product finally became usable cannot be a good thing. I'm kind of shocked actually unless the development team was a PITA to deal with as the cost savings can't really be significant.
I agree. I'm not sure how this turned into an argument over the morality of what Garmin did to its team or which city is a better place to live. Purely from a customer perspective a major shakeup like this can't be good. Then again, given how long it took Garmin to get Connect working properly in the first place, it suggests that their commitment to it was never all that strong. If it were, I'd feel more confident that they could pull off this transition without a major disruption.