// PERSONAL PROJECT / FULL-STACK DEVELOPMENT WEB LIVE

SiteBahi.

A working day. A connected system.

A bilingual, mobile-first platform that brings construction teams, building owners, and suppliers into one connected workflow.

Open live site

MY CONTRIBUTION

Product interfaces, APIs, cloud data, and offline synchronization

STACK

React · TypeScript · Tailwind CSS · Cloudflare Workers · D1 · R2

PLATFORM

Web live · Android closed beta

Try the offline demo

sitebahi.inWEB

WEB + MOBILE

Capture the day. Keep work moving.

Attendance, daily work, materials, and site evidence connect to a daily report and the next day's plan.

PUBLIC PRODUCT PREVIEW / DEMONSTRATION DATA

01 / THE PROBLEM

One day.
Many moving parts.

Product interfaces & workflowsRole-aware APIsOffline records & synchronizationBilingual web experienceCloud data & mediaWeb & Android contracts

A construction day creates many small records: who worked, what changed, what arrived, and what needs a decision. SiteBahi brings those records into a shared daily workflow, with a different view for each person involved.

The product connects site attendance, daily work, material requests, photo and voice evidence, owner review, and supplier operations. The web experience supports English and Hindi, with local records and queues for interrupted connectivity.

02 / PLAY THE WORKFLOW

Lose the signal.
Keep the work.

Write a sample report offline.
Watch it reach the shared record.

SITEBAHI / SYNTHETIC DEMONSTRATIONOffline

01 Save on the device
02 Reconnect & synchronize
03 Review any conflict

Start offline. Write a sample report and follow its journey.

Device copy

SAMPLE SITE / DAILY REPORT

Site prepared for the next stage.

Outbox

0pending changes

Your next change starts here.

READY

Shared record

SAMPLE SITE / DAILY REPORT

Site prepared for the next stage.

Try a harder scenario

Simulate a failed sync

Save offline, change the shared sample, then reconnect to see a conflict. Use the checkbox to see a failed sync retain its queue.

.offline-demo-controls { display: none; }This interactive demo needs JavaScript. Read the sequence: save a device copy, keep the change queued while offline, reconnect, compare record versions, and clear the queue only after confirmed synchronization. If both versions changed, choose the report explicitly.

03 / UNDER THE HOOD

Connected layers.
Clear responsibilities.

The product, the access boundary,
and the records behind it.

EXPERIENCE01

React · Vinext · TypeScript · Tailwind

A bilingual PWA with distinct role interfaces. An Expo / React Native Android client shares the versioned API contracts.

APPLICATION02

Cloudflare Workers · REST · Firebase Auth

Versioned endpoints resolve verified identity, membership, site, and role at the API boundary. Domain calculations stay separate from screen components.

DATA03

D1 · R2 · IndexedDB

Tenant-scoped relational records and protected media in the cloud. PIN-protected local records, mutation queues, and conflict state on the web client.

04 / ENGINEERING CHOICES

The details
behind the product.

Constraints, implementation,
and the tradeoffs they introduce.

Keep a day's work available offline.

CONSTRAINT

Site connectivity can be interrupted while a person is recording work.

IMPLEMENTATION

The web client keeps scoped records and queued changes in IndexedDB, with a PIN-derived encrypted device vault. Queues retain retry and conflict information for synchronization.

TRADEOFF

Offline capture needs visible sync state and conflict handling. A local save cannot stand in for confirmed cloud synchronization.

Put access rules behind every screen.

CONSTRAINT

Contractors and owners share site progress while some records must stay private.

IMPLEMENTATION

API authorization resolves tenant membership, site, and role from the authenticated identity. Private records are filtered at the boundary, alongside role-specific interfaces.

TRADEOFF

The API carries the access decision; hiding an interface control alone is insufficient. Shared work and private records need distinct contracts.

Share the contract. Respect the device.

CONSTRAINT

Web and Android need consistent records while their storage and security primitives differ.

IMPLEMENTATION

Both clients use versioned diary endpoints and shared domain rules, while web and native clients keep separate protected local stores.

TRADEOFF

A shared API reduces contract drift, while platform-specific storage still requires its own implementation and validation.

05 / THE PRODUCT TODAY

Built.
And live.

The web product is live at sitebahi.in. Visitors can explore its public product previews and demo entry point. The screens here use demonstration data; no customer records or adoption statistics are presented.

Visit sitebahi.in Back to portfolio

06 / LET’S CONNECTLET’S MAKE SOMETHING USEFUL.

Have a complex problem?
Let’s make it clear.

santosh.ray.dev@gmail.com GitHub LinkedIn Résumé