Crafting experience...
6/12/2026
Built At
Progress x GitNation
Hosted By
GitNation
Talks & workshops by core teams and top engineers.
What is the problem you are trying to solve? Who does it affect?
The main problem is that people at conferences and hackathons often do not make the best decisions based on their actual goals. They may want to meet founders, recruiters, developers, investors, or people working on similar ideas, but the event schedule usually does not help them choose where to go or who to talk to.
Networking is also stressful and random. Attendees often do not know who else is attending, what their background is, what they are looking for, or whether they are relevant. This means people waste time approaching random people, miss better connections, get rejected, or do not know how to start a useful conversation.
This affects students, developers, founders, recruiters, speakers, investors, and anyone attending a conference or hackathon who wants to make the most out of it.
Idea Explanation
My idea is a conference co-pilot platform that helps attendees create a personalized agenda and connect with the right people at the right time.
Users can build their own agenda based on their goals, interests, and preferences. The platform then connects their agenda with other people attending the event and uses AI to suggest the best people to meet.
The AI can show why someone is a good match, what their background is, when both people are free, and what to say to start the conversation. It also helps the person being approached because they can know who wants to meet them and why, making networking less awkward for both sides
I built the project as a solo hacker, so I focused on creating a clear frontend flow that shows how the product would work in real life.
The app starts with a signup/onboarding page. The user enters basic details like their name, email, username, ticket number, and LinkedIn profile. The idea is that LinkedIn can be used to understand the user’s background, skills, interests, and professional goals.
After that, the user can go to the events page. This page shows recommended events and all available events. Users can filter the events and add the ones they like to their own agenda.
The agenda page stores the user’s selected events and helps them organize their day. This is important because the meet-and-greet feature connects with the agenda instead of working separately.
The meet-and-greet page lets users find AI-based matches. The matching system uses the user’s goals, event choices, profile, and availability to suggest people they should meet. Each suggested match can include their profile, why they are a good match, possible conversation starters, and an option to say hello or find free time.
In a full version, the frontend would make requests to a backend. The backend would handle user accounts, event data, AI matching, agenda updates, and meeting suggestions. The database would store users, event information, selected agenda items, attendee profiles, and match results.
So the frontend is what the user interacts with, the backend handles the logic, the AI helps with recommendations and matching, and the database stores all the important information
One of the biggest challenges was deciding what the main focus of the project should be. At first, there were many possible features, like AI pages, event pages, planner tools, filters, and networking tools. It was easy for the idea to become too big and messy.I overcame this by narrowing the project down to the most important flow: helping the user build their own agenda and then using that agenda to suggest the best networking opportunities.
Another challenge was making the app feel useful instead of just looking nice. A conference app should not only display information. It should help the user make better decisions. So I focused on how the event planner and meet-and-greet system could work together.
Since I worked alone, I also had to manage everything myself, including the idea, design, frontend structure, and user flow. That was challenging, but it also helped me understand the whole product properly.
I accomplished a strong product idea with a real problem and a clear user flow. The project is not just another event schedule app. It is a smarter conference assistant that helps people plan their time and make better connections.
I created the structure for the main pages, including signup, events, agenda, and meet-and-greet. I also developed the main logic of the product: users choose events, build their agenda, and then receive AI-based networking suggestions based on their goals and timing.
I learned how important it is to simplify an idea. A product does not become better just by adding more features. It becomes better when every feature actually helps the user.
What are the next steps for your project? How can you improve it?
The next step would be to connect the frontend to a real backend and database, so user profiles, event data, agendas, and matches can be stored properly.I would also improve the AI matching system by using LinkedIn data, attendee profiles, user goals, event attendance, and calendar availability. This would make the recommendations more accurate and personal.
Another important next step would be calendar integration. The app should be able to compare two users’ agendas and suggest the best free time for them to meet. I would also add better profile summaries, smarter conversation starters, and a system for users to send connection requests or say hello directly inside the app.
In the future, this could become a complete conference networking platform for hackathons, tech conferences, startup events, and professional networking events. The bigger goal is to help people stop wasting time at events and actually meet the right people, attend the right sessions, and leave with real opportunities.