Business systems
Role-based portals for operations, inspections, staff requests, CRM, asset records, dashboards and reporting — built around the way people actually work.
I build mobile apps, business systems, APIs and websites around real operational problems. My work includes private workflow tools, public applications on the App Store and Google Play, and the backend systems that keep them running. I like software that is useful, understandable and maintainable.
I normally start by understanding the current process, what takes too much time, where information is being lost, and what the software genuinely needs to make easier.
Role-based portals for operations, inspections, staff requests, CRM, asset records, dashboards and reporting — built around the way people actually work.
React Native applications for iOS and Android, plus Android TV work, backed by APIs, authentication, notifications, admin tools and store publishing.
Laravel applications, REST APIs, databases and integrations that connect mobile clients, external services, scheduled work and administration systems.
I maintain long-running applications, troubleshoot production problems, update integrations and improve systems step by step after the first release.
Some projects are public and some were built privately around a specific operational need. Together they show how I approach mobile, backend and business-system work.
A business receives imported parts that must be inspected before acceptance. Operators choose a job and part number, view the reference image, then record passed quantities or faults with notes, photos and traceability details.
Role-based access gives operators, management and customer users different views of the same records. The platform also covers jobs, items, fault definitions, timesheets, operator performance, and monthly, yearly and part-number reporting.
My role: I designed, developed and maintain the full Laravel system — from the database structure and inspection workflows to permissions, administration screens, customer access and reporting.
A private set of tools I built around practical operational needs I encountered at work. Staff-facing workflows cover leave requests, equipment and uniform records, forms and resignations, while manager tools support employee records, approvals and document handling.
The system also includes master rosters and work zones, QR-based asset records with usage and condition history, before-and-after photo registers with PDF export, and operational and audit dashboards.
My role: I designed, developed and maintain the full system — from the database structure and staff and manager workflows to PDF generation, QR asset tracking, dashboards, access controls and deployment.
An iOS and Android support platform for people affected by Rett syndrome, their families and carers. It brings together centrally managed information, therapies, research, books, specialist listings, notifications and consent-based emergency information.
The Laravel backend supports Google and Apple sign-in, shared profiles with invitation and member controls, feedback, push-device management, and administration tools for content and family services.
My role: I am responsible for software development across the React Native application, Laravel API and administration system — from authentication and shared-profile workflows to data structure, deployment and store publishing. The organisation provides the subject-matter direction and health content.
An independent iOS and Android application I built for checking Melbourne metropolitan and regional train information more directly using public timetable data. It covers service status, disruptions, routes, stations, departures, timetables and nearby transport information.
Behind the application is a Laravel API that handles metro and regional rail flows, upstream transport data, live vehicle locations, route delivery history, device notifications, feedback and application updates.
My role: I designed, developed and maintain the full software stack — the React Native application, Laravel API, administration tools, external data integrations, notifications, deployment and both store releases.
Independent third-party application · Not affiliated with a transport authority
A long-running IPTV player for Android phones, tablets and television devices. I built backend APIs and administration tools for authentication, server configuration, device management, billing, feedback and application support. Users can manage their own playlists through the web side and synchronise them with registered devices.
Building and maintaining it taught me a lot about API versioning, device management, mobile/backend communication and keeping software working across different Android and television environments.
My role: I designed, developed and continue to maintain the Laravel backend and APIs they use, the customer web portal for playlist and device management, and the internal administration dashboard for users, servers, devices, billing, feedback, support and application releases.
A CRM platform I built for real-estate teams. Each customer record brings together contact details, call history, notes, reminders and property requirements, with CSV contact imports and direct call, message and email actions.
The wider system includes request tracking, customer groups, calendars and Google account synchronisation, public digital business cards and property-related calculators. Development is archived because support for the project ended.
My role: I designed and built the full Laravel platform — from the database and customer workflows to the administration interface, permissions, calendar synchronisation, imports, public business pages and deployment.
These projects can be opened and tried directly. They show some of the decision-making, data and integration work behind the larger systems.
A decision-support application based on the Analytic Hierarchy Process. One practical use is structured candidate selection, where criteria such as experience, technical ability and communication can be weighted before applicants are compared. The same workflow can be reused for many decisions involving competing priorities. Users can review results, save previous decisions and open detailed calculations through a QR workflow.
My role: I designed, developed and maintain the mobile application and Laravel API, including Google and Apple sign-in, result storage, QR-to-web results, deployment and both store releases.
A grocery-deal platform that imports current Coles and Woolworths specials, keeps price history and supports product search, categories, saved items and weekly deal emails. I built it to make frequently changing retailer data simpler to search and revisit.
My role: I designed and built the full application, including retailer import APIs, price-history storage, search, saved-item workflows, scheduled deal emails, frontend and deployment.
I care less about collecting technologies and more about understanding what needs to be built, choosing tools that suit the job, and knowing how the finished system works.
I started programming at university with Visual Basic and then C#. Later I found PHP, which changed my direction. I kept learning through real projects, moving into Laravel, JavaScript, APIs, React and React Native as the work required it.
I do not claim to know every tool. When a project needs something unfamiliar, I learn it, work through the problem and make sure I can maintain what I build.
Most of the things I build begin with a process that is too slow, fragmented or difficult to follow. I try to understand the people, data and decisions behind it before choosing the technical approach.
I prefer steady improvements, clear responsibilities and systems that can be understood and maintained after the first release. Modern tools help me work faster, but I remain responsible for the decisions, the code and the finished result.
If you want to talk about a project, a software or IT role, something you have built, or a system you want to improve, send me a message.
I read the messages myself.