API and Integration
Going API first is the most robust way to build a scalable product but it wasn’t where Niice started. In the early days, the app was very tightly coupled with the interface on the same server as the backend along with multiple others. This affected performance, scalability, and our ability to move faster and develop quicker. We had to stage our API builds according to capacity and budget to keep the business moving forward while we were gradually moving over to a solely API-based product.
“Our software doesn’t exist in a vacuum, it’s critical that we understand our place in someone’s workflow and play nice with all the other tools they're using” - Chris Armstrong, Founder, Niice.
Integrating with Slack allowed Niice to seamlessly slip into existing workflows of creative teams. On-boarding a team internally to a new tool is incredibly challenging, the Slack integration was a small helping hand we were able to provide at very little development cost.
As Niice transitioned from a tool for individuals to an enterprise platform for teams the Dropbox integration allowed two-way sync to get lots of content in and out of Niice quickly. This is vital for non-design team members who want to contribute fast - just put it in Dropbox, Niice does the rest.