Training
Build your frontend on Udghatan's SDKs with Claude
A practical tutorial for Developer SDK partners: plan a vertical app, start from an Udghatan starter repo and the @ab-ecosystem SDKs, brief Claude, test and deploy.
Developer SDK partners build their own product on top of Udghatan's backend. Udghatan runs the heavy infrastructure (WhatsApp Business API channels, the CRM gateway, the live inbox, authentication) while you design the frontend your customers see. An AI coding assistant like Claude makes this much faster, as long as you give it good context and work in small steps. This tutorial walks through the process from idea to deployment.
What you'll learn
- How to plan a focused vertical app
- Which @ab-ecosystem SDKs and starter repo to start from
- How to write a project brief (CLAUDE.md) that keeps Claude on track
- An iterative prompting workflow, with example prompts
- How to test and deploy safely
Step 1: Plan a vertical app
General-purpose inboxes already exist. Partners do best with an app built for one industry and one job, such as a clinic front-desk app, a real-estate lead app or a coaching-institute admissions app. Before writing any code, answer these on one page:
- Who uses it? For example, a clinic receptionist on a phone, between patients.
- What are the three screens they'll use every day? For example, today's conversations, a patient's contact card, and sending a reminder template.
- Which Udghatan capabilities does it need? Login, contacts, live chat, templates, campaigns, a store (AI Store)?
- What will you leave out of version one? Write it down. It stops scope creep, yours and Claude's.
Step 2: Pick your SDKs and starter repo
Udghatan's SDKs are typed TypeScript npm packages in the @ab-ecosystem organisation, published at ab-ecosystem.com. Types are bundled, the clients have zero dependencies, and they ship as ESM and CJS. Each package includes its own documentation (README, JSDoc and reference pages), which is ideal context for Claude.
| Package | Use it for |
|---|---|
@ab-ecosystem/cpaas | WhatsApp Business API channels, CRM contacts, bulk campaigns, message templates and the realtime live chat inbox |
@ab-ecosystem/sso | Drop-in React auth and account UI: login with 2FA, signup, forgot password, session validation, account settings |
@ab-ecosystem/aistore-admin | Headless ecommerce admin: products, orders, customers, inventory, shipping, taxes, themes, webhooks |
@ab-ecosystem/aistore-storefront | Headless storefront: catalog, cart, checkout, customer accounts, payments, search, theme assets |
@ab-ecosystem/ai-photo-detector | Event photo management with AI face search |
Rather than starting from a blank folder, start from a starter repo. The first one is the WhatsApp Cloud API Omnichannel Inbox & CRM: a React Native + Expo app for Android, iOS and web, released under the MIT licence. It includes a shared inbox (WhatsApp, Instagram, RCS), CRM, Kanban boards and WhatsApp campaigns in 17 languages, and it uses @ab-ecosystem/sso and @ab-ecosystem/cpaas. One app can serve many workspaces through an Access ID. See SDKs and Starter repos for the current list.
git clone https://github.com/ComBotAI/WhatsApp-Cloud-Api-Omnichannel-Inbox-Crm.git my-clinic-app
cd my-clinic-app
# follow the repo's README to install dependencies and run the app
Adding an SDK to another project works like any npm package, for example npm install @ab-ecosystem/cpaas. Here's the documented pattern for listing CRM contacts:
import { CrmClient } from '@ab-ecosystem/cpaas';
const crm = new CrmClient({ gatewayUrl, clientId, authToken, origin });
await crm.contacts.list({ search: 'acme', rows: 50 });
For anything beyond this example, read the package's own docs, and make Claude read them too. Don't let it guess method names.
Step 3: Write a project brief (CLAUDE.md)
Claude Code reads a CLAUDE.md file at the root of your project at the start of every session. Use it to describe your app, your rules and where the truth lives. A good brief is short, specific and kept up to date.
Step 4: Prompt iteratively
Work in small, testable steps. Ask Claude to explore and plan first, review the plan, then let it implement one piece at a time.
Explore
Plan
Implement one slice
Fix and refine
Keep Claude grounded: when it uses an SDK method, ask "which doc page is that from?". If it can't point to one, it's guessing. Commit after each working slice so you can roll back easily.
Step 5: Test
- Test against a dedicated test workspace and test phone numbers, never a live customer's account.
- Check each core screen on a phone, a tablet and the web build.
- Test the edge cases: no contacts, a very long conversation, a lost connection, an expired session.
- Send real template messages to your own number and confirm variables fill correctly.
- Ask Claude to write tests for the logic you added and to review its own changes for security issues.
Step 6: Deploy
- Move all keys and workspace settings to environment configuration for each environment (test and production).
- Build the web version and host it on your own domain, and use your normal app store process for Android and iOS builds.
- Onboard one friendly customer first and watch how they use it for a week.
- Set up a simple support channel and a changelog before you onboard more customers.
Each SDK product has its own monthly or one-time partner fee plus end-user costs. See SDK pricing. For more detail on the SDK program, read the Developer SDK overview and Building with Claude in the docs.
Key takeaways
- Build for one industry and one job. Write down what's out of scope.
- Start from a starter repo and the @ab-ecosystem SDKs, whose bundled docs are Claude's ground truth.
- Use CLAUDE.md to set rules, then explore, plan and implement in small slices.
- Test on a test workspace, then launch with one customer before scaling.
Practice
Write a one-page plan and a CLAUDE.md for a vertical app of your choice. Then clone the starter repo, run the "Explore" prompt above and compare Claude's summary with your own reading of the code. Did it cite the SDK docs for every method? If you'd like to build on Udghatan, apply for the Developer SDK partnership.
Next lesson: Going live checklist