They are similar except that Netlify's Form transforms your forms into its own thing. This makes it more difficult to customize the after actions because you don't control the final code. Note that Netlify does offer limited customization of the after actions as you can see here: https://docs.netlify.com/manage/forms/setup/#success-message...
Any alternative that is hosted or uses iframe will encounter this kind of frictions.
In comparison, with Wait, you'd just call `fetch(...)` and do whatever you need after `fetch(..)` succeeds or fails. For example, one landing page might say thank you afterward. Another landing might show the installation instructions after the user submits their emails. The whole code is controlled by you.
It's like you call your own backend except it's hosted in a different domain, and your landing page can be hosted as a static site with no backend.
If you are interested in trying it out, I'd love to work with you to make it successful for you. Thank you!
Any alternative that is hosted or uses iframe will encounter this kind of frictions.
In comparison, with Wait, you'd just call `fetch(...)` and do whatever you need after `fetch(..)` succeeds or fails. For example, one landing page might say thank you afterward. Another landing might show the installation instructions after the user submits their emails. The whole code is controlled by you.
It's like you call your own backend except it's hosted in a different domain, and your landing page can be hosted as a static site with no backend.
If you are interested in trying it out, I'd love to work with you to make it successful for you. Thank you!