SurveyCTO

Hi Ryan, thanks for leaving this review (though, for full disclosure, I see that you work for crowd review so reviewed our platform specifically for the site and, I assume, did not use it for an actual research project). Just wanted to correct you regarding user permissions - we do in fact have a user role available for someone to be able to download data but not be able to manage/modify forms (the "data manager" user level).

Also, regarding a native iOS app, agreed that it would be a good addition. However, we don't have plans in the near future to add an iOS app for two reasons:

1) We have web forms that will run in any browser on any OS.
2) Our entire platform is built on top of a widely used (in the research and international development communities) open source set of code called Open Data Kit, which was developed at the University of Washington. It was specifically developed in Android because Android OS is much more conducive to open source efforts compared to iOS.
3) Another reason that the focus was on Android is that the goal of ODK (and SurveyCTO as well) is to facilitate surveying and data collection efforts in the research/humanitarian/non-profit world where data collection is done in resource constrained settings in developing countries. In such places, Apple devices have almost 0% usage - they are very hard to find and incredibly, incredibly expensive. Whereas everyone and anyone can and does use Android devices.
4) You didn't mention it in this review but you will have noticed that our core feature - and what distinguishes us from the likes of SurveyMonkey or SurveyGizmo - is that our surveying Android app is designed to run completely offline since our users use us in areas with limited or no internet connectivity. I only mention this to clarify that the organizations we hope to help will use us because we work offline, unlike other surveying tools out there. And places where you need to work offline are places where you will almost certainly be using an Android, rather than an iOS device.

Hence, for us, there isn't enough reason to justify the extra cost of building out a native iOS app just yet. We are always following our users' needs of course. If we notice an increased demand for an iOS app from our potential users, we would definitely be open to building one out.