editor’s note: a story about Feedly UI design practical article, actually is the Feedly team to the headquarters of Google exchange learning experience, according to the Material design of Design standard interface, but not the final version. After returning to Google headquarters, after this communication, the Feedly team finally made a prototype and completed the entire APP revision, and this article came along.
a few weeks ago, we went to a Material Design workshop at Google headquarters, where we explore a Feedly if the design specifications follow the Material Design what it is, and then write an article "MATERIAL DESIGN FEEDLY, founder of the battle!" talk about Revision of actual combat experience to do a simple, experience sharing.
in February 10th, I and my team members, Edwin and Sean, went back to the Google headquarters again and explored the design techniques more thoroughly with the Material Design team. Frankly, Google’s artistic director, Rachel Been, is truly our mentor, and she tells us a few of the core design principles of Material Design.
through the garage in Google for 2 years of communication, we really completed the Feedly for a mobile, interactive design prototype. After a few weeks of polishing and refining, we finally finished our first Material Design product. Now you can download the latest version of Feedly on Google Play. (domestic friends can download
apps from Google Play in APP software stores such as cool markets)
emotional experience design
In these two days of
, we focus on rethinking the visual design of user discovery experience Google. When the user just uses Feedly, you’ll see the introduction of APP and start building your own news and information sources by step-by-step guidance, which is what we call the user discovery experience.
in the face of this link, Rachel’s main design direction is to make this process experience more emotional, immersive, so she put forward the following advocacy:
visual design is superior to text: how do you use images instead of simple text labels to render each element better?
planning is better than algorithms: can we provide search results based on human planning and ideas, instead of using a single algorithm to recommend the best results?
select rather than flat list: let search results >