Pudding, changing taste buds

I'm almost done with my original vision for Pudding. I've literally got some server config to do, and another night's worth of code tweaking.

I've been thinking a lot about what Pudding does, how it does it, who it's competitor's are, and how they work.

Pudding is built around the simple idea of a design group and a client organization. The design group can see all the projects, and "clients" can only see projects that are associated with their "client organization". Only people in the design group can upload, and only people in the client organization can click the "approve" button.

I had a pretty rigid workflow in my head when I made these decisions. But after a lot of thought, and trying to demonstrate Pudding to people, I'm starting to think it's too brittle.

Design projects, teams, and the work they're doing are more fluid and unpredictable.

I was planning on launching in the next day or three.

This sounds crazy, but I want to take the time now to loosen up the app a bit. I've got some ideas and I think I'll have to make some data-model changes. I'd hate to launch it and have to make these changes with people already signed up.

I'm hoping I can implement what I'm thinking of in less than 5 working sessions. That means Pudding can still launch before the end of the month.

Wish me luck! :)