<?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 J Rachel Pierce on Medium]]></title>
        <description><![CDATA[Stories by J Rachel Pierce on Medium]]></description>
        <link>https://medium.com/@jrachelp?source=rss-7ca1fc330bf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*19EnnvOf6OFgyIsWxAuLag.jpeg</url>
            <title>Stories by J Rachel Pierce on Medium</title>
            <link>https://medium.com/@jrachelp?source=rss-7ca1fc330bf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:50:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jrachelp/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[Get Local — UX Case Study on Moving Application]]></title>
            <link>https://jrachelp.medium.com/get-local-ux-case-study-on-moving-application-b991139b889e?source=rss-7ca1fc330bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/b991139b889e</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[J Rachel Pierce]]></dc:creator>
            <pubDate>Mon, 06 Dec 2021 04:04:42 GMT</pubDate>
            <atom:updated>2021-12-06T19:52:10.887Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0OMMAEiOeDH19ahd1DA7gQ.png" /></figure><h3>Get Local — A UX Case Study on Moving to a New City</h3><h4>Service Design ➡️ Product Design</h4><p>As a college senior, recruiting season is biting at my heels. How do I find a job? Where should I apply? And specifically, in <strong><em>what city</em></strong> should I apply? I soon realized that my anxieties were validated by similar questions coming from my peers.</p><p>I began thinking about the challenges associated with moving, even before thinking about comparing U-Haul prices — how does one know and feel confident in their decision of picking a new place to live?</p><p><strong>Here’s the solution I came up with to address this problem: </strong>An application that lets you explore neighborhoods using aggregated information from digital resources and input from local residents.</p><p><strong>Timeline:</strong> Approx. 3 weeks</p><p><strong>Tools:</strong> Figma, Google Forms</p><h4>OVERVIEW</h4><p>So how did I reach this solution? By practicing the art of empathizing with the user, doing research into the problem, and iterative design. Below, I split my work into five categories: Discover, Define, Ideate, Design, and Review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AbimPMolpFI3FOwjof03Og.png" /></figure><h4>1. Discover</h4><p>I started my discovery process by doing “desk research” into moving statistics, to really understand the scope of the market. Did you know on an average year, about 10% of Americans move? That’s over 30 million people. What surprised me more however, was the information on college graduates. With such large bodies of people all moving to relatively the same places, I started to think about narrowing the scope of my project, or at least the audience from <em>everyone</em> that moves, to just recent graduates and young families, as these were the two main demographics of people who move. With age, one is less likely to move.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rP2KJySXWJXpDY9d9uQsnw.png" /></figure><p>Check out my sources to the above statistics for more reading, (<a href="https://www.wsj.com/graphics/where-graduates-move-after-college/">this one</a> and <a href="https://www.movebuddha.com/blog/moving-industry-statistics/">this one</a>).</p><p><strong>The Survey — </strong>I conducted a survey through Google Forms for any-aged college graduate to take. I received 8 responses, with respondents ranging in age from 21 to 56. One of the main reasons you conduct surveys is to gain insight into the depth and breadth of your users and their attitudes/actions. I used their answers to then create design criteria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*45d5ZrWiXlyHmq0QqTTmIg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KIlzGvNTfypEcCPQ5XFoCw.png" /><figcaption>Two survey questions. 50% means half of respondents chose that answer.</figcaption></figure><blockquote>“What factors made you choose the location you did?”</blockquote><p>The top answer was affordability, followed by being close to work, and then good location/close to friends or family.</p><p>Using these answers, I gathered that if being affordable was a key component to their decision, it should be a feature highly emphasized in my application. <em>Maybe a dashboard that shows cost of living, average rent, and average home price in the area?</em></p><p>Additionally, if being close to work was also a strong component, then it would make sense to have a feature that can show neighborhoods by distance from a location, such as a work address. <em>Maybe a google maps integration that can filter neighborhoods by distance and average price?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YcH_UNrAlTSehfuPJLUt_Q.png" /></figure><h4>2. Define</h4><p>Now with a little more information, I needed to start to define the key user problems. So, I started to break down the challenges of moving. As with a lot of life’s problems, the challenges didn’t all boil down to one easy-to-identify reason. In order to help narrow down the root of the problem, I made a root-cause analysis.</p><p><strong><em>Root Cause Analysis </em></strong><em>— </em>A method of problem solving, with the primary aim to understand problems in terms of their causes. This will help us address the main problem, and not just the symptoms.</p><p>First, let’s define the problem: <strong>Why is moving to a new city difficult?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bd85saubGMfbgqwV2se6sQ.png" /></figure><p>Above, I identify three main pain-points:</p><ul><li>It’s difficult to find a good location</li><li>You might not know anyone</li><li>You have to change your routine</li></ul><p>I broke down each pain-point into several ‘causes’, for example: not knowing the neighborhood, it’s hard to find new places to meet people, it’s difficult to put yourself out there, it’s hard to adjust to a new environment, etc.</p><p>Then, I didn’t stop there. I kept asking why.</p><p><strong>Why</strong> is it difficult to find a good location? <em>Because I’m not familiar with the city.</em></p><p><strong>Why</strong> are you not familiar with the city? <em>Because I don’t live there or haven’t traveled there.</em></p><p><strong>Why</strong> would living there help you make your decision? <em>Because if I knew the area I would know what the best places are.</em></p><p><strong>Why</strong> would knowing the best places help you find a good location? <em>Because I want to live somewhere close to the things I prioritize.</em></p><p>Thus, by breaking down each problem to their root, I identified three pieces of the puzzle that my solution should include: access to local knowledge, a community, and an emphasis on the exciting parts of moving somewhere new.</p><p>With the information gathered from the survey, I wanted to hone in on the journey that a sample user group (college graduates) would take.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KYbKcY7ny3CudxJbg-_cWA.png" /></figure><p>Above, I wanted to dive into the journey from initial spark to acclimation. I talked with a graduate who moved to a new city about their journey, pain-points, and general experience.</p><p>I identified several key frustrations and challenges in this journey:</p><ol><li><em>Where to start finding reliable information</em></li><li><em>Difficulties finding a trusty worthy realtor service and/or roommate</em></li><li><em>The actual move itself, from the U-Haul to finding the first night’s dinner</em></li><li><em>Making new friends</em></li></ol><p>These let me further think of possible solutions that could address one or more challenges. A few ideas I floated around were a “Welcome to the City” onboarding, and alumni network connecting you to graduates of your university who live in the area, a moving survival guide with essential information and organization, and a social network to let people explore ideas and have meetups.</p><p>These ideas were all so big and could be explored much more thoroughly in their own right, so I chose to focus on the most important features that could be useful, and then develop the design of the application from that organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*brLE7vky9sMH2uJ801_mNw.png" /></figure><p>To help with this, I created a chart to help me understand what features were most important to include on a MVP. I had a limited time frame for this project, so some features would have to take the back-burner.</p><p><strong><em>MVP Prioritization Matrix </em></strong>— a useful method of prioritizing features based on impact of the feature, and the effort it takes to implement the feature.</p><p>With more clarification on what features to include, I transitioned to the design on my application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cSB-M_phuuFGOORFTOuRXg.png" /></figure><h4>3. Ideate</h4><p>I got to work creating wireframes of different screens. While I would like to flesh out the flow of the application, my timeline dictated that I could only develop a select few. So, I decided to focus on both desktop and mobile screens of the ‘landing page’, map, and dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U2DZGLbnSDaXwySC955IoA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MeH88MllszMcapw4j5hBgA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C8Nf3k0nDqMwNUEBGRUiNg.png" /></figure><p>These wireframes I’ve decided to show came from trial and error. I spent hours and hours sketching by hand different quick iterations before I finally settled on what screens I wanted to show and how they should look.</p><p>Challenges I faced during this process included:</p><ol><li><strong>What features to prioritize.</strong> I referred back to my research (<em>as any user-centered designer should do!</em>) to find that cost of living and affordability should take priority, including the feature on the map that can suggest neighborhoods within a certain distance from an address (i.e. your work).</li><li><strong>How to layout the information. </strong>I went for a side navigation that uses layers, as this is comparable to the way a city operates, split into different neighborhoods and boroughs, which are then divided into different communities.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_KiOgC79z5oA4BXl-VuL6A.png" /></figure><h3>4. Design</h3><p>Once the wireframes were completed, I focused on the visual identity of this application. As shown in the designs below, the content and layout primarily stayed the same, except for a few small points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P8jntXHLVK6I9mltVT53Rw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0OMMAEiOeDH19ahd1DA7gQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P3KsQpsbuBR6ehl_H10HeA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QRjcFq6cisLsxydmXNhevA.png" /></figure><h3>5. Project Insights &amp; Takeaways</h3><p>While I identified a large problem and broke it down into smaller pieces, it didn’t mean I can address it all. I struggled with figuring out how to capture all the elements that my research suggested would be useful.</p><p><em>Too many</em> <em>features is a problem in itself.</em></p><p>In future iterations, I would like to conduct more user research with a larger base of respondents, as well as design enough screens to prototype interactions.</p><p><strong>In the meantime, thank you for reading!</strong></p><p><em>Please feel free to drop your comments, ideas and feedback below or reach out to me at </em><a href="/service/mailto:jrachelpierce@gmail.com"><em>jrachelpierce@gmail.com</em></a><em> if you’d like to work together ☕️</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b991139b889e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NYC Trees and Property Values: Data Visualization]]></title>
            <link>https://jrachelp.medium.com/nyc-trees-and-property-values-data-visualization-c94ca35da042?source=rss-7ca1fc330bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c94ca35da042</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[keplergl]]></category>
            <category><![CDATA[nyc]]></category>
            <category><![CDATA[tableau]]></category>
            <category><![CDATA[trees]]></category>
            <dc:creator><![CDATA[J Rachel Pierce]]></dc:creator>
            <pubDate>Mon, 12 Apr 2021 22:52:06 GMT</pubDate>
            <atom:updated>2021-04-13T18:52:47.620Z</atom:updated>
            <content:encoded><![CDATA[<p>Using the <a href="https://www.kaggle.com/nycparks/tree-census?select=new_york_tree_census_2015.csv">2015 NYC Tree Census</a> and <a href="https://www.kaggle.com/new-york-city/nyc-property-sales">NYC Property Sales</a> datasets from Kaggle, I wanted to explore the environmental and economic correlations between trees and property values by zip-code. For the visualizations I used Kepler.gl and Tableau.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eA0kBUtUpxlHq7pU50hw4A.png" /><figcaption>A map of every tree recorded in the 2015 census, by species. Using Kepler.gl</figcaption></figure><h3>Overview of Trees</h3><p>In my initial data analysis of the Tree census dataset, I determined the zip codes with the largest number of trees, which fall into the Staten Island borough.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*PfGJuY4PPcSqiC212-dYtw.jpeg" /><figcaption>Number of Trees by Zip Code. Using Tableau</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*uV1mk0MHavu4tesHrt-THA.jpeg" /><figcaption>Total trees per borough. Using Tableau</figcaption></figure><p>However, Queens has the highest total number of trees at 250,551 with 133 unique species, representing about 37% of all recorded trees in New York City. It is important to note here that the dataset <strong>does</strong> <strong>not</strong> count trees which are within designated parks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*NODLsEuE3cfK_svj4lnrDw.jpeg" /></figure><p>The next goal of my exploration was to determine the most common species of trees, and in which borough are they most populous. The London Planetree represented about <strong>12.7%</strong> of all trees, followed by the Honey Locust at <strong>9.4%</strong>, the Callery Pear at <strong>8.6%</strong>, the Pin Oak at <strong>7.8%</strong>, and Norway Maple at <strong>5%</strong>.</p><h3>Species Visualizations</h3><p>A series of visualizations to illustrate the species of trees by location in New York City. The first map features a cluster plot of the top species within the area. The following feature the top 5 most common species. Four out of five of them correlate relatively strongly with certain areas of the city, except the Pin Oak which appears in the same quantity all over.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zs_ONgEvuVvdLnWsfrzNLA.png" /><figcaption>Cluster Map of Quantity and Species (purple: London Plane Tree, pale yellow: Honey Locust, darker yellow: Callery Pear, red: Norway Maple). Kepler.gl</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yqo6phk6aYXaxxe5poAIDQ.png" /><figcaption>London Planetree. Kepler.gl</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XOyeJT2LxYjXx-41zbizTw.png" /><figcaption>Honey Locust. Kepler.gl</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODpvr8gHkqsL7HZQskpcYw.png" /><figcaption>Callery Pear. Kepler.gl</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fuWJRpGOjB7pUl6lwrMZCg.png" /><figcaption>Pin Oak. Kepler.gl</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9GTfXQBo9uiDQXCQ0dnW1Q.png" /><figcaption>Norway Maple. Kepler.gl</figcaption></figure><h3>Tree Conditions</h3><p>Some of the census data included information about the status of the tree (poor, fair, good) and its condition (alive, dead, stump). Additionally, the diameter of each tree is recorded, seen in the third image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Uu7hziH0ArVJVMHdT2IJQ.png" /><figcaption>Trees marked being in “poor” health. Kepler.gl</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UC8UHORJO6_jxul9g7Dvig.png" /><figcaption>Heatmap of dead trees. Kepler.gl</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*BbEpzlFFToLMKbTuAGm5ag.jpeg" /><figcaption>Average tree diameter by zip code. Using Tableau</figcaption></figure><h3>Economics?</h3><p>I originally sought out to find a correlation between the tree census data and demographic and economic makeup of the city. The first map I made separate of any tree data is a visualization of the average property sale per zip code in 2016.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gANrB5FDpdXBgpHfQWjJ6w.jpeg" /><figcaption>Property Sale Averages by Zip Code. Using Tableau.</figcaption></figure><p>My first observation is that this map is a near inverse of the tree diameter map; the higher the average property sale, the less likely the tree is larger. This correlation could closely align with the density of infrastructure, and/or the age of the trees and developments. Additionally, the Norway Maple map also appears to be an inverse, closely aligning with the diameter map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*IJqbCHlfUYLf0N4laIMz3g.jpeg" /></figure><p>Above is a map of the average year the buildings being sold were built. All of these observations lead to me to ponder a few possibilities for these results. Is the species of tree tied to the infrastructure of an area; i.e. are smaller trees more likely to be planted in areas with many skyscrapers and high density, or are they younger as these developments tend to be? Are some species more likely to be ‘pricey’ or add higher property value than others?</p><p>These questions cannot be answered with the scope of this project — but the visualizations and data do provide interesting insight into the environmental and economic makeup of New York City.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c94ca35da042" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Very Quick Evaluation of Twitter’s Web Interface]]></title>
            <link>https://jrachelp.medium.com/a-very-quick-evaluation-of-twitters-web-interface-e9ee006f4d79?source=rss-7ca1fc330bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9ee006f4d79</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[interfaces]]></category>
            <category><![CDATA[digital-product]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[twitter]]></category>
            <dc:creator><![CDATA[J Rachel Pierce]]></dc:creator>
            <pubDate>Thu, 28 Jan 2021 03:36:39 GMT</pubDate>
            <atom:updated>2021-04-20T05:55:45.515Z</atom:updated>
            <content:encoded><![CDATA[<h3>Twitter’s Website — an Evaluation of Form</h3><h4>TL;DR: Twitter’s website needs some updates in navigation, layout, and responsiveness.</h4><figure><img alt="Screenshot of the “write tweet” box before anything is written." src="https://cdn-images-1.medium.com/max/790/1*rw0Bu0TqwHJxS_jG79teqg.png" /><figcaption>A tweet ready to be typed.</figcaption></figure><h4>A Website for an App</h4><p>With<a href="https://developers.google.com/web/showcase/2017/twitter"> 80% of Twitter usage occurring on a mobile device</a>, an evaluation of Twitter’s web interface offers a unique perspective on the social media giant.</p><h4>What is Twitter Trying to Accomplish?</h4><p>Twitter was founded in 2006 with the mission statement: “to give everyone the power to create and share ideas and information instantly without barriers.” Using this goal, we’ll explore how Twitter upholds (or fails to uphold) their mission by looking at the effectiveness of the platform’s services, navigation, and layout on its web application.</p><blockquote>“. . . to give everyone the power to create and share ideas and information instantly without barriers.”</blockquote><blockquote><a href="https://investor.twitterinc.com/contact/faq/default.aspx#:~:text=The%20mission%20we%20serve%20as,a%20free%20and%20global%20conversation."><strong><em>Twitter’s mission statement</em></strong></a></blockquote><p>If you look at the different social media apps — Facebook, Instagram, and Snapchat — Twitter fulfils a niche that these other apps don’t: <strong>short content posts</strong>. A limited 280 character count and limited images allowed per tweet creates a need to be ingenious<strong> </strong>by saying the most in a short space. The focus is not inherently meant for posting and curating a photo gallery (Instagram), or sending quick images to friends (Snapchat), or even for longer, blog-like posts (Facebook). In the nature of social media apps, the app version tends to be more functional and easier to navigate than its website, which we especially see in Twitter.</p><h4>Exploration in Responsivity &amp; Intuitiveness</h4><p>I tested the interface on various screen sizes (full laptop screen, resized to half-screen, and again on a larger monitor) because a website in 2021 <em>needs</em> to work cohesively between different screens and display sizes — and there were noticeable variations between my 13&quot; and 22&quot; screens. These variations included differences in what icons are included in the navigation and the distribution of space.</p><p>That said, regardless of screen size, both of these areas are part of larger problems with the web interface.</p><p>First, the left-hand navigation is too convoluted, redundant, and confusing. Second, the website is divided into three columns, each taking up an inefficient amount of space on the screen.</p><figure><img alt="Screenshot of Twitter’s website from smaller laptop screen" src="https://cdn-images-1.medium.com/max/1024/1*EiuDsI5gbXCz_JpuX3NOfQ.png" /><figcaption>A screenshot from my laptop’s 13&quot; screen.</figcaption></figure><p>Let’s start at the navigation, just look at it. There are <em>nine </em>different icons on the left-hand side (even more on the larger screen). As a web user, this can be very confusing without any text to guide us, (which does appear on a larger screen). Some points of conflict:</p><ul><li>The icon of a person goes to the user’s own account, but the icon of a person at the bottom is for switching accounts.</li><li>The blue bird icon and the home button right under it both take you to the home page, something that could be consolidated.</li><li>Making the window smaller adds a search magnifying glass icon that replaces the hashtag icon.</li></ul><p>Additionally, the distribution of space is awkward. The main timeline of content is small relative to the webpage, which is especially true with the smaller screen size. The other column containing the larger blocks “What’s Happening” and “Who to Follow” are nearly two-thirds the size of what should be the most essential part of the website. The “What’s Happening” column and the navigation stay in place on scroll; the timeline is the only section that continues to move, creating an awkward moment of viewer interaction.</p><figure><img alt="Screenshot of Twitter’s website from larger monitor" src="https://cdn-images-1.medium.com/max/1024/1*tvlx9NK-YzW3gI1sioudXQ.png" /><figcaption>A screenshot of Twitter from my larger, 22&quot; monitor.</figcaption></figure><p>For the larger screen size as shown in the above screenshot, the navigation has text for each icon (a few different icons than the smaller screen though) and the timeline and the right column have a slightly better proportion. But the main thing to note: the amount of white padding around the main content. This space could be better distributed.</p><h4>A Suggestion for Improvement</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*PzjfY2sVPN3nUPmnWjDQKw.png" /></figure><p>Above is a possible rearrangement of the website’s flow. My suggestions include enlarging the timeline in comparison to the “what’s happening” section, moving the navigation from the side to the top right and consolidating the amount of icons, and moving the search bar to above the content.</p><h4>Some Final Thoughts</h4><p>The main critique I put forward for Twitter’s web interface is the layout of the site itself. Besides this semi-unresponsive navigation and awkward spacing, the website is <em>functionally</em> very much like its app counterpart.</p><p>In some way it makes sense that mobile application is easier and more pleasant to use than the website: the main users are young, <a href="https://blog.hootsuite.com/twitter-demographics/#:~:text=More%20than%2080%25%20of%20Twitter&#39;s,7%25%20vs%208%25">44% of U.S. adults aged 18–24 use Twitter</a>. Twitter’s interface efforts seem to be focused for the mobile device, leaving their web application somewhat awkward in flow and subpar intuitiveness of navigation.</p><p>Overall, for a company whose primary purpose is to be a mobile app, their website isn’t half-bad for usability. My final remarks: the navigation could be consolidated, and the white space should be better utilized with greater consistency across screen-size.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*ucqSziHawwfOjHD4Fe_5hg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9ee006f4d79" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>