Industry
Operations
Case Study
Greenland Komarov Management
Field work was coordinated through calls, spreadsheets, and photos in camera rolls. I built a full monorepo platform with a manager web app, a worker mobile app, and a dedicated API that gives each role the workflow it actually needs.
Project Overview
Greenland Komarov coordinates people, locations, equipment, chemicals, tasks, deadlines, and photo evidence across field work. Phone calls and spreadsheets made current status difficult to see and finished-work documentation difficult to recover.
I designed and built the current system as a Bun and Turborepo monorepo with dedicated web, mobile, API, and documentation applications.
A web-and-mobile operations platform with separate manager and worker experiences, a dedicated API, role-based access, task evidence, and push reminders.
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
- Hono
- React Native
- Expo
- PostgreSQL
The Challenge
Managers plan work across projects and people. Workers need a focused list of what comes next. Treating those roles as one interface with hidden buttons produces a compromised experience and increases permission risk.
Operational proof must also remain attached to the task, user, and time it belongs to instead of disappearing into private message threads or camera rolls.
Approach
I split the product into role-specific clients over one typed backend. Better Auth sessions and service-level guards enforce organization and role boundaries, while Hono services own business rules for projects, tasks, workers, managers, resources, images, feedback, notifications, and audits.
The current monorepo replaces earlier standalone Supabase prototypes with a dedicated API and shared packages, giving web and mobile clients one active architecture.
The Solution
Managers use a Next.js web application to coordinate projects, assignments, task items, deadlines, workers, equipment, chemicals, usage records, images, and feedback. Workers use an Expo mobile app with focused task flows, authentication, image submission, and push notifications.
A Hono API uses Drizzle and PostgreSQL for data, Better Auth for authentication, Expo Server SDK for push delivery, and node-cron for deadline reminders. Uploaded images are currently written to the server upload directory with metadata stored in the database, not to Supabase Storage. Password resets use emailed codes and revoke existing sessions after completion.
Key Challenges
-
enforcing genuinely different manager and worker capabilities over shared operational data
-
tying images, materials, equipment, and feedback to the correct task lifecycle
-
keeping web and mobile clients synchronized through one typed API
-
delivering reminders and password recovery without weakening session security
The Outcome
The platform replaces fragmented coordination with one operational model. Managers can see ownership, status, resources, and evidence; workers get a focused mobile view of assigned work and reminders.
Moving from the earlier Supabase prototype to a dedicated Hono and PostgreSQL backend also made authentication, permissions, scheduled work, notifications, and audit behavior explicit in one service layer.
Context
The most important product decision remains the role split: shared data underneath, purpose-built manager and worker experiences on top.
Related case studies
Other projects with related architecture decisions, platforms, or product challenges.
Client Operations Workspace
An in-development operations platform that unifies client records, documents, deadlines, durable workflows, and human-reviewed AI assistance.
TypeScript · Next.js · Hono · tRPC · PostgreSQL
View case study →Noema
A private, offline personal media library for books, podcasts, audiobooks, structured reading progress, and knowledge capture.
TypeScript · React Native · Expo · TinyBase · SQLite
View case study →