
Show Notes
Daniel and Manton check in about the Apple Vision Pro. Is it on the precipice of failure? Is there a killer app for it? How would the Apple Vision Pro have done if a smaller company came out with it? They talk about playing the long game vs. the short game, and how much harder it is to play the long game as a struggling indie. Focusing on finessing little things in a product or adding new features, and working on the features of an app or service that a customer expects the app or service to do.
The post Episode 606: A Billion-Dollar Flop appeared first on Core Intuition.
More from Core Intuition
Manton and Daniel react to the latest Apple event, with thoughts on the iPhone Duo design and the Apple Watch AI features.
Manton and Daniel check in about what they’ve been up to for the past six months. They talk about Micro.blog’s new video hosting features, Daniel’s son’s college search, and Tim Cook’s rumored retirement. Finally, they ask, and answer the question: “Can you replace Steve Jobs?”
Daniel and Manton return for a special episode of Core Intuition. They talk about WWDC 2025, running the bleeding-edge betas, and how Manton finally started using a build server with Xcode Cloud, while Daniel ventures into GitHub Actions. They also can’t help talking about AI, considering the progress that has been made in only the five months since they discontinued the podcast. Finally, they close with an optimistic take on Liquid Glass and the future of the Mac.
This is the final episode of our podcast. Thank you so much to everyone who has listened and supported us over the years! We’ve loved doing the show.
Manton and Daniel catch up on the latest developments in the WordPress vs. WPEngine kerfuffle, and continuing after-effects. They talk about Matt Mullenweg's tendency lately to deliver seemingly calm and encouraging messages that are nonetheless laced with evidence of his spite towards antagonists. Finally they talk about Automattic's decision to reduce its own contribution to WordPress Core development, and the implications for the rest of the WordPress community.