Arshia Lashgari
← Work03 / 03

garden-ops

GardenOps

Role I designed and developed GardenOps end-to-end, covering product architecture, data modeling, application logic, native Apple UI development, persistence, accounting calculations, invoice workflows, synchronization, testing, debugging, and reliability improvements. I was responsible for translating real operational requirements into a maintainable application architecture and for solving complex state-management and multi-device data consistency issues.Year 2026
GardenOps dashboard showing interventions, financial summaries and operational activity.

Overview

In brief

GardenOps transforms the operational workflow of a small gardening or landscaping business into a structured digital system. The application centralizes customer management, interventions, employee work tracking, costs, invoices, payments, and profitability while keeping the experience optimized for iPhone and iPad.

A major engineering focus was reliable local data management and multi-device synchronization. The application uses SwiftData for persistence and a custom local Wi-Fi synchronization system based on snapshots, stable identifiers, timestamps, and conflict-aware merging.

Context

Project context

The project was created to solve the operational complexity of managing a gardening business where customer information, completed jobs, employee hours, expenses, invoices, and payments can otherwise become fragmented ac

SOLUTION

One Workspace for Operations, Accounting, and Field Work

Section body
GardenOps brings the core operations of a gardening business into one native application.

The system allows users to manage customers and interventions, record collaborator work, track expenses and materials, create invoices, register payments, and review the financial performance of the business.

Instead of treating these functions as separate modules, GardenOps connects operational activity directly to its financial impact. Labor entries affect collaborator costs, expenses contribute to the real cost of each intervention, and customer payments remain clearly separated from employee compensation.

This creates a single, structured workflow where operational and financial data remain connected from the moment a job is created through invoicing, payment, and profitability analysis.

The result is a system designed around the real workflow of the business rather than a collection of disconnected administrative tools.

Result

Outcome and impact

GardenOps became a complete operational management application capable of handling clients, jobs, collaborators, labor costs, business expenses, invoices, payments, and profitability.

The application includes persistent invoice drafts, recovery after application interruption, safe local Wi-Fi synchronization between devices, and financial calculations that distinguish employee costs, customer payments, expenses, and owner profit.

The most recent reliability work successfully passed 43 automated tests and simulator builds, with physical multi-device validation remaining as the final synchronization verification step.

A concrete project

Have a similar problem to solve?

Discuss your project