Lunchbox

William Holley's (waholleyiv) USDA E.A.T. School Lunch UX Challenge Submission

Live Form Here.

Design

Lunchbox maintains the feel of a traditional form while offering enhancements which only an electronic-form could support.

  • ###Layout

Rather than breaking up each entry process into an individual step, Lunchbox maintains the cohesive Steps from the Prototype Application. This decision was made in order to keep the form from feeling unapproachably long, and to reduce the possibility of duplicate entries.

  • ###Colors

Blue acts as the primary color as blue is psychologically perceived as trustworthy, reducing stress and creating a sense of calmness and confidence. 1 $blue: #00B4FF;.

Yellow is utilized within Action buttons such as Save for Later and Calculator. Yellow is a cheerful color; as such it is chosen to alleviate any potential anxiety the user might experience concerning postponing form completion or seeking mathematical help. $yellow: #f1c40e;.

Red is utilized to denote Question Beacons adjacent to terms that have expanded definitions. Red is chosen as it clearly stands out against Blue and is easily noticed by the eye. $questions: #E91E63;.

  • ####Multiple Languages

Users can pick between English or Spanish. As of 2014, 17.4% of the US population is either Hispanic or Latino; offering this option is vital to reduce inaccuracy stemming from lingual misunderstanding.

When the application is loaded, it attempts to automatically determine the browser's language using navigator.language || navigator.userLanguage || navigator.browserLanguage and load the appropriate introduction (English or Spanish).

  • ###Ethnicity & Race

As optional fields, Ethnicity and Race are only displayed when triggered by the user through an Action button. This decision was made in order to alleviate potential pressure users may feel (to fill out their Ethnicity and Race) because these optional fields appear adjacent to required fields.

  • ####Calculator

A full working calculator is provided wherever Earnings are requested in order to minimize mathematic errors.

  • ####Save State

Lunchbox allows users to save their form responses and language preference in order to finish later. After this save has occurred, users notified that they can return at any time to continue and are prompted to bookmark the page address. This is accomplished by creating Local Storage Cookies using app.form.saveAsCookie().

On load, Lunchbox checks Local Storage to see if it contains a previous view or user_data. If these are both found, Lunchbox returns the user to their previous progress within the form.

  • ####Editing

When the user reaches the end of the form, they are given the opportunity to review their inputted data and make edits if need be. The appropriate view is displayed with all previously entered data templated in.

Development

The architecture is a standard MVC pattern located within /app.

To run the app on your local machine:

  1. Ensure the npm and git commands are installed on your computer.
  2. Download the source code: git clone https://github.com/Vivism/Lunchbox.
  3. Install dependencies: npm install.
  4. Start the server: npm start.

Household Retrieval

An administration panel is foregone in favor of a client-device-agnostic REST API endpoint. To retrieve all Households from the Database, send a HTTP GET request to /api/lunchbox. For security purposes, data: {'key': KEY} is required. KEY is defined within var lunchbox_key on Line 7 of server.js. The Household Object contains its creation date, the language chosen by its author, the data inputted from the form, and a eligibility boolean (true or false).

To test out the API without a custom AJAX call, call getLunchboxes(KEY) within your web browser's developer console.

Technology

Feedback

Feedback was given by a native Spanish speaker and can be found (here).

The MIT License (MIT)

Copyright (c) 2016 William A. Holley IV

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Share this project:
×

Updates