Documentation for a historical release of Infusion: 1.3
Please view the Infusion Documentation site for the latest documentation.
If you're looking for Fluid Project coordination, design, communication, etc, try the Fluid Project Wiki.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Problem

Solution

Problem Statement: Currently most web applications use the standard http file browse and upload service provided with the <input type="file"> form field.

  • Only one file can be selected at a time for upload.
  • Interface is inconsistent from browser to browser even down to the labels on the browse button.
  • The application can not specify the file type or types that are accepted in the current context.
  • The browser does not provide meaningful or consistent feedback on the upload process.

Wireframes What does the Uploader look like and how does it behave?

Storyboards: How, when, and where would the user use an Uploader?

Design Pattern

Users

Catalina and Christy are some of the users whose needs we primarily considered when designing the Uploader.
Fluid Personas are a collection of various types of important users whose needs we need to consider throughout the design process.

Users' needs

Context of use: Where in the systems we support is an uploader being used currently?

Functional Requirements:

Primary & Secondary Scenarios: In what scenarios would the Uploader be used?

Uploader User Testing

User Testing Protocol: Describes how the Uploader would be tested with the users

User Testing Results: Describes how the users interacted with the Uploader prototype and what improvements can be made

Preparing for Implementation

Storycards: Decomposes the Uploader into small implementable chunks

Functional Specification: Uploader Specification

  • No labels