Jay Miles

Product Design @Capterra - previously @FiscalNote

[Jay Miles @jayzmiles]

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 - https://t.co/tLbOinXNcy

[Maggie Appleton @Mappletons]

@swyx 17. This collection has now matured into a full grown essay documenting the history of "digital gardening" as an ethos 🌲
https://t.co/zvViVfKIe5

[Jay Miles @jayzmiles]

I think it's safe to say it's impossible to benchmark test any design prototype (paper prototype, figma, axure, stand-alone code) against a live product - at least without a big asterisk

[Jay Miles @jayzmiles]

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) - https://t.co/q9maCUPiYP

[Jay Miles @jayzmiles]

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 - https://t.co/kEaiIYIfbl

[Jay Miles @jayzmiles]

Axure's worked well for prototyping some text-based interaction, but it can get a little slow and almost always requires some code

[Jay Miles @jayzmiles]

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 - https://t.co/4WBbwdQiSs

[Jay Miles @jayzmiles]

Here’s another example of text-based prototyping using @typeform - https://t.co/cJL3to6gN1

[Jay Miles @jayzmiles]

it's fixed! all is well

[Jay Miles @jayzmiles]

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

[Jay Miles @jayzmiles]

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)

[Jay Miles @jayzmiles]

3) organizing related designs that describe functionality from different angles (particularly helpful for logic-heavy stuff). Being able to step through different states or scenarios makes it obvious what cases aren't accounted for.

[Jay Miles @jayzmiles]

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

[Jared Spool @jmspool]

All design debt is technical debt.

All technical debt is design debt.

There is no difference.

[Maxim Leyzerovich @round]

building anew without repair of the old is not an act of creation, but a pattern of destruction

[Jay Miles @jayzmiles]

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.

[Jay Miles @jayzmiles]

@round percolate?