Difference with Webform

Well for the start let say that the biggest difference is that you have dynamic javascript form builder in qforms, and that is something that you do not have in webform.

Second big difference is that qforms is lot easier and simpler then webform. End user can easily create forms with qforms (or at least I hope that that is a case).

Third, qforms will always stay easy/simple and light or at least it will try to be like that in the future - main idea is easy and very fast form creation for end users. All other complex things will be added to separate module if and when they are needed - core will always be simple and small.

Now Drupal Gardens now have something similar a dynamic form builder - combination of webform, form_builder and I think one additional module that was developed by Acquia. But qforms development started before this was publicly announced by Acquia - if I know it back then maybe I would not develop qforms. But again Gardens form builder is more complex for end user then qforms and you need 3 big modules on the end...

So webform under the hood and for end user is something that is very different comparing to qforms and that is OK, both modules try to cover different use cases. Webform is much heavier and more powerful (at least for now) and qforms idea is to keep everything simple, small and easy.

I think now that we finally have a solid base developed we will move future development of qforms towards form builders like google forms or gravity forms for wordpress - for example we will implement some of the gravity forms end user workflow in future release of qforms.

One thing that would convince me to use something other than Webform would be if the substitute had full views integration of the submitted form results. It is very difficult to do with Webform because of the way data is stored. See: #680386: Views integration for the webform_submitted_data table
Will this module have full views integration? Are the form submissions stored differently? If not, I see no great value in duplicated effort. If so, I will probably start using this module instead of Webform.

Hmm views integration, well I though about that also - at least there are two possible ways how it can be done.

Are the submissions data stored in some other way? Nope I don't think so, that's why exposing submitted data to views is difficult but possible.

So will this module have full views integration - maybe. Currently we are ready to release stable 1.0 release. After that we can go in any direction we want. There are a lot of things we are planning for future release, please check http://drupal.org/node/1087734. My personal preference for next task is to work on better form builder tool, but if other users thinks that something else is priority we can adjust our plans.

Do you have some plans about joining forces with webform which get contribution from DG about simplified UI?

Do you have some plans about joining forces with webform which get contribution from DG about simplified UI?

No plans for now, but if somebody have an idea how can we do something together I am willing to discuss.

But I think it will be very complex and big job and probably a lot of webform internal stuff would need complete rewrite. That is one of the reason we decided to develop new solution 5 months ago when we asked our self what to do - combination of webform, form_builder and one addition custom module that would bind that two modules seemed like a very complex thing... Not to mention we would need to collaborate our work with maintainers of two other modules, and this also takes time. And finally we didn't have slightest idea that Acquia is doing something similar.

Also Drupal Gardens UI contribution is great stuff but I still find it too complex for regular end user (and I think you need 3 modules for this, not one).
In the end our goal is to reach easinest of Gravity Forms for WP or Google Forms - qforms will not be the same like those two solutions but what we want on the end is to give Drupal end users the same level of comfort that this two solutions offers.

One more thing. I rarely like a situation when you have only one contrib module solution for your problem - before qforms you only had webform module. But I also don't like situation when you have 10 modules that gives you 80% of the same functionality. So one good solution is very nice thing, but 2 or 3 good solution are sometimes even better because you then have healthy competition ;)

But as I said in the beginning if somebody have some good idea how we could join forces I would like to hear it.

Webform lucks support for i18n even though it has been requested more than 3 years ago #245424: Make Webform multilingual (i18n) aware through contributed modules

is qforms planning on adding support for multilingual sites ?

Hmm views integration, well I though about that also - at least there are two possible ways how it can be done.

What are the 2 ways to integrate Qforms with Views?
I need to display the submitted results of the Qforms filtered by certain fields on a page, but don't have a clue how to do this.