Survey industry and general use of digital form is huge. For most use cases like entry form, survey forms or even during the hackathon companies like router were asking hackers to fill google form, which is centralised.
The second part is the ability to perform on-chain activities like airdrops, eligibility checking, proper report generation without the users requirement to share details like email, phone number which have no use but automatically gets picked up by web2 forms.
Survey and auditing is important part of an organisation and DAO is no exceptions, current tools allow voting on proposals, or floating forms on discord. The degree of decentralisation is equivalent to number of individual participants you could remove before the system collapse, decentralised forms are another individual which do not affect the nature of DAOs or already existing decentralised systems.
Many people are crazy about their info privacy while many are eager to sell them for money, this data-to-reward technology can boost up this industry and also has capabilities to uplift research surveys.
Challenges we ran into
First problem was to decide the system to be on-chain or off-chain, because it can be problematic even for companies like router to get as many as 2000 hard and dedicated crypto hackers to pay for gas fees. So, we decided to create a hybrid system, for host can choose between off-chain and on-chain forms
First technology we chose for off-chain database was OrbitDB, but due to some technical errors we couldn't get it working. Then we created a small Django based server to store form cids, and response cids allong with their creators.
PLANNED The data on ipfs is public, what if some surveys wants to keep their response private? We planned to do rsa encryption of response and then encrypt the rsa private key with form creator's public key and which allow only the form creators to view the responses
PLANNED We build the smart contract, but couldn't add this part in the final build. Even our build is not final.