🚀 Version 0.6.8 — Stability, Deployments & Backend Improvements

This update is mostly behind the scenes, but it’s a big one. The focus here was to make the first steps towards stability, scalanility and soother consistent workflow down the line. As I had touched on in my last post it was time to move on from Replit.

⚡ Stronger, More Reliable Deployments

• The backend (API) is now properly packaged so it runs consistently on Vercel
• No matter how the project is structured, the system knows how to find and run the API
• All API routes now go through a single, clean pathway
• Added a simple /api/health check so we can quickly confirm everything is working
• Fixed edge cases that previously caused random deployment failures. (Mostly typescript bundling issues) 👉 Result: Deployments are now much more predictable and far less likely to break.

🩺 Better Database Stability & Reliability

• The app now has multiple ways to connect to the database if one fails
• Improved handling for serverless environments
• Reduced chances of connection issues during high traffic
• Added tools to quickly check database health and diagnose problems
• Improved security settings for production connections 👉 Result: Fewer database errors, better performance, and easier debugging.

💻 Improved Local Development

• Fixed environment setup issues (cross-env)
• Local development now behaves much closer to the live production app
• API requests are properly routed when running locally 👉 Result: Less “it works locally but breaks in production” problems.

🧩 Cleaner, Safer Codebase

• Improved type safety across the app (helps prevent hidden bugs)
• Better alignment between frontend and backend data handling
• Cleaned up core systems like API calls and shared logic
• Improved error handling so issues don’t silently fail 👉 Result: More stable features and fewer unexpected bugs.

📚 Better Dev Tools & Standards

• Added internal guides for working with the database (performance + security)
• Standardized development structure across the project
• Locked important configs to prevent accidental breakage 👉 Result: Easier to build, easier to maintain, and easier to scale.

🫡 Closing

This is once again not a super flashy update, more than one that I feel NEEDED to happen. DB is now running through Supabase and deployment is running through Vercel. The platform is now more stable, deployments are more reliable, and the foundation is much stronger. This is the kind of work that hopefully makes everything else faster and smoother moving forward.

On a personal note to everyone, sry for not being around basically at all this past month. Prepping for a big move across the country and have been super busy with the family recently. Love and miss you guys!

Hey guys, this post probably isn't going to be as "glamorous" as many of the other posts. lol. Been jumping back in a lot to the biz dev side of things and holy S**t my world got rocked for a bit. Its been a while since I've touched any of those considerations, so much of my focus went towards foundational development and getting the idea to be functionally visible that I somehow completely separated myself from the other side of the coin.

Lots and lots of research more than actually putting pen to paper this past month. I'm probably exhausting myself in more directions than necessary but a lot has hit the table that is making me want to get this to market. I'm very much the kind of person who has no idea what I'm doing in the world of tech and to that extreme I tend to over think and unknowingly probably overcompensate on issues that would be better off put to a "down the line" kind of situation...

Ok, enough rambling. I've got some strong considerations of onboarding but i want to make sure its all done appropriately and where everything is at right now, I think I can set the business and the dev up for a slightly better situation. So I've been auditing the codebase multiple ways using multiple agents. Claude, Gemini, GPT... This is all at this point been standard practice, but I've really been doing my best to comprehend the issues that have been coming up and it has been, "fun".

Once I feel like I'm at a comfortable point working with what I'm familiar with, coderabbit, and maybe a few other tools will work their way into the process. The two that Ive been spending most of my time learning is Sentry.io and posthog. Event tracking is something I think is absolutely necessary especially considering that the entirety of this dev cycle has been vibe coded. Yes, get a capable dev on the team, but I'm more than positive that at this point it would take months to understand everything that has been built more or less to clean up what isn't "correct" or just outright "ai slop". Posthog and Sentry should give me a considerable amount of feedback on issues to know what "NEEDS" to be tackled first.

Replit, where ive been hosting everything and running the database has taken another incredibly large step in the wrong direction in my opinion. They are no longer granting access to files on Replit and are doing everything they can to separate themselves from any form of a somewhat competent developer. Actively doing what I can to part ways from the platform, sadly.

Considerations of what to do with funding has taken a rather large portion of the time that I have to contribute currently to Resonant. I've got a rather large move for myself and the family on the horizon that will be taking us across the US in less than 6 months. Huge opportunity for myself and for Resonant. Everything from tech stabilizing, legal and compliance related stuff, insurance overheads, runway considerations... The funding has been a huge win and also a massive stressor. Luckily I am still at a point where nothing has to happen right now and I have a decent amount of time to strategize how that will all play out.

All things considered this month has had a years worth of ups and downs. Well not necessarily downs more than a welp, guess I gotta work more and a lot harder kinda position. Definitely not complaining. I am more than numbers can count to committed to realizing Resonant, no bump in the road is gonna knock this pony off its course. Patience is a virtue and time is a commitment. Looking forward to telling you guys some exciting news in the next update or two.. or three.. lol, it'll get there. Lmfao. Baby steps in the right direction.

Version 0.6.6 — Event Promotions, Ticket Transfers & Major UI Overhaul

Hey everyone 👋 Been trying to push myself a lot recently to get this to launch ASAP! I've got 2 more venues committed to the platform and have inadvertently started Friends & Family funding 🥳 Funding is set to close at $100,000 in the form of 10 SAFEs. Ill make sure to include some pics of the SAFE so you guys can get a glimpse of how I'm going about it.

This release is a large-scale improvement across event management, ticket ownership, mobile responsiveness, and overall UI structure. A lot of components were refactored to improve long-term maintainability while introducing two major systems: Event Promotions and Ticket Transfers.

🎪 Event Management & Promotion System

🔧 Event Management Refactor

• Major overhaul of the Event Management component with improved structure and expanded functionality
• Better event statistics display and tracking
• Cleaner social link handling and image URL exclusions
• More stable state management and filtering logic

📢 Event Promotion System (NEW)

• New Event Promotion Dialog allowing venues to promote events from outside of the network
• Configurable promotion radius: 25, 50, or 100 miles
• Flexible duration selection (auto-expires on event date)
• Automatic cost calculation based on radius + duration
• Dedicated promotion tracking in database with status + expiration monitoring

This introduces a monetization layer while giving venues more visibility control over their events.

🎫 Ticket Transfer System (NEW)

🔄 Ticket Transfer Manager

• Full interface for managing incoming and outgoing transfers
• Accept, decline, cancel, or let transfers expire
• Support for both free transfers and paid ticket sales
• Real-time transfer status updates

🛡️ Secure Transfer Infrastructure

• Token-based validation system
• Transfer expiration logic
• Payment integration for paid transfers
• Full transfer history tracking

This adds real ownership flexibility to tickets while keeping transfers secure and trackable.

📱 Mobile Responsiveness & Layout Improvements

• This update significantly improves mobile usability:
• Prevented layout stretching beyond viewport width
• Improved tab navigation and menu toggles
• Better responsive grid handling across events and profile sections

Overall result: cleaner layouts, fewer broken sections, and much better small-screen usability.

📋 Booking & Contract System Enhancements

• Several core booking components were refactored:
• Improved booking management workflows
• Updated contract proposal dialog and viewer
• Improved availability checker logic These changes focus on stability, clarity, and better UX during high-friction workflows.

🏗️ Major Component Refactoring

Large structural improvements across:

• Profile page
• Venue about editor
• EPK tab
• Discover page
• Event page
• Stats tab
• Sidebar navigation
• Merch store
• Event cards
• Create event dialog

These refactors improve readability, maintainability, and long-term scalability of the codebase.

🛣️ Server & API Expansion

• Major expansion of API routes
• New endpoints for promotions and ticket transfers
• Enhanced notification integration

🎨 Styling & Design System

• Significant CSS refactoring
• Improved design system consistency
• Enhanced dark mode and light mode design
• Stronger responsive design patterns across components

📊 Summary

• 60 files changed
• ~9,900+ insertions / ~3,700+ deletions
• 2 major new systems (Event Promotions + Ticket Transfers)
• Extensive mobile + layout improvements
• Large-scale component refactoring

🧠 Why This Matters

This release strengthens both the business side (event promotion + ticket ownership flexibility) and the user experience side (mobile stability + layout consistency). It’s one of the heavier infrastructure updates, but it makes the platform feel more complete, scalable, and production-ready.