Product Design @Capterra - previously @FiscalNote
Washington, DC
Joined December 2014
- Tweets308
- Following435
- Followers119
- Likes1.4K
here’s a walkthrough and review of @todoist's interaction design. I’m a big fan and thought I’d pick it apart to explain why - link.medium.com/zrr6nNqTUib
Jay Miles retweeted
17. This collection has now matured into a full grown essay documenting the history of "digital gardening" as an ethos 🌲
maggieappleton.com/garden-hi…
out of school, I didn't appreciate how important fidelity is to learning what you need from prototypes. I don't know if paper prototyping still plays as significant a role in design education, but I've definitely seen them abused (and abused them) - library.gv.com/paper-prototy…
the GV post makes a strong case for why you wouldn't want to use paper prototyping in the formative evaluation of a prototype - even worse though, is trying to use paper prototypes in summative evaluations - nngroup.com/articles/formati…
Doing a little research into prototyping more realistic/representative text-based interfaces and came across this post from @mattrothenberg - it's great. Curious what other resources might be out there - hackernoon.com/adventures-in…
Here’s another example of text-based prototyping using @typeform - uxdesign.cc/20-minute-typefo…
figma's new support for multiple flows per page is pretty nice. I think I'll still be creating navigation pages for prototypes, but it's going to make working with other designers on a single prototype much more manageable
ALT An image of 5 frames on Figma's design canvas with arrows showing the prototype connections between them. The first frame at the top-left of the image, which reads "all flows", links to each of the two flows within the prototype. Below the first frame, there are two rows each with two frames. Each row is a distinct flow within the prototype.
if you don't connect flows though, the sidebar reflects what's going on in the viewport. you do lose out on links between flows. (2/2)
2) organizing "scenes" in a scenario for a prototype I'm evaluating with someone else - it's nice to be able to jump to a specific section to ask follow-up questions
Jay Miles retweeted
All design debt is technical debt.
All technical debt is design debt.
There is no difference.
Jay Miles retweeted
building anew without repair of the old is not an act of creation, but a pattern of destruction
Thank you for sharing, @pwthornton. To add, I think overviews of prototyping typically focus on evaluating prototypes with users. That's a great benefit of prototyping, but not the only one.
This Post is from an account that no longer exists. Learn more
