Business systems
Portals, quality control, CRM, staff workflows, dashboards and reporting built around the way a business actually works.
I build mobile apps, business systems, APIs and websites. Some are public products and some are private tools built around how a business actually works. I like keeping things simple, useful and easy to understand.
I normally start by understanding what people are doing now, what is taking too much time, and what the software actually needs to make easier.
Portals, quality control, CRM, staff workflows, dashboards and reporting built around the way a business actually works.
iOS, Android and TV applications, including the backend, APIs, admin tools and publishing work behind them.
Laravel applications, websites, APIs, databases, admin systems and integrations that connect the pieces together.
I also like taking something that already works, finding the slow or annoying parts and improving it step by step.
Some projects are public. Some were built privately for a specific business need. The private ones are shown without client or company names.
A business receives parts from overseas that need to be checked before they can be accepted. I built a system where staff can open each job, see the item, reference photos and what needs to be checked, then record whether each item passed or has an issue.
The system keeps the inspection history and tracks how much work each operator has completed. Management can review operator performance, completed jobs and yearly results. The company sending the parts has its own dashboard showing passed items, failed items and reports.
A mobile support platform for Rett syndrome families and carers. The project includes the mobile application, Laravel API, administration system, authentication, family information, documents, emergency information, therapies, research and multilingual content.
I work on both sides of the project — the application people use and the systems behind it that manage the data.
One of my earlier larger mobile projects. I built the APIs behind the application as well as the systems used to manage playlists and devices. Users can manage their playlists through the web side and sync them with their devices.
This project was built before AI became part of my development workflow, and a lot of what I learned about APIs, mobile applications and backend communication came from building and maintaining systems like this.
A CRM platform I built for real-estate teams in Turkey. Agents could record phone calls, keep notes about who they contacted and what they were selling, organise follow-ups and use an agenda to keep track of the people they needed to contact again.
The system also included engagement tools and could create a portfolio website from the properties and information already stored in the platform. Development stopped when support for the project ended, but it remains an important project because it brought CRM, follow-up tools, property data and websites together in one system.
These are easier to open and try directly. They also show a different side of the work I like doing.
A decision-making app for comparing options more clearly using the Analytic Hierarchy Process. The goal is simple: break a difficult choice into smaller comparisons.
A Melbourne train app made to check train times and service information more directly. I built it because I wanted something simple for daily use.
A web project for checking supermarket specials and comparing prices. It came from a simple idea: make weekly shopping information easier to use.
I am not trying to know every language or framework. I care more about understanding what needs to be built and getting it working properly.
I started programming at university with Visual Basic and then C#. Later I discovered PHP and that changed the direction for me. I kept improving with PHP, Laravel, JavaScript and jQuery, and over time moved into React and React Native as well.
I do not try to hold on to every language just because I used it before. If I need something for a project, I learn it, work through the problem and keep improving it.
Most of the things I build start the same way: there is a problem, something takes too much time, or the software does not quite fit what people are trying to do. I enjoy working out how it should work and then building it.
These days I use AI where it helps me work faster, check ideas or get through repetitive work. The tools have changed, but understanding the problem and making the decisions still matters.
If you want to talk about a project, a software or IT role, something you have built, or something you want to improve, send me a message.
I read the messages myself.