4 ms·
Not bad for guesswork, as you are correct management never wanted to prioritize it, but w.r.t. devs, you are off the mark. Internally there have always been tho
by alanh 11y ago
Not bad for guesswork, as you are correct management never wanted to prioritize it, but w.r.t. devs, you are off the mark. Internally there have always been those who wanted to work for it. I have been privately told (in late October 2015) by a former Twitter employee who is, shall we say, intimately familiar with Twitter/Mac:
> Twitter has always seemed to hate the idea of a Mac app and has either tried to kill it or let it rot. At this point I think 3 generations of rogue devs inside the company have basically had to sneak around management to work on it.
> Interesting to see them publicly announce an update. Rumor is they've completely outsourced development though.
- rubyn00bie 11y agoThanks for the info! Interesting management was contemptuous of it. I wouldn't have expected that. Though with that said, I'd like to lay a bit more guesswork down now. Those devs were probably good, I'd guess too good (for these purposes), and that management wanted them focused on core products which serve their target better... Like iOS? So it is probably less about contempt for the Mac product and more about the best usage of resources. I have a feeling the rogues at Twitter who want to work on this are in a pretty high pay grade, even compared to the folks at the shop that made it. So it even still probably saved money. With all that, has Twitter made the best use of those developer resources? I have no clue.
- guelo 11y agoI wonder what would happen if one of these large internet companies with top engineering talent would fire all their product managers and designers. That's how Google worked back when they had their period of highest innovation.