GoLomba

Students often find competitions through separate social posts and chat groups. GoLomba brought discovery and organizer publishing into one MVP so participants could browse opportunities from a shared catalog.

Problem

Competition information arrives in different formats and channels. Students need dates, categories, requirements, and organizer details before they can decide whether to enter. Organizers need a place to publish the same core fields.

Role and scope

I contributed to the frontend within the team. We did not keep a feature-level ownership log, so I describe the team build and avoid sole-owner claims.

Process and decisions

The MVP joined two paths: a participant browses competition records, while an organizer submits a new opportunity. The frontend presented both paths and connected them to the team backend.

The team treated GoLomba as an MVP, which kept the scope around discovery and posting instead of a full competition-management system.

MVP output

The team finished a React and Vite frontend connected to a Go service. The MVP covers opportunity publishing, catalog browsing, competition details, and the registration path.

We did not track active users, published competitions, successful registrations, or usability tests after the bootcamp.

Limits

The project lacks a role breakdown, research notes, and release report. I would need commit attribution and a user test before presenting it as more than a bootcamp MVP.