Normally we start our designs in Balsalmiq but sometimes it makes more sense just to scribble on some sticky notes and start building. This is one of those times. The big effort here was figuring out the workflows and deciding what not to do.
With some knowledge of Harvest’s API and some stickies, we were able to determine that it was likely possible to “attach a contract to an estimate” as our focus group had suggested. This would involve:
Before we started building our add-on, we spent some time listening. We did two things:
Read Harvest’s API documentation and did some basic prototyping. It’s easy to paint yourself into a corner if you don’t know the limits of the integration you’re building.
Met with a group of Harvest users to discuss what their needs are. People don’t always know exactly what they want, but it’s worth finding out what they think they want! We plan to measure and learn from how people behave as well but that comes later.
We’ve set out to build a number of Add-ons for integrating Inkdit with other applications over the coming months. This series of posts is our real life experience of How To Build an Add-on. If you are thinking of building an integration for your web app, we hope that sharing our experiences will be helpful.