Leaf.app
The Project
After years of facing many run-of-the-mill agency challenges, and using the “silver bullet” management tools, we asked ourselves: Why can't we build a better solution?
We dove into this question head on, leading us to build an entirely new product to help our customers get the most of their experience with us and streamline some of our workflows. This project is still a work in progress, but we're excited to give you a look behind the scenes.
The Process
Kickoff
The LeafApp project has been alive alongside our client work for some time in our agency's histroy. It has evolved over time as we have, but one thing has stayed the same: To make a product that ultimately leads us to be a better agency. And, as a byproduct, make other agencies better too.
We started the iteration process by having round-table discussions on impactful features we could include. We took to the whiteboard to draw out user experiences we felt would work best and discussed the pros and cons. Ultimately, we landed on some features to start off with and started designing and coding.
Development process
Once we had the designs completed and the front end of the site coded, we needed to make the components of the site actually function with real user data. We isolated feature sets for our MVP (minimum viable product), proposed a tech stack where we would use a Node/Express/Mongo tech stack, and began modelling the data and planning out the user experience. About two weeks into the process, we realized that we needed to build a feature set for admins in order to set up the end-user facing experience, so we started working collaboratively to build out a side for the admins. Along the way, we realized that an application like this could be even more useful for somebody using the admin side than the very specifically tailored client side, so we took a step back and decided to pivot our focus for the site.
On Desktop
