Designer as Writer
stasaki.com
Designer as Writer
1–10 of 14 posts
Re: Designer as Writer
#2Re: Designer as Writer
#3- Oversized font which means I can't skim the article
- Sliding columns for seemingly no reason other than to confuse the reader (Also makes it impossible to skim the article)
- Really unintuitive navigation system (Click on a part of the paragraph) that I didn't find until I randomly hovered my mouse over it
I didn't read the article, the design and layout actively put me off, which is kind of a shame because I think the topic is interesting.
Re: Designer as Writer
#4Re: Designer as Writer
#5Re: Designer as Writer
#6Design must be subservient to usability. It was painful for me to scroll, so much so that I gave up. It may have been acceptable on a wide desktop, but his article was so janky on my 2020 iPad that I had to stop reading.
Re: Designer as Writer
#7Design must be subservient to usability. It was painful for me to scroll, so much so that I gave up. It may have been acceptable on a wide desktop, but his article was so janky on my 2020 iPad that I had to stop reading.
I really really like this quote. Did you come up with this? Hits the nail right on the head, and is actually a key to helping developers better understand how to design effectively. Namely, to come at design from the perspective of an interface as an 'information architecture'. And how this is key to making design easy and more understandable for a engineering oriented mind.
I wrote a short article about this here: https://simpleprogrammer.com/information-architecture-develo....
Re: Designer as Writer
#8Design must be subservient to usability. It was painful for me to scroll, so much so that I gave up. It may have been acceptable on a wide desktop, but his article was so janky on my 2020 iPad that I had to stop reading.
> Design must be subservient to usability. I really really like this quote. Did you come up with this? Hits the nail right on the head, and is actually a key to helping developers better understand how to design effectively. Namely, to come at design from the perspective of an interface as an 'information architecture'. And how this is key to making design easy and more understandable for a engineering oriented mind.…
Not OP, but it seems related to 'form follows function' [0]. Incidentally, my favourite graphic design rule is 'communicate don't decorate'.
Re: Designer as Writer
#9Earlier quoted context omitted.
> Design must be subservient to usability. I really really like this quote. Did you come up with this? Hits the nail right on the head, and is actually a key to helping developers better understand how to design effectively. Namely, to come at design from the perspective of an interface as an 'information architecture'. And how this is key to making design easy and more understandable for a engineering oriented mind.…
> Design must be subservient to usability. Not OP, but it seems related to 'form follows function' [0]. Incidentally, my favourite graphic design rule is 'communicate don't decorate'. [0] https://en.wikipedia.org/wiki/Form_follows_function
Is another fantastic one.
I'm really getting into the idea that design is basically all about guidance. Mapping a goal-worthy journey for the user. Which is why we use words like 'journey' and 'story' often when describing UX issues.
Thanks for the comment and the link! Very enlightening.
Re: Designer as Writer
#10Earlier quoted context omitted.
> Design must be subservient to usability. Not OP, but it seems related to 'form follows function' [0]. Incidentally, my favourite graphic design rule is 'communicate don't decorate'. [0] https://en.wikipedia.org/wiki/Form_follows_function
> communicate don't decorate Is another fantastic one. I'm really getting into the idea that design is basically all about guidance. Mapping a goal-worthy journey for the user. Which is why we use words like 'journey' and 'story' often when describing UX issues. Thanks for the comment and the link! Very enlightening.