Gaming-Grade Performance for SaaS: The Superthread Origin Story

From 'Small Fish' to Game Engine Architect

My journey started over 25 years ago. I’ve been a programmer all my life, though the last decade has been spent leading teams and making high-level architectural decisions.

About 16 years ago, I found myself working for a massive multinational. The people were great, but the environment was pure politics. You could achieve something monumental, but unless you played the political game, you were just a small fish in a huge tank.

The iPhone and the 'Miracle' of HTML5

Then, the iPhone changed everything. It wasn't just a phone; it was a real computer with a desktop-class browser. Before this, mobile browsers were basically static text. But the iPhone brought HTML5, which allowed us to push pixels and run native-feeling applications directly in the browser.

I was obsessed. I started experimenting with a game called World of States and realized that browser graphics were hardware-accelerated. It was miraculous. I pivoted to building an HTML5 and JavaScript game engine, a powerful, cross-platform tool that could run on anything from a laptop to a phone.

Lessons from the High-Performance Trenches

Being in the engine space was tough, especially with giants like Unity in the mix, so we pivoted to becoming a game studio. Our final project, Forces of Freedom, was a 5v5 real-time multiplayer mobile shooter.

This was 'hard mode' for technology:

• Authoritative Servers: The world ran on the server so players couldn't hack their devices to cheat.

• The 17ms Rule: We were pushing 300,000 to 500,000 triangles every 17 milliseconds on an iPhone 5 from 2012.

• Networking Chaos: We had to make real-time combat smooth over unstable 3G and 4G connections.

Building games at that level teaches you one thing: Polish is everything. If it isn't delightful and perfectly responsive, it won't succeed.

The 'Famous Big Tracker' Crisis

After a career break, I took a PM role at a 200-person startup-turned-scaleup. This was my first time using the 'famous' enterprise issue tracker and documentation tool.

I was horrified. The interface was clunky. The speed was abysmal, pages would load in three seconds one minute and six seconds the next. It was clearly built on an ancient tech stack.

When I asked my team why they used it, the answer was depressing: 'We hate it, but we have to use it because there isn't a 'power tool' alternative that does what this does.'

The Birth of Superthread: Speed, Delight, Flexibility

That was the spark. I realized I could bring the gaming experience, where every pixel matters and speed is the absolute essence, into the SaaS world. I built a prototype, and it felt right.

I quit my job to build Superthread on three main pillars:

1. Lightning Speed

If we can render 500k triangles on a 2012 phone in 17ms, you shouldn't have to wait 6 seconds for a ticket to load. Speed isn't just a feature; it’s a requirement.

2. Pure Delight

We’re moving away from 'clunky and austere' enterprise vibes. We want Superthread to be a place you want to be. We’re obsessed with the details because that’s how you build a product that people actually love.

3. Total Flexibility

Most tools try to tell you how to run your company. We believe only you can decide how to organize your team. Superthread is designed to be a tool you can craft to suit your organization, not the other way around.

Experience a workspace built for speed.

Stop waiting for your tools and start shipping. Sign up for Superthread

Further Reading & Resources

• The Anti-Bloat Philosophy: Why we prioritize speed over complex features.

• Superthread vs. Jira: Why teams are switching to a faster, cleaner alternative.