When you spend as much time in ProtoShare as I do, you quickly notice the benefits of reusing your work. To reuse a piece of content that you’ve already created, instead of rebuilding content from scratch, saves time and, of course, increases productivity.

I get a lot of questions about working with States, and in particular when and how to use some of the more obscure State Navigation components. In this 3-part post we will dissect a few of the example widgets that we’ve recently added to the new Stencils and Widgets Library in an effort to better understand the usage and configuration of stateful components.

As you know, we’re big on stakeholder and team collaboration here at ProtoShare, especially early on in the website and application development processes. The more you collaborate early on in the process, the better the final result will be – and the less rework you’ll have to do later.

As a company, we really have two goals: We want every one of our customers to love ProtoShare, and we want every one of our customers to love the experience of working with us.  Seriously. We’re always trying to get closer to the “love” on both of these goals.

Prototyping is a key element to the requirements discovery, definition, and validation process when building web applications. However, it’s all too common for teams to spend too much time in the prototyping phase, thereby defeating the purpose of creating a prototype in the first place. Here are several best practices to ensure you and your team get the most from your prototyping process.