Tagged ‘ui_saving’

As obvious as it sounds, saving requires some form of authentication. Here is a more recent sketch to support saving and loading with authentication. Work can be saved as a web link, or stored locally. Similarly, work can be opened from a recent list of projects which have been worked on online, or a project can be opened from a user’s local computer.

The idea is to delay the login or registration beyond saving and loading. Hence, users would be able to save and load without having to create an account. In this scenario, if a user has not logged in and saved work, a cookie should keep the session alive until he or she comes back in the future to resume work (or to create an account).

How could users save their work using fluidIA? These few sketches play off on the idea that saving of the work could happen in at least two ways. Users could potentially be able to save their work as a web link URL, allowing easier sharing. On the other hand, users who feel more secure about their data being stored locally, could do so by means of the second saving option. This sketch also explores the idea of saving data locally by means of a Firefox plugin. Perhaps this same functionality could also be achieved by means of Google Gears or an Adobe AIR application. This “save as URL” sketch also suggest that the possible name of the URL would be checked in real time for availability.