I work from discovery through launch and handoff.

Selected systems, data, publishing work, and public software built from the first conversation through launch.

Software you can see.

My public Apple-platform work reflects the same approach I bring to client systems: understand the real work, test the behavior, and leave a result the next person can understand.

Libraried app icon

Libraried: UI Components

A hands-on SwiftUI reference for iPhone, iPad, Mac, and Apple Vision.

See published apps

Client names and identifying details are omitted from the examples below.

Discovery through working Preview

Turning a complicated business process into one connected system.

The work began with calls, spreadsheets, and staff knowledge. I translated that into business rules, a data model, screens, and connected handoffs for the work the company handles every day.

  • Shared records for the people, products, projects, and documents involved
  • Secure data model and clear boundaries with outside services
  • Focused testing, Preview deployment, reliability work, and production readiness

Workbook to catalog import

Making inconsistent inventory data ready to review and import.

A large workbook contained product details, quantities, images, and exceptions that did not fit a clean commerce catalog. I built a repeatable transformation and review process around the source data.

  • Parsed irregular records into consistent product and option information
  • Normalized source data and recovered missing relationships
  • Merged duplicate records without hiding conflicts
  • Split the result into reviewable import groups and compared it with the existing catalog

Modernization without a risky cutover

Improving search, publishing tools, and SEO while preserving an established site.

The website already had years of content, familiar navigation, and multilingual behavior people depended on. I improved live paths in place and built newer tools in parallel before changing production.

  • Language-aware search, filters, canonical links, and content paths
  • Protected publishing tools built and source-tested
  • Structured data, sitemap work, performance, and deployment verification
  • Existing content and editorial identity preserved throughout the work

Have a process or system that does not fit a neat category?

That is normal. Show me how the work happens and where it gets difficult.

Discuss the work