The future of design is really not a space where you say I’m going to design a screen for X. It’s a space where you say, I need to design something that needs itself to be able to work across a massive, countless number of experiences
device independent. To be platform independent. To be destination independent
What we’re finding is that as people move across experiences. The content is maintained, but the context is what is subtly shifting. You want to make sure that design is in a position that it can maintain the content as it subtly shifts the context across those pieces. The design tools need to do that as well.
, “Hey, these guys are coming after us, we have to do something quickly in order to respond to it?” Or, do you see it as, potentially, validation that you’re doing something right, that you’re in the right space, or that is the right space to be in? Do you look at it as a chance to keep yourself honest about what you are working on and what is important to you, and what you’re getting right and what you’re not
I come from this world of Flash. The parallel is interesting simply from the fact that Flash let you do design work and then prototype and then build it. It always amazed me when designers would present their work as a bunch of static comps, or even wireframes.
Hey I want these kinds of features.” They’re going to start to validate whether that makes sense or not. I think, and they’re much better at figuring out, as that tool evolves, how deep they want to go into that. It may very well be the case that they decide doing these fairly simple, testable prototypes is as deep as they want to go, versus saying that they’re actually generating code to hand over to engineers on the other side. Time will tell.
