I’m leaving for Los Angeles to attend Apple’s ‘Pro and Tell’ experience next week, and with a long flight ahead of me, I’m going to try something: getting work done on the iPhone Duo. This probably won’t come as a huge surprise to anyone who’s been reading MacStories for the past decade and more: once...
Apple Investigating Options for Extending Web Content Under iPhone Duo’s Safari Controls→
Jen Simmons, writing at the official WebKit blog:
Safari 27.1 does bring one change to users. Now, when someone holds iPhone Duo partially folded like a book while looking at a PDF on the web, Safari 27.1 automatically shows PDFs as two pages side by side. When they open the screen flat or close it fully, Safari switches back to one page.
I didn’t know about that, likely because I prefer saving and reading PDFs offline. The most interesting tidbit from this otherwise (very) technical blog post, however, is the fact that Apple is actively looking into ways to let web developers extend their websites’ content underneath the Safari controls shown on the right side of the iPhone Duo’s screen:
You might have noticed the outer display of iPhone Duo is wider and shorter than other iPhone displays. To give content more vertical space, iOS moves controls to the side.
In Safari 27.1, web content does not currently extend to fill the space behind these controls. Just like on other platforms, Safari looks at the web page and extends its background color to fill the space.
We would like to give web designers and developers the ability to design and use that space in more creative ways. Perhaps you want to extend your header background across the full width of the display, for example. It might seem like there’s just one obvious way to make this possible, but really there are many possibilities.
Since getting my iPhone Duo review unit yesterday, this is what has annoyed me the most. I dislike how all kinds of websites are simply cut off on the right side of Safari on the outer display. You can see this in action on MacStories itself: while we have fully updated our website to take advantage of the iPhone Duo’s new viewport sizes, there’s nothing we can do to extend the toolbar and other elements under Safari’s controls on the right side of the display. The result looks like a poor implementation on our end, but it isn’t.
I hope Apple’s Safari and WebKit teams can figure this out; once they do, we’ll update MacStories for the iPhone Duo again.
Taking a Knife to the Kickstand Case
iPhone Duo Review Roundup: Great Hinge, Messy Apps, and Everybody Misses Face ID
iPhone Duo reviews are out today, and while I was hoping that this year I’d get to review this hybrid device under embargo, it hasn’t happened (I hope it will, someday!). I’ve spent the past few hours reading, annotating, and watching as many Duo reviews as I could, and I’ve compiled the most interesting bits and common themes in the roundup below.
The broad strokes are consistent across all the reviews: the Duo’s hinge and the matte inner display are terrific; the lack of Face ID and a telephoto camera are serious trade-offs; and most third-party apps aren’t ready yet. But there’s plenty of nuance in the details, and even some disagreement (about the speakers, of all things).
Let’s dive in.
The ESA Comes for Anbernic
This week on Next Portable Console, Anbernic reveals more RG DDS details and prices leak, Nintendo commits to physical games, Ayn teases the Portal 3, and Anbernic’s history of selling handhelds loaded with bootleg games catches up to it.
Then on NPC XL for Patreon members, Federico’s gaming PC suffer’s a mishap and John gives PyroWave a try on his Apple devices.
Also available on YouTube here.
HomeView and Apple’s Home Reset
This week on AppStories, John and Federico talk about Apple’s new HomeView, the HomePod mini 2, and Apple TV 4K (4th gen).
Then for AppStories+ subscribers, Federico and John dive into the world decomped video games, with a warning for what’s to come for developers on Apple’s platforms.
Also available on YouTube here.
We deliver AppStories+ to subscribers with bonus content, ad-free, and at a high bitrate early every week.
To learn more about an AppStories+ subscription, visit our Plans page, or read the AppStories+ FAQ.
AppStories Episode 506 - HomeView and Apple’s Home Reset
43:22
This episode is sponsored by:
- Claude – Discover what’s possible. Try Claude today.
Unpacking 20,000 iPhones
Using a Clipboard Manager for Reusable Agent Prompts
In working on two iOS apps (as I mentioned last week) with a complex multi-agent architecture revolving around T3 Code, Claude, Codex, and pstack, I find myself reusing specific prompts for specific agents on a regular basis. At some point weeks ago, I realized that there had to be a better way than remembering how...
Why Aren’t AI Labs’ Apps Better?→
Ben Davis (co-host of one of my favorite new podcasts this year, Nerd Snipe) has a fascinating take on a question I’ve seen many in the Apple community ponder as well: if these frontier models are so good, why do most AI apps from the big labs still kind of suck?
Davis wrote about this in relation to the ChatGPT/Codex desktop app, which has turned into a bit of a kitchen-sink design phenomenon with all kinds of features crammed into a UI that has two left sidebars, multiple modalities, and all sorts of disjointed menus.
To me the most interesting thing here is the implied question of “if the Codex team has unlimited tokens on really powerful unreleased models, why is the product getting worse?”
The lazy answer is “it’s just vibe coded slop, real artisanal code wouldn’t be like this”. Anyone who still says this is a moron and you can ignore them.
“Vibe coding” is not the problem. Frankly, these models are better at writing code than pretty much anyone at this point. You tell the model to make something and it’ll make that thing quite well. And also to be clear, Jira was horrid before LLMs existed. Good and bad products have always existed, and I actually think you can make infinitely better products now when using the agents properly (see T3 Code and Grok Bot).
I’ve been reviewing apps for over 17 years. Without a doubt, the most basic “vibe-coded” app created with Opus 5.5 today is infinitely more stable and nicer than any first app from an amateur developer in 2009. So if we agree that these models can write good code now, why is it that so many apps are still bad?
As we argued in our interview with OpenAI’s own Andrew Ambrosino (the irony is not lost on me), it comes down to human discernment, taste, and other qualities that can’t be turned into “metrics” for a model…at least not yet.
Davis continues:
To put a more precise definition on it, I think this “taste” is the ability to make good decisions in places where there isn’t a programmatic verification function.
For example: “make this function really fast” isn’t a “taste” task it’s a hill climbing task (make changes => test changes => repeat until goal met) which the models excel at right now (I think that any problem which can be expressed in this shape can be solved now by Opus 5.5)
“Which of these color palettes do you prefer?” is a “taste” question. You can’t really put a verifier on it other than your own opinion AKA your own taste. It’s a simple little example, but everything from codebase structure to dashboard layout to how features in chatgpt fit together all fit under here. Their implementations are “correct”, the tests pass, I just hate the choices they made.
“The tests pass, I just hate the choices” sums up my experience with coding agents perfectly. We’re working on our first two apps for MacStories (more in the near future), and while I’m not writing the code, I have to spend so much time thinking about usability decisions, onboarding flows, iOS best practices, and “it just doesn’t feel right” issues that models haven’t been able to abstract yet. I have to wonder if, in a rush to maximize infinite token usage and build everything “because why not?”, perhaps the big labs may have ignored these other aspects of good software design. I strongly believe that there’s more to a great app experience than elegant code that passes tests.
Knowing how these things can change so quickly in this scene, I’m sure this post will be obsolete in a few months. Maybe even weeks. But at this moment in time, Davis’ article is spot-on and human decisions still make a dent in software coded by agents.





