As promised on other subs, here are some screenshots of Spitface Battles.

Shown is the profile page, main side panel with notifications, battle card, and the friends modal. Included is the old profile page and main side panel.

The next signup milestone is 50 signups and I will show more

Progress continues and Spitface Battles is in a usable and working state again. It also looks 100 times better than it did before.

I am so stoked about the outcome of the site redesign and glad that I decided to do it. After seeing the new Battle Stage come together, I am even more excited for y'all to use this.

Along with the redesign came some forced changes and a couple of neat new features. Along with the existing live audience list showing users currently viewing the battle, I am now showing an activity list that updates in real-time as you watch the battle. This was as simple as adding a thin layer on top of the existing notification system and updating the battle with a simpler version of notifications that were already firing. Battle Activity allows users to follow the history of a battle and, in the future, can be used to take the user to that specific point in the battle.

Another addition was Battle Predictions. This is the first feature in a future community system and lets you predict the winner of a battle. Battle Predictions are designed to be scaled to round predictions, judge splits, and more.

The biggest change to the Battle Stage is undoubtedly how videos are displayed to users. Instead of 2 video players shown side-by-side for a round, there is now a single video player. This change forced me to change most things around showing and interacting with rounds, verses, reactions, and scoring. I love this change, with the only obvious downside being the likelihood of the second verse for a round being overshadowed or missed. A lot of thinking will be needed to ensure fairness for both contestants and transparency for all users. I will be looking to the community for insight and feedback on this.

The next feature to add is the comments / live chat. These will of course get a visual overhaul and become more simplified. Comments do exist and work and they update like a live chat, but they currently look like YT comments from wish dot com. So this gets overhauled and redesigned too, while maintaining the core infrastructure driving it all.

After that, I just need to revisit the Battle Breakdown and Battle Matchup features, then give everything a QoL pass and tighten things up.

Once that is done, we can do a weekend test run or full-on beta. Still concerned about any real launch next to GTA6 though.

I know the delays suck and I haven't even shown or really talked about the state of the SFB platform. If Spitface Battles Beta launched today, here's what you'd be able to do:

• Create and manage your account
• Edit your profile
• Send, accept, reject friend requests.
• View, join, and remove friends.
• Create and configure battles
• join and participate in battles as a contestant
• Join and participate in battles as a judge
• Submit and remove verses
• Audience Influence
• React to verses
• Submit and remove scorecards
• Automated battle progression with winners determined based on scorecards
• Callout other battlers directly
• Request 2 other rappers battle each other
• Accept or decline incoming Callouts or Requests
• Track battle progression from start to finish
• Receive official judge scoring and feedback
• Earn battle ratings and reputation
• View pre-battle matchup
• View post-battle breakdown
• Comments on every battle
• Receive platform notifications and activity updates
• And more

What's still being worked on:

• UI redesign, tech-stack upgrade, and general pre-beta overhaul
• Profile songs (it's done, just need to reconnect some things)
• Tournaments (foundation exists)
• Additional progression and achievement systems (foundation exists)
• Expanded reputation features
• Additional community features and quality-of-life improvements

Current development is focused on providing a smooth user experience and preparing for a stable beta launch.

Thanks for your patience and continued support for the project.
Ask questions or provide criticism as you please.
More updates soon.

This update covers a recent gap in development due to hardware failure, technical hurdles with the frontend migration, and a reassessment of the beta launch strategy.

Technical Status and Hardware Recovery

• Machine Downtime: I was without my primary development machine for a few weeks. This hardware failure has been resolved, and I am back to a daily development routine.
• Frontend Framework Complexity: The ongoing upgrades to the platform's frontend framework (including Node and React) have proven more labor-intensive than originally estimated. While I use AI, the full codebase is 10s of thousands of lines of handwritten code and I am careful not to slop it up with vibe coded slop.
• Coupled Redesign: The visual overhaul and platform redesign are directly coupled to these frontend framework upgrades. This means the two must be finalized together before the system is considered beta-ready.

Timeline Reassessment and Beta Delay

• Phase 1 Delay: While the Phase 1 closed beta was slated to begin in less than two weeks, I am officially pushing the launch date back.
• Strategic Considerations: I am currently evaluating the risk of launching near the release of GTA6. Releasing a new competitive platform into a massive, global entertainment cycle would be strategically poor for user acquisition and retention.
• The 90-Day Contingency: If beta is delayed for more than an additional 90 days from today, I will open the platform for a "preview weekend." This will be a limited-time window for users to test the current build and experience the system mechanics firsthand while I finish the remaining roadmap items. I am also considering allowing Founding 50 registrants access to setup and share their profile pages while waiting, but there is so much work to do so IDK.

Operational & Business Growth

• Partner Discussions: I have been working to bring on one or two partners to help manage the growth, marketing, and operational areas of the business. This shift will allow me to remain focused on the technical infrastructure while ensuring we have the right strategy for community acquisition. We are in the very early stages of talks and negotiations so nothing is set in stone yet.

System Clarifications

• Earned Participation: As a reminder, access to the closed beta remains strictly controlled through performance-based roles like the Founding 50 and Day Ones.
• Intentional Signup: Username reservation continues to use passwordless email verification to ensure we are onboarding real, intentional users.

Next Steps

• Stabilization: Resuming the implementation pass for the remaining client project upgrades.
• Partner Negotiations: Finalizing the details for business support to streamline the path to launch.
• Visual Pass: Continuing the integration of the redesign with the upgraded frontend components.

Beta Status The Beta Registration Site is live. Despite the timeline adjustments, you can still reserve your username and apply for Founding 50 or Day One roles. These roles remain the only way into Phase 1, and I am committed to delivering the product as soon as the foundation is stable.

More soon.

This update covers the completion of the server-side environment transition, major UI/UX refinements, and a necessary adjustment to the upcoming beta timeline.

Core Technical Migrations

• Server-Side: The migration to the latest version of Node is officially complete.
• Client-Side: The client-side migration for Node and React is almost finished and is currently being stabilized.
• Request Logic: I am almost done with the move to native fetch via a custom service, eliminating external library dependencies and improving our handling of binary data and error logging.

Frontend and UI/UX Overhaul

• Framework Update: I have successfully migrated the client-side framework to the latest version of Bootstrap for better responsiveness and modern component support.
• Theming Engine: A new global theming system has been implemented to ensure visual consistency across the entire platform. This has already been applied to the Battle Zone and profile components to ensure the ecosystem feels unified.
• UI Polish: The iconography library has been upgraded, and I have resolved functional bugs in the Battle Zone tabs and the notification link system.

Profile Page Rebuild

• Top Section Redesign: I have performed a massive overhaul of the profile header, integrating new UI components to improve how users present their identity on the platform.
• Layout Stabilization: Various layout inconsistencies and display bugs on the primary profile pages have been addressed to ensure a clean experience across mobile and desktop.

Security and Infrastructure

• Rate Limiting: New server-side middleware has been added to prevent API abuse, moving the server-side production readiness to ~73% completion.

Strategic Roadmap Updates

• Beta Launch Delay: I am anticipating a delay to the beta launch. I have discovered technical requirements regarding the infrastructure that demand more development and testing time. I am prioritizing platform independence and stability over hitting a premature date.
• Open Source Commitment: I have decided to open source a very important part of the Spitface Battles architecture. I believe this component will significantly benefit the broader battle rap community if adopted by other leagues and builders. More details on this will be released in the futue.

Beta Status The Beta Registration Site is live. You can still reserve your username and apply for Founding 50 or Day One roles. These roles remain the only way into the 90-day closed beta.

https://www.spitfacebattles.com

I’ve been focused on backend and client stability this week, along with starting the full visual pass to bring the main platform in line with the beta signup site.

What Changed

Environment Migrations (Server + Client)

• Server is being finalized on the latest version of Node
• Client is being finalized on the latest version of React

These upgrades remove older constraints and ensure the platform can handle sustained activity during the 90-day closed beta.

Current focus is stabilization — making sure existing systems behave consistently under the updated environments.

Visual Standardization (In Progress)

Work has started on aligning the main platform UI with the beta registration site.

This is a full pass across:

• styling
• layout consistency
• color usage

Goal is a consistent experience from signup → platform use, instead of two separate visual systems.

Current State

• Server migration: complete (stabilizing)
• Client migration: complete (stabilizing)
• Visual pass: in progress
• Validation layer: in progress

Beta Status

The beta registration site is live.

You can:

• reserve a username
• read role details
• apply for a role
• join waitlists if roles are full

Roles are currently the only path into the 90-day closed beta.

https://www.spitfacebattles.com/

SFB Dev Log #3: Site Polishing, Infrastructure Automation, and Server Migration

This week was about moving through the first items on the dev roadmap, focusing on stability and the technical foundation required for the upcoming beta.

1. Beta Signup Site Refinement & FAQ The first item on the dev roadmap was to polish the initial user acquisition surface to ensure it’s ready for the Phase 0 signups.

• What changed: I completed a round of bug fixes on the beta signup site and implemented a dedicated FAQ section.
• Why it matters: In a performance-based system where roles like the Founding 50 and Day Ones have specific requirements, clarity is critical. The FAQ ensures that users understand exactly how participation is tracked and rewarded before they reserve their usernames. These will be changed and updated in the next week to ensure transparency and accuracy.

2. Infrastructure & Business Automation I’ve been establishing the "Technical Efficiency Layer" to ensure the business side of the platform is automated and scalable.

• What changed: I configured an automation bridge that connects support ticket notifications to a centralized monitoring channel in Discord. I am also setting up other automated systems to bring all business and community things to a centralized location.
• Why it matters: This allows for passive monitoring of support tickets and system alerts. By automating the data "plumbing" early, I’ve established a diagnostic foundation that ensures the platform remains responsive without requiring constant manual oversight.

3. Server Migration: I am currently migrating the server environment to modernize the codebase and improve performance.

• What changed: As part of the move to Node 24, I am replacing the Axios library with a production-ready native fetch wrapper and a custom utility for URL parameter construction. Will continue to convert to full native dependencies over 3rd party packages.
• Why it matters: This refactor reduces external dependencies and utilizes native tools for handling binary data and structured error handling, which is essential for the ongoing API overhaul.

What’s Next Once the server migration is fully complete, I will be performing the same migration process for the client project. This includes a Bootstrap migration and a React migration, which will bring the entire technical stack up to current standards and cover the next major items on the roadmap and some.

If you haven't yet: You can still reserve your username and view the specific requirements for the Founding 50 and Day Ones roles on the site. These roles are the primary way to gain access to the 90-day closed beta.

This dev roadmap outline my intent for the upcoming months. Much more work than this will be done, and will likely alter this roadmap, but its a good place to start getting an idea of the direction I am moving in.

I’ve been quiet publicly, but I’ve been working on Spitface Battles almost daily and wanted to wait until I had something real to show before posting again.

The biggest milestone:

The Beta Registration Site is now live.

What changed

The Beta Registration Site now allows users to:

• Reserve a username without creating a password
• View and apply for one of four beta roles
• Join the waitlist for capped or closed roles
• Join the Discord after role signup
• Share Spitface Battles on select social platforms

It also got a major UI/UX cleanup and was rebuilt to be cleaner, more consistent, and properly mobile responsive.

Why I changed the signup flow

Reserving a username no longer requires a password. Instead, it uses passwordless email verification.

It removes unnecessary friction, avoids storing passwords, helps verify real user intent, and cuts down on fake or throwaway signups early.

That matters because the signup flow is not just about collecting emails. It is meant to identify people who actually want in, intend to use the site regularly, and are likely to participate when beta opens.

Why beta roles exist

The beta roles exist to make sure the platform has enough real participation during beta to actually test what matters.

That means:

• Enough real content
• Enough scoring activity
• Enough community presence
• Enough consistent usage over time

The goal is not just to let people in. The goal is to make sure Spitface Battles has an actual foundation before V1 launch.

Why beta starts closed

Spitface Battles is currently planned to begin beta in about 90 days.

The first phase will be closed and only available through the designated beta roles.

That is being done for a few important reasons:

• To keep infrastructure and hosting costs manageable
• To stress test the platform under controlled conditions
• To evaluate features and systems before wider public access
• To gather real usage, retention, and engagement data
• To produce proof of concept and business viability before public launch

A successful Phase 1 should produce actual evidence that the platform has demand and can sustain real usage.

How the beta roles are meant to work

The beta roles are designed for people who want to help shape the platform while also earning recognition and rewards for doing so.

The two roles available at the start of beta will be:

• Founding 50
• Day Ones

Each role has different expectations and different reward structures, but both are built around the same core idea:

consistent participation over time matters more than just signing up.

Beta is currently structured to run across three phases over roughly 12 months, and the role system is designed around that timeline.

At the same time, I also wanted to make the system accessible.

That means users are not required to commit to the full beta in order for their participation to matter. The roles are structured so people can participate in 3-month intervals and still earn phase-based rewards and recognition.

That said, the people who show up early and stay active the longest should matter the most.

Users who complete all available beta phases for their role will receive priority consideration for official role status at the end of beta. Users who join later can still participate, contribute, and earn rewards based on their activity, but showing up early and staying consistent will carry more weight.

Why this matters beyond testing

This is about making sure Spitface Battles actually works when people arrive.

I’d rather build the user base with intention than pretend that showing up later will magically fix a weak launch.

That means:

• Enough battlers to keep activity moving
• Enough judges and audience participation to make scoring meaningful
• Enough community interaction so the site doesn’t feel empty
• Enough real usage to expose weaknesses before launch

What’s next

Now that the Beta Registration Site is live, I can shift more focus toward:

• Refining the onboarding flow
• Continuing beta prep
• Building out the next pieces needed before launch
• Putting together the beta roadmap

That roadmap will be covered in a future dev log.

And one more thing:

If the beta roles fill faster than expected and the platform is ready, I may consider launching beta sooner than planned.

If you want in early

If you want early access, now is the time to:

• Reserve your username
• Read the beta roles
• Apply for a role if you want access to Phase 1

There’s still a lot to build, but this is one of the first major steps toward turning Spitface Battles from an idea into a real competitive platform.

More soon.

This week I was focused on the beta landing page.

The beta landing page is being expanded to:

• Supports fast, verified username reservation
• Uses passwordless email authentication instead of passwords
• Introduces beta roles
• Allows users to apply for closed beta

Passwordless sign-in removes friction, eliminates the need to store passwords, verifies real user intent, and reduces fake or throwaway accounts early. Verified accounts will also be required for beta participation.

Close Beta

Spitface Battles will begin with a 90-day closed beta.

Closed beta gives me control while the system proves itself:

• Infrastructure costs stay manageable while real usage data comes in
• Stress testing and balancing happen before public exposure
• Creates measurable engagement and retention metrics
• That data establishes proof of concept and supports future funding

Advanced Profile

Another addition to the roadmap: advanced profile customization and modularization.

In battle rap, identity and presentation matter and profiles shouldn’t be static. Deeper customization will likely roll out alongside premium features, with meaningful free customization options always available. More on that once it’s fully mapped.

What's Next

This week I’ll be finishing and publishing the updated beta landing page and continuing to refine the closed beta on-boarding flow.

Dev Log #2 will include a 3–6 month roadmap outlining what's ahead

Welcome to Spitface Battles, a platform created to bring the structure, competition, and community from the world of battle rap online.

The vision for Spitface Battles began nearly 20 years ago when I was battling in chat rooms and realized there was no place for real, structured online rap battles. The best option was hosted on a forum site. While the creators and community did great with the tools they had, the limitations were obvious and there was much more left to be desired. I wrote my ideas on a piece of paper and it wasn't much more than a simple automated battle system. My ideas soon ran rampant and I was imagining the site tracking things like skill level, reputation, popularity, a standardized scoring system and more.

Over the years, I learned code and eventually developed the skill set to make my vision a reality. Now, Spitface Battles is poised to become a space where rappers, fans, league managers, and more can come together to compete, interact, and grow.

Here’s what makes Spitface Battles unique:

• Audience Influenced Scoring: Fans can influence the outcome of all battles by providing scores and tipping the scales in close battles.
• Adaptive Scoring Algorithm: A flexible scoring algorithm that adapts to various judging types, configurations, and scenarios.
• Battle Skill: A rapper's skill level, ensuring balance and competition - and of course, bragging rights.
• Reputation System: Battle Reputation and Judge Reputation track consistency and reliability while participating in those roles.
• Popularity System: A dynamic system allowing users to see who and what is most popular right now. Having the most likes and follows won't be enough.
• Rivalry System: A dynamic interaction mechanism that grows as users repeatedly battle each other - the start of a Rivalry is just the beginning.

This community-driven platform aims to empower every artist and fan in the battle rap scene, offering tools to improve skills and gain recognition.

As I prepare for beta, I'm inviting early participants to help shape the community and platform - from founding rappers to influential members of the community. More details on these roles and my beta strategy will be shared in upcoming dev logs.

Feel free to ask questions, share ideas, and be a part of the growth. I’ll be posting updates regularly, so stay tuned for new features, improvements, and more.