2. Most prototypes don’t produce usable code but can be an artifact in the handoff process to designers and developers. In fact, an interactive prototype is the best artifact for them to look at to see what you are trying to accomplish. In this regard, prototyping fits well into the agile development process as a way to more clearly define the feature backlog for your development team.
3. If you do a lot of prototyping, it may be worth learning a tool that can do more than the simple ones. A simple tool with less functionality may meet basic needs. Tools that are more robust, with features that produce prototypes that more closely match the final system regarding interactivity and visuals, will be harder to learn.
4. Collaboration features collect feedback and manage comments. If you have a process for gathering and managing feedback, you may not need built-in collaboration features. If not, doing customer testing and validation without a way of recording comments is not a good idea.
5. Some prototyping tools are more integrated than others. If you use a certain design tool, for example, Photoshop, Illustrator, or Sketch, it will save time if you can directly use files.
6. Are you designing for a smart phone, tablet, laptop, desktop, or multiple devices? You should consider prototyping for how you want the application to work on each type of device. Some prototyping tools are friendlier to responsive design.
7. What’s your budget? Prototyping tools range from free to very costly. Some have free trials.