Inspiration
LoboLoop came from conversations with contractors and field-service businesses. The same problems kept appearing: schedules in one place, certificates somewhere else, equipment tracked separately, and workers relying on calls, texts, and paper to understand what they need for each job.
I wanted to build something that goes beyond basic task management. Before a worker is sent to a job, the system should be able to check whether they are available, properly qualified, and equipped to complete it safely.
What it does
LoboLoop connects the back office with workers and supervisors in the field.
Managers can create and schedule tasks, assign workers and equipment, define qualification requirements, request documents, and monitor work from the back-office application.
Workers can use the mobile app to receive tasks, upload requested documents, complete checklists, capture photos, signatures, GPS information, and hours, and continue working when there is no internet connection.
LoboLoop also supports worker availability, scheduling-conflict detection, certificates and expiry tracking, assets and maintenance, sites, forms, notifications, weather-related workflows, and QR-based public forms.
How we built it
LoboLoop is built across three connected applications:
A Java and Spring Boot backend A React and TypeScript back-office application A React Native mobile application for workers and supervisors
During Build Week, I used Codex with GPT-5.6 across all three codebases. It helped me inspect the existing architecture, implement end-to-end workflows, debug integrations, refactor code, and coordinate changes across the backend, web, and mobile applications.
Rather than generating isolated screens, I used Codex to work through complete workflows. A change to worker eligibility, for example, could require updates to database models, backend validation, APIs, back-office warnings, and mobile behaviour.
Challenges we ran into
The largest challenge was time. I discovered Build Week only shortly before the deadline, while LoboLoop already covered multiple applications, native mobile functionality, offline behaviour, and cloud integrations.
Other challenges included:
Coordinating changes across three repositories Keeping web and mobile behaviour consistent Handling offline data and synchronization Validating schedules, qualifications, documents, and equipment together Preparing a clear product demo in under three minutes Sharing enough of the project for judging without exposing production credentials or private AWS infrastructure Documenting local setup for a multi-tenant system that does not yet include an automated clean-database tenant bootstrap
Accomplishments that we're proud of
I am proud that the submission demonstrates a real workflow across the complete system instead of a collection of disconnected prototypes.
The back office, backend, and mobile application work together to manage worker qualifications, equipment eligibility, document requests and approvals, task execution, and offline field activity.
I am also proud of how much progress Build Week created. The deadline pushed me to connect workflows, improve reliability, refactor existing code, prepare the repositories, and turn a complex product into a focused 2-minute-and-59-second demonstration.
What we learned
Learned how much I don't know about video editing, I'm also learning everyday about how contractors work since its not a field I'm familiar with.
What's next for Loboloop
I still have a long way to go in order to have a product that is really competitive in the marketing, I do think AI can level the Odds for a solo dev like me, trying to take on entire companies.
Log in or sign up for Devpost to join the conversation.