SyncUp: Plan Events. Split Expenses.
Why I Joined the 2025 DeveloperWeek Hackathon
I participated in the 2025 DeveloperWeek Hackathon as both a designer and Product Manager. Why would a designer join a hackathon meant for devs?
Designing. Use it or loose it! – Being out of work for a while, I wanted to dive back into design and challenge my creative skills. I hadn't used that part of my brain for a while outside of my portfolio, and stepping away from the job search to just enjoy designing is a good reminder of why I loved design to begin with.
Connect with my roots. Development. – I sought to connect with developers in the Bay Area and gain insights into the most valued skills in this competitive market. Previously being a developer lets me understand technology. But the industry has always moved quickly and connecting with devs is a great way to know where technology is headed and what people are excited to build and explore in this next phase of the tech industry
Challenging Myself – This two-week hackathon required both design and development to be completed within a tight timeline, testing my design abilities, communication skills, and planning efficiency with an engineering team. I've been working solo for many months now and working with a team allowed me to flex my muscles and ignite a collaborative spirit.
So... what did I actually create?
Identifying the Problem
The Challenge: Event Planning & Expense Management
Planning events with friends can be frustrating due to misaligned information and cost distribution. People often struggle to keep track of details, coordinate expenses, and maintain smooth communication.
The Solution: SyncUp
A unified platform that enables users to:
Access event details in one place
Message others about event logistics
Track and split expenses seamlessly
My Role: Product Manager & Designer
Team Members
Strallia Chao: Frontend Lead
Stéphane Nyobe: Backend Lead
Michael Pereira :Design Critique & Testing
Aashritha Machiraju: Developer
Hackathon Requirements
To qualify, our project needed to:
Be a web-based application
Solve a real-world problem
Involve some level of data management
Feature Planning
After initial brainstorming, we asked: "How do we stand out in a saturated market?"
To answer this, I conducted a competitive analysis, identifying standout features from existing applications. We saw an opportunity to integrate expense management, event recommendations, and messaging in a way no other app had done before.
Competitive Analysis Breakdown
Designing with Devs
Establishing User Flows and Database Structure
I started with user flows and sketches, ensuring that key interactions were clear for both frontend and backend teams. These flows informed how the backend would structure data.
After discussions with Stéphane Nyobe, we determined that the system required six interconnected databases to support the app's functionality.
Database Diagram Created by Stephane Nyobe
Wireframing and Prototyping
With foundational flows in place, I quickly transitioned to wireframing and prototyping in Figma, working asynchronously with Strallia Chao on frontend implementation.
Mid Fidelity Designs
In parallel, I collaborated with Michael Pereira to conduct design critiques, identifying flaws in logic, flow, and edge cases.
Image of notes and potential changes to make for one aspect of product during critique session.
Iterating Based on Development Constraints
Design Doesn’t Always Translate
Once Strallia implemented early wireframes, we found that some designs were too cramped and raised accessibility concerns. I revised the layouts to improve spacing and usability.
Overcoming Technical Challenges
Twilio API Integration
We wanted to use Twilio to send email notifications about unpaid expenses, but integrating and troubleshooting a third-party service within our short timeline proved difficult.
Database Connection Issues
As we refined the app, we encountered unexpected database connection errors. Debugging these highlighted the importance of managing complex database relationships effectively and something to consider when building scalable designs and design systems.
Reflection
This hackathon was a valuable experience, allowing me to:
Hone my design and product management skills under time constraints
Improve my ability to work cross-functionally with engineers
Adapt quickly to unforeseen design and technical challenges
SyncUp addressed a real problem, and while our final product didn't win any awards, it was a testament to effective collaboration and rapid iteration. It served as a reminder of why I love designing technology.