React or Retool?

If you're embarking on an internal tools development project, you might be wondering - should I use Retool , or build from scratch using #reactjs or my favorite web development stack?

Maybe you're intrigued by the productivity gains of Retool, but nervous about giving up the power of a fully custom web application?

Luckily, you don't have to choose between one or the other. You can use Retool within a hybrid architecture in one of two major configurations.

1️⃣ Retool "on top"

You can use Retool as your primary UI and authentication provider for end users, and embed custom components and API services from a web application you control.

💪 Advantages

• Use Retool to handle a lot of heavy lifting for UI and backend services
• Remarkably fast development cycles

🤨 Considerations

• Not quite as many customization possibilities as a fully custom web app

2️⃣ Custom web app "on top"

You can build a fully custom web app as your primary UI and auth provider. Then, you can selectively embed Retool UIs (powered by Retool Embed) and use backend resources and workflows built in Retool.

💪 Advantages

• A custom web app provides maximum flexibility for unique requirements
• Can selectively outsource work that's faster/easier in Retool

🤨 Considerations

• Gain less productivity from Retool than you might otherwise, since you're using fewer platform features

Have your cake 🍰 and eat it too 😋

These hybrid architectures enable developers to use Retool when Retool is faster and better, and custom web apps when greater control is needed. Learn more about hybrid architectures in Retool on the blog!