Who is the target market for what you are describing though (or for divshot for that matter)? Is it meant to be for slightly less technical people? Is it meant to take over all development/developers in the future?
Being a seasoned developer, front, middle and back end, I find this an interesting product, but something that I would likely never use more than "playing around". I'm not trying to troll here, I'm legitimately curious if anyone else feels this way.
Edit: I did sign up for an invite over a month ago, and I am legit excited to give it a go.
We're building Divshot to be a tool that professional developers and designers use every day. I totally understand the "I would never use it for more than playing around" approach, but that's how it starts (see e.g. http://cdixon.org/2010/01/03/the-next-big-thing-will-start-o...). All I can say is give it a chance, watch how it grows, and I think you'll change your mind.
Right, but which part of the dev/design process is it taking over? Do you guys see divshot taking over production ready front end development the way Balsamiq (and the likes, arguably) took over pen & paper?
Given the predecessors to divshot in the WYSIWYG world, expect many developers and designers to be extremely open minded, yet very skeptical.
We definitely expect some skepticism given past WYSIWYG entries into the space, but we consider our prime directive to be "No matter what, the output is clean."
We hope to be a tool that developers will use to rapidly prototype an interface at the beginning stages of an application and then continue to use it to experiment or quickly build new functionality throughout the app lifecycle. Hope that answers your question.
Being a seasoned developer, front, middle and back end, I find this an interesting product, but something that I would likely never use more than "playing around". I'm not trying to troll here, I'm legitimately curious if anyone else feels this way.
Edit: I did sign up for an invite over a month ago, and I am legit excited to give it a go.