Inspiration
I thought that despite having a lot of friends I love, I wasn't seeing many of them as much as I would want to. This led me to question why this was. What I landed on was that one part of it was the difficulty of making plans together, putting something together.
What it does
I created Hango to make it easier to find events I would love to attend with my mates. It aggregates all the events in Sydney, gives personal recommendations on what to do, shows which other friends would enjoy attending it, and comes with a full itinerary builder with a sharable webview, so your friends don't even have to own the app to join your plans!
How we built it
Acquire event from sources/deduplicate/enrich via LLM etc. It's all kept in a Supabase database. Expo (react-native) is used for the front end to use one codebase for both iOS and Android.
Challenges we ran into
- Deduplication was a pickle, since events can be under be different names at different places, but be the same thing (and other semantic duplicates that only become obvious after further processing etc.)
- Frontend can always be finnicky, react native isn't as cross platform as you'd like.
Accomplishments that we're proud of
- The whole thing! Jokes aside, I get really happy every time someone tells me they went to an event they wouldn't've otherwise attended without Hango.
What we learned
The whole stack essentially. From Oauth to what Supabase was, how to use cloud, what a deduplication pipeline looks like, challenges of cross-platform development etc.
What's next for Hango
Hopefully a wider adoption base in Sydney, as well as rapid iteration through actual user feedback. It's easy to keep something you put in a lot of effort into close to your chest for fear of failure, but we must put it out there, and if needed kill our darlings as feedback suggests.
Built With
- expo.io
- firebase
- gcp
- llms
- posthog
- python
- react-native
- sentry
- supabase


Log in or sign up for Devpost to join the conversation.