Hackathon Event App

Tight deadlines

This wasn’t a “nice to have later” project. The app had to be ready for a specific Hackathon date. No delays, no extensions, no extra hands joining midway. At the same time, it still had to work well on both platforms.

Solution

Our team picked what actually mattered for the event and ignored the rest. Some ideas were dropped early. Others were simplified. That’s how the app made it to release on time.

‍

Features kept changing midway

What looked like a clear plan at the start didn’t last. As the event took shape, new ideas kept popping up. Some made sense, some didn’t, but all of them competed for time and attention.

Solution

Instead of freezing the scope, the team treated it as a moving target. We checked ideas quickly inside the team, kept the useful ones, and quietly let go of the rest without turning it into a big process.

‍

Our design was just too cool (for real)

The first versions of the UI looked great on screens. In code, though, some animations, transitions, and screen logic started to pile up and made things harder than expected.

Solution

Design and development met halfway. Together, we reworked some aspects and simplified others. The goal was to keep the feeling of the design without breaking the app.

‍

The complexity of the NFT idea

The team wanted to make the Hackathon feel more memorable, so participants received personalized NFT rewards after the event. The idea worked well for engagement, but it also introduced extra complexity around wallets, external platforms, and onboarding users unfamiliar with NFTs.

Solution

The team didn’t try to hide the complexity. They walked users through it step by step. First, we created accounts outside the app and then manually assigned the NFTs. Everything worked well during the event.