Nifty idea, but it needs to export to .ics or some other widely accepted calendar format. Also, have you considered implementing this as a Facebook app? That's where most of my non-work event invitations show up. Also, it looks like you could do the functionality client-side in Javascript, which would reduce server load at scale. Still, though, definitely a step forward for people who work block schedules.

Awesome stuff. I've added the calendar format to the list of features.

A very neat, useful application.

I second some of the other feedback here (saving details, better labelling of on or off days, .ics export).

One extra feature you might want to add: ability to check a date in the future without having to scroll through the calendar months. So, in your wedding example, I could put in my shift details, the start date, and the date I'm checking, and it would tell me whether I'm free or not.

That was my original intention, but we designed for the general case instead of the specific. I think we will add this in eventually.

I see. I wouldn't consider it a priority request. And don't get me wrong: I think the site's functionality at the moment is great: quick, simple, straightforward. I've already emailed it to the three people I know who work shifts :-)

Link: http://shiftfrog.com

Great name and looks useful. Make it work on any mobile phone and it will be really useful. On my Samsung S8300, the submit button is invisible.

On the calendar, you should clearly label on and off days. It's not immediately obvious.

Your site mentions you've developed an algorithm. What does it do apart from adding days and accounting for holidays? :-)

It does the same on my HPtouchpad. We'll be fixing that.

We have that on our todo list.

Honestly, nothing else yet. The designer put the text in there. Trust me my algo is nothing like developing an algo for netflix recommendation or google search.

You don't need clever algos to make something useful. I just wanted to know if there was something non-obvious I was missing.

This is very cool, I love the idea, and the implementaion is great too.

My only comments are:

It should save what you enter, eg: I put 4 days on, 4 days off, and while it did show the right shift info, the fields reverted to 4 days on, 3 days off.

The date field would benefit from a date picker.

Out of interest, how (if at all) are you planning to make money from it?

I worked with a designer on this and the project had a few goals, but the last of them was to make money.

1. I wanted to learn ruby + sinatra. This was just to see what I could build acting as the programmer + sys admin.

2. The designer and I both want to work together on bigger and bigger projects. This was a test to see if we could work together well and not hate each other at the end.

So there never was any plan to make money off of it. If you have any suggestions I'd be open to them.