Full-stack products
Web applications, databases, CMS work, storefronts, product galleries, and the operational details around them.
Lucas Boyles / Independent software developer
Products,
tools & worlds.
I build useful software across the seams: full-stack web products, desktop tools for real workflows, and systems for games people actually play.
Based in Iowa · Open to remote, hybrid, contract, and full-time work
01 / Selected work
Built to be used.
A small, honest slice of independent work across web products, developer tooling, and game-adjacent systems.
01
Project Grail
A full-stack progression tracker for Project Diablo II. Built around a real game community and validated through a live league deployment.
02Catwalk
An open-source, cross-platform organizer for 3D-print model files—built to make a messy library navigable again.
03KwikTip
A contextual World of Warcraft addon for instance guidance, maintained for the current game and used by players in the wild.
04KwikTiles
A browser-based grid-level editor for multi-floor maps, semantic tiles, typed actors, generation, and game-engine export paths.
05KwikShack
A gallery and sharing companion for World of Warcraft housing builds, connecting blueprint codes with browsable player-made work.
02 / Practice
Range with a center.
The mediums shift. The recurring job is making complicated things understandable, dependable, and satisfying to use.
Desktop & dev tools
Purpose-built software for organizing work, compressing repetitive steps, and making complex data feel manageable.
Game systems
Tools, data, UX, and technical systems that respect both the people building the game and the people playing it.
Self-hosted operations
Local AI infrastructure, Docker services, automation, and practical deployments with fewer unnecessary moving parts.
03 / How I work
Make the useful thing.
I prefer concrete requirements to theater, durable systems to clever detours, and software that earns the right to grow.
01
Start with the workflow and the real constraint—not a fashionable architecture.
02
Keep the system legible: clear boundaries, useful names, and fewer surprises for whoever maintains it next.
03
Ship a working core, learn from its use, then add complexity only when it has paid for itself.
04 / Contact
Have something worth building?
I’m open to thoughtful full-time, contract, and collaborative work—especially where product judgment and technical range both matter.