Absolutely. 1ftp actually uses HTTPS on the client end to secure the connection, over port 80. There is no direct FTP connection for users, only on the backend to the server. The service acts as a gateway, though its transparent to the user.
Those things are commonly unavailable on Windows servers, in my experience. This is probably due to some combination of crappy administrators, difficulty of installation, lack of tooling, etc.
Those things are great for tech-savvy developers, but the majority of folks still use FTP - it's the defacto method for connecting to a webserver, and is what every web host emails to their customers. 1FTP will be a heck of a lot easier to set up than Git, or anything else.
It may not seem so to an experienced developer, but the experience for an end user with things like that is an absolute nightmare. We're trying to make it easier, not harder :)
I actually refuse to work with FTP. More developers should. Hosts should refuse too.
There are some good GUIs for SCP that reduce the barriers of entry to the same level as FTP.
IMO you're trying to solve a problem that shouldn't be solved. Maybe turn your 1FTP app into an SCP interface. That way the "difficult" things you describe become easy.
By this logic (musn't force anyone to learn anything) we should all still be using IRC and USENET instead of Skype and web forums. So you want to provide a nice layer of abstraction over file transfers, that's laudable. What doesn't make sense is predicating your abstraction on a shitty protocol with a multi-decade long history of security issues. Best of luck to you in any case.
