Just a quick update. I’ve included the links to some various platform prototypes. Hopefully this information helps!
andrea

I’ll try to post a couple examples to this blog post this week so that you can test on a couple different devices. Thanks!

How can we ensure we are building this in the right aspect ratio for devices we’re testing… or does it automatically scale the width to the device?

Thanks for the post!

Currently we are relying primarily on using ProtoShare’s stateful Review URLs to link a Rally User Story to one or more ProtoShare wireframes. Rally’s built-in rich text editor allows us to embed a Review hyperlink directly within the description field of a User Story. For a highly decomposed story this often means just embedding a single hyperlink to a specific ProtoShare Design state. When dealing with more abstract stories however, we often include multiple links that may demonstrate a sequence of states within a Design, highlight specific annotations, or even illustrate competing ideas across multiple Designs or Pages.

This approach is very flexible, and relatively easy to follow when using Rally as the “front-end”, however we also recognize the need to reference Rally artifacts directly from within ProtoShare. Unfortunately, Rally does not offer an easy mechanism to reference individual artifacts by URL, so we are currently limited to typing in the IDs of Rally artifacts within the contents of any relevant ProtoShare objects ( Topic, Annotation, Component Notes, Documentation etc ).

Internally we tend to use this cross-referencing the most when using ProtoShare’s discussion functionality. For example, it is often the case that when discussing a new UX concept we will want to continually refer back to the underlying user needs. An evolving discussion within ProtoShare also quite often leads to a refactoring of one or more User Stories in Rally.

Some of our customers have also expressed a desire to link an external requirement directly to single Annotation in ProtoShare, however after some experimentation, I’m not convinced that such a mapping would be flexible enough. We use Annotations to highlight or clarify specific functional aspects of a wireframe, but they are not nearly as formal or rigid as the acceptance criteria that we eventually define for a Rally User Story. Expanding the Component Specification for this purpose is also a possibility, but that too seems like a difficult mapping when considering the relatively volatile and imprecise nature of a prototype’s components.

Ultimately, I think I would find it most valuable if ProtoShare had the capability to link multiple external artifacts to a Design and display their contents alongside the internal Discussion, Annotations, or Page Documentation. The ability to independently link externally referenced items to one or more Design states would also be hugely helpful. What do you think? How do you imagine your development artifacts would work best within ProtoShare?