iDropper is an FTP file transfer system in two parts: There is the iDropper application, and the FTP file transfer "droplets" which it creates.

An administrator uses iDropper to configure a droplet, which is a tiny, self-contained application that acts as an FTP client on the end-user's computer. But unlike typical FTP clients, the end-user does not have to enter complicated Hostname, Username, Password or other parameters in order to use it. All those settings are configured by the administrator.

Once the droplet is configured, it can be saved and distributed to whomever needs it via e-mail, website download, disc, flash media, etc. The end user then copies the droplet to his computer desktop. All the end-user must do to use the droplet is to drag and drop files and/or folders onto the droplet's desktop icon.

iDropper works by creating a "droplet", which is an entirely self-contained FTP client that points to a particular folder on an FTP server. This droplet has all the FTP host name, login and password information embedded in it. The user of the droplet requires no knowledge of FTP, no login, and no password. He simply drags and drops files onto the droplet, and they are delivered. See the diagram below for an illustration of the basic workflow:

In this basic process, an Administrator uses iDropper to configure a droplet. The Administrator then distributes the droplet to the End User via e-mail. The End User then installs the droplet on his desktop. Once the droplet is installed the End User simply drags and drops files and/or folders onto the droplet. The droplet connects to the server via FTP and the files are uploaded to the folder chosen by the Administrator. The Administrator then retrieves the files from the server.

But that's not all. Where iDropper truly excels is after file delivery. Droplets can be configured to send you an E-mail message after the delivery, so you know when files have been uploaded to your server.

You can configure your droplet to send the user to a Web Page after the upload is complete. This could be a special confirmation/acknowledgement page, or simply your company home page.

Droplets can also collect information about the job (Job Info) and deliver that information along with the files. You can create a custom form that is presented to the end-user when files are ready to be uploaded. The form will be transmitted in XML or plain text format (your choice) along with the files.

Web Scripting takes this a powerful step further. After delivery the droplet can POST to a web server just like a web form would in a browser. Any number of fields can be defined and POSTed. The names of the files are POSTed as well as the Job Info file location. A server side script (like PHP, JSP, ASP, etc.) that receives the POST can do nearly anything with it. It can move files, unzip them, update a database, send e-mail to an account rep; you can use custom scripts to fit into your workflow.

See the diagram below for an illustration of a more advanced workflow:

In this example, the Administrator has created a droplet that is configured to interact with a PHP script by sending POST variables to the script's URL. The script is written to send e-mail to the Administrator and to interact with a customer order database. The droplet has also been configured to generate a Job Info form, to be filled out by the End User when uploading files. The Job Info form could prompt the user for customer ID and a description of the job. Finally, the droplet is configured to create a ZIP archive of all the files sent with it.

As this scenario plays out, the Administrator creates and saves the droplet using the Web Script Notification feature, the Job Info feature, and the Archiving feature. He sends the droplet to the End User via e-mail. The End User installs the droplet and drops files/folders onto it. The droplet opens the Job Info form and prompts the End User for information. Once the form is completed, the droplet creates an archive of the files and uploads it to the server.

In a process completely invisible to the end user, the droplet sends POST variables to a PHP web script. The script generates an e-mail message which is sent to the Administrator and logs information about the file upload into a customer order database. The Administrator receives the e-mail, retrieves the files from the server, and can track the job through the customer order database.

Printers, publishers and service bureaus love it! Software developers use it to deliver builds. Distributed workgroups use it to share project files.

iDropper is ideally suited to the commercial printing and prepress industry. Commercial printers and prepress shops must handle large volumes of files from their customers. These files may include all the resources necessary to print an entire job: a page layout file (like QuarkXpress), font files, PDF soft proofs, EPS or Illustrator artwork, etc.

To receive these files, the printer is faced with several imperfect solutions: to receive them via e-mail, which can choke a mail server; to receive them via CD-ROM or other media, which creates a productivity drain as all that media is handled through multiple processes; or to receive them via FTP, which in the past has required that the customer be familiar with FTP, have an FTP client installed, and be granted permission to access a mission-critical resource (introducing a security risk).

iDropper provides a better solution. With iDropper, the printer's IT administrator creates a secure FTP droplet for each customer, with all the sensitive access parameters hidden from the end-user. iDropper frees up the mail server, saves on bandwidth, and eliminates the need to constantly check the inbox and delete messages. And iDropper can replace a mountain of CDs!

In addition to the core functionality, iDropper adds powerful workflow features, such as Job Info forms, Web Scripting and Web Page notification. These features can be plugged into an existing workflow or serve as the basis for developing a brand-new workflow.

Of course, iDropper is not limited to the printing and prepress industry. iDropper is also well suited for creative services agencies, magazine and newspaper publishing, software developers, geographically distributed workgroups, and anybody who makes or receives frequent FTP uploads.

If you need to receive a large number of files from outside sources, iDropper can increase your productivity, reduce customer support time, and drastically reduce the amount of digital media handling necessary to get the job done.

Without iDropper you are faced with three imperfect options for receiving files: via e-mail, via CD-ROM or other media, and via FTP. FTP is by far the best option, but it requires an FTP client and someone with the knowledge to use it on the other end of your pipeline. If the person on the other end of the pipeline is technologically challenged, you can burn precious time explaining the process to them, getting them set up with an FTP client, and then configuring that client to connect to your server. AND you have to open up your server to them, creating a potential security threat.

iDropper eliminates these problems by creating a digital self-addressed, stamped envelope, in the form of a "droplet", which contains all the FTP connection information within it. End-users simply drag and drop files onto the droplet for delivery. It requires no technical knowledge on the part of the end-user whatsoever.

iDropper also has advanced workflow features to add even more productivity to the process. Droplets can be configured to send you an E-mail message after the delivery, so you know when files have been uploaded to your server.

You can configure your droplet to send the user to a Web Page after the upload is complete. This could be a special confirmation/acknowledgement page, or simply your company home page.

Droplets can also collect information about the job (Job Info) and deliver that information along with the files. You can create a custom form that is presented to the end-user when files are ready to be uploaded. The form will be transmitted in XML or plain text format (your choice) along with the files.

Web Scripting takes this a powerful step further. After delivery the droplet can POST to a web server just like a web form would in a browser. Any number of fields can be defined and POSTed. The names of the files are POSTed as well as the Job Info file location. A server side script (like PHP, JSP, ASP, etc.) that receives the POST can do nearly anything with it. It can move files, unzip them, update a database, send e-mail to an account rep; you can use custom scripts to fit into your workflow.

Yes, we take data and network security very seriously. All the settings are encrypted using a 128 bit key. We don't specify the exact algorithm to prevent cracking. It is similar to DES. Droplets made with registered software can only be opened with the same, registered software. So, if you make a droplet with your registered software no one else will be able to open it. Passwords are never readable.

Trial copy droplets can be opened by anyone.

iDropper for Mac and Mac droplets require Mac OS 10.3.9 or higher. Windows droplets require Microsoft Windows XP SP2 or higher.

iDropper application installation requires 5 MB of disk space.

Yes, iDropper for Mac is a Universal application, made to run on both Intel- and PowerPC-based Mac computers.