There is, in some quarters, an opinion that you should use FTP for file transfers and HTTP for web traffic. There is some logic to this if you are transferring very large files and many web hosting companies will limit the file transfer size to 512Mb per request.
If limits are put in place, then the only option is FTP, but this restriction can easily be lifted on a dedicated web host platform.
In fact the limit at hardcoreVids.tv is a whopping 40Gb !
The main benefits of HTTP or uploading via the web site:
The real kicker though is Why would you want to upload via a separate App and then when done, go back into the web site and then start providing video data (or launch) when you can do everything in one place?
These days, FTP is mainly used when you want to port across an entire directory or folder structure from one PC (server) to a remote server (e.g. hosting) and that’s fine for entire web sites, but if you just want to send 10, 20, 50 video files then there is no reason to use FTP for this, if, as we do, have close to zero restrictions on what you can just upload.
Modern web systems should not expect users to separately login with a username and password and wrestle with FTP client software when a simple click of a Select Files button and OK (just as you do with email attachments) is far more intuitive.
FTP has its place in the software development world, but there is no need to burden users with rather clunky (or #tech) systems to upload videos.
And finally, for security reasons, we don’t really want users poking around the folder structures on our server and possibly uploading non-image or non-video files, albeit the FTP user would be rooted to their personal folder, but hackers use FTP upload to load server-side scripts. With HTTP systems this is all transparent and we restrict the upload of files to images and videos.