blocks|key|1476270|text|笔和纸或白板。更喜欢与最终产品的外观和感觉合理分离的样机。在讨论交互和完成一项工作需要多少点击时，更换纸质模型的速度非常快，所有人都很明显，这并不代表最终产品几乎完成了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476271|几年前，我参与了一个项目，我们制作了一个非常详细的GUI模型，甚至在它后面有一些代码来模拟事件流。对于让软件的用户提供反馈和输入来说，这是非常棒的。对于这个项目来说，这绝对是一场噩梦，因为我们总是落后于用户的期望，毕竟他们已经看到了它很好的工作，对吧？|1476272|最糟糕的是，一些被丢弃的代码最终被包含在发布的产品中，并成为后来维护的噩梦(最初没有投入太多精力来构建它，因为它是被丢弃的，然后用户已经看到了这种行为，它变成了系统主要部分的逻辑的事实实现)。|1476273|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Pen and paper or a whiteboard. Prefer mockups to be reasonably divorced from the final products look and feel. While discussing interactions and how many clicks it takes to get a job done it's very fast to change paper mock ups and its obvious to all concerned that this doesn't represent the final product being almost finished. 
Years ago I was involved in a project where we produced a really detailed GUI mock up that even had some code behind it to simulate the flow of events. It was fantastic for getting the users of the software to give feedback and input. It was then an absolute nightmare for the project because we were constantly behind where the users expected us to be, after all they had already seen it pretty much working, right? 
Worst of all, some of that throwaway code ended up being included in the released product and was a nightmare to maintain later (there wasn't much thought put into structuring it originally 'cos it was throwaway, then the user had seen the behavior and it became the de-facto implementation of the logic for a major piece of the system). Yuk.

blocks|key|1227116|text|我使用Balsamiq+http://www.balsamiq.com/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1227117|太棒了。|1227118|entityMap|0|LINK|mutability|MUTABLE|url|http://www.balsamiq.com/^0|C|O|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I use Balsamiq
<a href="http://www.balsamiq.com/" rel="noreferrer">http://www.balsamiq.com/</a>

It's awesome.

blocks|key|4444249|text|我用Visual+Studio创建html页面。这很可能是Dreamweaver，FrontPage，NotePad%2B%2B。对我来说，这有CSS和html的好处，几乎完成的时候，我完成了样机。通常，使用您计划用来创建可交付内容的工具或技术来制作原型会更容易、更有效率。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4444250|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I create html pages with Visual Studio. This could easily be Dreamweaver, FrontPage, NotePad++. To me this has the benefit of the CSS and html being nearly done by time I am finished with the mockup. Usually it is easier and more productive to do your prototype in the tool or technology you plan to create the deliverable in.

blocks|key|1227149|text|您可以使用图形用户界面编辑器，例如NetBeans集成开发环境、QtCreator集成开发环境或Xcode集成开发环境中的编辑器来创建图形用户界面模型，而无需为所有的图形用户界面事件实现处理程序。然后，可以对此GUI进行评估，并可能重新设计。一旦GUI看起来像它应该的样子，那么就可以正确地处理事件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1227150|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can use a GUI editor such as the one in the NetBeans IDE, the QtCreator IDE, or the Xcode IDE, to create a GUI mockup, without implementing handlers for all the GUI events. This GUI can then be evaluated, and possibly redesigned. Once the GUI looks as it should, then events can be properly handled.

blocks|key|1476362|text|我使用了多种工具组合来实现UI。如果静态的外观和感觉是我正在测试的，那么我会使用纸和白板草图的组合。一旦你开始做更详细的设计，这些东西很快就会被丢弃。就像"Hamish+Smith“说的，你需要在你的模型和最终产品之间有一定程度的分离。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476363|当我想测试我的设计的交互性时，我以前使用过纸质模型，但我更喜欢使用PowerPoint，它为用户提供了一种更好的与应用程序交互的方式，而不是不断地让我向他们展示一个按钮将把他们带到哪个页面以及某些功能是如何工作的纸质草图。我只是对它进行了设置，所以单击PowerPoint幻灯片上的按钮或链接就可以转到与该按钮在实际应用程序中的位置相对应的幻灯片。|1476364|目前，我一直在使用微软的SketchFlow，它是Expression+Blend的一部分，它给人留下了深刻的印象。不过我并没有经常使用它，所以我还没有意识到它可能带来的任何限制。此外，我尝试过Balsamiq，它看起来也是一个很好的应用程序，但我仍然没有充分使用它来发现它的局限性。我想说清楚，虽然我只是将它们用于交互性测试，以取代PowerPoint，但我仍然认为静态模型最好使用纸张和白板完成。|1476365|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I have used a combination of tools to do UIs. If the static look and feel is what I am testing then I use a combination of paper and whiteboard sketches. These are quick to do and are easily thrown away once you start working on the more detailed designs. Like "Hamish Smith" said, you want some degree of separation between your mockups and final product.

When I want to test the interactivity of my designs, I have used paper mockups before, but I prefer to use PowerPoint which provides a better way for users to interact with the application than constantly having me show them the paper sketches of what page a button will take them to and how certain features work. I just set it up so clicking on the buttons or links on a PowerPoint slide takes you to the slide that corresponds to where that button would take you in the real application.

Currently I have been playing around with Microsoft's SketchFlow that is part of Expression Blend, and it is pretty impressive. I haven't played with it a lot though, so I am not yet aware of any limitations it may pose. Also, I tried Balsamiq and it seems like a good application too, but again I haven't used it enough to find its limitations. I want to make it clear though that I am only using them for Interactivity testing to replace PowerPoint, I still think that static mockups are best done with Paper and whiteboards.

blocks|key|4444437|text|我最近在http://www.guuui.com/issues/02_07.php的一个项目中使用了一个visio插件。该项目大约有60页，这使得绘制屏幕变得非常容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4444438|entityMap|0|LINK|mutability|MUTABLE|url|http://www.guuui.com/issues/02_07.php^0|4|11|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I recently used a visio add-in at <a href="http://www.guuui.com/issues/02_07.php" rel="nofollow noreferrer">http://www.guuui.com/issues/02_07.php</a> on a project. The project has 60 or so pages in it, this made drawing the screens pretty easy.

How do you prototype your software UI? 
What's your experience? 
Could you please share with me? 
Thanks in advance!

How do you prototype your software UI?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

你如何制作你的软件UI原型？你有什么经验？你能和我分享一下吗？提前感谢！

问你如何制作你的软件UI原型？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问你如何制作你的软件UI原型？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问你如何制作你的软件UI原型？
EN