61–70 of 73 posts
Earlier quoted context omitted.
Thank you for using Tally and all the kind words! We just finished our help center migration, so happy to hear you like it. :)
Is the help center custom built?
Earlier quoted context omitted.
That wasn't my point. I meant the feature is available to a very small subset of our users. Then even a smaller subset chooses to use it and I believe, it's up to the form creator to add a disclaimer on why this is necessary for their use case.
I'm not usually a big privacy person, but the way you're responding to this is a dealbreaker. This feature is fundamentally unethical. The fact that it's paywalled and not everyone uses it changes nothing.
This looks great! Curious what tech stack/framework you're using?
Backend: Node, Express, Typescript, Sequelize (MySQL)
Hosting: Google Cloud
Earlier quoted context omitted.
That wasn't my point. I meant the feature is available to a very small subset of our users. Then even a smaller subset chooses to use it and I believe, it's up to the form creator to add a disclaimer on why this is necessary for their use case.
I'm not usually a big privacy person, but the way you're responding to this is a dealbreaker. This feature is fundamentally unethical. The fact that it's paywalled and not everyone uses it changes nothing.
Consider an implementation of "draft" submissions. Imagine you wanted to implement such a feature on top of some form builder. You would require such a feature.
I don't necessarily agree or disagree with the points raised on ethics here, but there's a very real consideration when you're offering a library/package/feature, sometimes you have to expose guts that can be used improperly in order to enable certain featuresets. I think it's obvious why someone building such a tool as OP would offer such a feature as is in discussion, because they would lose money otherwise from implementations that require this feature.
So, if a subset of things that can be done with your work are nefarious, how much effort are you meant to put in to make it ethical to sell your work? Is it inherently always unethical to build a tool which can be used to nefarious ends?
Edit: Found it
Very nice product! That said, > Partial submissions > Collect answers from people who filled in a part of your form, but didn’t click the submit button. Capture data from lost leads, find drop off points and improve your conversion rates. From a user point of view, I really hate this. I’d say collecting data about drop off points is fine, but secretly collecting answers not intended for submission is a dark pattern t…
I'm not sure I understand here this issue. When I'm using typeform, and I click "next" or scroll to the next question, I've always assumed that has meant "submit this answer". I don't consider the entire thing a form, and at some point I may go "ok, I'm done answering your questions, I don't want to do this anymore", and I leave. I don't assume at that point that nothing has happened. I answered a bunch of questions…
I don't understand why you would necessarily think that. The forms can be styled to look like regular forms, with multiple fields per page.
E.g. this registration form: https://tally.so/create?templateId=ywaZnM
I took the above warning as saying that if I type my first name in the first field, then change my mind and go away without submitting anything, then they record my first name.
My actions (leaving after I typed in something, without hitting submit) would in no way look like I intended to submit an entry.
While I think your expectation that there are other forms that do this is possibly valid, I don't think that many other forms I encounter every day do do this, and I would be grossed out if they did.
I've seen this and I really like it. I think the UI is great, and love the overall direction of the product. I know this will be hard to hear, but I want to provide my best feedback. As a CTO, I will rarely, if ever, use a product like this that's not (at a minimum) open core. I just can't risk building technical and business momentum around a startup that I don't know the longevity of. I have no problem paying for s…
budibase.com
Earlier quoted context omitted.
I'm not usually a big privacy person, but the way you're responding to this is a dealbreaker. This feature is fundamentally unethical. The fact that it's paywalled and not everyone uses it changes nothing.
> This feature is fundamentally unethical Consider an implementation of "draft" submissions. Imagine you wanted to implement such a feature on top of some form builder. You would require such a feature. I don't necessarily agree or disagree with the points raised on ethics here, but there's a very real consideration when you're offering a library/package/feature, sometimes you have to expose guts that can be used imp…
A user knows what a draft is, and would agree to such a feature upon pressing a button that indicates that the draft will be saved for later by submitting the form verbatim as-is to the server
Saving everything a user types in, without a user's informed consent, is a severe trust violation.
Earlier quoted context omitted.
> This feature is fundamentally unethical Consider an implementation of "draft" submissions. Imagine you wanted to implement such a feature on top of some form builder. You would require such a feature. I don't necessarily agree or disagree with the points raised on ethics here, but there's a very real consideration when you're offering a library/package/feature, sometimes you have to expose guts that can be used imp…
You can build anything you want after acquiring the end user's informed consent. A user knows what a draft is, and would agree to such a feature upon pressing a button that indicates that the draft will be saved for later by submitting the form verbatim as-is to the server Saving everything a user types in, without a user's informed consent, is a severe trust violation.
Again, OP isn't selling things directly to end-users, so I don't know how the OP is meant to acquire the end user's consent, informed or not. The OP is exposing abilities in a tool which enables his end users to turn around and deliver something to their end users. My question is how culpable OP is for abuse of his tool's abilities, and what level he must go thru to put abuse protections in place to be not morally culpable for his end user's treatment of their end user's, and your answer is "OP needs to get informed consent". Ridiculously simplified.