Primary

"Helped us formalize and scale our testing"

Commenti: Very positive!

Vantaggi: Ease of use, features, documentation and annotation abilities

Inconvenienti: Nothing to really call out for this area

"Very good tool for sharing the process"

Vantaggi: As a freelance application designer, I often work with small teams that don’t have much (any) experience with the UX process. Primary not only captures the user flows, it’s also a great tool for explaining the process to newbies.

Inconvenienti: Primary is opinionated. I honestly cannot decide whether that’s a good thing or not. It’s certainly better than trying to be all things to all people, but my opinion doesn’t always coincide wit’s that of the Primary designers.

"Good Idea But Needs More Functionality"

Commenti: I think it’s a great idea for a tool but it thus far under-developed.

Vantaggi: I liked having a new way to visualize a user flow.

Inconvenienti: I was charged after already having attempted to cancel. I didn’t find that the app served my needs. It didn’t have the breadth of functionality I would have expected and just during my initial use I discovered several show-stopping bugs.

"Primary makes end user journey experience easily to prototype, without needing a prototype."

Commenti: Primary is great to brainstorm complex website flows, showing them to the client, and finding out what isn't going to work much faster and more cheaply than building a real prototype.
Thumbs up from me!

Vantaggi: Once you get the hang of the concept behind Primary, the system is very easy to use, with drag-and-drop widgets, paste-to-upload wireframe images, or integrations with wireframe generators. Branching of pathways as the "visitor clicks different options" is also intuitive to follow.

Inconvenienti: There is a mental visualisation issue I have, with the fact that a "click" is really between one pageview and another, but it is not represented that way.
I personally would like to see the same user action shown at the bottom of one step in Primary, and the top of the next. Possibly even show it between the two steps in the Flows view.
But really, it's not that difficult to get used to how Primary does it.

"Love the product but there is room for improvement :)"

Commenti: I love the concept and find primary extremely helpful during out handoff processes. The section Document is powerful (and I suggest to enhance it, also with easy-to-generate-and-read printable documents). However we as a team still have some issues when it comes to configuring it as some things are not easy to use / navigate as we would like, with the result that we think configuration takes more time than it should. Also sometimes we are forced to use other tools (InVision for presenting, Markdown editor / Office Word to create printable documentation) and spend one or two hours every handoff to explain how Primary works and can be navigated to others. We will continue to use it hoping these feedback can be taken into account in your roadmap :)

Vantaggi: Sharing journeys and flows with an important focus on the documentation (what the user do, how the system respond..) and the possibility to create and re-use elements (interfaces, rules, data...). It's a great help when passing the project over the developer team in a structured way and with all the information needed that cannot be explained in the interface itself.

Inconvenienti: The value proposition (at least the one I perceived) is great. But the product still lacks some important features in my opinion.
- a full screen presentation mode, similar to InVision. The current presentation mode has great focus on the user and system actions. This is great in 2 cases: 1. sharing a project to a team that is already familiar with the interfaces 2. sharing a project with minimal interfaces with the goal to share a common understanding of the flows. But in many cases a navigable full screen view is better for presenting.
- releases cannot be edited to add/remove a flow. generally once created is not easy to understand what is inside a release and what is not, you need to go in presentation mode to understand that.
- it's not crystal clear how I should I use groups and how they relate to journeys (given that groups are not even visible in presentation mode)
- generally speaking navigation in the journeys and flows should be improved. small thing: we have very long flow names as we use User Stories. This is a problem in most cases are names are cut and we cannot recognize what flow we are selecting
- configuring flows should be easier. Examples: duplicating flows (also in bulk), reordering steps or branches, copying a step in a flow into another flow...