Hibernating Projects

Can a web service be seasonal and remain relevant?

That’s what I’m going to find out.

I’ve been running Get Biked for just over a year now. It’s been great. 2014 had a beautiful biking season and Get Biked saw lots of bikes finding themselves good homes.

But things are cooling down, both in the city and on Get Biked. During the summer, there were between five and twelve new bikes listed each week. These days there’s usually between one and two bikes listed each week. So what happens now? I see a few options:

  • I could continue to send a weekly email with existing listings (but risk annoying emails without much content)
  • I could send an email only weeks when a bike is listed on the site (but lose the regularity that Get Biked is known for)
  • I could put Get Biked to sleep for a few months (but be forgotten forever)

I’ll be turning the Get Biked site off for a few months starting in mid-November.

What does that mean?

No new bikes will be added to the site and the weekly email will be put on hold. I plan on starting the service again in mid-April, 2015, when things start warming up in NYC.

What will happen over the winter?

This allows the Get Biked service to get a few updates over the winter, gives me time to think about where I’d like to take the service, and to relaunch in the spring which will hopefully bring more publicity than a continuous service would.

In a web where “out of sight, out of mind” is the name of the game, I do worry that bringing Get Biked back in the spring will be harder than it was to launch it. I’ll be sure to report back once the 2015 version of the site has launched to compare the initial launch against the re-launch. I’m curious to see the results.

Got a bike to sell?

The last Get Biked email of 2014 will go out on November 25. If you have a bike you've been meaning to sell, submit it this week!

I’m all ears

Got any suggestions or features you’d like to see in the next version of Get Biked? Send me an email and let me know!