Freud asked, “What does a user really want?” Ten-plus years into web development, we still don’t know. One of the biggest problems in creating and delivering a site is how to decide, specify, and communicate exactly what we’re building and why. Use cases can help answer these questions by providing a simple, fast means to decide and describe the purpose of your project. In this quick-reading article, Messieurs Carr and Meehan introduce use cases and their, uh, uses.
More from A List Apart
We keep using that word, "responsive," but do we all mean the same thing by it? The debate continues, as it should, while the word in its web context works its way into our language. But by the time its meaning coalesces, will we even need it anymore?
From the Blog
As a developer, a large amount of my time is spent reading documentation. An even larger amount of time is spent finding said documentation. Or it was, until Dash entered my life.
Public speaking is tough. You’re trying not to say “um” too much or speak too fast or crash your presentation or poop your pants or do any of the million horrible things that, in those first few minutes you’re up on stage, feel way too possible. Now there's a guide that makes it a little easier.