Prebit vs Dukaan — Developer Experience

Prebit's core API layer — typed REST APIs for products, orders, inventory, customers, discounts, fulfillment, and analytics. Event-driven with a durable outbox for reliable downstream delivery.

Prebit's Next.js-powered rendering engine for web storefronts. Uses Incremental Static Regeneration (ISR) to serve instant static HTML from Cloudflare edge caches while streaming dynamic UI islands — outperforming Shopify Liquid with sub-100ms TTFB.

Prebit's Expo & React Native framework for native mobile app development. Powers high-performance iOS and Android shopping apps with native navigation, offline cache, and direct integration with Prebit Commerce Engine APIs.

Prebit's compiled template language. Unlike Liquid's runtime interpolation, Bit compiles to a deterministic AST with a formal grammar — enabling Monaco completions, static checks, and safer AI-assisted editing.

A fully typed client SDK for both storefront and server contexts. Exposes commerce primitives (cart, products, search, checkout) with full type inference — no runtime surprises.

Local development tool for theme development, app validation, and deployment. The `validate` command runs the same manifest/scan checks the App Platform review system uses.

OAuth authorization-code + PKCE, scoped API access, HMAC-signed webhooks, Ed25519-signed releases, and a sandboxed extension runtime.

Internal APIs powering the no-code builder. Not generally exposed for custom storefront development.

Rigid, predefined templates customized via a visual dashboard. No underlying code access for developers.

Tightly coupled frontend and backend. No official headless framework.

Optimized, but closed checkout flow. Customization is restricted to built-in settings.

All development and customization happens via the web admin panel. No local CLI for developers.

Growing plugin library primarily focused on Indian social commerce and WhatsApp integrations.