Why Hops?

Before explaining why you should use Hops, let's discuss the concept of internal tools.

In our work, we encounter various types of tools. While some of these tools include business messengers and email clients, there are also essential tools for product operations, such as product back offices (commonly called admin panels) and customer management services. At Hops, we define these essential tools for product operations as internal tools.

Traditional Internal Tools

Internal tools have requirements that are strongly tied to the characteristics of the product being operated, which means there are no general solutions available. Therefore, to create internal tools that meet these requirements, direct development is the only option. However, in rapidly growing organizations, there's already limited time to develop features for the main product to achieve business goals.

As a result, the functionality provided by internal tools often can't keep up with product development speed. The lacking features in internal tools are handled through manual work, such as programmers directly executing queries, and this manual work gets repeated every time. This makes it difficult to prevent errors from mistakes, and with customer requirements rapidly increasing but limited time available for operations, it's not sustainable in the long term.

Internal Tools Built with Hops

So how are internal tools built with Hops different from traditional ones?

Hops offers a way to quickly and easily create and operate internal tools by utilizing your existing resources. Most importantly, since you can use your existing databases and backend servers as is, you can easily build internal tools capable of data processing without new API development or infrastructure setup. Additionally, by combining dozens of components provided by Hops, frontend development becomes unnecessary as well.

Let's look at this process in more detail.

First, connect your existing database or backend server to Hops as a data source. This immediately allows you to define workflows for data processing tasks. Then, by linking workflows with various components provided by Hops, you complete a page. While a single page can serve as an internal tool by itself, you can also connect multiple pages organically to develop it into a larger internal tool system.

There Are No Limits

While Hops' provided components are sufficient in most cases, sometimes you might need more specialized components when advancing your internal tools. The Hops development team has prepared a special feature so you won't have to give up or wait for new components to be added in such situations. You can export your page as a TypeScript project using the React library, extend it however you want, and redeploy it to Hops. We'll cover this in more detail in the relevant documentation.

Start Now

Interested in this new way of building internal tools? Feel free to read more documentation, or if you're short on time, start using Hops right now. If you have any questions, don't hesitate to contact us at contact@hopsoffice.com. We'll make sure to respond as quickly as possible.