Yes. And in most of those meetings where the researcher invalidated the leaders, the leaders have left the meeting saying (and thinking? I’m not sure) they were validated. So because of the leaders we have we should skip the meetings and research in both cases.
But apps can just rejigger into widths that fit. It would be more of an issue back when mobile sites were first becoming responsive and we pragmatically chose 2 or 3 media query widths to serve different layouts and then applied the same thinking to mobile apps. Of course the initial mobile apps, particularly on iPhone, stuck to just one and later just a few sizes themselves. As there was a wider range we did things more responsively on a continuum.
I still think the broader point of there being design reasons to hit these ratios stands and is great. I just think the idea that it needed to be precisely twice the width so apps can fit full-sized doesn't hold too much because there isn't really a "full size" notion. Or if there is, the full-size is probably the double width one. If it wasn't exactly twice the width, most apps are already built to fit into varying iPhone/mobile screen widths.
Despite all the responsive design tools and declarative layouts to ensure a great layout even on an oddball resolution... the fact is that in practice it's nontrivial, and remember that the companies that make most of the apps you use have finite design and QA budgets. They need to actually use the resolution in question in order to really do a good job of designing for it, and giving them double the work, for a $2000 and up phone which probably won't be super highly adopted, is a recipe for getting apps that end up with layouts that aren't optimized properly on one (or both) of the screen sizes.
My point is largely that the nontrivial work you've described is the norm today. What's being asked for tomorrow is not new. Most apps are already set. Not just because of work Apple does to make it easier for apps to "port" out of the box, but because the multiple sizes that apps are already prepared to handle across iPhones, iPads, and resizeable iPad apps (and to the extent that devs are having React Native handle this, then across Android too).
So it's a lot of work, yes, but it's work that's already been done and that engineering teams already assume in their processes. The future is the same because this has been the status quo for a few years. Whether the Duo has a 2:1 ratio or something slightly different, the apps are at about the same readiness for it.
I'm not calling you a liar or anything, I get that yeah, no apps really survive today that are laid out statically for each resolution.
I'm just saying that they don't release a new version of Uber, Instagram, etc. without checking to see what that flexible and responsive layout looks like on the most popular devices and, where important UI ends up suboptimal on one of them, it'll be tweaked before release. And I'm saying that nobody really wants more of these 'significant formfactors' to check.
This is already something every app needs to deal with on iPad, where users can arbitrarily resize apps and windows. And apps that support landscape layout on phones have always needed to support their UI being rendered in different aspect ratios.
At WWDC this year, Apple introduced a tool[0] to let developers arbitrarily resize their simulated iOS device screens.
Flexibility and adaptivity are more front-and-center for iOS devs than ever.
I agree it will feel super nice to go from the front screen to the dual screen and have nothing "move". And similarly it will feel "mildly infuriating" if it doesn't do that.
I also think that I (personally) don't need a front screen and would love to have whatever cost savings or improvements would come if there weren't one. This last sentence is of course a me thing, but I mention it because I think that if people start on the front screen and then open the Duo, they may just want the full screen app or something else entirely. I'm not sure the use case of being in your banking app device folded, deciding midway through flow to open it, and wanting to be in the same UI is really what I want. The part I question is what's going on that step 2 came about—I think it's either you want to go into more depth on it or you're just opening the device the way you would had you not been in your banking app.
The case where I open it to find the app using half the screen and then I have to press something or drag something to make it full screen is not that great (and isn't great today with current iPad window resizing). The best case I can think of for wanting the app in the same size format when I open it is for is something like multitasking, I guess we'll see how that looks or feels and how you get the second app open (or whether it's very common use case anyway).
In general, I've long felt the folding tech is for tablet use cases not for phone use cases. I think Apple's foray (finally) into it more or less validates that. Even though there will be a meaningful number of people buying it to replace their phone, I think this is largely because their phone use is already tablet use case-y (for entertainment especially). I assume many people will also buy it as a(n expensive) tablet replacement in addition to their phone, which is perhaps related to the timing of iPhone Handoff (same SIM on two phones) too.
You’re absolutely right, but I need to go to the bathroom/get some coffee/take a smoke break/get back to this task now so we’ll have to discuss this further later.
Very much agree, but also (not saying you're saying otherwise) stealing, lying, entitlement (which is possibly just stealing and lying), and scamming "work." These are checked in large part by a person's aversion to it not just by its lack of working. Of course dark patterns work. If what one says increasingly inches towards 100% misrepresention (but shy of it), people will "mistake" what's being said. "Mistake" doing a lot of blame shifting.
"You're never going to convince someone to stop doing something that is making them money." Reasonable, but I would soften from "never". There was less of it at one point—and it seems logical to guess we have less today than we'll have tomorrow. The main reason is likely that we simply didn't know about these tricks yet, but somewhere below that on the list of the reasons is that some people dropped off from doing it at lesser forms of misrepresentation. Or they made the case against it at work resulting in them either winning (and their projects perhaps did less well) or them losing and being overrun by those more willing. With losing possible also leading towards leaving, not getting promoted, or getting fired. This is just a way to say that there are people who do forgo money, they just might not be around or visible for various reasons. And, as implied by the difficulty of convincing people to not make money, their (former) coworkers prefer that on some level even if they don't believe they agree with stealing or lying. But losing or earning less money is not the same as having no choice.
There used to be less data to optimise from. Doing ordinary business is a low risk strategy, compared to dark patterns. Now we have data to enable us to do dark patterns without risk.
It might generalize to tech rather just engineering. The same pitch was made for marketing and SEO roles, designers, product managers to varying degrees.
I interviewed with a startup that I thought I was a pretty good fit for. I'd had the same role at a company that did the same thing they were doing just three years ahead of them. That led to fairly nuanced interviews with each interviewer because I was familiar with their projects and more generally had a sense of what their roadmap looked like. And that put me into a final presentation interview with a bigger group that included the CEO/founders pretty quickly.
Towards the end, after others had asked questions, the CEO asked how I was using AI and about the tools I was using. I mentioned using Claude Code to quickly build basic prototypes of my first few stabs to rule them in/out/iterate. I thought this was a pretty good answer in the situation—Claude Code was pretty new at the time, I really had been using it this way, and I thought it was good for a large meeting with a broad set of people where I probably can't get too detailed. I'm not sure she paid much attention, but followed up with "Do you know what Lovable is?" I hadn't. She said something along the lines of "I'm not sure exactly, but it seems to be what all the cool kids are using."
Anyways, afterward I looked it up, and I was kind of bummed because I felt I was using the more advanced method (for the situation), but the CEO didn't know it, and I likely came off as behind.
Agreed, but I think some logic follows that as increasingly more incentives are needed then maybe people just don't have these principles. People seem to want it both ways—both to get the thing they want, but to be seen as not having taken it. To be seen as principled without standing for the principle. So we hear that taking a "principled stand is great and all, but". That line is right, it just implies the person doesn't believe that much in the principle.
It's questionable though how much the programmer is operating under it. The programmer's work may need to comply, but there are a bunch of things that can reduce how much the programmer themself deals with it.
There are the executives, the lawyers, the product managers, sometimes the designers, who to varying degrees determine this before they land in the requirements the programmer sees. But there are also the libraries and APIs the company pays to handle compliance so that the company and the programmer doesn't. The programmer implements the library (and may not even had a say in or necessarily care which one was chosen).
Even if you get a crispy set of requirements from all parties you are still responsible for implementing all of then while making sense of the existing system (and from my experience significant issues arise at this stage when the full extent of requirement implications ia better understood). On top of that you might also be responsible for operating the thing, participate in compliance doc writing and do ongoing maintenace.
Yes, these things reduce (not necessarily how to zero) how much compliance the programmer is doing. They aren't figuring out how to get a car legally on the road, they're still figuring out how to get a car to do car things. The compliance questions the engineer sees are largely engineering questions. Sometimes hard engineering questions.
Absolutely there can be a bunch of hard things wrapped around easy things. When those things can't be separated neatly than it doesn't make sense to separate them such that we can call the easy parts easy (or even parts really).
That said, it's still reasonable to think that once (and only once) the hard part is done, then the easy part is easy. It would just be wrong to think that you can do the whole thing without having to do hard parts. I think the argument here is that with AI this is more possible—that the tasks are more separable. Even if it's the same one person doing the hard stuff and then passing what they learned to the AI to do the easy stuff.
Two reasons they might not separate well (there are others):
- If in a company's product development it's hard(er) to have one person doing H and another doing E, then you're generally going to have one person doing H and E. More or less, this means a person can only do E easily if they do H beforehand. So hard things are required no matter what.
- People come in whole persons. If people skilled/educated to do H tend to be the same people skilled/educated to do E (can be because of how programming is educated, but also can be because there aren't that many programmers), then you're always going to be plugging programmers who have both H and E into roles and it'll probably be more efficient to plug them into roles requiring both rather than just H or just E. You could, within that population, determine who is comparatively advantaged (and we do do this mildly with senior vs junior or with "architects"), but plugging a person into an E-only role is going to involve that person questioning what happened during the H part beforehand. In part because they're good enough at H to question it, but more importantly because they're implementing the H such that they're aware when their E might not be as easy as it could be.
Both of these seem like they might be less true now with AI (and also perhaps because there are more programmers).
I think they are saying that it's difficult to "maintain manners" for hundreds of thousands to millions of diverse "I, the individual" 's. It's great that you don't struggle with that yourself, but your manners can be made entirely irrelevant by 1 person in a public place who has anti-social behaviors (doesn't share the same set of "required" values for that society).
You're right, it can be read as it being difficult for society to maintain manners. I agree and I should have been clearer. But I also think you may be misunderstanding what I said to fit it into your own model. There is a difference between manners and what results from them. You can maintain (what you believe to be) good manners without it improving society to your liking. This is "irrelevant" in the sense of not changing things, but it is not irrelevant to maintaining your manners. Conforming to the bad manners is the more likely culprit to the bad outcomes anyway.
Caving on manners to avoid the "struggle", or rather, caving on manners because one benefits from doing so is just a reflection of how much one values the values. This is simply saying that more often than not we can maintain them, it just might not be worth it to us.
The actual question is if you could move to another country with a very different system of "manners" (read: culture) and throw out your learned behavior and adopt theirs.
My experience living in an incredibly multi-cultural immigrant dense area, is overwhelmingly "No". People like their "home" cultures (generally they believe its the best), and they tend to carry some degree of resentment for their new society for not recognizing that. It creates endless friction at the edges (whereas core values tend to be pretty similar globally).
Japan doesn't really deal with this at all, and what immigrant ingress they have is usually fueled by people trying to live a Japanese like life.
reply