Understanding Integrations

The power of TurboETH lies in its modular integration architecture. This design allows developers to customize, interchange, and upgrade application components as needed. Here’s a deeper look at how they work:

Core Concepts

Isolation: Each integration is independent, mitigating risks associated with changes to other parts of the codebase.

Reusability: Integrations can be reused across projects or shared within the community, promoting collaborative development.

Scalability: As your needs grow, you can easily scale your application by incorporating additional integrations.

How Do They Work?

Initialization

Integrations are designed for effortless setup and teardown. They can be added or removed by simply copying their corresponding core and api folders and installing the required dependencies. For streamlined integration setup when creating a new project, consider using the TurboETH CLI, which automates the selection and configuration process.

Interaction

Depending on the integration type, the interaction varies. For instance, smart contract integrations use custom hooks, while API integrations provide interfaces to external APIs.

Composition

You can combine integrations to build robust, scalable Web3 applications. An application could use an API integration to fetch data, a smart contract integration to interact with on-chain contracts, and an SDK integration to leverage third-party SDKs.

In summary, TurboETH’s integrations streamline development, reduce redundancy, and promote reusability, enhancing the developer experience.

View the integrations branch to see all of the current integrations.

TurboETH Integrations Branch

Integration Types

Core Integrations

Core integrations are an essential part of the TurboETH template. They cannot be removed from the project and are intended to be used in every app.

⛓️ Smart Contract Integrations

Smart contract integrations are specifically designed to streamline the interaction with smart contracts. This is accomplished using custom hooks generated by the Wagmi CLI, paired with purpose-built components and hooks.

🧰 API Integrations

API integrations are designed to simplify the interaction with external APIs.

πŸ’» SDK Integrations

SDK integrations are designed to simplify interactions with protocols and applications that offer SDKs for use.

πŸ”§ Utility Integrations

Utility integrations are designed to streamline the development process, offering practical tools and utilities for your app, or to assist in creating new integrations.