首先使用 SketchFlow 进行 UI - 我关心 UI 外观吗？
没有问题：UI 优先软件开发。但首先要做 UI 需要什么呢？
我开始建立一个网站，一个复杂的网站，并且知道我开始关心用户界面。我决定从 SkecthFlow 开始，而不是开始编码 html+css。现在，我很困惑。我想绘制精确的草图吗？意味着要考虑颜色、字体，确保按钮看起来像网页链接……等等，还是只是构建应用程序草图流程？意思是放置一个文本框和按钮。我需要先在 SketchFlow 中实现所有内容吗？
我正在寻找最佳实践。
There is no questions: UI-First Software Development. But what does it takes to do the UI first?
I started to build a website, a complicated one, and know I start to concern about the UI. Instead to start coding html+css, I decided to start with SkecthFlow. now, I'm very confused. Do I want to build a exact sketch? meaning to think about colors, fonts make sure that the button will look like a web link... etc, or just build the application sketch flow? meaning put a textboxes and buttons. Do I need to implement every thing in SketchFlow first?
I'm looking for best practice.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当我制作线框图时，目标是不让用户/审阅者担心颜色/字体/等。而是让他们关注 UI 工作流程/屏幕流程的细节以及他们想要使用的特定类型的控件。即使控件的放置也是次要的，除非它影响可用性。
这就是为什么 SketchFlow 附带了 UI 看起来像手绘黑白黑板画的样式集。
许多非程序员（以及一些程序员）都沉迷于颜色、字体和图形设计，这可能会在项目早期占用大量时间。当功能全部确定并正在开发时，所有这些都可以轻松完成。
When I am doing wireframes, the goal is to NOT have the user/reviewer worry about colors/fonts/etc. but rather to have them focus on the details of the UI workflow/screen flow and specific types of controls they want to use. Even placement of the controls is secondary unless it impacts usability.
That's why SketchFlow comes with the style set that has the UI look like hand-drawn black and white chalkboard drawings.
Many non-programmers (and some programmers too) get hung up on colors, fonts and graphic design, which can suck up a bunch of time early in a project. All of that can easily be done later, when the functionality is all decided upon and in development.