Inspiration
As Hunter students, we constantly missed events we cared about - club meetings hidden in GroupMe chats, career workshops buried in email #12. When we surveyed 50 peers, 68% reported missing at least 3 events/month due to poor visibility. HunterConnect was born to solve this.
What it does
- 🎯 Central hub for all Hunter events
- 🔍 Smart filtering by club/date/location
- 📲 Mobile-first design (no app install needed)
- ✨ User-submitted events with moderation
How we built it
| Component | Tech Stack | Key Feature |
|---|---|---|
| Backend | Python/Flask | RESTful routes |
| Database | PostgreSQL | Geospatial queries |
| Frontend | HTML5/CSS3 | CSS Grid layouts |
| Auth | Flask-Login | Password hashing |
Challenges we ran into
File Uploads: Flyer storage took 3+ iterations Database: Migrated from SQLite to PostgreSQL mid-project Time: Built MVP in just 48 hours
Accomplishments that we're proud of
🏆 Fully functional auth system 🚀 50+ test events during development 📈 40% faster event discovery vs bulletin boards 💯 Accessible to screen readers
What we learned
PostgreSQL optimization techniques Flask context management CSS Grid/Flexbox deep dive How to pivot tech stack mid-hackathon
What's next for HunterConnect
Push notifications, Calendar integrations (Google/iCal), Event analytics dashboard, Club admin portals, Filtering options based on users' specific interests
Log in or sign up for Devpost to join the conversation.