diff options
| author | Bradley Taunt <bt@btxx.org> | 2024-06-08 13:43:37 -0400 |
|---|---|---|
| committer | Bradley Taunt <bt@btxx.org> | 2024-06-08 13:43:37 -0400 |
| commit | 16d28628aca9b2d356de31c319f5e7bc0f5b2b02 (patch) | |
| tree | 11947abb71e38cbe75116871694a44c33d257763 /build/improving-receipt-ux | |
| parent | dcfb172704f3afb68a30425029ec834be2883274 (diff) | |
Remove incorrectly generated files, fix up markdown articles
Diffstat (limited to 'build/improving-receipt-ux')
| -rw-r--r-- | build/improving-receipt-ux/index.html | 19 |
1 files changed, 2 insertions, 17 deletions
diff --git a/build/improving-receipt-ux/index.html b/build/improving-receipt-ux/index.html index 539411d..30f4fb9 100644 --- a/build/improving-receipt-ux/index.html +++ b/build/improving-receipt-ux/index.html @@ -3,11 +3,12 @@ <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> + <meta name="color-scheme" content="dark light"> <link rel="icon" href="data:,"> <title>Improving Receipt UX</title> <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" /> -<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> +<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> </head> <nav> @@ -16,46 +17,30 @@ <main> <h1 id="improving-receipt-ux">Improving Receipt UX</h1> - <p>2019-05-15</p> - <p>There was a pretty interesting article posted a couple days ago about rethinking the standard receipt design that I found quite compelling. Although, as good as the concept is, I think it can be improved (simplified) even further.</p> - <h2 id="what-was-the-redesign-exaclty">What was the redesign exaclty?</h2> - <p>Overall <a href="https://twitter.com/datatoviz?lang=en">Susie Lu</a> did a wonderful job tackling such an old and forgotten design. She fixed some major pain points with the current receipt layout:</p> - <ul> <li>Bubble chart to visually indicate total spent per category</li> <li>Categorized items by percentage of total spent</li> <li>List individual items in descending order based on cost</li> <li>Bar charts to compliment the item listing order</li> </ul> - <p>Curious how her redesign looks? <a href="https://www.fastcompany.com/90347782/the-humble-receipt-gets-a-brilliant-redesign">Take a look at the original article</a></p> - <h2 id="what-did-this-concept-get-wrong">What did this concept get wrong?</h2> - <p>Simply put: <strong>paper waste</strong>. </p> - <p>Using bubble and bar charts from a visual design perspective is great - but not so eco-friendly in this instance (since we are dealing with physical paper waste). It might seem like a small nitpick but with hundreds of thousands (if not millions) of receipts printed daily, this extra paper space required would add up quickly.</p> - <p>Fortunately, I think with some minor tweaks we can keep the underlying principles of the new redesign, while creating a more eco-friendly layout. We can save more space and therefore save on the overall paper needed.</p> - <h2 id="receipt-redesign">Receipt Redesign</h2> - <p>Let’s take a look at my redesign concept:</p> - <p>With this layout we are able to keep all the key concepts that <a href="https://twitter.com/datatoviz?lang=en">Susie Lu</a> initially introduced with her receipt design while preserving more space.</p> - <ul> <li>Categories are still listed by percentage of total spent</li> <li>Individual items are organized in descending order based on cost</li> <li>Uppercase and lowercase elements are used to distinguish parent / child items instead of additional space or dividers</li> </ul> - <h2 id="final-thoughts">Final thoughts</h2> - <p>The original redesign from a visual perspective is <em>wonderful</em> but when you start to think about implementing it into the real world, it seems slightly impractical. My redesign concept is far from perfect (I’m sure I’ve overlooked some use cases) but I think it’s a strong step forward for redesigning our archaic receipt layouts.</p> <footer role="contentinfo"> <h2>Menu Navigation</h2> |