Case study · Monster Tree Service

Tree crews,one app.

A field-operations app for a tree-care company of ISA and Utility Certified Arborists: crews pick up tasks, assign work, track equipment and log maintenance from one login, designed for iOS and Android.

iOS & Android appField operationsTask & equipment management
Monster Tree Service screenMonster Tree Service screen
What we shipped
Task boardJob photos & commentsEquipment registerMaintenance logTeam assignmentiOS & Android
01 — The product

Built for the crew, not the back office

Field work does not happen at a desk, so the app is designed phone-first around the three things a crew actually touches: the tasks they own, the equipment they run, and the record of who did what. Everything opens two taps from the home screen.

A task board at the centre

The home screen is a live task list with All-tasks and My-tasks views, a status on every card and a filter, so a worker sees exactly what is theirs today.

Equipment that carries its own history

Each asset holds its category, service dates, hours, documentation and a running maintenance log, so a machine's story travels with it instead of living in someone's memory.

Comments and history on every job

Task detail keeps a threaded comment feed and a full change history, so an update from the field is captured against the work rather than lost in a text message.

02 — The problem

Why does a tree-service crew need its own app?

Tree work is dispersed, physical and equipment-heavy. The information a crew needs is exactly the information a desktop back office loses: what is assigned right now, whether a machine is due for service, and what happened on site.

Three things follow from that: the job happens on a truck or in a canopy, not at a desk; equipment cannot quietly lapse out of service; and with crews split across sites, accountability has to stay legible on every task.

100

screens across the full design — every empty, filled and error state included.

03 — Goals & challenges

What the app had to get right for a crew in the field

A phone in a gloved hand, on a truck or under a canopy — the whole design starts from that constraint.

Goals

Two taps from the truck

  • Open two taps from home — the task board, a job, or the equipment register.
  • Assign and prioritise — an assignee and a due date set before work starts.
  • Track equipment properly — service dates, hours, documentation and a maintenance log.
  • Keep every update on record — job photos, comments and a full change history.
Challenges

Why it was hard

  • The whole experience has to work one-handed, in the field, not at a workstation.
  • Grinders, lifts and saws need scheduled service tracked without a spreadsheet nobody opens.
  • With crews split across sites, ownership of a task has to be legible at a glance.
  • The full design runs to well over a hundred screens, including every empty, filled and error state.
04 — How a job moves

How does a job move through the app?

The app follows the real shape of field work: someone raises and assigns a job, a crew member works it on site, and it is closed with a record attached.

  1. 01Dispatch

    Raise and assign

    A task is created with a due date, priority and an assignee pulled from the crew, so ownership is set before the work starts.

  2. 02Crew

    Work it on site

    The assignee opens the job from their My-tasks view, sees the linked equipment and description, and adds photos and comments as the work happens.

  3. 03Record

    Close with a record

    The status moves to complete and the change history and equipment maintenance log keep a durable record of what was done.

05 — On the phone

What does the app look like in the hand?

These are the real screens, drawn phone-first. The flow runs from login to a task board, into a job with its photos and comments, and across to the equipment register.

Sign in
App preview
01 • Sign in

A branded login with password reset and verification, so a crew member is one tap from their day.

Task board
App preview
02 • Tasks

All tasks and My tasks, each card carrying a status, due date and assignee, with a filter to narrow the list.

Task detail
App preview
03 • Detail

Status, priority, due date, linked equipment, job photos and a comment-and-history feed on one screen.

New task
App preview
04 • Create

A new job is raised with an assignee, due date and priority in a single guided form.

Equipment
App preview
05 • Equipment

The asset register at a glance, ready to open into a machine's full record.

Maintenance
App preview
06 • Maintenance

Category, service dates, hours, documentation, associated components and a full maintenance log.

06 — Visual design

What does the app look like, and why?

A single warm coral is reserved for the primary action on every screen, so a gloved thumb always knows where to tap. Ink and a calm grey scale carry the dense task and equipment data, and a green frames the brand around the tree-service identity.

Colour
Action coral
#F06543
Forest ink
#16321E
Text ink
#111827
Muted grey
#6B7280
Placeholder grey
#9CA3AF
Surface
#F3F4F6
White
#FFFFFF
Typography
Screen title · 700Task board
Section heading · 600Equipment detail
Card title · 600Raise and assign
Body · 400The assignee opens the job from their My-tasks view.
Caption · 500ASSIGNEE · DUE DATE · PRIORITY
FAQ

Building a field-service mobile app

What does a field-service app like Monster Tree's do?
It gives a dispersed crew one signed-in place to run the day: a task board with statuses, due dates and assignees; a task detail with priority, linked equipment, job photos, comments and history; and an equipment register that tracks service dates, hours, documentation and a maintenance log. It replaces the clipboard, spreadsheet and group chat that field teams usually stitch together.
Why build it as a mobile app rather than a website?
Because the work happens away from a desk. Tasks are picked up on a truck or under a canopy, so the whole experience is designed phone-first for iOS and Android, with large tap targets, a clear primary action and screens that open two taps from home. A desktop tool would simply not be where the crew is.
How long does it take to build a field-operations app like this?
A first release covering authentication, a task board, task detail with comments, and an equipment register with maintenance logs is typically a multi-week build across design and two platforms. The full design here runs to well over a hundred screens including every empty, filled and error state. Shanti Infosoft scopes it on a short call and returns a fixed quote.
Does the app track equipment maintenance?
Yes, and that is one of its strongest features. Every asset carries a category, service dates, hours utilised, documentation such as manuals and warranties, associated components and a running maintenance log. For an equipment-heavy trade like tree care, that record travelling with the machine is what keeps grinders, lifts and saws from quietly falling out of service.
Can more than one crew member work the same jobs?
Yes. Tasks are assigned from a crew list, each job shows its assignee and priority, and the comment-and-history feed records every update. A worker can filter to My-tasks to see only what is theirs, while a lead can view all tasks across the team, so accountability stays legible even with crews split across sites.
Let's build

Have field crews running on clipboards and group chats?

Tell us how your business actually works and we'll tell you honestly what it takes to build — the task board, the equipment log, the lot. No deck, no pitch.