Goals

From flud

[edit] Target Users

  • targetted squarely at individual end-users and the small office / home office. As such, the software must be dead simple to install and run. No technical expertise is needed. No servers need to be installed or maintained. No tech support staff is required. No babysitting or monkeying with settings once the client is installed.

[edit] Functionality

  • indestructible backup. Neither flood, famine, hurricane, nuclear strike affecting many nodes in the flud network, nor the complete failure or death of the flud backup software team (or supporting company[ies]) will render flud backup unusable.
  • transparent backup. Backups occur without user intervention, on a regular basis.
  • out-of-the-box working. If the user does nothing more than just install the software, it should have reasonable defaults for backing up important data (home directories, MyDocuments, etc). No configuration is required (though customized configuration is possible).

[edit] Attributes

  • simplicity. The internal architecture, as well as the interactions with the user, should be as dead-simple as possible. No manuals, quick-start guides, or howtos should be required.
  • efficient. The memory, CPU, and disk space requirements should be reasonable.
    • delta compression should be provided as a separate layer, to efficiently backup only file differences.
  • beautiful. The interface should be alluring. Users should be drawn into by its attractiveness and simplicity, so much that they encourage others to try it out.
Personal tools