Skip to content
YA
All work
Release-readyDesktopWebBackend

Vellora

A premium, offline-first point of sale for cafés, restaurants and small kitchens.

Status
Commercial product. My role: frontend developer on contract (2026) — redesign of the UI and design system.
Period
2026
Platforms
Windows · Desktop
Repository
Private — available on request
Live
—
Vellora marketing site in Arabic

01Overview

Vellora runs on the business's own computer. Orders, customers, receipts and backups stay in a local SQLite database, so the counter keeps working when the internet does not. Kitchen display, ESC/POS printing, tables, modifiers, loyalty, tax packs and Arabic/English are built in; Drive backup and WhatsApp bills are optional.

By the numbers

screens redesigned
15+
screens redesigned
CV
design-system primitives
15+
design-system primitives
CV
business-logic changes
0
business-logic changes
CV
  1. 02The problem

    Cloud POS systems stop the counter when the connection drops — exactly during the rush. Small kitchens need something that prints, routes orders to the kitchen and survives a bad network, without an IT department.

  2. 03The solution

    An Electron app that hosts its own Express API and a standalone kitchen-display server on the same local SQLite database (WAL mode), with a statically exported Next.js renderer talking over HTTP and WebSocket.

04Key features

  1. 01

    Every order type

    Counter, dine-in, takeaway and delivery; tables, held orders, modifiers, add-ons, discounts and loyalty points.

  2. 02

    Kitchen display

    Kitchen stations and order tickets served by a dedicated local server.

  3. 03

    Printing that explains itself

    ESC/POS over USB, network and Bluetooth; Test Print reports the real failure — offline, out of paper, cover open, driver error, timeout.

  4. 04

    Safe migrations

    A timestamped backup is taken before any pending migration; migrations are additive and tracked with SQLite's user_version.

05Screens

06System architecture

  1. L1Electron main
    • Express API :3001
    • Kitchen display :3002
    • Printing
    • Backups
  2. L2Renderer
    • Next.js (static export)
    • React
    • Zustand
    • shadcn/ui
  3. L3Data
    • SQLite (better-sqlite3, WAL)
    • Additive migrations
    • Tax packs
  4. L4Optional cloud
    • Google Drive backup
    • WhatsApp bills
    • Reporting
Both servers share one SQLite database; the renderer is a static Next.js export.Diagram — derived from the source code

My contribution

Frontend developer (contract, remote): redesigned 15+ application screens and 15+ reusable shadcn/ui component primitives into a cohesive premium design system, while strictly preserving the existing business logic and data flows; standardized theming, spacing and component APIs.

Technology

  • Electron
  • TypeScript
  • Express
  • Next.js
  • React
  • Zustand
  • Tailwind CSS
  • shadcn/ui
  • SQLite
  • WebSocket
  • ESC/POS
  • Playwright

How this was verified

Source and README reviewed. The product website was served locally from the repository and captured in a browser; the POS itself needs its Electron backend and was not run here.

Related projects

Next project

CodePort