Our Story

There are already a bunch of various content management systems on the market. So why would we bother to build another one?

The idea to build Coppy came to us when we were building an instant-payment feature for a mobile bank. There were about 10–15 screens and several call-outs that we used to explain the new product to our users, answer their questions and lessen their concerns.

As we launched the feature, we realized that the hard-coded copy in the app did not work well for us: every time the product or design wanted to tweak the text, we had to submit a new build to the store. Additionally, we had to approve each change with our legal team to make sure the copy in the app was clear, easy to understand and compliant. The whole process involved multiple parties and was complicated and time-consuming.

For our next launch, we started to search for a better solution.

As we already used a headless CMS for our blog posts, our first instinct was to hook it up to our app and allow our product, design, and legal teams to update the app copy at any time. Very soon, we realized that it was not quite working for us:

• it was tedious and time-consuming to build content schema for each screen, especially as they were changing during development;
• the cost of getting the content into the app was growing pretty significantly as users were using the app daily.

Ultimately, we wrote our internal server-driven framework that was serving the content from our servers. This approach expedited our next launch, yet it had its shortcomings:

• product, design and legal had to nudge the engineers to update the app coppy;
• we were loading the content every time the user was going through the flow, which wasn't a great experience and added additional load on our servers;
• it was still tedious to update the content structure (we had to deal with backward compatibility and make sure each version of the client was getting the correct copy).

When we faced these challenges, we realized that there was a need for a tool that streamlined content management in mobile apps. The tool that makes this process quick, reliable, and straightforward. And we decided to build Coppy.