Show HN: Chalkboard, a better way to plan/spec software projects
chalkboardhq.com
chalkboardhq.com
After registering, I see the value. 10 years ago, I used to have to plan websites by mocking up each page, printing them out, and taping them all up onto a giant wall with post-it notes explaining what the user can do on each page. This was the only way that management could really visualize and understand what changes we were making. This allows you to do that without the wall, and the collaboration is a nice addition. It's also a great way to look back and see how a project came to light. I often jot down these sorts of notes when planning a web app.
I recommend you reconsider being so inspired by 37signals that it's hard to tell your site apart from theirs. I think I'm being kind in how I'm describing this to you. It's very confusing for any user who is familiar with 37signals and it makes your product less trustworthy.
The design of this website isn't really that cool, it's more (like you said) a standard SaaS website, as we're still validating our assumptions regarding our solution to the problem with an MVP.
PS.
I was struck by the same feeling. The layout, the -hq suffix, the big sign-up button, the scroll, the minimalism, the friendly phrase, and not to mention "the product" (collaboration), AND THE PRICING (149$) :) worth building on other's market study.
Chalkboard is a project my partner Abi and I started several months ago. Chalkboard is a collaborative tool for laying out software features, user stories, and screens in a way that is organized and communicative. Abi worked in web consulting with remote teams and wanted a tool that let him easily define project requirements with clients then hand the project off to designers/developers.
Chalkboard lets you quickly define software features / user stories and then create step-by-step user flows for them. User flows are linked up to application screens that you specify and can upload mockups for.
A lot of people have suggested we integrate/tie into Balsamiq. We have been talking about this since day one but have hesitated reaching out to them until we are 100% sure that this app can become a useful product.
ETA: Sorry, I didn't read the error message. It's a 404, not a 500. Reproducible every time I try to create a project.
My first impression is that it's a flow chart in the form of an outline. The outline looks like something I could just as easily type into any text editor. Why not make it a visual flow chart?
We actually started out by displaying user flows as flow charts... we quickly realized that flow charts are an inefficient way to display a comprehensive batch of sequential user actions and application flows. It IS easier to type outlines in a text editor than mess around with flow charts.
We transferred that realization to this web app.
Our user actions are linked to application screens, which gives you a good overview of how your user interacts with your application.
The page you were looking for doesn't exist.
2. On my 13" the screenshots are too big, then I have the chat widget overlaying on top.