Earlier quoted context omitted.
It's still inferior to Google Maps tho. It's not outright bad, but for directions/traffic Google Maps is still miles ahead (at least in random European countries).
Shouldn't it be kilometers ahead in random European countries?
What Apple’s quiet failure can teach you about your business
51–57 of 57 posts
Re: What Apple’s quiet failure can teach you about your business
#52This is what happens when you're a design company masquerading as a tech company. Do they design beautiful products? Abso-freaking-lutely! Can they develop complex software/systems? The evidence strongly suggests a resounding, no! They struggle enormously at providing solid cloud services, their websites suck (particularly their developer portals), they can't write a functional USB stack, macOS has more bugs than eve…
Are you seriously suggesting that their teams of cpu engineers, battery engineers, material engineers, wireless engineers and electric engineers, among many, many others, don't have the chops required to design, build and manage the complexity of maybe one of the most valuable products in the world right now? all because you think their software engineers are not as good as you?
How do you think they got to be one of the most valuable and profitable companies of all time? by luck?
Re: What Apple’s quiet failure can teach you about your business
#53Earlier quoted context omitted.
It's still inferior to Google Maps tho. It's not outright bad, but for directions/traffic Google Maps is still miles ahead (at least in random European countries).
Shouldn't it be kilometers ahead in random European countries?
s/random European countries/everywhere except GB/
Re: What Apple’s quiet failure can teach you about your business
#54Earlier quoted context omitted.
"throw shit at the wall and see what sticks" - Is this really a bad thing? You have to try things in the real world to get anywhere. Are there any companies that can see into the future to see what works?
> "throw shit at the wall and see what sticks" - Is this really a bad thing? If you're one of the people who pay real money for a product that doesn't stick, yes.
But that can always happen to any product.
Re: What Apple’s quiet failure can teach you about your business
#55> I would rather commit seppuku than fail -- Elon Musk on failure
Project Titan is not a failure but it has suffered major setbacks, the credit or blame for which lies with Tim Cook. It takes unrelenting passion and fanaticism to wield the fortunes in your favour. Jobs had this and Musk has it too.
If project Titan is not about building a car then it's just about components. Apple has historically owned the vertical and there is little exciting about being a component supplier. It's a losing bid. Google does mapping better than Apple. It does voice recognition and AI better than Apple. The car manufacturers desire a steely grip on their UX and design so Apple's strengths there won't come into play either. Ive's own ambitions seem to indicate the poor state of cars:
> “There are some shocking cars on the road,” Ive said. “One person’s car is another person’s scenery.” To his right was a silver sedan with a jutting lower lip. Ive said, quietly, “For example.” As the disgraced car fell behind, I asked Ive to critique its design: “It is baffling, isn’t it? It’s just nothing, isn’t it? It’s just insipid.” He declined to name the model, muttering, “I don’t know, I don’t want to offend.” (Toyota Echo.) [1]
I for one would have loved to see an Apple Car and disruption of the auto industry. Am hoping Apple hasn't conceded on the bigger vision but it does seem bleak at the moment.
[1]: http://www.newyorker.com/magazine/2015/02/23/shape-things-comeRe: What Apple’s quiet failure can teach you about your business
#56Earlier quoted context omitted.
> "throw shit at the wall and see what sticks" - Is this really a bad thing? If you're one of the people who pay real money for a product that doesn't stick, yes.
But that can always happen to any product.
Absolutely. So when I'm looking at a product, one of the things I ask myself is, "does this company have a history of releasing immature products, or dropping support for their products quickly?" Obviously it can't be foolproof, but if either of those is a company's general MO, then it's more likely to happen to a new product of theirs, than a company which rarely does that.
Re: What Apple’s quiet failure can teach you about your business
#57I don't call this events failures, I call them tries . And many, many tries are required to learn and create a single success. But maybe that is why I'm no analyst .
I can't help but see this as a post hoc rationalization. When Steve Jobs was at its helm, did Apple have failures that it needed to rebrand as "tries"?
[deleted]