3 ms·
>Not sure about "unwarranted". Debatable yes, but they made the decision that the previous product was not evolvable and rewrote the whole bloody thing from scr
by Karunamon 15y ago
>Not sure about "unwarranted". Debatable yes, but they made the decision that the previous product was not evolvable and rewrote the whole bloody thing from scratch. It took them a good two years (assuming they started right as FCP7 got out the door), there was no way it was going to happen with full feature parity short of taking twice as long.
Then that's what needed to happen - it was half baked, put it back in the oven for a while. But releasing a flagship product (Final Cut is THE video editing app of choice on Mac) in the state that FCPX was done in was complete lunacy.
>Not like they don't have a history of it, they did the same when they rewrote iMovie.
But that's iMovie, consumer grade software. The worst you'll do by changing it around is tick a few people off who will hopefully get over it.
If I were a videographer and found out that I could no longer open or save in a format that is industry standard and that I rely upon, my very first reaction would be to wonder what the developers were smoking, followed by wondering the same about Apple, followed by leaving a bad review on the store page (They shut down reviews on FCPX it was getting so bad.. and keep in mind, you can't review things on the app store that you haven't installed at least once), followed by petitioning for my money back.
- masklinn 15y ago> Then that's what needed to happen - it was half baked, put it back in the oven for a while. But releasing a flagship product (Final Cut is THE video editing app of choice on Mac) in the state that FCPX was done in was complete lunacy. That's one point of view, with which I don't agree. By releasing it when they did and building upon this, Apple could/could have built a better product with a live feedback loop in the field. The core engine was there for using or complaining about, and for people for whom it was insufficient, FCP7 still worked just as it would have worked had they waited longer to release FCPX. What Apple failed here was managing expectation and their release, the basic strategy is not only sound but a way to get a better product in the end.
- glhaynes 15y agoI agree with your evaluation, though I'd also add that there was quite a bit of concern about no longer being able to get licenses for FCP 7 that took quite a while to get cleared up (IIRC, it wasn't possible at all to get them, at least from Apple, for a few weeks). I think that's what really took it from a "calm down, stick with what already works until the new infant version is suitable for you" story to a "this could really mess up some businesses" story.
- masklinn 15y ago> I agree with your evaluation, though I'd also add that there was quite a bit of concern about no longer being able to get licenses for FCP 7 that took quite a while to get cleared up (IIRC, it wasn't possible at all to get them, at least from Apple, for a few weeks). True as well. I'd put that in the "botching the release" part