没有原型图如何开始界面设计_从原型开始

没有原型图如何开始界面设计

When you're creating an application, such as a client's database, or complex workbook, do you start with a prototype, or do you dive right in?

在创建应用程序(例如客户的数据库或复杂的工作簿)时，您是从原型开始还是直接涉足？

At the Unstructured Ventures blog there's an article entitled How To Fail, which lists 25 business guidelines, and alternative idea for each guideline. Number 7 discusses prototypes, mockups and samples.

在Unstructured Ventures博客上，有一篇名为“ 如何失败”的文章，其中列出了25个业务准则以及每个准则的替代思路。 数字7讨论了原型，模型和样本。

"7. Build prototypes, mockups and samples. Instead: Start building in a format and medium as close to the finished product as possible, and iterate, iterate, iterate."

“ 7.构建原型，模型和样本。取而代之：开始以尽可能接近最终产品的格式和媒介进行构建，然后进行迭代，迭代和迭代。”

I've read numerous books and articles that list the merits of prototypes and mockups, but I've never created one. I always start working in the actual application, where I can test as I go. I've got notes from my client meetings, or their list of specifications, and maybe a rough sketch of where I'm headed, but that's it.

我读过许多书籍和文章，列出了原型和模型的优点，但我从未创建过。 我总是开始在实际的应用程序中工作，可以随时进行测试。 我从客户会议上得到了一些笔记，或者是他们的规格清单，也许还有我前进的方向的粗略草图，但是仅此而已。

This approach works well for me, especially in a database, where I can build a little, then test it with sample data, before building the next piece.

这种方法对我来说效果很好，尤其是在数据库中，在构建下一部分之前，我可以先构建一点，然后使用示例数据对其进行测试。

你的方法是什么？ (What's Your Approach?)

Do you create prototypes? Always? Sometimes? Never? What benefits do you get from your approach?

您是否创建原型？ 总是？ 有时？ 决不？ 您的方法有什么好处？

翻译自: https://contexturesblog.com/archives/2008/10/17/start-with-a-prototype/

没有原型图如何开始界面设计