mmahemoff
In closed form, it’s tiny, especially with keyboard active. Not something I’d want to be using for more than two minutes, let alone reading or watching videos on. This was my main concern, but I soon realized closed form is “pocket mode” since in my pocket is just about the only time the phone is closed. Occasionally I’ll pull it out and, keeping it closed, select some audio, set up a call, or emoji-react, then put it back. The rest of the time the phone is open, whether I’m out or at home, charging or not.
Another problem is what OP mentions, touch ID. It seemingly jumps around like whack-a-mole because of the 8 possible combinations of (open/closed state) x (orientation). There’s even more dimensions to hammer your muscle memory if you also consider which hand you’re using or whether you’re using it with one versus two hands.
I’m gradually getting used to guessing where the Touch ID is though. I do prefer it for wallet payments since the finger is already on the button. I’ve learned to double-click and verify before making any attempt to tap the phone.
The keyboard in open mode is full-width, and that’s not fun to swipe-type on. I think Apple overlooked this since they omitted the iPad setting to reduce the keyboard size. I expect that’s coming eventually.
As for apps, many third-party apps are still using un-responsive layouts like the early iPad days. Some, e.g., Kindle, are outright non-functional when the phone is open. Certain companies will rave about their AI chops yet they’ve been unable to compose a few magic prompt words to target Duo. This will improve in time.
I’ll live with all these trade-offs for the bigger screen. Reading and video were obvious applications, but using maps when mobile was a pleasant surprise. It feels like folding out an old paper map. It’s very readable in the sun too. I prefer reading on electronic display to e-ink due to the responsiveness, so it’s a big win to have an electronic display that doesn’t suffer from glare.
I think preferences will heavily depends on lifestyle. In particular, people who drive a lot won’t see the same benefits. If you spend a lot of time walking or on public transport, it’s a game changer.
Party B has already committed to uphold B-C. Entering A-B may put them at risk of violating that agreement by appearing to grant Party A rights that Party C never granted to anyone but Party B (and maybe even rights that Party B doesn't enjoy). Party B's options are don't consent to A-B (e.g., withdraw from Meta program), take down the Party C content (which would suck if they've already paid for it), or negotiate a carve-out with one or both of Parties A and C.
(IANAL)
However, UX can also be improved by some simple heuristics that could be seen as mechanistic by the standards of modern LLMs.
Performance and responsiveness, for example, contribute to UX even when the UI remains fixed. I’d wager Fable-level LLMs could improve perf on most open-source GUIs by benchmarking typical use cases and progressively applying standard tricks like caching, buffering, batching network calls.
It will probably keep most of its value too, if hardware price inflation continues.
I had written off dual screen when the square layouts were the norm, but I think Apple has struck a good balance here between screen size and price+chunkiness+serviceability. I won’t be holding my breath for an iPhone Trio. (Not to be confused with Palm Treo.)
As tech became more pervasive in the past couple of decades, it became commonplace for pundits to spout nonsense on the topic. Those takes should give anyone in tech pause about how everything else is reported.
There are certainly developers with a practice of triaging and action user-submitted reports, but unfortunately it’s opaque to the one who reported it.
Most people don’t directly use open source, and reporting bugs in closed systems is rarely rewarding.
With the issue trackers that are common in open source, a bug reporter gets to watch the bug report’s lifecycle.
They can see what the developer – and others – think about the bug report. Is it a real bug? Was it reported previously? Is it worth fixing? Does the report contain sufficient detail to reproduce it?
With enough time, the reporter will learn if the bug is fixed or discarded or ignored. At the outer loop, they can become better reporters of bugs by seeing this play out enough times.
In contrast, bug reports to a typical end-user application go into a black hole from the moment they’re submitted. Even if said bug is eventually fixed, the reporter will be none the wiser about whether their submission was even looked at, let alone triggering the fix.
If that’s the case, you could consider using pre-render JavaScript to detect what day it is in the browser. Then temporarily redirect Sunday-identifying browsers to a “Closed On Sunday” page.
It was removed early 2011. Is this what happens when they can't decide on who won?
https://hacks.mozilla.org/2026/05/behind-the-scenes-hardenin...
Another thing about early users is they are also longer-term users (assuming they are still on the platform) and have seen the platform evolve, which gives them a richer understanding of how everything fits together and what role certain features are meant to serve.
An additional benefit of isolating the account is it would help to limit damage if it gets frozen and cancelled. There's a non-zero chance your bot-controlled account gets flagged for "unusual activity".
I can appreciate there's also very high risk in giving your bot access to services like email, but I can at least see the high upside to thrillseeking Claw users. Creating a separate, dedicated, mail account would ruin many automation use cases. It matters when a contact receives an email from an account they've never seen before. In contrast, Amazon will happily accept money from a new bank account as long as it can go through the verification process. Bank accounts are basically fungible commodities, can easily be switched as long as you have a mechanism to keep working capital available.
First, extremely cumbersome and error-prone to type compared to swipe-typing on a soft keyboard. Even highlighting a few sentences can be problematic when spanning across a page boundary.
Second, navigation is also painful compared to a physical book. When reading non-fiction, it’s vital to be able to jump around quickly, backtrack, and cross-reference material. Amazon has done some good work on the UX for this, but nothing is as simple as flipping through a physical book.
Android e-readers are better insofar as open to third-party software, but still have the same hardware shortcomings.
My compromise has been to settle on medium-sized (~Kindle or iPad Mini size) tablets and treat them just as an e-reader. (Similar to the “kale phone” concept ie minimal software installed on it … no distractions.) They are much more responsive, hence fairly easy to navigate and type on.
We conclude this week has been a prosperous one for domain name registrars (even if we set aside all the new domains that Clawdbot/Moltbot/OpenClaw has registered autonomously).
The content may vary between regions though, e.g., you open Netflix in another country and no longer see a show you’re watching while see other ones appear. This can sometimes feel like a feature more than a bug.
Deflating is the moment when Arnie's autobiography audio switches from his own voice to a random American-accent narrator. (After chapter 1 or so?)
I guess time-constrained celebrities are, or soon will be, using AI to read their books in full.