4 ms·
> In addition, there was a pronounced tendency for Proteus and my work practices to co-evolve — it seems doubtful that starting out with the final version of P
by JKCalhoun 5y ago
> In addition, there was a pronounced tendency for Proteus and my work practices to co-evolve — it seems doubtful that starting out with the final version of Proteus would have been useful.
I have been puzzling over this comment in his conclusion. It almost suggests the device needs to behave one way when you first get it, evolve somehow as you begin to use it a certain way. As both the user and creator of course he could add features, embellish where he found shortcomings in the ways he began to use it. The only analogy I can see for "the rest of us" is to have short-cuts for certain workflows that the eventual power-users will discover.
And (his conclusion) this was amusing:
> Common beliefs about designing products for users-that designers' intuitions aren't to be trusted, that designers are poor at predicting how a technology will be used, that iteration is an inherent part of design, that features will be used in unanticipated ways, that users are poor at articulating what they really need-carry over even to the case where the designer and the user are one.
I'm not sure if he is saying he mistrusts himself to design a thing for himself, or that others mistrust him to design a thing for himself.
It appears this work was done at Apple when they still had an "ATG" (Advanced Technology Group). For better or worse, Steve Jobs blazed in and "got rid of the egg heads" as part of his saving the company as it circled the drain. (He got rid of the campus library as well, sigh.) It seemed a bit boorish at the time, and maybe it was, but I can also see how these sorts of things were ... distractions ... while the Apple was taking on water fast and needed bailing out.
Reflecting on it a bit more, Jobs more or less replaced the Big Thinkers with Big Designers. I think Apple certainly lost some things in the fire.
- barrkel 5y agoThis is the cycle most applications go through. Apps start out simple and attract beginner users who don't have many needs and aren't intimidated by a complex interface. When users reach the limits of the app, they clamour for more features, and the application gradually gets more complex, more powerful, and because the complexity is incremental, the users grows in skill along with it. Eventually, the app is large, complex and intimidating, and ripe for disruption by a new simplified app attracting a new generation of beginners who don't understand the need for the complexity and would need to invest too much time to gain a feeling of competence. The new generation of apps are also usually better in some dimension, don't get me wrong, but there's also usually a turnover in userbase required to make a big shift forward, because the forward move is accompanied by a few steps back everywhere else.
- quesera 5y ago> It almost suggests the device needs to behave one way when you first get it, evolve somehow as you begin to use it a certain way. I think this is true for a lot of interfaces. I've never seen a successful implementation though. The common "Advanced" menu options are a clunky workaround. A successful example in fiction is Neal Stephenson's A Young Lady's Illustrated Primer, which is a fictional ~textbook from his excellent (real) book The Diamond Age.