Customized UI

A fully custom conversation UI built from @akapulu/react hooks plus Daily primitives. You build the call surface yourself — video tiles, mic/cam/end controls, transcript, loading and error states, and tool toasts — and end with a post-call review screen (recording + transcript). Use it when you need full control over markup and state wiring. Two folders:

backend/ — Express server that holds your API key and calls Akapulu with @akapulu/server
frontend/ — React app (Vite); @akapulu/react plus a direct @daily-co/daily-react because this app imports DailyVideo. No @akapulu/react-ui.

Prerequisites

Node.js 20+ and npm
An Akapulu API key — akapulu.com/api-keys
A scenario — akapulu.com/scenarios (guide)

Setup

Clone the repo:

git clone https://github.com/Akapulu/customized-ui.git && cd customized-ui

Install and configure the backend. Copy backend/.env.example to backend/.env.local and add your API key:

cd backend && npm install && cp .env.example .env.local

AKAPULU_API_KEY=your_real_api_key_here

Set your scenario id in backend/server.ts:

const connectPayload = {
  scenario_id: "<your-scenario-id>", // <--- replace with your scenario id
  avatar_id: "1285bfe4-3512-4b34-93ad-196098597a1c",
  runtime_vars: {},
  record_conversation: true,
  show_ai_label: false,
};

record_conversation: true is required for the post-call review to have a recording to show. Start the backend (localhost:3001) and leave it running:

npm run dev

In a second terminal, start the frontend:

cd frontend && npm install && npm run dev

Open localhost:5173 and click Start call. When the call ends, you land on the review screen.

How it works

The frontend (localhost:5173) calls your backend (localhost:3001), which calls Akapulu with your API key. This demo does not authenticate users. Anyone who can reach /api/connect can start a conversation on your account. Before production, authenticate users on that route. Pass those headers with config.headers on AkapuluProvider (object or a function called when the request is sent). The backend exposes four routes:

// POST /api/connect              →  starts a conversation (record_conversation: true)
// GET  /api/updates              →  polled while the avatar boots
// GET  /api/conversation-details →  transcript + metadata for the review screen
// GET  /api/recording            →  streams the recorded video

On the frontend:

src/App.tsx — AkapuluProvider (points at the backend) plus a single reviewId state that decides which screen shows (live call UI or conversation review).
src/CustomConversation.tsx — the custom call surface: useAkapuluSession for lifecycle, Daily hooks (useDaily, useVideoTrack, DailyVideo) for video, useAkapuluMediaControls for mic/cam, useConnectChime for the connect chime, useAkapuluEvents for tool toasts, and AkapuluBotAudio for audio.
src/ConversationReview.tsx — post-call screen; fetches details and polls until the recording is ready.
src/styles.css — the call surface styling.

Prebuilt UI — minimal AkapuluConversation demo
Prebuilt UI (styled) — styled prebuilt UI + post-call review

View on GitHub

customized-ui

Overview

Web SDK examples

Example scenarios

Scripted video clips

Prerequisites

Setup

How it works

View on GitHub

​Prerequisites

​Setup

​How it works

​Related examples

​View on GitHub

Prerequisites

Setup

How it works

Related examples

View on GitHub