June 14, 2026WEB APPS
Booking systems: custom vs off-the-shelf
Custom booking system vs off-the-shelf scheduling tools: when ready-made apps are enough and when building a custom system is worth it — the real tradeoffs.
BLOG
Notes on building web apps and portals — dashboards, client portals, internal tools, and app UX that holds up in production.
Looking for the service behind these posts? See my web app service page.
June 14, 2026WEB APPS
Custom booking system vs off-the-shelf scheduling tools: when ready-made apps are enough and when building a custom system is worth it — the real tradeoffs.
June 14, 2026WEB APPS
What makes a dashboard usable, not merely pretty — the UX principles I build to: one job per screen, the key number first, progressive detail, and fast data.
June 14, 2026WEB APPS
How long it takes to build a web app: realistic timelines by phase — a simple tool in weeks, a full multi-role app in months — and what makes estimates slip.
June 14, 2026WEB APPS
How much a web app costs to build in 2026: realistic ranges, what drives the price (features, roles, integrations), and where the budget actually goes.
June 14, 2026WEB APPS
Internal tools, build vs buy: when off-the-shelf software is enough and when a custom internal tool pays off — the real tradeoffs in cost, fit, and control.
June 14, 2026WEB APPS
PWA vs native app: the honest tradeoffs in reach, cost, and device features — when a progressive web app beats building for the app stores, and when it doesn't.
June 14, 2026WEB APPS
The signs you've outgrown spreadsheets and need a web app — broken sharing, version chaos, manual errors, no access control — and what to build instead.
June 14, 2026WEB APPS
Auth and user roles in a web app: authentication vs authorization, role-based access done simply, and how to avoid over-engineering permissions in v1.
June 14, 2026WEB APPS
Website vs web app — which does your business actually need? The clear line between them, by what your users do, plus when a portal or app earns its cost.
June 14, 2026WEB APPS
What a client portal should actually do — the core jobs that make one worth building (access, status, files, messaging) and the features that only add bloat.