<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tyler Miller on Medium]]></title>
        <description><![CDATA[Stories by Tyler Miller on Medium]]></description>
        <link>https://medium.com/@tylermiller.is?source=rss-565cabdaade------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4WxlL-FZb1PENdg7mJanqw.jpeg</url>
            <title>Stories by Tyler Miller on Medium</title>
            <link>https://medium.com/@tylermiller.is?source=rss-565cabdaade------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:51:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tylermiller.is/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Systemizing color for change]]></title>
            <link>https://uxdesign.cc/systemizing-color-for-change-9dde4d0018e4?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dde4d0018e4</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[colors]]></category>
            <category><![CDATA[interface-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Wed, 24 Oct 2018 19:02:29 GMT</pubDate>
            <atom:updated>2019-06-06T20:44:50.331Z</atom:updated>
            <content:encoded><![CDATA[<h4>In the age of “dark mode”, how can websites and applications adapt to platforms that change?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yJl38-su_Kaoze6M" /></figure><p>People were excited when Apple announced dark mode on Mac this year. Dark mode is nothing new; dark mode has been supported on other operating systems and integrated into many applications for years now. As “dark mode” becomes more prevalent application and website developers are tasked with building software that supports it.</p><h4>Blending In</h4><p>Customization has always been a part of software. People react emotionally to color and identify with their favorites. The push for dark mode is one part customization and one part optimization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7zZxvv9KtQP1e4fFuOcyfw.png" /><figcaption>Before dark mode, all the cool kids were changing their accent and highlight colors (not really).</figcaption></figure><p>Screens move with us as we travel between dim and bright environments. In bright environments screens have to compete with the light around them, and there, dark-on-light (DoL) interfaces <a href="https://ux.stackexchange.com/questions/53264/dark-or-white-color-theme-is-better-for-the-eyes">perform better</a>. Inversely, when you check your phone in a movie theater DoL interfaces seem too bright. Screens can blend in to their environment by adjusting the brightness of the screen or through changing the color of the interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IfiVAk1nzb4_be0gnoXDQw.png" /><figcaption>Bright screens ruin dark rooms (photo via <a href="https://www.npr.org/sections/alltechconsidered/2016/04/14/474226195/clash-of-the-screens-should-movie-theaters-allow-texting-amc-says-maybe">NPR</a>)</figcaption></figure><p>Choosing not to offer a dark mode negatively impacts the experience a user has with your product. If dark mode is enabled and your product is the <em>only</em> application that doesn’t change, the user will blame your product.</p><h3>Designing Color Systems for Customization</h3><p>At Frankly, we work with a wide range of partners who want the applications and websites created by our platform to invoke their brand. Similar to dark mode, branding often involves changing the color scheme of a website or application. We use <strong>color pairs</strong> to make customizing color systems a breeze.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZbimAuJQ_g5w1SBHBDigNA.png" /></figure><h4>Color Pairs</h4><p>The simplest interfaces are composed of a background and a foreground element. Instead of applying color to elements, apply colors as a pair to the component:</p><pre>&lt;component class=&quot;cp-default&quot;/&gt;</pre><p>At its core a color pair is one background color and one foreground color. Components often contain more than two colors, but never contain more than one background color.</p><h4>Naming</h4><p>Color pairs rely on describing color functionally instead of visually. Typically we see three main sets of colors: the core, washes, and accents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7JiMr4fj0_ZnKBSl_VWgVw.png" /></figure><p>The core is made up of the background and foreground colors. These colors should be high-contrast to ensure visibility of foreground elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZlC2s2U_2Bhk4Wx4HrBn_Q.png" /></figure><p>A Wash is a mix between the foreground and background color. Often these colors are grays or tints (a mix of hue &amp; white) but the term wash is more appropriate because it isn’t specific. Usually washes exist in a scale of two to five colors and are used for elements like borders, dividers, and disabled/empty states.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZdIG3uETxcDmMIXcxQjSLg.png" /></figure><p>Accents describe hues that add meaning to the interface but are not required for the interface to work. An accent can be a stand-alone color or be scaled like washes. Typically accents are used for calling attention, denoting interaction, and error states.</p><p>There are many ways of naming colors functionally and this is just one of them. A good naming system keeps pairs free of duplicate colors, keeps them small in size, and enables pair swapping.</p><h4>Fallbacks</h4><p>The default behavior of a color pair should be to make foreground elements visible to the user. Structure your color system so that the fallback color of foreground elements is the foreground color:</p><pre>.cp-default {<br>    color: var(--cp-default-foreground);<br>    fill: var(--cp-default-foreground);<br>    border-color: var(--cp-default-foreground);<br>    background-color: var(--cp-default-background);<br>}</pre><h4>Storing Color Pairs</h4><p>Consider the platform you’re designing for when deciding how to store color pairs. I prototype with CSS often and a tricky thing about CSS is that there are four ways to color something: background-color, fill, color and border-color.</p><p>Using the previous fallback code you will never need to specify the color of any element to be foreground except in the case that an element needs a background color of foreground. This is a rare case, but occasionally elements like dividers are just an empty div. To solve this we’ll make an element <strong>modifier</strong> that we attach to elements that require this behavior:</p><pre>.cp-default .bg-foreground {<br>    background-color: var(--cp-default-foreground)<br>}</pre><h4>Modifiers</h4><p>For every color other than background and foreground you need a modifier. Modifiers allow you to specify which elements require a color other than the default of foreground. If your color pair is large, this can be a lengthy process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-dU5VA27j9-cKxWDp24Pw.png" /><figcaption>It may look daunting, but it’s easier to manage than it looks</figcaption></figure><h4>Nested Components</h4><p>Not all components need a background color. When styling nested components don’t apply a color pair to an element that shares color pairs with its parent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-4QalH-M-AT4O0kK1nnizQ.png" /><figcaption>Over-applying color pairs can lead to confusing redundancy</figcaption></figure><p>Modifiers are used to overwrite element styles when necessary by adding an additional class to any foreground elements within a component:</p><pre>&lt;component class=&quot;cp-default&quot;&gt;<br>    &lt;read-button class=&quot;text-accentPrimary&quot;&gt;<br>        Read<br>    &lt;/read-button&gt;<br>&lt;/component&gt;</pre><pre>...</pre><pre>.cp-default {<br>    color: var(--cp-default-foreground);<br>    border-color: var(--cp-default-foreground);<br>    background-color: var(--cp-default-background);<br>}</pre><pre>.cp-default .text-accentPrimary {<br>    color: var(--cp-default-accentPrimary);<br>}</pre><p>Here, the read-button takes a new text color without using a new color pair.</p><h4>Layering Colors</h4><p>Some systems may require layering colors. Treat layered colors as another modifier using the background or background-image property:</p><pre>.cp-default .bgi-accentPrimary {<br>    background: <br>        linear-gradient(rgba(0,0,0,1), rgba(0,0,0,0)), <br>        var(--cp-default-accentPrimary)<br>}</pre><h4>Use Cases</h4><p>It’s important to outline the different types of color changes that might happen in your system so you can apply color pairs correctly. A default color pair is pretty self-explanatory:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ynKnQVCJQSVqHTg1Ws3R0g.png" /><figcaption>The default color pair is applied to all three cards</figcaption></figure><p>Changing a theme is a change to the default styles of a component. You can accomplish this by changing the values of the design tokens or by pointing to new tokens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H05gR0kl-Ld2VBh2btbghw.png" /><figcaption>Now the cards are using a “Dark mode” theme</figcaption></figure><p>Occasionally a single instance of a component will need a different color pair. A layout might require variation to break up repetitive content or content might require a different background color to stand out in a list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9sAu_XymW57aZDE3HqgEgg.png" /><figcaption>A component with a color pair that trumps the theme styling</figcaption></figure><p>If the change is required for the layout to be effective, the color pair should be configurable on the layout:</p><pre>&lt;component class=&quot;cp-accentblue&quot; /&gt;</pre><p>If the content requires the change, there should be a flag on the content that tells the component to change when it receives the flag:</p><pre>&lt;component :class=&quot;object.classOverride&quot;</pre><p>This was a common pattern in the local broadcast space as “Breaking News” often required a colored background to stand out among other content.</p><h3>Common Issues with Color Pairs</h3><p>While building our color system we made a few mistakes. Some of them are obvious, but others less so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_1K9k5m9G3IlY3OhsQF7kQ.png" /></figure><h4>Inverting Your Default Pair</h4><p>You might be tempted to just swap your foreground and background colors when you are creating a dark interface but always test them. Many colors do not perform the same when used inverted and a different color may be needed to achieve the affect you are looking for.</p><h4>Accessibility️️</h4><p>It won’t be covered in depth here but it’s important to say anyway: <strong>Always test color pairs for accessibility.</strong> Make sure that the color<strong> </strong><em>and</em><strong> </strong>the size of the text pass accessibility standards. Here’s an unsolicited plug for a simple tool:</p><p><a href="https://usecontrast.com/">Use Contrast</a></p><h4>Opacity</h4><p>Opacity can be a useful tool but its effects vary between different color pairs, especially when dealing with hues. When changing the opacity of an element be aware that swapping the element’s pair may cause the element to look more washed out than you initially intended.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NtHmC4mqbAW83BI0o5Ks1Q.png" /><figcaption>Opacity doesn’t always translate the same across different color pairs</figcaption></figure><h4>Create Boundaries</h4><p>Not every part of an interface needs to change when a user selects a theme. Parts of an interface may use a DoL scheme when in dark mode, just as every element doesn’t need to have a white background when in light mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NimIFna831p-wpl3_rYwCw.png" /></figure><p>For our articles, we used category pills with different background colors to denote what category an article was at a glance. We decided to only use the category pills on top of images so we didn’t have to worry about the background color clashing with an interface theme.</p><h4>Technical Problems</h4><p>There are a few edge cases to be aware of when using backgrounds that are not white for interfaces, although they’re unlikely to encounter unless you’re dealing with users uploading photos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/0*TDoTyqkv9tRFiDiO" /><figcaption><a href="http://www.graphicmania.net/creating-gif-images-without-white-borders-problem-in-photoshop-2/">Source</a></figcaption></figure><p>PNGs and GIFs with transparency bits instead of alpha channels are built to think that white is the natural background of any element and create white artifacts when blending colors into transparency. Using spatial anti-aliasing with text will cause you to encounter the same problem.</p><h3>The Future of Interface Color</h3><p>I’ve been trying dark mode for the past few weeks, and most of my applications already support it. This makes it even more jarring when an application I’m using doesn’t. So far, the two biggest offenders have been my internet browsers and mail apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O1nitNjM8-hyrJ1cyt-c_w.png" /><figcaption>Not the end of the world, but certainly jarring</figcaption></figure><p>This should be unsurprising; website &amp; email designers are not accustomed to this paradigm yet. There are whispers of a future where we can listen to device settings through media queries (<a href="https://twitter.com/sindresorhus/status/1004413215554428929?lang=en">cough</a> <a href="https://twitter.com/rmondello/status/1007400236514504706">cough</a>), but they don’t exist yet. In the mean time, design using color pairs to make the eventual switch painless.</p><p>As product designers, it’s our role to think about every instance of our product and how users perceive it. In a future where our websites and applications are meant to listen to user’s UI preferences, we should gladly accommodate them.</p><p><em>Many thanks to Michael Bachman, Lauren Banks &amp; Ashley Bauer for help on this project. Originally written in 2017, updated for 2018.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dde4d0018e4" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/systemizing-color-for-change-9dde4d0018e4">Systemizing color for change</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nuxt Prototyping: Storing Design Tokens & Dummy Data Globally]]></title>
            <link>https://blog.prototypr.io/nuxt-prototyping-storing-design-tokens-dummy-data-globally-adf97ab47eeb?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/adf97ab47eeb</guid>
            <category><![CDATA[nuxtjs]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 18:36:57 GMT</pubDate>
            <atom:updated>2018-10-26T22:59:28.417Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YeXvBVxWUALN3OnzjQzI0g.png" /></figure><p><em>If you’re unfamiliar with Nuxt or Vue I recommend reading </em><a href="https://blog.prototypr.io/prototyping-with-nuxt-vue-surge-456c4ae3d6e5"><em>my previous post</em></a><em> on the topic to get started.</em></p><h4>Design Tokens</h4><p>Often times when designing we use systems meant to extend throughout an entire application. CSS makes it easy to do this with <a href="https://medium.com/eightshapes-llc/tokens-in-design-systems-25dd82d58421">design tokens</a> but in component based JavaScript frameworks like Vue &amp; React, CSS is often distributed by default.</p><p>There are a couple of different ways to get around this. You can store your tokens in a higher-order component like a page or layout. You can also create a CSS/SCSS file in your assets folder and link to it in your Nuxt config file. The latter is what I recommend as it keeps your tokens out of your components.</p><p>To do this, create a new styles.css file in your assets folder. Open nuxt.config.js and find the css property of your module.exports . If you do not see one simply add one. Inside you need to provide a path to your styles.css file as a string:</p><pre>// ~/nuxt.config.js</pre><pre>module.exports = {<br>     ...<br>     css: [<br>          &#39;~/assets/styles.css/&#39;<br>     ]<br>     ...<br>}</pre><p>The tilde tells Nuxt to find the top level assets folder and the single quotation marks define the path as a string. The css property is an array, so you can list as many paths in it as you’d like. This is a great way to integrate a CSS reset into your application or separate your CSS tokens further.</p><p>Design tokens can be created with CSS or with SCSS. The main difference is that custom properties in CSS must be assigned to an element in the DOM. As long as you specify the highest-order element in your application you should be fine. I use :root as it ensures my custom properties are passed throughout my application.</p><pre>// ~/assets/styles.css</pre><pre>:root {<br>     --cp-indexcard-foreground: black;<br>     --cp-indexcard-background: white;<br>}</pre><p>Now I can reference these tokens in any of my components, layouts or pages.</p><blockquote>⚠️<br>If your development server was running before you added the link to your CSS file in your config you will need to <strong>restart your development server</strong>. To do this, close the console running your development server and start it again.</blockquote><h4>Storing Dummy Data</h4><p>Design tokens can also be stored in the same place as our dummy data: the Vuex Store. Vuex is built into Nuxt but not activated by default. The store is a collection of data that is accessible by all parts of your application.</p><p>To activate the store navigate to the store folder and create an index.js file. Inside the file paste the following:</p><pre>// ~/store/index.js</pre><pre>import Vuex from &#39;vuex&#39;</pre><pre>const createStore = () =&gt; {<br>    return new Vuex.Store({<br>        state: {<br>            <br>        }<br>    })<br>}</pre><pre>export default createStore</pre><p>Anything you place inside the state object will be accessible throughout the app. Here’s an example of some real article data from CNN:</p><pre>// ~/store/index.js</pre><pre>state: {<br>    articleList: [<br>        {<br>            title: &#39;The worlds largest organism is dying, but there are still ways to save it&#39;,<br>            timestamp: &#39;&#39;,<br>            description: &#39;Behold the Pando aspen clone, a sprawling carpet of vibrant green-yellow quaking aspens occupying more than 100 acres outside the Fishlake National Forest in Utah&#39;,<br>            imgUrl: &#39;<a href="https://cnn.it/2OBmcmp">https://cnn.it/2OBmcmp</a>&#39;,<br>            webUrl: &#39;<a href="https://cnn.it/2P8Dgzp">https://cnn.it/2P8Dgzp</a>&#39;<br>        },<br>        {<br>            title: &#39;Banning plastic straws is a little like spitting in the wind&#39;,<br>            timestamp: &#39;2 hours ago&#39;,<br>            description: &#39;The world is heating up dangerously and the oceans may be dying. In this context, the UKs proposed plan to ban plastic straws feels a little like spitting in the wind.&#39;,<br>            imgUrl: &#39;https://cnn.it/2EDd4cn&#39;,<br>            webUrl: &#39;https://cnn.it/2q7DAjX&#39;<br>        },<br>        {<br>            title: &#39;A new, cheaper Tesla model 3 is on its way&#39;,<br>            timestamp: &#39;1 day ago&#39;,<br>            description: &#39;Tesla is now offering a slightly cheaper version of its lowest priced car, the Model 3&#39;,<br>            imgUrl: &#39;<a href="https://cnn.it/2EB14rB">https://cnn.it/2EB14rB</a>&#39;,<br>            webUrl: &#39;<a href="https://cnn.it/2Cu56Q7">https://cnn.it/2Cu56Q7</a>&#39;<br>        }<br>    ]<br>}</pre><p>You can reference the data by pointing to the store from a component:</p><pre>// ~/pages/index.vue</pre><pre>&lt;template&gt;<br>    &lt;section&gt;<br>        {{ this.$store.state.articleList[0].title }}<br>    &lt;/section&gt;<br>&lt;/template&gt;</pre><pre>...</pre><p>Now your data is separated from the design! You can add articles to the list, change the order of articles or their contents all without digging through your components.</p><blockquote>⚠️<br>If your development server was running before you created your index.js file you will need to <strong>restart your development server</strong>. To do this close the console running your development server, and start it again.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ylCMBHJUNLPFCfFukeVlQ.png" /></figure><h4>Passing Data Down</h4><p>In the example above we’ve created a list of articles. When working with lists repeating the component code for each article can be tedious.</p><pre>// ~/pages/index.vue</pre><pre>&lt;template&gt;<br>    &lt;section&gt;<br>        &lt;article-card/&gt;<br>        &lt;article-card/&gt;<br>        &lt;article-card/&gt;<br>    &lt;/section&gt;<br>&lt;/template&gt;</pre><pre>...</pre><p>Vue can render lists using the v-for directive. V-for will tell Vue to make an instance of the component for each of our article objects and pass the object to the component.</p><pre>// ~/pages/index.vue</pre><pre>&lt;template&gt;<br>    &lt;section&gt;<br>        &lt;article-card <br>            v-for=&quot;article in this.$store.state.articleList&quot;/&gt;<br>    &lt;/section&gt;<br>&lt;/template&gt;</pre><p>Sometimes that’s enough, but if the data needs to be passed on to another component within the instance you’ve created you need to explicitly send and receive the data using props.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gnjsm47yj3R9mgFUaATUJA.png" /></figure><pre>// ~/components/article-card.vue</pre><pre>&lt;template&gt;<br>    &lt;section class=&quot;article-card&quot;&gt;<br>        &lt;ac-title/&gt;<br>    &lt;/section&gt;<br>&lt;/template&gt;</pre><pre>...</pre><p>Here’s an example of an article-card component that contains an ac-title component. In order for the ac-title component to access the title of the article-card, we need to declare the title as a prop and bind it to the article-card.</p><pre>// ~/pages/index.vue</pre><pre>&lt;template&gt;<br>    &lt;section&gt;<br>        &lt;article-card <br>            v-for=&quot;article in this.$store.state.articleList&quot;<br>            v-bind=&quot;article&quot;/&gt;<br>    &lt;/section&gt;<br>&lt;/template&gt;</pre><p>The initial component that receives the object can be bound to the individual props of the object or to the entire object. You can bind the entire object by using the name given to the object by the v-for directive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BpusdfmI67DZsToB0JTeYQ.png" /></figure><p>A good analogy for passing props is playing catch. Binding is throwing the ball, but you also have to catch it. You catch the ball by declaring the prop in the nested component. Both steps are always required to pass props between components.</p><pre>// ~/components/article-card.vue</pre><pre>...</pre><pre>&lt;script&gt;<br>    export default {<br>        ...<br>        props: [&#39;title&#39;],<br>        ...<br>    }<br>&lt;/script&gt;</pre><pre>...</pre><p>Declaring the title prop inside your components export function will register it as a prop. Now, you can bind it to the component, explicitly sending the prop to another component inside it. Individual properties can be bound using Vue’s colon syntax and require a name. It can be the same name or whatever you’d like.</p><pre>// ~/components/article-card.vue</pre><pre>&lt;template&gt;<br>    &lt;section class=&quot;article-card&quot;&gt;<br>        &lt;ac-title :title=&quot;title&quot;/&gt;<br>    &lt;/section&gt;<br>&lt;/template&gt;</pre><pre>...</pre><p>In order for our ac-title component to receive the prop, we must also register the prop in the ac-title&#39;s export function.</p><pre>// ~/components/ac-title.vue</pre><pre>...</pre><pre>&lt;script&gt;<br>    export default {<br>        ...<br>        props: [&#39;title&#39;],<br>        ...<br>    }<br>&lt;/script&gt;</pre><pre>...</pre><p>Now, we can reference the title inside the ac-title component:</p><pre>// ~/components/ac-title.vue</pre><pre>&lt;template&gt;<br>    &lt;section&gt;<br>        &lt;h1&gt;{{ title }}&lt;/h1&gt;<br>    &lt;/section&gt;<br>&lt;/template&gt;</pre><pre>...</pre><h3>Separated Concerns</h3><p>By keeping our data, structure and visual design code separate we can improve our oversight on a project. If you need to update your dummy data, head over to your store. Need to change a design token? Open styles.css. There are many different ways of implementing separation of concerns, but I’ve found this one works the best for me with Nuxt so far, and if another way works better for you I’d love to hear about it.</p><p>There’s a lot of things I skipped in here: how to write HTML/CSS, how components work in Vue or how to take advantage of Nuxt’s folder structure.</p><p>There’s plenty of resources on HTML &amp; CSS on the internet, and if you’re a designer just beginning to learn either I would highly recommend looking into <a href="http://cssgridgarden.com/">CSS Grid</a> &amp; <a href="https://flexboxfroggy.com/">Flexbox</a> — two alignment tools I wish I’d had when I was starting out.</p><p>I’m no engineer, so I’m under-qualified to teach anyone about the nuances of Vue or Nuxt. Instead, I can recommend my teacher <a href="https://www.udemy.com/user/maximilian-schwarzmuller/">Maximillian Schwarzmüller on Udemy</a> (this is not a sponsored post). His courses on Vue &amp; Nuxt helped me enormously, and I owe him a lot!</p><p><em>If you’re stuck or you have a question, drop a comment or message me! I’d love to help try to get you unstuck.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adf97ab47eeb" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/nuxt-prototyping-storing-design-tokens-dummy-data-globally-adf97ab47eeb">Nuxt Prototyping: Storing Design Tokens &amp; Dummy Data Globally</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Keeping Pumps Pumping]]></title>
            <link>https://medium.com/@tylermiller.is/keeping-pumps-pumping-5ff892b9feeb?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ff892b9feeb</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[material-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Wed, 10 Oct 2018 04:26:01 GMT</pubDate>
            <atom:updated>2018-10-15T16:46:56.143Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Communities in rural Tanzania depend on water pumped from wells — but keeping the water pumping isn’t easy.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1iQrQspj0qzn-ItQzU5Cmw.jpeg" /><figcaption>A woman carries water in Tanzania, via <a href="https://www.flickr.com/photos/cesar/3973283010/in/photolist-7477Bu-S8JKKm-24FGB1U-bnMYbq-dgHK1E-fh1PTn-Qh1YrG-Gay353-WhyDHt-CYcrNV-dV2EKT-d9WidC-21cA9Ad-23BgCeA-SWnwZK-oPkaAv-2vX7Je-9vSuyz-23JN4oE-23p9UE9-23bePtg-23Ft1ey-YcUMUw-22gdHgy-ZhF877-7YCFuB-zYdhKZ-GUQ3Na-NWoqUJ-9j4nFK-YhEeyY-Mivs29-DLYC5J-SY9XS2-mxXnMz-22WpQpf-T5ZDwR-8ScL6b-WpTKqZ-WuFpZg-P8ZaF3-MnjZ4y-y7YXHU-D8crdb-21BtJVA-y9MxoW-efDqS2-ZiNgce-rYa6kV-VzM1aa">Flickr</a></figcaption></figure><p>It’s easy to forget but every day clean water is pumped straight into our homes, while cell service providers beam overlapping signals to ensure we stay connected. But in Tanzania, neither of these things are a given — parts of the country lack well-developed plumbing and consistent cellular service. <a href="https://welldone.org/">WellDone</a> is a non-profit trying to help underdeveloped parts of Tanzania by building hardware that keep wells pumping clean water.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*fetuet2j-U4bUbtm.jpg" /><figcaption>The MoMo, or mobile monitor, tracks pump data.</figcaption></figure><h4>The Problem</h4><p>WellDone designed a solar-powered computer called the <a href="http://momo.welldone.org/">MoMo</a> to track the performance of pumps. The data is broadcasted to local engineers, who inspect pumps they suspect are malfunctioning. Engineers write reports to document what they find, logging their opinions alongside the data.</p><p>The data generated by the MoMos and the reports published by the engineers are available through an interface called the Strato Portal. The portal allows engineers to create automatic SMS notifications when thresholds are passed, for example if no water is pumped for 24 hours.</p><p>When WellDone approached CodePath, the only way to access the data was through the browser — limiting the scope of how WellDone could communicate with engineers. By developing a mobile application, WellDone hoped to provide data and tools to engineers regardless of where they were.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*HVW966cm1nex7bzk.jpg" /><figcaption>An engineer tests a well outfitted with a MoMo</figcaption></figure><h4>The Users</h4><p>Engineers analyzed data in the morning at their homes or workplaces (usually near cities) to decide which wells needed a visit. They would select equipment based on the data or reports before driving to the well —possible spending 30 minutes to two hours to reach wells that required assistance. Even upon reaching a pump, repair is not always possible, as each engineer has their own set of skills and tools. A report is drafted using a smartphone or whatever is on hand, and in most cases pictures are taken. The engineer then begins the trek home, submitting the report upon their return.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oEYXO_dO_f8YwA9sSWNnxg.jpeg" /><figcaption>The user journey had high peaks, but even deeper valleys.</figcaption></figure><p>We mapped out what we knew about the engineers, and from their journey we determined three major issues:</p><ul><li>Inconsistent access to data forces engineers to miss important updates to wells, transporting information manually to and from sites.</li><li>Engineers have no way of coordinating between themselves, be it on which wells to tackle or who has what ability/tools.</li><li>Traveling to and from pumps requires knowledge of roads and traffic that engineers have to source for themselves.</li></ul><h4>The Team</h4><p>Our team was connected to WellDone through <a href="https://codepath.com/">CodePath</a>, an educational organization that teaches programming in the evening over eight weeks. I joined the inaugural iOS for Designers course in 2014, where we learned how to use xCode and Objective-C to prototype applications. The course culminated in a group project, where members of CodePath’s different courses are work together to help a non-profit organization develop an application.</p><p>The team consisted of two designers, Mario &amp; Myself, two iOS engineers Robert &amp; Kasia and two Android engineers Aparna &amp; Rajat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZFZc8fRGnmP2XRqIhJ295Q.jpeg" /><figcaption>Excited about our final prototype! (From left: Mario, Myself, Kasia &amp; Robert)</figcaption></figure><h4>The Process</h4><p>With just eight weeks to design, develop and test our prototypes, we dove in. We spent the first week wireframing, determining what made the most sense. Due to the strict timeline and natural distance, we weren’t able to test our wireframes with actual engineers, so we asked friends and colleagues for feedback instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nB57dQ2j1IAaNTrSwsx5kA.png" /><figcaption>Initial wireframes for the MVP.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/321/1*R2h1R6xcIpUjjSjdaPwKQg.gif" /><figcaption>The first pass on our iOS application</figcaption></figure><p>The project required us to build a prototype of our application in Objective-C as well as in Java, keeping us conscious of platform differences throughout. Three of our four-person group were learning Objective-C, so our initial concepts focused on the iOS application.</p><h4>iOS</h4><p>The core of the application is managing pumps: viewing reports, creating reports, and navigating to pumps. We believed that the map view would be a focal point, although this would lead us to interaction patterns we would later discard as “too gimmicky”.</p><p>Using the map as a background for the application, the pump view became a component that could be swiped up and on to the screen when desired by the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*7ZVAke2-UfUfYscSq6x6Tg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*4JrKyr1mqR3a4_2pITBS2Q.png" /></figure><p>Swiping left or right would increment which pump you were currently viewing, while still enabling the user to manually orient themselves on the map by dragging and pinching.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*hoxtmq5-LGQ9TnrgUL20EA.gif" /><figcaption>Version two of our prototype</figcaption></figure><p>Our first pass was a lot of fun to prototype — but our unusual interaction patterns and use of UIBlurEffect was excessive. We toned it down, segmenting the main view, making the map one of two main views alongside the pump list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7FUUN9mpKVSKRHHE6v0jrw.png" /><figcaption>Version three of the iOS application</figcaption></figure><h4>Android</h4><p>Taking what we’d learned from the previous two weeks, we began translating the application to Android. We were excited — Android dominates the smartphone market in Africa, and had key features that would give us an edge against the poor data network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*HkLSygoCTj-5lAW9i8MpaQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*p0rvfK-_-SzNMF3zv3CWnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*anQmHk9bZjfYzq-Lq-iB6w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*zjjGFGvhgwcpdY8wXQREIA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*zVG_31jaxNvTsg8XYyuP_w.png" /><figcaption>Data coverage in Tanzania, via Cellmapper (From top left: Halotel, Airtel, Vodacom, Zantel, Combined)</figcaption></figure><p>SMS coverage is more consistent than data in Tanzania, and WellDone was already leveraging text messages to alert engineers to pump status changes using Strato. By encoding report data, the application could send &amp; receive reports via SMS. When an Android phone received an encoded message from a specified sender the application would decode the contents and create an updated report for a pump.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/473/1*4dwBNP8wn4PEvkn_xGP6Zw.gif" /></figure><p>Six weeks into the project and we had two functional, albeit messy, prototypes. Just as we’d begun the project Google announced Material Design, and not wanting to get bogged down in exploring the new system we had opted to work with KitKat’s design to make headway. Looking for opportunities to really shine at the public demo, we returned to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zEQ8MqR1w8k9CHu43RE_dw.jpeg" /></figure><p>Revisiting the design of the application we looked back over our original concepts, hoping to expand the functionality of our application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*R4XuzJRKniGiwbCiDjFftg.png" /><figcaption>Initially, 8 weeks seemed like a lot more time</figcaption></figure><p>With a bit of time to spare we chose to focus on rounding out status and notifications. Now, when an engineer adds a pump to their route, other engineers receive a notification and the pump’s status is changed to “in repair” — and other engineers would appear on the map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*24nyK0CBY2JDsqKV9JkcFQ.gif" /><figcaption>Recording of our final prototype in action!</figcaption></figure><h4>The Response</h4><p>At CodePath’s internal demo, we walked judges through our prototypes by casting the devices to a projector. With the SMS functionality built into the Android application, we were able to send an SMS during the demo, changing the application’s data in real time.</p><p>The judges loved it — and selected our Android application as a finalist for the public demo. Grateful to have more time to work on our application and emboldened by our success, we worked hard to break further ground, making sweeping changes to the look and feel of the application in the next two weeks.</p><p>Further impressed by the progress we’d made, the judges awarded our group with first place.</p><h4>The Next Steps</h4><p>For the sake of everyone observing during the demo, we had developed the application in English. English is commonly spoken in Tanzania, but the most common language is Swahili. Testing our designs in Swahili would be a necessary step moving towards production.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M2nePHVBnN_QqxTIX63jow.png" /></figure><p>Regrettably, we weren’t able to spend time exploring engineer profiles. If we had, we might have been able to help them organize further, allowing them to filter pump issues by required skills or tools that matched their ability.</p><p>CodePath was a great opportunity — and it was bittersweet graduating. Eight weeks sounded like a long time, but it was far too short. Like any good team, we became invested in our users’ happiness, and it was tough to not be able to push this project further.</p><p><em>Much thanks to CodePath, Mario Delgado, Robert Karl, Kasia Hayden, Aparna Jain, Rajat Bhargava &amp; Thomas Chen for help on this project. Originally written in 2015, updated for 2018.</em></p><p><em>If you’ve got a few dollars to spare, please consider donating to WellDone:</em></p><p><a href="https://welldone.org/">WellDone.org</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ff892b9feeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping with Nuxt, Vue & Surge]]></title>
            <link>https://blog.prototypr.io/prototyping-with-nuxt-vue-surge-456c4ae3d6e5?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/456c4ae3d6e5</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Thu, 04 Oct 2018 22:23:01 GMT</pubDate>
            <atom:updated>2018-10-10T08:52:04.870Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gmccZc_2Tgkt8cb5lM907Q.jpeg" /></figure><p>Prototyping is the second-measure in product design. I’m sure you’re familiar with the old adage “measure twice, cut once” — and if you aren’t prototyping, you aren’t measuring twice.</p><p>The main goal of prototyping is to <strong>get feedback from users faster</strong>. If you can approximate a product and still get positive feedback, you know you’re on the right path. Secondly, the act of prototyping forces you to describe the product in transitions, rather than in states. States are static snapshots of a product, representing a single point in time — transitions are everything in between.</p><p>The natural transition for a designer looking to prototype is to animate images. When I began prototyping, I made videos with After Effects and Photoshop. As I began doing increasingly complex animations, I started to realize the limitations of prototyping with videos. Videos play linearly, and are not interactive — whereas code is.</p><h3>Why write code?</h3><h3>Daniel Eden, In 🇬🇧 Edition on Twitter</h3><p>yes, designers should CODE C oordinate O utfits D ark colors E very day</p><p>As a designer, consistency is part of my job. I became fascinated with design systems over the past few years, and as I did I spent a lot of time researching different ways to codify design decisions.</p><p>The funny thing about codifying design decisions is: you’re programming. Coming up with a list of font sizes or colors? You’re describing an array of variables (or constants, if you’d rather). Are there toggle-able elements shared across multiple components? Sounds like a prop.</p><p>Understanding how different programming languages construct interfaces informs the way you speak about your designs. If you can communicate better with an engineer, you’ll see better results.</p><p>Every language is different, and what you learn here will not translate to Swift or Java. However, understanding these technologies should make it easier to understand others.</p><h3>Why these technologies?</h3><h3>skʌlkat on Twitter</h3><p>Using a fork of https://t.co/k6zhEvx45D to generate a scale of grays derived from brand colors then applying them to components.</p><p>I use web technologies for prototyping because they’re flexible. The web lives on your computer <em>and</em> on your phone — URLs just work. I can send a link to someone and all they have to do is open it.</p><p><a href="https://vuejs.org/">Vue</a> is a JavaScript framework, similar to React. Frameworks make writing JavaScript simpler. Similarly, <a href="https://nuxtjs.org/">Nuxt</a> is a Vue framework — it makes writing Vue applications easier. <a href="https://surge.sh/">Surge</a> is a tool that allows you to publish your code to the web in a very simple manner — you don’t even need to own a domain to do so.</p><blockquote>Before continuing, you should take time to read about these frameworks and try them out in online code editors like CodePen or CodeSandbox. You may prefer React, and wish to use <a href="https://www.gatsbyjs.org/tutorial/part-zero/">Gatsby</a> instead of Nuxt. That’s perfectly fine — but this article won’t work for you.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*5apjxAiAm_507Li5" /><figcaption>An unfortunate reality, via <a href="https://www.monkeyuser.com/">MonkeyUser.com</a></figcaption></figure><p>If you don’t understand what “single-command web publishing” or “progressive javascript frameworks” are, that’s OK. I didn’t understand a lot of it when I got started. What’s important is that you can still use this technology without understanding it, and you’ll understand it better by trying.</p><p><a href="https://medium.com/@tylermiller.is/using-code-to-design-1d7433a9e528">I cover installing the basics in a previous post</a>, and once you’re vaguely familiar with Terminal, Homebrew &amp; Node, you should continue. Installing the packages above is odd if you’re used to an application window popping up, because there is no interface, it’s just ~there~, in the background.</p><h4>Installing Surge</h4><p>Surge isn’t covered in my previous post, but it’s dead simple to install:</p><pre>npm install --global surge</pre><p>If you encounter an error here, add sudo before install.</p><h3>OK, so how do I prototype?</h3><p>Now that everything is installed, we’re ready to go — and you won’t have to do that again for a while.</p><h4>Creating a Project</h4><p>When you want to start a new prototype, you will need to create a new project using terminal. First, navigate Terminal to a location you’re comfortable installing the project in, like your desktop. Open a new Terminal window and enter:</p><pre>cd desktop</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B_eGzJQME3XMhF37Z_oa0A.png" /></figure><p>Then enter this:</p><pre>npx create-nuxt-app &lt;prototype-name&gt;</pre><p>Replace the &lt;prototype-name&gt; above with whatever you like. You’ll be asked a few questions:</p><ol><li>Project Name: hitting enter will use the name of the project you just entered</li><li>Project Description: add one if you wish, but it’s not required</li><li>Use a custom server framework: select <strong>none</strong> by hitting enter</li><li>Use a custom UI framework: select <strong>none</strong> by hitting enter</li><li>Choose rendering mode: use the down arrow to select <strong>Single page Application</strong>, then hit enter.</li><li>Use axios module: select <strong>no</strong> by hitting enter</li><li>Use eslint: select <strong>no</strong> by hitting enter</li><li>Use prettier: select <strong>no</strong> by hitting enter</li><li>Author Name: hit enter to use the default, or enter something different if you wish before hitting enter.</li><li>Choose package manager: you can use either here. I’ve been using NPM, so I recommend selecting <strong>NPM</strong> by hitting enter.</li></ol><p>Ten questions may seem like a lot, but it’s mostly hitting enter without thinking — You’ll get used to it, I promise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z341j2uy_8GnQ_HL8BU0JA.png" /></figure><p>Once you’ve answered these questions, your project will start initializing. You’ll see a new folder appear where you specified with Terminal.</p><h4>Seeing your Work</h4><p>Terminal will list a couple of commands after the project is initialized. For them to work, make sure to navigate Terminal to your new project folder:</p><pre>cd &lt;prototype-name&gt;</pre><p>A local server will allow you to see your project as you work. To launch the project locally, enter:</p><pre>npm run dev</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IspgBwngPw7yCM6nyZ3HAw.png" /></figure><p>When terminal finishes, head to <a href="http://localhost:3000/">http://localhost:3000</a> using your browser to see your prototype running! This URL will only work on your computer — in order to share the prototype, we’ll need to publish it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RRcFVXrn0d_WvNx6GNikLA.png" /><figcaption>This is the default content of create-nuxt-app. For extra credit, try to change the text.</figcaption></figure><h4>Publishing a Project</h4><p>To get it in front of a user on their own device, we need a URL — this is what Surge is for, and it’s super simple.</p><blockquote>Small sidebar: Surge is a tool for hosting static websites. We don’t really need to get any further into it, but it’s important to note that Nuxt can generate static websites, and that’s one of the reasons we’re using Nuxt with Surge.</blockquote><p>In order to generate a static website from your Nuxt project, use terminal to navigate to the project folder, then enter:</p><pre>npm run generate</pre><p>This will create a new folder inside the project called dist . It contains your static website. We’ll navigate to dist using terminal now:</p><pre>cd dist</pre><p>Then, we enter:</p><pre>surge</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k-ibxhcb2YEt3OalxpxtvQ.png" /></figure><p>Kind of anticlimactic, right? You can customize the body of your URL, or just use whatever random string they give you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UuC0GtZ94PsIskmHu4eptA.png" /></figure><p>That’s it! Try visiting that domain and you should see your website. If you see a Surge error, make sure you remembered to navigate to the dist folder before running surge. Send the URL to other people, ask them what they see, if it works, and what they think. Then give yourself a pat on the back — you just launched your first prototype using Nuxt &amp; Surge!</p><p>There’s a lot of things I skipped in here: how to write HTML/CSS, how components work in Vue or how to take advantage of Nuxt’s folder structure.</p><p>There’s plenty of resources on HTML &amp; CSS on the internet, and if you’re a designer just beginning to learn either I would highly recommend looking into <a href="http://cssgridgarden.com/">CSS Grid</a> &amp; <a href="https://flexboxfroggy.com/">Flexbox</a> — two alignment tools I wish I’d had when I was starting out.</p><p>I’m no engineer, so I’m under-qualified to teach anyone about the nuances of Vue or Nuxt. Instead, I can recommend my teacher <a href="https://www.udemy.com/user/maximilian-schwarzmuller/">Maximillian Schwarzmüller on Udemy</a> (this is not a sponsored post). His courses on Vue &amp; Nuxt helped me enormously, and I owe him a lot!</p><p><em>If you’re stuck or you have a question, drop a comment or message me! I’d love to help try to get you unstuck.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=456c4ae3d6e5" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/prototyping-with-nuxt-vue-surge-456c4ae3d6e5">Prototyping with Nuxt, Vue &amp; Surge</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Re-Imagining Television]]></title>
            <link>https://uxdesign.cc/re-imagining-television-b09d03a2030c?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/b09d03a2030c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[broadcasting]]></category>
            <category><![CDATA[interface-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[apple-tv]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 18:31:22 GMT</pubDate>
            <atom:updated>2018-10-11T00:44:26.726Z</atom:updated>
            <content:encoded><![CDATA[<h3>Re-imagining television</h3><h4><em>As more televisions become “smart”, local broadcasters are looking at how they can translate &amp; expand their TV experiences.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G2TVuNNbVPR3exSjj8ibcw.png" /><figcaption>Despite my best efforts, I couldn’t convince anyone that this was the right direction.</figcaption></figure><p>Globalization has turned our attention outward, empowering multi-national publications &amp; leaving home-grown institutions behind. Yet for much of the United States, local news is still preferred. Local anchors &amp; meteorologists are trusted sources of information — and rightly so: they have unparalleled access. Frankly builds tools that give local broadcast journalists an edge.</p><h4>The Problem</h4><p>“Cord-cutters” and Smart TV owners, once fringe groups, began to swell in the mid 2010’s with the advent of cheaper &amp; more sophisticated technology. By 2016, most popular programming was available without a cable bill — but local broadcasting lagged behind. Seeing a problem on the horizon, we sat down with our partners to discuss how to get local stations up to speed.</p><h4>The User(s)</h4><p>While the growth of Smart TVs &amp; cord-cutting is mostly attributable to newer generations, our partner’s audiences skew older (between 30–50 years old). Our challenge was to balance the user experience, enabling power users without leaving first-timers behind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fm_LkOO8okCLE_Fb8BGPFw.jpeg" /><figcaption>Interaction patterns vary wildly when it comes to television</figcaption></figure><p>Younger users prefer to watch in smaller stints, while older users watch for longer. Older viewers tuned in consistently, and were more likely to turn on the TV when they wanted to learn about a story. Younger demographics expected control; Older demographics expected the app to “just play”.</p><h4>The Team</h4><p>We were a four person team — one designer, one product manager and two iOS engineers. As the only designer on this project, I lead design end-to-end, although my colleagues on the design team lent their ears when I (often) asked. The team initially worked in parallel, contributing research from users, competition, thought-leaders and technical sources to establish requirements/restraints. Eventually, the team would expand to include external development teams as we began building the Amazon Fire &amp; Roku applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-4LEgugaanjQrvzWR3S1Q.png" /><figcaption>An early sketch of the application’s IA</figcaption></figure><h3>The Process</h3><p>We limited the MVP to Apple TV, aiming to work with as many native components as possible so we could launch the MVP as quickly as possible. If we were able to launch within a month, we’d have enough time to test it with focus groups and take a second pass before publicly launching.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*otBkmTdagun3vnxJa6LvOw.png" /><figcaption>Low-Effort MVPs are good places to start when in a time crunch</figcaption></figure><p>Our first pass looked a lot like any other Apple TV app — rows upon rows of rectangles. Viewers responded negatively to our prototypes, underscoring that watching the news was simpler — no navigation or selection was required once you dialed the channel. We’d been expecting this feedback, and were glad to validate it early in the development cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3x-MtkAHs0qxp5EHuPK2g.png" /><figcaption>Our Alpha ended up even simpler than we had planned</figcaption></figure><p>The words “just play” had stuck with us. We believed our TV application required two cornerstones to be successful: autoplay &amp; background playback.</p><p>Autoplay pulls the user into the experience immediately as the app opens, while background playback keeps the user immersed even while navigating. These features necessitated further interfacing: users need to know what videos are queued.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RaRRN1AStRxDgFNNH5O_qQ.png" /><figcaption>The queue tells you what content you’re watching and how many videos are queued</figcaption></figure><p>Accessible by swiping up while watching a video, the queue displays upcoming videos. Users are able to select another video if they find it more interesting. The queue fills with content that has the same classification as the currently playing video — content is classified through our platform’s CMS. We noted it would make sense to give the user a higher level of control in the future, such as adding and removing videos as desired, but at the time it was out of scope.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LC0_LF_rUk7tIndEghg7zw.png" /><figcaption>The new welcome experience</figcaption></figure><p>The second round of tests showed viewers were happier with the experience, but there was a pendulum effect: Apple TV regulars described the video-first experience as “jarring”. To combat this, the cold-launch experience was re-designed to let the user choose between instant playback or browsing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LPWYPUuygr4qbZsSdvIs6w.png" /><figcaption>Various cell sizes break down overwhelming repetition</figcaption></figure><p>Browsing was altered to include a variety of cell sizes, allowing partners to emphasize content while also making it easier on viewers’ eyes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iB2HBCYTmgp6d6bxSjYP6A.jpeg" /><figcaption>People love weather data — an example of the crowded initial interface</figcaption></figure><p>Weather was a challenge — TV is a poor medium for text-heavy content, and scrolling is difficult with the Apple Remote (and neigh impossible with Roku/Amazon).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4q-6I_6Rn3kpLnC12Rn6TA.png" /><figcaption>Simpler, but with all the same data</figcaption></figure><p>The initial design mimicked the tvOS native rows, but users were confused by the variety of cells and inconsistent navigation. Locking individual items into table cells proved problematic for modularity, too, as cells became overly tall or short as data points were turned on or off from the CMS.</p><h4>The Response</h4><p>We demoed the application at NAB in 2016 and stations began immediately reaching out to launch their own. By 2017, 80% of our partners had at least one TV app in their portfolio.</p><p>It can be difficult to measure the success of a new product as you aren’t measuring against a previous dataset. To track the effectiveness of our interface, we measured how often screens were visited in the two months post-launch. Search was the least visited screen, while Hourly Weather was the most viewed. The queue was called at least twice a session, and users selected a video from it almost every time. Session lengths averaged longer than we expected, though we suspect this was because we didn’t achieve the penetration in younger users that we were hoping for.</p><p><em>Much thanks to Michael Bachman, Edison Cruz, Lauren Banks &amp; Ashley Bauer for help on this project. Originally written in 2016, updated for 2018.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b09d03a2030c" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/re-imagining-television-b09d03a2030c">Re-Imagining Television</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Code to Design pt. 2: Git]]></title>
            <link>https://medium.com/@tylermiller.is/using-code-to-design-pt-2-git-a65ef3291ab7?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/a65ef3291ab7</guid>
            <category><![CDATA[code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[interfaces]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Sat, 10 Feb 2018 18:02:58 GMT</pubDate>
            <atom:updated>2018-02-10T18:04:04.583Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/@tylermiller.is/using-code-to-design-1d7433a9e528"><em>The previous Article can be read here!</em></a></p><p>As a designer, tracking work is a f#%king nightmare. The hype surrounding <a href="https://www.goabstract.com/">Abstract</a>, which launched earlier this year, was not misplaced. Git has always sounded dreamy, and while I’ve had some experience with it, a lack of workflow makes it difficult to break into.</p><p>I recently launched a website using GitHub Pages, which was pretty effortless. In doing so, i managed to use Terminal to clone the repository, make changes locally, create commits and push those changes back up to master.</p><p>I’ve used git before but things get rusty when you don’t use them, so I flipped back through the Code School x GitHub tutorial, which is a great way to get refreshed. By the end I was feeling very confident in my ability to actually use git.</p><p>I’ve peripherally heard that it’s poor practice to work directly on master, and just from a few years of working in tech I can understand why that’s the case. Unfortunately, working on branches currently makes it impossible for me to see the work I’m doing live. This is a huge disfunction for me, and so in order to go forward I’ll need to figure out how to see my work live, locally.</p><h4>Resources Used:</h4><ul><li><a href="https://try.github.io/levels/1/challenges/1">Learn Git in 15 minutes</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a65ef3291ab7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Code to Design, pt.1: Introduction]]></title>
            <link>https://medium.com/@tylermiller.is/using-code-to-design-1d7433a9e528?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d7433a9e528</guid>
            <category><![CDATA[code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[interfaces]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Wed, 17 Jan 2018 22:30:04 GMT</pubDate>
            <atom:updated>2018-02-10T18:06:01.817Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been attempting to teach myself to replace my design tools with code over the past year using Codepen and online tutorials to mild success,. I started this Medium series to keep track of my progress and hold myself accountable. I’ll return here to update and formalize any mistakes or errors so that this can turn into a reliable “how-to” document.</p><p>I now feel confident in my ability to structure HTML, style websites with multiple styling languages and understand the fundamentals of React. I lack a strong understanding of Computer Science and JavaScript</p><p><a href="http://codepen.io/">Codepen</a> has been a godsend for me, allowing me to progress without forcing me to learn more complex aspects of what I’m trying to do. In order to truly design with code, I need the following:</p><ol><li>Be able to create &amp; modify my development environment.</li><li>See my work in real-time.</li><li>Track my progress using GitHub.</li><li>Segment my work into manageable chunks.</li><li>Store data outside of the design.</li><li>Add and remove elements from a page.</li></ol><h3>#1 — Setting Up Development Environments</h3><p>A development environment is the ‘application’ for you to design within. The environment will contain all the functionality you need — and it is customizable. Digital designers are trained to open applications — programmers are trained to create their own. Sketch is changing this, but it’s still a little bit of a mental leap. I’ll refer to our development environment as the<strong> ‘design environment’</strong> once we get through the foundation.</p><h3>#1.1 —The Foundation</h3><p>There are a couple different layers when we look at a development environment. First, we’ll need to install ‘foundational’ software to be able to create our development environment. This software will be installed on your computer, and not need to be reinstalled with every project.</p><h4>Text Editor</h4><p>We’ll be using a text editor to write our code — there’s a ton of different ones out there, I was using Atom until recently when I was advised to check out Visual Studio Code by Microsoft “because it is faster”.</p><h4>Command Line &amp; Terminal</h4><p>Terminal is an interface that allows you to use command line to control your computer. Command line is like typing a message to your computer. We’ll use Terminal to set up our development environment.</p><p>We’ll start by using it to set up Xcode. Xcode is Apple’s developer tools, and will allow us to install more developer tools. You won’t interact with it much.</p><p>Open terminal and type:</p><pre>xcode-select --install</pre><p>Throughout this process, you may be asked to authenticate using your password.</p><h4>Ruby</h4><p>Ruby is required in order to install Homebrew, which I’ll describe next. macOS comes with Ruby already installed, which makes setting up Homebrew easy. I’m not entirely sure what Ruby does or why it’s needed to install Homebrew.</p><h4>Homebrew</h4><p>In order to get started, we’re going to need a package manager. A package manager simply installs software (read as “applications”). Homebrew will install the core functionality of our development environment: Node.js.</p><p>To install Homebrew, type:</p><pre>ruby -e &quot;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)&quot;</pre><p>Once this is complete, run this code to make sure it’s working:</p><pre>brew doctor</pre><p>You should receive a message that says “your system is ready to brew”.</p><p>Periodically, you may want to run brew-doctor and brew-update in order to keep Homebrew up-to-date.</p><h4>Node &amp; NPM</h4><p>Now that Homebrew can install our core functionality, we’re going to install our core functionality: <a href="https://nodejs.org/en/">Node.js</a>. Node is a JavaScript run-time environment, and it is going to be what we start to build our development environment with. This will ‘run’ our design, allowing us to interact with it.</p><p>Installing is simple:</p><pre>brew install node</pre><p>NPM is another package manager, specific to Node. It will help us install the specific functionality we want our development environment to have, similar to the plugins in Sketch.</p><p>Check that Node is installed and working by asking Node what version is installed: run node -v and npm -v.</p><p>You can update Node by running brew upgrade node.</p><h4>Bonus: Yarn</h4><p>Yarn is yet another package manager. It is a younger, hipper, faster version of NPM. I don’t understand enough about it to comment further, but I’ll be using it at the suggestion of my peers. I’ve heard it’s also best not to mix NPM and Yarn when installing packages.</p><p>Install yarn with:</p><pre>brew install yarn</pre><h4>Git</h4><p>Git is a version control system, used to track changes on files. GitHub hosts git repositories, and we’ll need it to use GitHub later, when we work on step #3.</p><p>Install it with:</p><pre>brew install git</pre><h4>CSS Pre-Processors</h4><p>Depending on a project, you may want to use a CSS Preprocessor like Sass or <a href="http://stylus-lang.com/">Stylus</a>. Preprocessors allow you to write CSS in different ways, and at runtime convert the CSS to vanilla CSS.</p><p>Some preprocessors require or allow for installation on your computer globally.</p><p>To install Sass globally:</p><pre>gem install sass</pre><p>To install Stylus globally:</p><pre>yarn add stylus -g</pre><h3>#1.2 — Project-Specific Tools</h3><p>Now that we have the foundational tools necessary to create our development environment, we can choose additional software to supplement it. We may use these tools with every project, or we may swap them out in certain circumstances. These tools are installed within a project however, and will need to be installed each time a new project is started.</p><h4>Webpack</h4><p>Webpack is a module-bundler that handles your dependencies for you. A dependency is a project-specific tool that is needed in order for the code to work properly.</p><h4>Vue.js</h4><p>We may choose to use a frontend framework like <a href="https://vuejs.org/">Vue.js</a> to our design environment. Vue is JavaScript framework for building user interfaces. Frameworks provide you with a template for your application. They are broader, attempting to encapsulate anything you could need.</p><h4>React.js</h4><p>Libraries, on the other hand, focus on making it easier for you to create your own application, but leaving much of that work up to you. <a href="https://reactjs.org/">React.js</a> is a well known library</p><h4>Bonus: Styled Components</h4><p><a href="https://www.styled-components.com/">Styled Components</a> is a JavaScript library that allows for styles to be saved in JavaScript instead of in a separate stylesheet. This is good for scoped styles that are not needed elsewhere in a design. I am not sure if Styled Components is meant to be installed globally or not, or if it is just installed in a project.</p><h4>Resources Used:</h4><ul><li><a href="https://www.howtogeek.com/211541/homebrew-for-os-x-easily-installs-desktop-apps-and-terminal-utilities/">Homebrew for OSX</a></li><li><a href="https://treehouse.github.io/installation-guides/mac/homebrew">Installing Homebrew</a></li><li><a href="https://treehouse.github.io/installation-guides/mac/node-mac.html">Installing Node.js</a></li><li><a href="https://www.w3schools.com/nodejs/nodejs_intro.asp">What is Node.js</a></li><li><a href="https://scotch.io/@brian_kimo/npm-vs-yarn">NPM vs. Yarn</a></li><li><a href="https://www.quora.com/What-is-the-difference-between-a-JavaScript-framework-and-a-library">What is the difference between a framework and a library?</a></li><li><a href="http://sass-lang.com/install">Installing Sass</a></li><li><a href="https://www.youtube.com/watch?v=o0xr1JRZOb4">Installing Stylus (~2:38)</a></li><li><a href="https://blog.envylabs.com/getting-started-with-webpack-2-ed2b86c68783">Getting Started with Webpack</a></li><li><a href="https://medium.com/front-end-hacking/what-are-npm-yarn-babel-and-webpack-and-how-to-properly-use-them-d835a758f987">What Are NPM, Yarn, Babel &amp; Webpack and How to Properly Use Them</a></li></ul><h4>Follow the series here:</h4><ol><li>Introduction — you’re already here</li><li><a href="https://medium.com/@tylermiller.is/using-code-to-design-pt-2-git-a65ef3291ab7">Git</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d7433a9e528" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Favorite Albums of 2018]]></title>
            <link>https://medium.com/@tylermiller.is/favorite-albums-of-2018-99de519f0ad4?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/99de519f0ad4</guid>
            <category><![CDATA[music]]></category>
            <category><![CDATA[2018]]></category>
            <category><![CDATA[album]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Sat, 13 Jan 2018 01:41:42 GMT</pubDate>
            <atom:updated>2018-01-16T20:38:53.000Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I had a lot of fun keeping track of this last year, so excited to kick this off again this year. I’ll be returning to this throughout the year to add — or remove — albums that stay in rotation.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*bXDh-YHUsI8VOHr-w6uyCw.png" /></figure><h3><a href="https://yazminlacey.bandcamp.com/releases">Black Moon</a>, by Yazmin Lacey</h3><p>Not quite an album, but an impressive solo flight from Yazmin. Lacey’s voice dances with the instrumentation, keeping your attention, but not distracting you. Great attention to album programming — excited to hear more from Yazmin.</p><p>Favorite Moments: Love the way she twists the title of <em>The Sun is Ours </em>in closing the EP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*MYN4pK2pSD4i5G1rNMn7ow.png" /></figure><h3><a href="https://porticoquartet.bandcamp.com/">Art in the Age of Automation</a>, by Portico Quartet</h3><p><em>Art</em> is cinematic, wide &amp; expanding. PQ strike a tone similar to seeing things from far away, making big things feel small and instilling awe.</p><p>Favorite Moments: The culmination midway through <em>A Luminous Beam.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*qmCRTJHixKT4aooftGqlvQ.png" /></figure><h3><a href="https://augustrosenbaum.bandcamp.com/album/vista">Vista</a>, by August Rosenbaum</h3><p>Interesting stuff brewing in Denmark between August, Coco O. &amp; Boom Clap Bachelors — fans of Kendrick might recognize the last name. Soul-ish jazz, calming introspection landing squarely between melancholy and uplifting.</p><p>Favorite Moments: Imaginary piña coladas in Belmondo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*7QzHKrlK7yu39dvG5jy0aA.png" /></figure><h3><a href="https://andreabelfi.bandcamp.com/album/ore">Ore</a>, by Andrea Belfi</h3><p>If one word can sum up this album it is tension — Andrea deftly builds it throughout each track, toying with your heartbeat.</p><p>Favorite Moments: There are a lot on this one, but the seemingly endless expansion around four minutes into <em>Lead</em> stands out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*HvSa7nEttt2kIjLTz8VmMA.png" /></figure><h3><a href="https://cosmic-compositions.bandcamp.com/album/--2">ज़ितम सिहँ</a>, by jitwam</h3><p>Also listed as <em>Selftitled</em>, jitwam’s first release showcases his exciting style across a spectrum of moods. An exciting blend of modern electronic styles, most notably beat tapes, he also draws from indie, jazz and funk. There’s truly something for everyone in here.</p><p>Favorite Moments: Distorted rhythms in <em>yesiknw</em>, twisted crooning in <em>alone</em> and acid-bent horns in <em>i ain’t scared of no devil</em>.</p><p>Last Updated: January 16th, 2018</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99de519f0ad4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Songs to Celebrate Life With]]></title>
            <link>https://medium.com/@tylermiller.is/songs-to-celebrate-life-with-d1a978b8d6d4?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1a978b8d6d4</guid>
            <category><![CDATA[music]]></category>
            <category><![CDATA[playlist]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Wed, 08 Nov 2017 03:54:44 GMT</pubDate>
            <atom:updated>2017-11-08T03:54:44.854Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FssmbArp01ns%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DssmbArp01ns&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FssmbArp01ns%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e2afef86c7d470c22e218447916b7f1c/href">https://medium.com/media/e2afef86c7d470c22e218447916b7f1c/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSVzfhlfIjxU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSVzfhlfIjxU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FSVzfhlfIjxU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/035b10a6440ce89a994719740fdd746a/href">https://medium.com/media/035b10a6440ce89a994719740fdd746a/href</a></iframe><p>This post is just beginning, check back for updates. You can subscribe to the playlist <a href="https://www.youtube.com/playlist?list=PLxfAtQ4aJ8jXnniH9RNtAbUir36KirR7o">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1a978b8d6d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Songs I Wanted to Buy Digitally Because I Didn’t Want to Buy the Whole Record]]></title>
            <link>https://medium.com/@tylermiller.is/songs-i-wanted-to-buy-digitally-but-couldnt-because-i-didn-t-want-the-record-872e76802870?source=rss-565cabdaade------2</link>
            <guid isPermaLink="false">https://medium.com/p/872e76802870</guid>
            <category><![CDATA[music]]></category>
            <category><![CDATA[techno]]></category>
            <category><![CDATA[house]]></category>
            <category><![CDATA[record]]></category>
            <dc:creator><![CDATA[Tyler Miller]]></dc:creator>
            <pubDate>Wed, 12 Apr 2017 06:09:46 GMT</pubDate>
            <atom:updated>2017-08-13T21:01:46.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/919/1*YLVuSVDInncyhJR8spU9KA.gif" /></figure><p><em>Just take my money 💸</em></p><p>Last updated August 12th 2017.</p><ul><li>Dubsons — <a href="https://soundcloud.com/trappedmusicldn/dubsons-cuburi-triunghiulareoriginal-mix-clip">Cuburi Triunghiulare</a></li><li>Ho Do Ri —<a href="https://soundcloud.com/ho-do-ri/ho-do-ri-portland-underground"> Portland Underground Gym</a></li><li>Rising Sun — <a href="https://soundcloud.com/rising-sun/b1-rising-sun-importance-live">Importance (Live)</a></li><li>Ally — <a href="https://soundcloud.com/art-feast/b2-kresy-ally-1">Kresy</a></li><li>Al Bradley —<a href="http://www.juno.co.uk/products/al-bradley-night-owl/638557-01/"> Night Owl</a></li><li>Shedbug — <a href="https://www.youtube.com/watch?v=s3ogZ2kc-cg">Mind Cloud</a></li><li>Roustam — <a href="https://www.youtube.com/watch?v=dpdRy5J14Eg">Fundamentally Wrong</a> &amp; <a href="https://www.youtube.com/watch?v=mg0F_Om_Y4E">My Bitchez</a></li><li>V.I.C.A.R.I. — <a href="https://www.youtube.com/watch?v=WLRJg4jYsIM">Unco Geno</a></li><li>DJ UFFE — <a href="https://oye-records.com/sgl.php?id=160299">Strange Brief Thing</a></li><li>DK Aakmael — <a href="https://www.youtube.com/watch?v=2dSYtUQKTXI">Deep Side</a></li><li>Orphidal — <a href="http://www.juno.co.uk/products/orphidal-moments/646018-01/">Black April</a></li><li>Groove Selecta — <a href="https://www.youtube.com/watch?v=MMyI9JDG7Nc">Hidden Agenda</a></li><li>Tone Series — <a href="https://www.youtube.com/watch?v=_WvDR7MPL1M">Machine Dream</a></li><li>Piyojo —<a href="https://soundcloud.com/thump/piyojo-pilates"> Pilates</a></li><li>Triptil —<a href="https://www.youtube.com/watch?v=cteR77lJ3Tw"> Oldiegoldie</a></li><li>Vincent Inc. — <a href="http://www.juno.co.uk/products/vincent-inc-antideepressant-ep/647821-01/">Wilder</a></li><li>Traumer —<a href="http://www.juno.co.uk/products/nick-beringer-traumer-jerome-c-kaleidoscopic-minds/649492-01/"> Bjorigine</a></li><li>Alex Font — <a href="http://www.juno.co.uk/products/alex-font-thirdstream-01/658376-01/">Musica Moderna (CDS Tribute mix)</a></li><li>Juniper —<a href="http://www.juno.co.uk/products/juniper-aramaic-ep/639923-01/"> Infinite Dub</a></li><li>Jose Lau —<a href="http://www.juno.co.uk/products/jose-lau-uprooted-soul-ep/659110-01/"> Mysterious Shaker</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=872e76802870" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>