I've been vibe coding apps for the last 10 months almost daily, at least according to my GitHub activity.

But May 1 will be my first big test.

In addition to everything else, I also run a software development conference called Stir Trek here in Columbus, OH. This will be the 17th year for the event, and the first time we will have an app for attendees.

For a team of 10 volunteers, building a cross-platform app with all of the data and capabilities necessary to serve 1,600+ attendees was just too much to take on. Until now.

This weekend, I'll be building a complete app, from start to finish, that provides the following capabilities:

• Full schedule view, with "build your schedule" capability.

• Speaker photos, names, and bios linked to their talks.

• Sponsor listings, with links to their websites.

• Dynamic polling throughout the event.

• Session review capabilities, for speaker feedback.

• Venue map (the event is held in a large movie theater)

• Emergency Reporting

I want to spend a little time talking about the emergency reporting feature, because I believe this is the most important one. There are some important issues, like audio/visual problems, that are useful to know about as they're happening. You don't want to wait for people to complain after a session, you want to fix it immediately.

But any time you gather a few thousand humans together, there's the potential for bad behavior. Harrassment. Aggression. Frustration. We want a way for our attendees to feel safe, to feel heard, to feel like they have a team of people listening and ready to help if they're uncomfortable.

This emergency reporting line is there for anyone, that needs anything during our event. Help. Guidance. Assistance. Safety. Medical Attention.

This has to work. It has to work reliably. It has to work reliably every single time.

May 1st is my first true test with vibe coding.