Industry
Operations
Case Study
Greenland Komarov Management
The field team ran on phone calls and photos sitting in camera rolls. Managers couldn't see what was finished. Workers didn't know the plan until someone called. I built the whole platform from scratch — web for managers, mobile for workers. The team opens it every morning.
Project Overview
Greenland Komarov's field team ran on phone calls and spreadsheets. Managers couldn't see what was done. Workers didn't know their plan until someone called. Proof of finished work lived in camera rolls. I designed and developed a workforce and task management platform from scratch for their internal operations.
Personal project for a real client. Authentication, task scheduling, push notifications, photo uploads, and project tracking — all on Supabase and Expo. The team uses it daily.
Workforce and task management platform for internal business operations, with role-based experiences for managers and workers.
Services
- UX/UI Design
- Web Development
- Product Strategy
Key Deliverables
- Responsive Design
- Custom Development
- User Experience Improvements
Platform Type
Web & Mobile Platform
Tech Stack
- TypeScript
- Next.js
- React Native
- Expo
- Supabase
- i18n
The Challenge
A manager in an office and a worker on a building site don't think about work the same way. One plans projects and assigns tasks. The other needs today's list and the next address. Putting both in the same app with different buttons doesn't work — they need different experiences that share data.
Photo proof of completed work was getting lost in text messages. Nobody could review it later. Nobody could tie it to a specific task.
Approach
Two role-based experiences, one database. Web for managers: assign tasks, schedule work, see who's available, review photo reports, track projects. Mobile for workers: today's numbered list, building locations, start and finish buttons, push notifications, camera built into the task.
Supabase for auth, data, and photo storage. Multiple languages because the team isn't monolingual. I defined the architecture, business workflows, and UX independently.
The Solution
Managers assign work with a person, description, location, and deadline. They review submitted before/after photos with timestamps and approve or send back. Project tracking shows what's in progress across the team.
Workers open the app in the morning, see their day in order, get push reminders, go to each job, mark it done, take photos as part of finishing — not as a separate chore they'll forget.
Managers think in projects. Workers think in "what's next." The app respects both.
Key Challenges
-
two genuinely different experiences with different permissions — not one app with role toggles
-
photos tied to task completion so documentation doesn't get skipped after the work is already done
-
push notifications that actually get workers to open the app in the morning
-
multiple languages without breaking layouts on small phone screens
The Outcome
Phone-and-spreadsheet chaos replaced by one system. Managers see status. Workers see their day. Photos attach to tasks instead of disappearing in camera rolls.
The real team uses it every day. Portfolio images are placeholders — I'm not putting actual job site photos on a public site.
Context
Personal project, real client, real daily use. The biggest decision was splitting manager and worker into separate experiences. Same data underneath, completely different screens and permissions on top.