151
デザインを考えるときに デザイナーが考えること デザイナーの頭の中秋葉ちひろ(@tommmmy)

Developers Summit 2013【14-E-4】デザインをするときにデザイナーが考えること〜デザイナーの頭の中〜

Embed Size (px)

DESCRIPTION

デブサミ2013(Developers Summit 2013)Action! 1日目のデザインセッション「デザインをするときにデザイナーが考えること〜デザイナーの頭の中〜」の発表資料(2013年2月14日) -------------------------------------------------- 途中、時間がなくて話せなかったところも入っています(そこがかなりいい話だったりする)ので、やっぱりここも実際に聞きたい!という方はまたどこかで呼んでくださいm(_ _)m よろしくお願いします。

Citation preview

  • 1. @tommmmy)

2. You need designer!? 3. You need designer!? Can you reach appropriate designer?Do you cooperate with them? 4. Baidu Japan Inc / Web Android 5. SimejiJapanese Input Method Editor SimejiSimeji 6. Android App Designs AndroidTipsDesign XML Android App Designs Android App Designs 7. 65 80 60 90 Android App Designs Android App Designs 8. 9. Dont you have such impression? 10. She looks too proud of herself. She seems to dislike stupid thing. 11. You may feel you dont go well in the term of words catchball 12. They imagine in their own world to make a wall around them when the others talk about programs. 13. It tends to... 14. So lets think about designers role.What kind of things would you like designers to do? 15. Can you explain what do you want designers to do? 16. 17. To be beautiful 18. To be beautifulThey may demand information architect to easy to see 19. To be cool 20. To be coolThey may demand to create visual images 21. I want something to be done 22. I want something to be done They may demand to put in artistic 23. My thinking when creating design. 24. 1 concept making2 architect of design3 design and implement4 effects 25. concept making Target 26. concept making Targetfix clearly, not so many target 27. 102030OL20 50 28. concept making when and how to use 29. concept making when and how to use suppose use case 30. Lets send grandchilds voice to grandparents! Lets send happy message to friends birthday! Lets record environmental sounds as alibi 31. concept making Design philosophy 32. 1 concept making2 architect of design3 design and implement4 effects 33. architect of designUsability 34. architect of design Usabilitythink based on human action 35. architect of design 36. too simpletoo much elements 37. too much action get lost to touch too simple too much elements 38. architect of designCommunication 39. architect of design Communicationinterface is a point between users and app 40. 41. 42. 43. Be simple Brenda Laurel 44. 1 concept making2 architect of design3 design and implement4 effects 45. design and implement express through graphics 46. design and implement express through graphicseasy to use / communication 47. Everything comes from observation 48. easy to use / communication Layout / Padding Grouping Photos / Illustration 49. 50. 51. 52. 53. 54. design and implementpretend to xxxxxx 55. design and implement Usability Target Lighting 56. 57. design and implement Usability Target Lighting 58. design and implementpretend to xxxxxx 59. Signiervisual sign which leads users for appropriate action () 60. - A Successful Failure 61. - A Successful Failure 62. - A Successful Failure 63. - A Successful Failure 64. - A Successful Failure 65. - A Successful Failure 66. - A Successful Failure 67. - A Successful Failure 68. - A Successful Failure 69. - A Successful Failure 70. - A Successful Failure 71. Signierwe can step on NOKONOKO, but cant on TOGEZO because he has prickles 72. Signierwe can step on NOKONOKO, but cant on TOGEZO because he has prickles 73. design and implement how to express design by code 74. design and implementI dont think about coding source when designing how to express design by codeI only think about to xxxxxx design when coding 75. how to express design by code Publish as images or express with source code 76. publishing as images can not proof against high densityexpress complicated graphicswhich are not expressed bycode should pay attention to aspect rate 77. publishing as images Dirty image can not proof against high densityexpress complicated graphicswhich are not expressed bycodeshould pay attention to aspect rateBreak aspect rate 78. express with source code OKno problem in high density decive can not express complicated graphics 79. 1 concept making2 architect of design3 design and implement4 effects 80. effects how to comfort users 81. effects how to comfort usersanimation & transition &sounds 82. effectsanimation and transition which users want to use- in the case exaggeratedly (ex. games)- how to comfort users in the case not too much (ex. tools)animation & transition &sounds 83. Smartphone with animation and sounds 84. Smartphone with animation and sounds 85. Smartphone with animation and sounds 86. Flashmake mockup by Flash... 87. 1 concept making2 architect of design3 design and implement4 effects 88. 89. 90. hopeful workflow and each roles 91. hearing why does this app need? 92. Dont put design to designers hand Hobby or background of client is important- / / Outdoor / Brands / Cars 93. Its the worst case Anyway, could you please design some petters? 94. bad case Please modify as the client says Director forwards email from the client. 95. 96. general knowledge which the team members should know for developerstodays session for designerswhat can we do with program Waterfall / Agiledevelopment methodology 97. T general knowledge which the team members should know They have general knowledge, and they have the basic knowledge And they have outstanding ability of somethingonillu eatiint hic facstraper gr 20 98. Tgeneral knowledge which the team members should know They have general knowledge, and high potential And they have outstanding ability of somethingEveryone knows what we can do with what technology on illu e ati int hicfac str ap ergr20 99. Whats the definition of Designer? 100. Whats the definition of Designer? Graphic Designer Interface Developer Logic 101. Each member has ownthe definition of Designer?Whats role Graphic Each member has basic general knowledge Designer Interface Common acknowledge (Apps philosophy and concept) DeveloperLogic 102. the condition to create fantastic product Makizushi team 103. Makizushi team 104. Makizushi team 105. Makizushi team Each member has own role Each member has basic general knowledge Common acknowledge (Apps philosophy and concept) 106. we dont need just a messenger who cant create something from hearing 107. ACTION! 108. ACTION! 109. ACTION! Designers can point out and direct because they know what is able through program Tips Engineers can point out and direct because they know the basic tips of design 110. ACTION! 111. 112. 113. Thank you so much!!!tommmmy