Skip to content

Selected work

Products shaped around the work people actually do.

Three different interfaces, each built around a specific workflow and its real boundaries. Product decisions come first; technology supports them.

01 / RouteFlow

Route operations without the scattered handoffs.

Delivery and field-service routes often begin as stop lists, then move through validation, planning, assignment, and mobile completion in separate tools. RouteFlow treats that sequence as one operational workflow.

routeflow.com.au (opens in a new tab)
Route detailSample operational data
RouteFlow route detail showing a sample route, map, stop sequence, and completion summary
RoutesDispatcher review
RouteFlow routes list showing sample route states and dispatcher controls
Driver view
RouteFlow mobile driver view showing a synthetic sample stop and completion actions
RouteFlow shown across dispatcher and mobile driver workflows.
Focus
Operational workflow
Surfaces
Dispatcher and mobile
Role
Product, build, deployment

02 / SDM Dashboard

A careful interface for a technical modelling workflow.

SDM Dashboard is shared open-source work developed through the Unstable Branch builder collective. The self-hostable platform brings data cleaning, queued R computation, maps, diagnostics, provenance, downloads, and comparison workflows into one workbench.

My contributions focus on the modern web platform, service integration, deployment, and release hardening alongside the project's other contributors.

The software is beta decision support, not ecological proof. Synthetic demo data, run state, and model evidence stay explicit so the interface does not imply certainty the analysis cannot provide.

View source (opens in a new tab)Unstable Branch (opens in a new tab)
Synthetic demo dataBeta decision support
SDM Dashboard interface using synthetic occurrence data, with modelling controls and map results
Example workspace onlyRun state, inputs, and model evidence remain visible.
Project
Unstable Branch collaboration
Contribution
Platform, integration, release work
Availability
Open source, self-hostable

03 / CycleSync

Privacy boundaries people can see and understand.

CycleSync is a local-first period-tracking PWA. Records stay on the device, core use works offline, and quick logging does not require an account or a remote profile.

Calendar marks and personal summaries distinguish recorded history from estimates in plain language. The application supports review and reflection without making medical claims. Portfolio screens use sample data from development builds.

cyclesync.net (opens in a new tab)
CalendarSample data · local-first PWA
CycleSync desktop calendar using sample data to separate recorded history from estimates
Today · sample data
CycleSync Today screen with sample on-device cycle data and quick actions
Calendar · sample data
CycleSync mobile calendar using sample data to distinguish recorded days from estimates
Insights · sample data
CycleSync Insights screen showing descriptive summaries from sample records
Quick log · sample data
CycleSync Quick Log screen using sample cycle information
CycleSync shown with sample data on desktop and in viewport-sized mobile screens.
Focus
Local privacy
Surfaces
Responsive PWA
Data
On-device, offline capable

Have a workflow that almost fits?

Start with the part that keeps creating work.

A useful first conversation is about the current process, not a feature list.

Discuss a project