Drop in ready-made React components when an AppKit flow needs to ship fast. This page shows the three component shapes and when to pick each one.Documentation Index
Fetch the complete documentation index at: https://companyname-a7d5b98e-feature-fumodocs.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Before you begin
Install the React packages, mountAppKitProvider, and import the default stylesheet. See Install AppKit in a React app.
Pick a widget level
AppKit UI widgets come in three levels:| Level | Use when |
|---|---|
| Default component | The app needs a ready-made flow with the package stylesheet. |
| Render-prop component | The app needs AppKit to own the state machine, but the layout must be custom. |
| Hooks and core actions | The flow no longer matches one widget, or state must be shared across a larger page. |
<TonConnectButton /> and <SendTonButton /> cover the full user flow. Render-prop components keep the same behavior while letting the app render custom markup. Hooks and core actions are the lowest level and fit flows that need fully custom product logic.
Start with a ready-made component
<TonConnectButton /> is the smallest example. It opens the TON Connect modal, restores the session, and renders the selected wallet address.
Move to a custom send flow
<SendTonButton /> keeps the AppKit transaction flow while exposing render props for custom UI.
Tips
Pick the widget level by control needs. Use a ready-made component for the smallest integration, render props for custom layout, and hooks or core actions when the flow needs more control than one widget can provide.Code example
See a working example that integrates<SwapWidget /> and <StakingWidget /> — try it live.
What to do next
- For a component-by-component walkthrough (Send, NFT, Swap, Staking, transaction progress), see Use UI widgets.
- For task-level recipes, switch to How to.