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 web for managers and 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 built an app the team actually opens every morning.
Personal project for a real client. The team uses it daily.
App for a field operations team, managers assign work on web, workers plan their day and send photo proof from mobile.
Services
- UX/UI Design
- Web Development
- Product Strategy
- Mobile Development
Key Deliverables
- Responsive Design
- Custom Development
- User Experience Improvements
Platform Type
Mobile Application
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 apps 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 experiences, one database. Web for managers: assign tasks, see who's available, review photo reports. Mobile for workers: today's numbered list, building locations, start and finish buttons, camera built into the task so they photograph before and after while the job context is right there.
Supabase for auth, data, and photo storage. Multiple languages because the team isn't monolingual.
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.
Workers open the app in the morning, see their day in order, 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 apps, not one app with role toggles, managers and workers have nothing in common in how they use it
-
photos tied to task completion so documentation doesn't get skipped after the work is already done
-
multiple languages without breaking layouts on small phone screens
-
replacing phone calls and spreadsheets with something the team would open without being forced to
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 on top. They don't share a mental model. The app shouldn't pretend they do.