When working with a client, I build several sets of HTML mockups. They range in fidelity, are responsive, sometimes have a bit of content, have a few animations etc. They usually come in batches - a set of linked screens that displays a user flow or a set of components. This part of my workflow is great.
But I also need to collaborate with client, so I then upload the mockups to a server and share a link to them to my client. After that, the client gives me feedback in meetings, calls, e-mails and so on. This approach has several shortcomings that I'd like to address:
- Versioning is handled manually using folder names, i.e. is unreliable and a chore
- There is no good way for the client to browse and compare versions
- The client get no navigation or overview of their mockups
- I have to add annotations, notes etc. as part of my HTML mockup (instead of related to the mockup version)
- The feedback from the client is located in an e-mail or in my notebook rather than in direct correlation with the correct version of the actual mockup, visible to me and the client
I know that using e.g. InVision would solve my problem, but I'm not interested in using a wireframing tool (or JPEG-to-wireframe tool). I often use the mockups going into the implementation phase. They also gets me full control over fidelity, from a sketchy set of boxes to final front-end code if I want to. This makes the dialogue with the client easier - "Resize your browser window to see the tablet view". Another nifty thing about them is that I can pull in the client's current website's base layout, or a widget that correlates with the change. I'm simply not interested in using a wireframing tool. If InVision supported HTML mockups, however, my problem would be solved!