// ESTABLISHING LINK

000%
OFFLINE

QUEUED 4

DARWIN NIFRAS

// Full Stack

Four layers — schema, API, interface, and deploy — assembling into one working product.

Scroll
Darwin Nifras

// FULL-STACK WEB DEVELOPER

Darwin Nifras

I build complete products end to end: typed APIs, real database schemas, and interfaces people actually use under pressure.

Most of what I ship runs where the network is unreliable, so I’ve learned to build software that stays correct when the connection doesn’t.

I’m based in Iloilo City, Philippines, and I work with clients anywhere.

  • BS Information Systems, Cum Laude — West Visayas State University
  • Software Developer Intern — PDRRMO Iloilo Province

// THE LAYERS

Take it apart and I wrote each piece

  1. Deploy

    CI/CD on Vercel, environment config, and the boring parts that keep it up.

  2. Schema

    Relational models built to the domain — 30+ tables on DRRM-ERS alone.

  3. API

    Type-safe endpoints with authorization enforced at the API layer, not the UI.

  4. Interface

    Accessible, responsive front ends that stay fast on a mid-range phone.

// SERVICES

What I build

One developer, the whole stack — requirements through deployment. Most of my work is web applications and the operational systems around them, plus the automation that removes the manual steps in between.

Web & Systems Development

Full-stack applications built end to end — schema, API, interface, deploy. Type-safe from the database to the button.

  • Full-stack web applications (React, Next.js, TypeScript)
  • Backend systems and type-safe API development
  • Database design and modelling (PostgreSQL, MySQL, Supabase, Prisma)
  • Business and operations systems — inventory, reporting, reconciliation
  • Authentication and role-based access control
  • CMS and WordPress work (themes, plugin configuration, hosting migration)
Start a conversation about Web & Systems Development

AI Automation & n8n

Cut the manual steps between your tools. Workflows that move data, trigger on real events, and — where it genuinely helps — use an LLM to read, draft, or classify.

  • Workflow automation with n8n — syncing, notifications, multi-tool pipelines
  • AI-assisted workflows for drafting, classification, and summarisation
  • Third-party API and webhook integration
  • Workflow and tooling audits with a concrete migration plan
Start a conversation about AI Automation & n8n

Data & Analytics

Turning operational data into something a decision can actually be made from.

  • Admin and executive dashboards
  • Power BI reports and data visualisation systems
  • Structured reporting systems (situational reports, operational summaries)
  • Reconciliation and variance analysis with auditable history
Start a conversation about Data & Analytics

Systems for hard conditions

Where the environment is the constraint — bad connectivity, spatial data, government reporting rules, sensitive records.

  • Offline-first architecture with local storage and sync strategies
  • GIS and spatial data visualisation (Leaflet, QGIS, GeoJSON)
  • Disaster reporting and field monitoring systems
  • PII-aware architecture with role-based data isolation
  • Network setup and simulation (Windows Server, Cisco Packet Tracer)
Start a conversation about Systems for hard conditions

Scoped and quoted per project

I don't publish packages, because the same feature list can mean two very different builds depending on who uses it and where. Tell me the problem and I'll come back with an approach, a timeline, and a fixed number. Open to international remote engagements.

Request a quote

// THE STRESS TEST

Three things I’m relied on for

Type-Safe APIs

End-to-end types from the database to the component, so a schema change breaks the build instead of production.

Authorization enforced at the API layer, with per-municipality data isolation.

Offline-First Systems

QUEUED

Local-first data, submission queues, and conflict handling for networks that come and go.

A race condition under rapid reconnects. Closed with a sync lock. 43 municipalities.

Data Integrity

Versioned, non-destructive history and constraints enforced at the database layer, not by convention.

An immutable ledger enforced by database triggers, with a full reopen audit trail.

// PROOF

Systems that shipped

  1. Offline-first systems2026

    Sole Developer · PDRRMO Iloilo Province

    Offline-first disaster-reporting system digitizing the NDRRMC SitRep workflow across all 43 municipalities of Iloilo Province. Modeled 21 report annexes in a 30+ table schema with versioned, non-destructive history and an offline submission queue with a sync debounce + lock that killed a field data-duplication bug. Presented live to the PDRRMO head; earned an approved 5-municipality pilot budget.

    • Next.js
    • tRPC
    • Prisma
    • PostgreSQL
    • Supabase
  2. Content architecture2025 – 2026

    Client Contract

    A 45-lesson interactive physics e-learning platform across 6 modules, mapped to 15 DepEd K-12 competency codes. An extensible formula and scene registry powers 15+ SVG/Canvas/WebGL simulations; a hand-rolled service worker (cache-first assets, network-first-with-fallback navigation) keeps it usable on school connections; a deterministic seeded-RNG renderer eliminated SSR/CSR hydration mismatches; and real-time Web Audio drives beat detection and live oscillator synthesis. 60+ components held together by living architecture docs.

    • Next.js 16
    • React 19
    • Three.js / React Three Fiber
    • Tailwind CSS v4
    • Service Workers / PWA
    revoltphysics.vercel.app— open the live REVOLT Physics site in a new tab
  3. GIS & spatial data2024

    Lead Developer · Undergrad Thesis

    A GIS platform mapping vulnerable populations (PWDs) for emergency response. Piloted in two Iloilo municipalities with above-average acceptability scores from MDRRMO evaluators.

    • React
    • Vite
    • Leaflet
    • GeoJSON
    • Firebase
  4. Deterministic domain logic2025

    Developer

    Offline-first rental-management PWA for 20 condo/parking units, with IndexedDB as the source of truth and a deterministic payment-allocation engine that stays correct under intermittent connectivity.

    • Next.js
    • React
    • Dexie.js
    • Service Workers
    • TypeScript
  5. Data integrity & auditability2025

    Freelance Developer

    Poultry distribution & reconciliation system with an immutable transaction history enforced at the database layer via triggers — the ledger can't be silently rewritten.

    • Next.js
    • Supabase
    • PostgreSQL
    • TypeScript

// HOW IT RUNS

Four steps, and you see it working from the first one

The same shape on every project, whether it's a provincial disaster office or a landlord running twenty units. No black box, no big reveal at the end.

  1. 01

    Scope

    I map the process as it exists today, including the spreadsheet nobody admits to. You get an approach, a timeline, and a fixed number before any code exists.

    You get: a written scope and a quote.

  2. 02

    Model

    Schema first. The data model and the access rules get settled while they're still cheap to change — they're the part you can't refactor later without a migration.

    You get: the data model, in plain language.

  3. 03

    Build

    Working software in front of you throughout, not at the end. It's deployed from the first week, so "it works on my machine" never enters the conversation and you can course-correct while it's cheap.

    You get: a live URL you can open any time.

  4. 04

    Hand over

    The deployment, the accounts, the documentation, and the code. You own all of it — there's no lock-in and nothing runs on infrastructure only I can reach. I stay reachable after launch.

    You get: the keys to everything.

// TOOLKIT

What I work in

Frontend

  • React
  • Next.js
  • TypeScript
  • Tailwind CSS
  • React Three Fiber
  • GSAP

Backend & data

  • tRPC
  • Prisma
  • PostgreSQL
  • Supabase
  • MySQL
  • IndexedDB / Dexie.js

Automation & AI

  • n8n
  • Make
  • Zapier
  • Webhooks & REST APIs
  • Claude

Mapping & analytics

  • Leaflet
  • GeoJSON
  • QGIS
  • Power BI
  • Firebase
  • MongoDB Atlas

Day to day

  • TypeScript
  • Supabase
  • GitHub
  • Vercel
  • VS Code
  • Claude
  • Figma
  • Framer

// TRACK RECORD

How I got here

  1. Nov 2025 – Present

    Freelance Software Developer

    Self-employed

    Commissioned client builds delivered end to end — requirements, architecture, implementation, deployment.

    • Rogers Manokan — poultry distribution & reconciliation, with immutable transaction history enforced by PostgreSQL triggers and a sealed daily-closure audit trail
    • REVOLT Physics — 45-lesson interactive e-learning platform mapped to 15 DepEd competencies, on a data-driven JSON content architecture
    • Cathy CCRMS — offline-first rental PWA running 20 condo and parking units on a deterministic, auditable payment-allocation engine
  2. Jan – Apr 2026

    Software Developer Intern

    PDRRMO Iloilo Province

    Sole developer of DRRM-ERS, digitizing the NDRRMC SitRep workflow across all 43 municipalities of Iloilo Province (486-hour internship).

    • Modelled 21 NDRRMC annexes in a 30+ table schema with versioned, non-destructive history (Next.js, tRPC, Prisma, Supabase/PostgreSQL)
    • Engineered an offline submission queue on Dexie.js/IndexedDB, with a sync debounce and lock that eliminated a duplication bug under field reconnection
    • Enforced authorization at the API layer, with per-municipality data isolation
    • Presented live to PDRRMO leadership — approved for a funded five-municipality pilot
  3. Dec 2025 – May 2026

    Social Media Manager

    Mellowglam

    Content strategy, posting schedule, and campaign coordination for a skincare brand. Sits here as employment history — brand and social work isn't something I take on as a service.

Education

BS Information Systems, Cum Laude

West Visayas State University

Undergraduate thesis: LOTIS, a GIS platform mapping vulnerable populations for emergency response — piloted in Zarraga and Santa Barbara with above-average acceptability scores from MDRRMO evaluators.

Read the case study →

What makes the work different

  • Built for real-world conditions, including low connectivity
  • Built around the people who actually use it, under pressure
  • Architecture to deployment handled by one person, end to end
  • Built to be maintained, not just demoed

// STATUS: AVAILABLE

Let’s build something that holds up.

Tell me what you’re trying to solve — where the process is now, where it needs to get to, and what’s in the way. I’ll come back with an approach and an honest scope, or tell you if I’m not the right person for it.

Based in
Iloilo City, Philippines (UTC+8)
Availability
Open to freelance & remote contracts

What helps me answer faster

  • What the process looks like today, even if it's a spreadsheet
  • Who actually uses it, and under what conditions
  • Your rough timeline and budget range