Jonathan Hipolito

What I built

• Product catalog across 12 categories, with search
• PC builder that checks CPU socket and memory compatibility, estimates power draw, and turns a build into a shareable link or quote request
• Cart and checkout with COD, GCash and bank transfer, plus order tracking
• Customer reviews, a gallery of released builds, and a page for each branch

What I built

• Doctor and specialty search on the landing page
• Profiles for each specialist, linking out to their own booking pages
• Pages explaining each area of practice, from robotic urologic surgery to breast oncoplastic surgery
• A Node.js and Express API with Sequelize and MySQL behind it, documented in Swagger, with Passport sessions for doctor and admin accounts

What I built

• Real tenancy: path-based workspaces with every query scoped to its workspace, a workspace switcher, and a second workspace one click away. Another tenant's address answers 404, the same as one that doesn't exist
• Accounts with hashed passwords and session tokens, owner, admin and member roles that can't leave a workspace without an owner, and invite links that hold a seat until someone accepts
• Free, Pro and Team plans with board, seat and request limits and gated features, each limit turning into an upgrade prompt. A 14-day trial that drops to Free when it ends, without deleting anything
• Billing in test mode: a checkout with succeeding and declining test cards, prorated plan switches, cancel at period end, and a test clock that runs renewals, failed payments, retries and cancellations, logged as the same webhook events Stripe sends. Real Stripe Checkout and signed webhooks switch on with a key
• The product itself: an inbox to triage new requests, revenue per request from the voters' plans, merging duplicates with their votes, internal notes, a drag-and-drop roadmap, and a changelog that marks requests shipped when it's published
• A platform console for the operator with MRR by month, plan mix, past-due and churned tenants, and read-only 'view as' for any sample tenant

What I built

• A schematic canvas editor: drag steps around, drag from a port to connect them, if/else and approval steps with yes and no branches, and a side panel to edit each step. Edits save as you go and every save is a new version
• Templates between steps: any field can use {{step.field}} from earlier steps, with click-to-insert chips and a warning when a field points at a step that hasn't run yet. Renaming a step rewrites every reference to it
• Four AI steps on Gemini, with Workers AI as the fallback: extract fields with types, classify into your own labels with a reason, write an email in a set tone from the studio's real policies, and summarize with sentiment. Each one returns checked JSON
• Durable runs on Cloudflare Workflows: every step retries on its own, a Wait step sleeps, and Ask for approval pauses the run until someone approves, edits or rejects the draft, even days later
• A live run view: the path lights up on the canvas as steps finish, branches not taken fade out, and the run log shows exactly what went into and came out of every step
• Five triggers fed by sandbox apps: an inbox, the studio's wholesale form, invoices you can mark overdue, a schedule, and a real webhook URL you can hit with curl. Actions land in sandbox sheets, team chat, a CRM and sent mail, each linking back to the run that made it

What I built

• A React Native app built with Expo: the day's route, job details with the equipment on site and past visits, GPS check-in on arrival, a checklist per job type, before and after photos from the camera, parts from van stock, notes, and the customer's signature on the glass
• Offline first: every change goes into an outbox on the phone and shows up on screen right away, then syncs when signal is back. Replays are safe to repeat, checklist taps merge by time, and if dispatch moved the job or changed its notes meanwhile, the tech is told what changed instead of anything being overwritten
• The phone and the server share one set of sync rules in TypeScript, so what the tech sees offline is what the server will accept
• A dispatch board with a drag-and-drop schedule per tech, open calls to assign, a live map of jobs and vans on free OpenFreeMap tiles, and each job filling in as the tech works it. Moving a job sends a notification to the phone
• Live over WebSockets from one Durable Object per visitor. The other four techs move through their day on their own so the board never sits still
• A tracking page for the customer with the tech's first name, van and arrival window, plus an Android APK built in GitHub Actions. On an iPhone or a laptop the same app runs as a web build inside the demo