• Jitachi Garcia, 8 years ago (edited 8 years ago )

    I like Tuhin's definition:

    Products—not just apps or websites

    What the hell do I even mean by that? Mostly that our work is no longer confined to interfaces inside a viewport in the browser or on our phones. The apps & the websites are just the means of interaction we enable. We are here to design the larger system of which the apps and websites are one aspect. It is equally our job (or should be, if it is not) to understand how they fit into the larger sphere of things. What is the product market fit? What do the release cycles of the app look like in terms of features? Does it make sense to launch feature A without sub feature 1, 2 and 3 which are part of the next release cycle? How similar do the app and the website need to be? Do they need to be optimized for particular use cases versus being at feature parity? What about our iPad app? How does the account creation flow work if a user connects via Facebook on iPhone but closes the app before they complete their profile? How do we handle this edge case if they open the app on a desktop device next? How does their data sync across platform and what are the design affordances for it? In a world of A/B tests and instrumentation of design, how do you tell the stories that need telling.

    (src: http://tuhin.co/what-kind-of-a-designer-are-you.html )

    0 points