WEB DEVELOPER · END-TO-END

I build web systems that keep working when the internet doesn't.

Independent full-stack developer. I take a project from database to deployment on my own — no hand-offs, no half-built demos. Two shipped, in-use products below.

STACK Node.js · Supabase · PostgreSQL · Cloudflare · PWA / MODE Remote, async-friendly / BUILDS Solo, end-to-end
01

Selected work

Two live products, picked to show range: an offline-first business system, and a full client-facing platform with zero backend.
Attendance, Overtime & Payroll System
A workforce management platform that keeps recording attendance even when the internet doesn't.
LIVE · 3 APPS

The problem

Small companies need one system for attendance, payroll and overtime — but most tools assume constant internet and one check-in method. This one had to run at a shared gate device, on employees' own phones, and keep working offline on both.

What I built

Three linked apps on one Supabase backend: an offline-capable attendance terminal (FaceScan or ID+PIN), an admin panel with live review and automatic payroll, and a self-service employee portal.

Challenges I solved

  • Offline-first recording — check-ins save locally and sync automatically once the connection returns, so a dropped signal never costs a record.
  • Automatic day-by-day payroll — a status-driven engine handles five owner-authorization states, auto-pays holidays and off-days, and applies a 2.0× overtime rate, recalculating live as records are reviewed.
  • No reliable holiday API existed — built a simple import flow so an owner loads a full year of national holidays in seconds.
  • A 7MB face-recognition model was too slow on weak mobile data — scoped FaceScan to the shared gate terminal only, and used a lightweight ID+PIN flow for personal devices.
Owner dashboard with attendance review and automatic payroll table
FaceScan terminal capturing a live check-in
Stack Node.js Express Supabase / PostgreSQL PWA + Service Workers face-api.js Render
Pola Clip — Video Repurposing Platform
A full client-facing service platform — intake, sample delivery, and a client portal — with zero backend.
LIVE · STATIC

The problem

Launching a video-editing service meant needing a marketing site, an intake flow, and a dashboard clients could log into to check project status — without paying for servers or a database before the business had its first client.

What I built

A 100% static, serverless site: a multi-step "free sample" request wizard, a code-based client portal, and a service agreement page — deployed on Cloudflare with no server to maintain.

Challenges I solved

  • Client login without a backend — designed a lightweight client-code system so clients check project status with no database or auth server.
  • A trust-first funnel — built the whole "sample first, pay later" journey end to end: request → free sample delivered → payment only after the client approves.
  • Zero infrastructure cost — fully static, so it redeploys to any static host in minutes with nothing to keep running.
Pola Clip before and after: long video transformed into a viral short clip
Pola Clip pricing page with three plan tiers
Stack HTML / CSS / JS Cloudflare Pages Wrangler Static / serverless architecture
02

Skills

What I use to take a project from idea to something live.

Frontend

  • HTML5 / CSS3
  • JavaScript (ES6+)
  • Responsive design
  • PWA & Service Workers

Backend

  • Node.js
  • Express
  • REST API design

Data

  • PostgreSQL
  • Supabase
  • Schema design

Deployment

  • Cloudflare (Wrangler)
  • Render
  • Git / GitHub

How I work

I build complete products solo — from database schema to production deployment — currently doing that under Pola IT. Both projects above went from a blank page to something real people use, with no team behind me. That's the kind of ownership I bring to any project, full build or a defined piece of a larger one.

LOCATIONMyanmar
AVAILABILITYRemote, async-friendly
WORKS BEST ASEnd-to-end / full ownership
COMPANYPola IT

Have a project that needs to be built end to end?

I take on full builds — one developer, start to finish. Tell me what you're trying to ship.