# dApp & Web3 App Development

> dApp development services: the web3 application layer around your contracts, from wallet and transaction UX to on-chain indexing that makes a protocol usable.

The application layer that makes a protocol usable: wallet flows, transaction-lifecycle UX, and on-chain indexing that turn contract state into a product people can actually navigate.

## The contract works. Nobody can tell.
A deployed protocol is raw capability with no surface: no way to see positions, no readable history, no path through a transaction that a normal user could follow. The value is real and completely inaccessible.

Web3 UX also breaks in ways web apps never do: pending and dropped transactions, chain reorgs, wallet quirks, gas confusion. Ignore them and users sign the wrong thing, or freeze and walk away.

## Make chain state legible and clickable
We build the read layer first: indexers and subgraphs that turn raw events into fast, queryable state, so the interface can show positions and history instead of forcing users to trust a spinner.

Then the write layer is engineered for the realities of chains: transaction-lifecycle UX that handles pending, failed, and reorged states honestly, wallet flows that are hard to misread, and gas made legible.

## What we build
- **Web3 frontends**: Interfaces that read and write chain state clearly, so a protocol becomes a product users can navigate.
- **Wallet & transaction UX**: Connect flows and transaction-lifecycle handling for pending, failed, and reorged states, made legible.
- **Indexing & subgraphs**: Event indexers and subgraphs that turn raw on-chain data into fast, queryable application state.
- **On/off-ramps & payments**: Fiat on-ramps and payment integrations that bridge tokens to bank accounts and cards, so users can get in and out.

## Stack
- **Frontend:** React, Next.js, wagmi, viem
- **Wallets:** WalletConnect, Ethers.js, Account abstraction
- **Data:** The Graph, Subgraphs, Indexers, On/off-ramps

## FAQ
**What do your dApp development services cover?**

The web3 application layer around your contracts: web3 frontends, wallet and transaction-lifecycle UX, on-chain indexing and subgraphs, and fiat on/off-ramps, everything that makes a protocol usable.

**Do you build the contracts too, or just the dApp?**

Both are available. Many teams bring an audited protocol and need the application layer; others want contracts, DeFi mechanics, and the dApp as one engagement across the three blockchain capabilities.

**How do you handle wallets and multiple chains?**

Through standard connect layers (WalletConnect, wagmi/viem) with account-abstraction support where it helps, and a chain-aware UX so users always know which network and asset a transaction touches.

**How do you make transaction UX trustworthy?**

By treating the transaction lifecycle as the core UX problem: clear pending, success, failure, and reorg states, human-readable summaries of what is being signed, and gas presented in terms users understand.

---
Canonical page: https://www.sentientarc.com/capabilities/dapp-development