LockerPulse is Getting Close…

LockerPulse Splash Logo

We’re only a few weeks away from the launch of LockerPulse, our new venture that I introduced back in February. Assuming all goes to plan, we’ll be live on Wednesday, May 12.

I haven’t really done an update in a while, but the project is coming along great. We’ve been using the final product internally for a few weeks now and I can honestly say that it has completely changed the way I consume sports, which is exactly what I was shooting for. I don’t bother opening up my Google Reader for sports news (I unsubscribed from all of my sports feeds) and I don’t bother visiting ESPN.com anymore because I get everything I need in my LockerPulse account.

None of this guarantees business success, but we did build something where we are our own target market. We scratched our own itch, which certainly has it’s advantages.

Um, so what exactly does it do?

Following sports news for your favorite teams can be overwhelming. Most people I know just have a bunch of bookmarks of their favorite sites that they check. RSS makes that so much more efficient, and so much more enjoyable. Problem is, the only people I know who actually use RSS to combine all of the national news (ESPN, Yahoo Sports, etc), blogs, and newspapers are web developers like myself.

LockerPulse is a RSS aggregator for the average sports fan who has no clue what RSS is. You visit the site, click your team, and all of the stories are available to read in an interface that is similar (but a little better in my opinion) to Google Reader.

That’s free, with updates for each team every 15 minutes, and will be supported by an ad platform that we are developing. The ad platform is a large part of the plan, but it’s not close to being ready so we’re launching without it (more on this below).

A premium account, which will cost $3.99/month with a 30 day free trial will give the user the following features:

  • The ability to read all of their teams in one “news stream”, with complete control to drill through by team/source, and subscribe/unsubscribe permanently from each individual news source.
  • Access to a live scoreboard of every game that’s currently taking place. The user’s teams scores show on an overlay across the bottom of every page.
  • AJAX updates of their news and scores – you just leave your browser open and the news flows in and the score overlay updates (this is my favorite feature, it’s so awesome)
  • A slick mobile site optimized for smartphones to read news and check scores on their phone.
  • A bunch more little features like a daily newsletter, but that’s the big stuff.

I realize that all of this is a bit abstract.  It sort of needs to be seen and used to appreciate it.

What’s our launch plan?

The plan isn’t very sexy, but it’s one that I think will work.

We’re going to do a “public beta that we’re not calling a beta” for a few months and then go from there. What does that mean? We’re going to be giving out free lifetime premium accounts to a bunch of people we know (friends, their friends, family, people we know in the web business and sports business), we’re going to be testing a micro social media campaign to gauge it’s effectiveness (we think Twitter is maybe our best marketing opportunity), we’re going to be soliciting feedback and collecting data, and then we’re going to go from there. We have a laundry list of things that we want to do, but none of that matters if the first 50 people that try it think it sucks.

This is an app on a level that I haven’t built before, so it’s important to make sure we didn’t royally screw anything up before going too crazy. Right now it looks like we’ll be adding 50k – 75k stories per month to our database. There’s a lot that goes into making that work efficiently.

It’s something we all believe in, and we’re lucky enough not to need any money from it, so we’re taking a long-term patient approach (which coincidentally might be the best approach regardless of how fast we want it to succeed…you can only speed things up so fast regardless of how much $ you invest in something).

Meanwhile, we’ll be working on our ad platform and tweaking things, and we’ll slowly but surely start increasing our marketing efforts as time goes on. I hope that the ad platform is done by late Summer, but I won’t launch it until it’s so good that people actually enjoy the ads (I know it sounds crazy, but I think we can do it).

What’s Left?

Just some quality control work, reviewing our sources for each team, and writing some of the content like the about page, terms of service, and all that fun stuff. Nothing too major.

You never quite know how good of a site or business you’re building until it’s actually launched, but I can safely say that this is the best web site we’ve ever built. And everything else we’ve done has been met with some level of success (mostly correlating to our effort put in to it), so I’m really really optimistic about the long term potential of this one.

13 comments on LockerPulse is Getting Close…

  1. Adam,

    Very cool. I’m looking forward to checking it out. I totally agree with scratching your own itch. It doesn’t guarantee commercial success but does insure the passion that is needed.

    • Adam McFarland says:

      Thanks Scott. That’s a great way of saying it – being your own target market ensures that you have the passion needed for the venture.

  2. Thanks for the update Adam. I’ve been following this for a while as you know, and I look forward to seeing the product that you’ve worked so hard to make happen. Based on what I’ve seen so far out of you and the rest of the guys, it should be very good.

  3. Adam – Can’t wait to see it in action. Please send me a beta link once you launch

    • Adam McFarland says:

      Don’t worry Anthony, you’re definitely on my list 🙂 Looking forward to getting your opinion as both a developer and a hardcore Mets fan.

  4. Dale Ting says:

    Looking forward to it Adam! The fact it scratches your own itch makes me feel like it’ll be great…

  5. Rob says:

    Sounds epic. I think the launch style you’ve got planned is a great way of testing everything with people whose opinions you value and not overloading the system. What’s likely to be the biggest headache with scaling? The database access, the bandwidth, support, or something else?

    Anyway, I’ll keep my fingers crossed for you – can’t wait to see it!

    • Adam McFarland says:

      Hmm, the biggest headache. From my limited experience, when a site gets an unexpected boost of traffic, the first thing to go is the database. Too many inefficient queries running at once. I’ve had it happen a few times (once with DI and once with Music Alerts), so with LockerPulse I spent a ton of time optimizing queries and doing other things to speed up performance and minimize the resources being used. I’m still somewhat of a novice on this stuff, but I’ve been reading about it like crazy for the past few months and I do have some experience, so I think we’ll be OK for a while. We’ll see though. If we have problems, they will be good problems to have 🙂

  6. Are you using MVC yet? 😉
    I have absolutely no idea how I’d build anything scalable or easily agile without it
    http://bakery.cakephp.org/articles/view/announcing-cakephp-1-3-0-stable

    • Adam McFarland says:

      Yea when we re-built DI I built my own MVC framework for our sites. I spent a lot of time researching and developing that last year…this has been more of a focus on query optimization, better database design, caching frequently accessed content, and all of the many many things recommended by YSlow http://developer.yahoo.com/performance/rules.html Not to say that the finished product is perfect, but at least we’re considering things that we hadn’t before. I also have a book on advanced MySQL sitting on my desk that I haven’t gotten to yet…hopefully sometime after launch.

  7. […] environment before. It has been a little worse than I had expected, but then again I wrote this just before launch: We’re going to do a “public beta that we’re not calling a beta” for a few months and then […]

  8. […] the site that we’re going to start aggressively marketing (i.e. taking it out of our “public beta that we’re not calling a beta“). Exciting times […]

Leave a Reply

Your email address will not be published. Required fields are marked *

Commenting Rules

I'm honored that you found this post interesting enough to leave a comment. Before posting, I have a few ground rules:

  • Please keep your comments as relevant to the post as possible.
  • No personal attacks or any other nastiness.
  • Your first comment is subject to my approval.

Thanks!