Edit widget versus Survey widget

[clt_cabq]

I'm curious if anyone has experience using either or both the edit widget or the survey widget and what that experience has been like, and if you would recommend one approach versus the other. My application is going to have a feature layer with up to 3 related tables that will be updated by end users. The survey widget seems attractive in part because we can develop reports on the s123 side that users may want for various purposes. The edit widget with its ability to edit related records seems pretty straightforward and simple to use.

Any thoughts if there are best practices or scenarios where one of these tools works better than the other?

[Laura]

I have experience using the Edit Widget, and it’s particularly useful for any geospatial editing needs. It’s also great for editing related tables, and my end users consistently find it intuitive and easy to use. The main trade-off compared to Survey123 is the reporting functionality, as the Edit Widget doesn’t offer built-in report generation. Ultimately, the choice will depend on your specific use case. It might be helpful to create sample workflows for both options, test them with a few users, and gather feedback to see which approach feels more intuitive. For those of us in the industry, both tools are relatively straightforward, but user feedback can make a big difference in choosing the best fit for your project.