<?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 CJ Huang on Medium]]></title>
        <description><![CDATA[Stories by CJ Huang on Medium]]></description>
        <link>https://medium.com/@cj-huang?source=rss-ffea3adc8862------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-HYpA6dJu-8kFtV6</url>
            <title>Stories by CJ Huang on Medium</title>
            <link>https://medium.com/@cj-huang?source=rss-ffea3adc8862------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 07:04:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cj-huang/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[玩龍與地下城的機器人]]></title>
            <link>https://cj-huang.medium.com/%E7%8E%A9%E9%BE%8D%E8%88%87%E5%9C%B0%E4%B8%8B%E5%9F%8E%E7%9A%84%E6%A9%9F%E5%99%A8%E4%BA%BA-c1c4caff0ddb?source=rss-ffea3adc8862------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1c4caff0ddb</guid>
            <dc:creator><![CDATA[CJ Huang]]></dc:creator>
            <pubDate>Mon, 05 Sep 2022 18:32:48 GMT</pubDate>
            <atom:updated>2022-09-05T18:37:43.646Z</atom:updated>
            <content:encoded><![CDATA[<h4>記漫遊賽博龐克之旅</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-jn_iQYUDtoFUzlb2qi4SA.jpeg" /><figcaption><a href="https://store.steampowered.com/app/1332010/Stray/">《<strong>Stray</strong>》是一款由法國開發團隊BlueTwelve開發的第三人稱冒險遊戲</a></figcaption></figure><p>這兩個月沉溺在新工作中，甚至忘了美國勞動節我有四天的假期。沒有規劃、這個夏天熱到炸裂、又看到網路上對這款新遊戲的評價，想想不如下載“Stray”到賽博龐克的世界中探險吧。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WI3PxlKltwBfZty0yYXnsg.png" /><figcaption>Rutger Hauer’s ‘Tears in the Rain’ From Blade Runner</figcaption></figure><p>自大學時期看了銀翼殺手後，賽博龐克這個迷幻的反烏托邦世界就深深吸引著我；仿生人與人類共存、陰暗潮濕的大城市、科技發達卻有著巨大的貧富差距、因為開發過度而造成空氣汙染劇烈……。身為互動產品設計師，在這個想像的世界中漫遊總能啟發對科技與哲倫的想法。我想熱愛賽博龐克的朋友們大概也都是著迷於無數生命在這個世界裡為了生存的奮鬥與掙扎、著迷於它們為了自我的信念在進退兩難中的取捨與抉擇。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qp4DHjlwPE9-gY5LhrHZhg.png" /><figcaption>貓的局外人視角是一個絕佳的設計</figcaption></figure><p>儘管許多工作室已經嘗試利用此世界觀開發遊戲讓粉絲們遨遊，這款“Stray”獨一無二的概念讓它在Steam上目前獲得了10/10的成績。正如其名“流浪”，玩家在遊戲中扮演一隻從上層世界不小心跌入底層的貓咪；此設定讓我嘖嘖稱奇；貓咪的身材與靈敏穿梭的特性成為了在賽博龐克這巨大壅擠的城市中漫遊的最佳選擇。在這個人類絕跡的世界中，曾經的伴侶機器人竟開始學習人類的生活模式與文化，有機器人愛上了街舞、大啖記憶體拉麵、冥想瑜珈、甚至為了龍與地下城而爭吵……。貓咪這個局外人的視角完美地滿足了人們對賽博龐克裡各個活靈活現人物的好奇心。身為一隻貓，玩家也無須為了裝備或是技能點而操心，開發者將重點體驗放在流浪的本質，記錄故事、品味各個城市才是這個遊戲的重點。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*76C_ABYOuPUt-wq-19VXXw.png" /><figcaption>身為一隻貓咪看的到的地方都到得了吧</figcaption></figure><p>我對這款遊戲的幾個抱怨是遊戲太短、城市太少、沒有攝影機。要怪就怪在環境藝術家把這個遊戲做得太美了，每個轉場細節幾乎都是底片殺手，讓我在邊玩的過程拍了好多照片留念。這邊放了幾張，怕雷的人可以跳過。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VhglVX22GCW37pcosmPJAA.png" /><figcaption>冰冷寂寥的舊機器不知多久沒人使用了</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XwReezcQ7_iNRdsiFzKsMQ.png" /><figcaption>被細菌感染的地區和可愛貓咪成了巨大對比</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LMVBtsTE9p0SlZ6qG07DOg.png" /><figcaption>我最愛的下水道城市</figcaption></figure><p>另外遊戲的劇情大致上都是預料之內。由於賽博龐克作品中常見的故事元素大概都被涵蓋在遊戲中，對我而言驚喜度沒有太高。這大概是把兩面刃；賽博龐克迷們八成能猜測到劇情走向，然而如果想給他們最原汁原味的世界體驗似乎也只能這樣編排故事？然而作為一個不到八小時就能通關的獨立工作室遊戲，這樣的產品仍應是接近滿分的吧。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1c4caff0ddb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visualization of Cryptocurrencies for Novice Users]]></title>
            <link>https://medium.com/visumd/visualization-of-cryptocurrencies-for-novice-users-3a2d34944fd1?source=rss-ffea3adc8862------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a2d34944fd1</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[visualization]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[CJ Huang]]></dc:creator>
            <pubDate>Tue, 15 Dec 2020 03:43:03 GMT</pubDate>
            <atom:updated>2020-12-23T05:40:23.433Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By </em><a href="https://cj-huang.medium.com/"><em>CJ Huang</em></a><em> and </em><a href="https://areddy6.medium.com/"><em>Arjun Reddy</em></a></p><p>Blockchain technology has become more and more popular after the emergence of Bitcoin. Cryptocurrency is one of the implementations of Blockchain, which has been benefiting over a 100 million people. However, the majority of people don’t have the chance to get to know this revolutionary technology. Therefore, most people don’t feel safe about it, although security is one factor cryptocurrency users have been advocating. Our motivation was to present cryptocurrency players and dynamics in a consumable and engaging mode.</p><h3>Goal</h3><p>Our project’s goal is to present a clear and unique view of the blockchain industry. By providing an interactive visualization of how blockchain plays a role in varied fields, we aim to create a traversable platform for intermediate users to understand better how blockchain implementations play a role in these domains.</p><h3>Sketching</h3><p>We looked at the industry category after traversing the block visualization represented by <a href="https://cryptorank.io/heatmaps">Cryptorank.io</a><strong> </strong>and other crypto ranking sources. With the top 1000 companies having different segments in the diagram, we manually tracked these to 52 industry categories. To further narrow our scope we were able to get a dataset for the domain category of currency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GWUDdJg_-p4UqpJa" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SBMG9KJmgeVre-WU" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NtKCCcZuuhl3M6K6" /><figcaption><strong>From left to right: Sketch 1, Sketch 2, Sketch 3</strong></figcaption></figure><p>With some help with how the table information displayed the data, we recreated these data points within our first sketch. We created a preliminary sketch (Sketch 1) of how the cryptocurrencies could be mapped using a radial visualization. Aided by the channels of color, position, and depth, our first sketch attempted to use different layers but with each layer visualizing price, net profit/loss (within a time span, for example — 24 hours or 7 days), Market Cap, Volume and Circulating Supply. These features would be mapped according to the central segment, which in this case is currency.</p><p>The strength of utilizing a radial map is that they offer a more presentable narrow scope of the data relative to boxed treemaps. Within the scope of each category, we can use the fields of position and depth to indicate multiple points of data for a single blockchain cryptocurrency. However, one of the weaknesses of this type of radial diagram is that more blockchain cryptocurrencies can take up additional segments within the circle. Additionally, there are some major players with significantly larger stats (For example- Bitcoin), and this segment share could affect the amount of information or distort the volume.</p><p>We further explored a more organized presentation of the categories in Sketch 2. In this sketch, the base circle is separated by sectors that represent different categories. Every round shape on the base circle is encoded by a dataset of one cryptocurrency. The area of this circle is decided by its Market Cap, whereas the distance from the center indicates its volume. The color of the circle(green and red) shows the positiveness and the negativeness of the price change. This design’s strength is that it shows the whole picture of the blockchain industry at a glance. Yet, the details of each cryptocurrency will not be easily recognized since there would be too many round items on the visualization at the same time.</p><p>Drawing from the ideas of Sketch 2 and Sketch 1, we created another sketch (Sketch 3) with a slightly different approach. The radial map would be divided into how many ever cryptocurrencies we choose to filter (in our data set for currency, top 100). The color of the segment would indicate a net profit or loss. For example, if the bitcoin currency has a net positive profit, it would be green. If it’s a loss, it would be indicated in red. The circumference allocated to each segment would be subject to the volume, market capital, or category. On hovering over a particular segment, the segment could expand depending on the visualization. We are also thinking of including a hoverable tooltip indicating the cryptocurrency, its price, volume, circulating supply and net gain/loss.</p><h3>Beta Release</h3><p>After cleaning the data to reflect our areas of concern, we played with multiple variables (In tableau) to recreate different types of data visualizations. In doing so, we attempted to connect the variables that showed significant differences in our visualization. We noticed the initial players in the rankings to have a significant distinction from the rest of the currency types. For example, Bitcoin had a substantial distinction from the others when it came to price, volume, and market capitalization. With this in mind, we diverged to create our prototype visualizations using two approaches. The first was to roughly map out our sketch using Adobe Illustrator to capture our data set. This gave us an opportunity to discover what kind of filters might work with the viz and how many data points could be expressed clearly at a glance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U8lIs-GThggY5Ig4" /><figcaption><strong>Fig 1:</strong> Rough Digital Illustration (Data not accurate) depicting the top-ranked currencies using a radial visualization. Here the color denotes either an increase (green) or a decrease (red) in performance, with the amount of area in the segments being depicted as the price.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FkiO_nI2j-nSv8vG" /><figcaption><strong>Fig 2:</strong> Rough Digital Illustration (Data not accurate) depicting a bubble diagram. The four domains are selected using the filters. Here the distance from the center denotes the volume, the size of the bubble reflects the price, and again the color represents performance.</figcaption></figure><p>These diagrams were created from the dataset but were produced by hand; they do not accurately represent the data since the entire viz was created manually on Adobe Illustrator. This was a precursor to understanding the contrasting data points and significant differences that existed within our data set. Some of the limitations of this were that only a certain amount of information could be depicted at a glance and that some of the data points were near negligible in contrast to larger data points. This was somewhat reflected in our next approach.</p><p>After this, we attempted to reinforce our understanding of the data using Tableau. In Fig 3-Tableau implementation 1, we tried to emulate the bubble-like illustration from Fig 2. The size of the circles represents the market capitalization and the distance from the left shows the volume of each cryptocurrency. Although this implementation strives to reproduce our design, we cannot show all the data points to our readers in one glimpse without scrolling. Trying to make it a radial layout might make the communication more efficient, yet it would also be a challenge for our final release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fnpgstlV_iuJitp7" /><figcaption><strong>Fig 3:</strong> Tableau Implementation 1</figcaption></figure><p>We tried to implement the data points in Fig 1 as a stacked bar graph in Tableau. In Fig 4, the orange bar represents the share in market capital, whereas the blue bar stacked on the orange bars shows the volume of each cryptocurrency. Bar graphs are always a preferred methodology in statistics and data viz because they are simple and easy to read. The shortcoming of this visualization, however, is similar to Fig 3 in that the readers cannot see all of the data points at a glance without scrolling to the right because the dataset is too big. Additionally, the currencies with smaller values cannot be seen at all. For example, BAL and BAND aren’t depictable in the graph.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zav8JJ2vQjqHrjYj" /><figcaption><strong>Fig 4:</strong> Tableau Implementation 2</figcaption></figure><p>The last implemented data visualization (Fig 5) showcases the volume of each cryptocurrency in one day. The green and red represent the positive and negative price change(±%) as taken from the rough digital illustrations. However, the difference between Bitcoin’s volume and other cryptocurrencies’ is significantly large; hence the readers can’t clearly read the bars of currencies with smaller volumes. We cannot encode both market capital and volume at the same time either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/0*1ajvYcOjEuuO3HHR" /><figcaption><strong>Fig 5:</strong> Tableau Implementation 3</figcaption></figure><h3>User Testing</h3><p>After we conducted our testing with four users, we found out that most users couldn’t grasp the cryptocurrency jargon and terms involved when referring to the legends or viz. The users didn’t immediately recognize the purpose of the data visualization. The users pointed out that we put too many cryptocurrency players in one chart, making it hard for users to understand values and make connections with concepts. To solve these problems, we lay out several updates that we want to do in the next iteration:</p><ul><li>Provide a clearer way to present the legends.</li><li>Clean up data points and make them easier to be differentiated from each other.</li><li>Provide more contexts or explanations for novice users.</li><li>Explain the relationship between market capital, volume, and price in a better way.</li></ul><h3>Final Visualization</h3><p>The data visualization presents the market capital and the volume of cryptocurrencies in the bubble charts and the bar charts. With the tab on the top, users can switch between different visualizations — Tab 1 shows the market capital in the bubble chart. Tab 2 presents it in the bar chart. Tab 3 shows the volume of cryptocurrencies in the bubble chart, and Tab 4 is the volume in the bar chart. The data visualization also provides definitions of terms for novice users. The legend describes the color encoding of different cryptocurrencies. If users want to get rid of nominating cryptocurrencies to look at the ones with relatively smaller volumes and market capital, they can take advantage of the visualization filters.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_aH8rPu58_Y%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_aH8rPu58_Y&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_aH8rPu58_Y%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/292cecad87115101fff388d95f6fc932/href">https://medium.com/media/292cecad87115101fff388d95f6fc932/href</a></iframe><h3>Takeaway</h3><p>This project gave us a valuable and grounding experience in creating data visualization. We initially tried to add too many channels in one single data visualization, this ended up making the design overbearing and slightly confusing to users. We found that the large difference between dominant cryptocurrencies and others can be a huge factor when trying to design a more readable chart.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a2d34944fd1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/visumd/visualization-of-cryptocurrencies-for-novice-users-3a2d34944fd1">Visualization of Cryptocurrencies for Novice Users</a> was originally published in <a href="https://medium.com/visumd">VisUMD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Visualizations Adapt]]></title>
            <link>https://medium.com/visumd/researchers-are-making-responsive-visualizations-easier-to-be-designed-3164c9e4273b?source=rss-ffea3adc8862------2</link>
            <guid isPermaLink="false">https://medium.com/p/3164c9e4273b</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[human-comuter-interaction]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[user-interface]]></category>
            <dc:creator><![CDATA[CJ Huang]]></dc:creator>
            <pubDate>Wed, 28 Oct 2020 02:49:39 GMT</pubDate>
            <atom:updated>2020-12-23T05:15:16.438Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Researchers are making it easier to design responsive visualizations.</em></p><figure><img alt="Man in blue hoodie using a smartphone in 14 Street station with a train nearby." src="https://cdn-images-1.medium.com/max/1024/1*6L48VyR_NJSwyQxdS9DhqA.jpeg" /><figcaption>Han, Hugh. Man in blue hoodie using a smartphone in 14 Street station with a train nearby.</figcaption></figure><p>Have you ever seen this kind of sloppy visualization when you browse your phone on a morning subway? One-third of the picture is out of frame; the text is too small to be read; the interactivities of the data visualization are not even functioning at all. You might close the app immediately, thinking about how unprofessional this content provider is — no information is delivered, which is contrary to the goal of a visualization.</p><figure><img alt="A messy visualization on a mobile view" src="https://cdn-images-1.medium.com/max/394/1*m0HkRcaLCFOND0jV6ZIP4Q.png" /></figure><p>Before I get any further, I have to admit this visualization is one of my side own projects. Creating responsive data visualization is challenging. However, researchers at the University of Washington and Adobe Research are building something amazing for visualization creators such as me.</p><p>Jane Hoffswell, Wilmot Li, and Zhicheng Liu notice the issue — Mobile devices are important platforms for consuming information nowadays. About 60% of Americans get news on mobile devices, and only about 30% of them are using desktop devices for information. Yet, lots of data visualization is not adaptive to different sizes enough. When a thoughtless responsive visualization shows up on the users’ mobile screens like my project, it can ruin their moods to enjoy the articles&#39; story-telling.</p><p>The researchers examined 231 data visualization from 53 news articles and interviewed 5 journalists to discover more insights into the topic. From the surveys they’ve done, they classified the techniques people usually use when designing responsive visualizations into 6 actions: <strong><em>no change, resize, reposition, add, modify, and remove. </em></strong>These actions are beneficial in creating clear representations with essential information. They found that it is more common for designers to <em>remove</em> than <em>add</em> content when creating mobile views. There are also more responsive techniques used in portrait than landscape views. In some cases, designers even completely recreate the visualization for different device sizes.</p><p>Although various techniques can be used when designing responsive visualization, the process still takes lots of creators’ time and effort. Therefore, the researchers proposed a system focusing on representing the responsive views of the visualization design, aiming to ease the restlessness of the design process. They identified the following 4 guidelines before they started building the responsive visualization system:</p><p><strong><em>#1: Show cross-device previews. </em></strong>Providing immediate, visual feedback across different devices simultaneously allows designers to evaluate their works smoothly. They can further decide which design should be consistent across devices and which choices should be customized on a particular view with the previews.</p><p><strong><em>#2: Enable simultaneous cross-device edits. </em></strong>The feature can speed up users’ design process. It can also lower the chance of errors and inconsistency from repeated manual edits.</p><p><strong><em>#3: Facilitate device-specific customizations. </em></strong>The visualization&#39;s adaptiveness to particular device sizes is the core of designing effective, responsive visualization designs.</p><p><strong><em>#4 Support propagation of edits.</em></strong> It is common that when designing visualizations, designers only focus on refining one specific device size. Tools that propagate edits to other sizes can highly accelerate the design process.</p><figure><img alt="The system presents several shelf panels on the left and a main panel with designs of different device views on the right" src="https://cdn-images-1.medium.com/max/1024/1*DI_b94bpcR0sDV4Tv1rXow.jpeg" /><figcaption>Overview of the system.</figcaption></figure><p>Based on the guidelines identified, they implemented a responsive visualization design tool that shows a synchronized representation of designs across multiple screen sizes. The<em> main panel </em>displays different views of the design. The <em>toolbar</em> and other panels show the information of visualization components. The system support group selections of visualization components both within and across views such that users can simultaneously edit different views or create customization of a specific view. The system enables more flexible and iterative workflows with its design. For example, the designer can quickly explore the impact of high-level design decisions with the <strong>simultaneous editing</strong> and the <strong>cross-devices previews</strong> features. She can also <strong>customize a single device view</strong> by selecting visualization components in a subset of views. <strong>Propagate edits</strong> allows her to apply a device-specific design decision to other device views.</p><blockquote>“A key benefit of our system is that it allows designers to iterate fluidly back-and-forth between these global and local editing modes.”</blockquote><p>To better understand how the system work, I highly recommend watching the videos on the <a href="https://homes.cs.washington.edu/~jhoffs/website/resources/supplemental/responsive-supplemental/index.html">example gallery</a> Jane provided. From these demos, you can get a sense of how the system works and how it is different from other visualization authoring approaches. The system’s expressiveness and flexibility for supporting the iterative design process of responsive visualization are impressive and admirable. I’m looking forward to their next steps on this exciting system. My project mentioned above truly needs an easier way to be recreated — We all know the pain when polishing our design works on different device sizes.</p><p>This blog post is based on the following paper:</p><ul><li>Jane Hoffswell, Wilmot Li, and Zhicheng Liu. <a href="https://homes.cs.washington.edu/~jhoffs/website/resources/papers/2020-ResponsiveVisualization-CHI.pdf">Techniques for flexible Responsive Visualization Design</a>. In <em>Proceedings of the ACM Conference inf Human Factors in Computer Systems</em>, 2020.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3164c9e4273b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/visumd/researchers-are-making-responsive-visualizations-easier-to-be-designed-3164c9e4273b">When Visualizations Adapt</a> was originally published in <a href="https://medium.com/visumd">VisUMD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[iOS14 BackTap 的小故事]]></title>
            <link>https://cj-huang.medium.com/ios14-backtap-%E7%9A%84%E5%B0%8F%E6%95%85%E4%BA%8B-a6a325100fbc?source=rss-ffea3adc8862------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6a325100fbc</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ios-14]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[CJ Huang]]></dc:creator>
            <pubDate>Thu, 17 Sep 2020 19:37:18 GMT</pubDate>
            <atom:updated>2020-09-18T03:16:51.197Z</atom:updated>
            <content:encoded><![CDATA[<h4>還有最近學Inclusive Design的事</h4><figure><img alt="iOS 14 Logo" src="https://cdn-images-1.medium.com/max/1024/1*ioHSR9AqxxcbDBzSL_iwgw.png" /><figcaption>iOS14 image from <a href="https://www.apple.com/ios/ios-14/">Apple.com</a></figcaption></figure><p>這幾天有個有點迂迴的小故事，覺得挺有意思的，收穫很多，也讓我對蘋果的信仰值又加了一點。</p><p>我這學期修了一門課<strong> Inclusive Design</strong>。</p><p>上課時有一個題目：視障使用者在只能用單手的情況下（例如提取重物）如何做Zoom in放大的這個動作。<br>使用者的故事大概是這樣：<br>Hannah是一個視力曾經受損的同學。她需要用手機的Zoom in 放大功能才能辨識手機上的畫面。可是放大這個手勢基本上需要兩隻手才能做到（一手拿手機，一手用兩個指頭放大）。所以她去超市買東西要回家時，因為一隻手提塑膠袋，只有單手可以用，她就沒辦法放大她手機上的地圖來找路。</p><p>我跟我同學討論了一下，發現我們想到同一個解法：在手機背後加入input裝置，這樣他就可以用在手機背面用兩指操作放大縮小的功能，正面的大拇指可以拖移畫面。</p><p>懂Apple的人或設計師這時候大概都已經在偷笑了，因為iOS有Zoom Controller這個功能。他長得有點像大家常用的”小白點”( AssistiveTouch)，一顆白白的。使用者用單手單指Press&amp;Hold，手機就會放大畫面，Hold&amp;Pan即可拖曳畫面。這就解決的剛剛上課提到的，單手放大問題。</p><p>可是Zoom Controller的”放大深度”是不可及時調整的。我的意思是，使用者單手單指點下Zoom Controller時，手機只能放大到固定的深度。雖然使用者可以在設定中客製化他需要的放大深度，但是還是沒辦法像用兩隻手指頭那樣，隨情況、隨時地調整需要的放大深度。所以我就在想，在背面加入一個input裝置，還是有用吧？又或者其實視障使用者不太需要這種細節的微調調整的功能？</p><p>想著想著，兩天就過去了，然後iOS14發布後，我看了下更新內容清單。<strong>Back Tap。 Back Tap!!!<br></strong>我揉揉眼睛你有沒有搞錯？ 先不要嚷嚷</p><p>這個功能是一個新的手勢，使用者可以在手機背後點兩下或三下，完成例如截圖、鎖屏、或Zoom的功能。<br><strong>Zoom。Zoom!!!<br></strong>沒搞錯吧，這太猛了啊，跟我還有我同學上課想到的很類似。</p><p>我整個超炸裂興奮，就開始研究這個新功能。結果發現這個手勢目前只能搭配開啟或關閉Zoom Controller。 還是沒有辦法達到所謂微調深度的功能。</p><p>雖然有點失望，可是開啟或關閉也算還蠻實用的，兩個小白點在手機畫面上面很容易誤觸，就像都已經Remote working了家裡除了兩個小孩，地上還有一隻狗一樣。</p><p>講了半天，問題還是沒解決。</p><p>不過這一整個過程下來，我感受到數位產品設計有太多的細節（又或者我喜歡說：永遠都有更多細節），也很想看看Apple未來會怎麼運用這個設計。</p><p>雖說如此，這個功能還是蠻酷的，大家可以點擊手機背後兩下就鎖屏或截圖。算是蠻方便又酷的功能。“Inclusive Design Process出來的產品，可以Benefit比目標用戶更多的用戶。”，這就算是一個例子吧。當然其他例子還有很多很多，不過這算是我這幾天感受最深的一個。</p><p>這門課真的很好玩。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6a325100fbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[淺談 Apple Widget 設計準則]]></title>
            <link>https://cj-huang.medium.com/%E6%B7%BA%E8%AB%87-apple-widget-%E8%A8%AD%E8%A8%88%E6%BA%96%E5%89%87-58264880b464?source=rss-ffea3adc8862------2</link>
            <guid isPermaLink="false">https://medium.com/p/58264880b464</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[CJ Huang]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 03:23:34 GMT</pubDate>
            <atom:updated>2020-07-13T04:56:49.293Z</atom:updated>
            <content:encoded><![CDATA[<h4>iOS14 Home Screen的未來之戰</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NZjXPLRnbjw_E_K6eVRgTg.png" /><figcaption>Widgets from <a href="https://www.youtube.com/watch?v=GEZhD3J89ZE">Apple</a></figcaption></figure><p>Apple在2020年的WWDC發表了全新的<a href="https://www.apple.com/ios/ios-14-preview/">iOS14</a>，此更新將包含了Home Screen的新功能— Widget。沒有看過WWDC的朋友，這個功能簡單的解釋就是app icon不再只有一個圖標，許多資訊現在可以直接在這個進化版的app icon—”Widget”上呈現，讓使用者原本要進入app內才能完成的任務，現在在home screen上即可完成。這說明了設計師與開發者在未來可以考量使用者需求，將最重要的資訊”surface”(表面化)到Home Screen上。Widget更是一個跨iPhone、iPad以及Mac的全新Feature，所以了解如何設計一個好的widget是非常重要的。在WWDC中Apple的Human Interface Designer提出<a href="https://developer.apple.com/videos/play/wwdc2020/10103/">Widget的設計原則</a>，以下來淺談一下我自己的筆記。</p><p>Widget設計時分為兩個思考階段。<strong>Ideation與Creation</strong>。Ideation階段提供了大方向資訊設計的處理，而Creation階段則在視覺與互動細節上提供了設計的指導方針。</p><h4>Ideation: Principles, Editing, Multiples</h4><p>Widget設計的首要重點是資訊。設計師需要了解到底什麼資訊對於自己App的使用者來說是最重要的，再將這些資訊surface到widget上面。Apple提供的3個Principles為<strong>Personal、Informational、Contextual。</strong></p><p>Personal的資訊講求呈現私人資訊以提供使用者與App情感上的連結。例如照片app會直接在widget上呈現使用者的照片。Informational是在說將最重要的資訊向上移動，達成所謂”Glanceable”：使用者可以一眼就瞥見所有最需要的資訊以減少使用者點擊進入App中的麻煩。Contextual的資訊則可以讓使用者感受到自己的下一步被神奇地預測了，此即<em>Contextual Design</em>一書中所說的”Direct into Action”。(當然Smart Stack的功能已經為不同的Widgets提供了contextual prediction，這邊所討論的是指在同一個App的widget中如何選擇需要提供的資訊。) 天氣這個app提供了一個很棒的contexual實例。在還沒下雨時，App提供每一小時的天氣狀況。然而下雨後，因為使用者可能會最在乎什麼時候雨會停止，所以提供每分鐘的雨量強度的資訊。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UKcRlWsPd0Gi5T01pXl3qQ.jpeg" /><figcaption>在下雨後提供更高解析度的資訊</figcaption></figure><p>在思考的時候可能會發現這三個原則會有重疊的現象，這是沒有關係的。Design Principle提供設計的方針，非黑即白的定義分野並不是我們在這邊的主要目的。</p><p>接下來便可開始思考我們要提供給使用者多大的自由度去呈現(Editing)他們的widget。最直覺的例子就是在天氣、時間中，設計師會提供地點給使用者做選擇。在此iOS又提供了「單一App多Widget」的功能。例如，使用者可以同時製作兩個時鐘widget，而分別呈現不同時區的時間。iOS的這個設計幫設計師減輕了很多負擔。試想，如果要在同一個widget上面呈現多個地區的天氣，那會是視覺上很大的挑戰。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qt_4OuIbf0zEqxjEd3bkig.png" /><figcaption>同時在Home Screen上呈現兩個時區</figcaption></figure><p>最後則思考是否有需要提供不同種的widget。例如股市App提供多支股票以及單一股票的兩種設計。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iaiy6WKpIYjyoOWpgRgwIQ.png" /><figcaption>單支股票在Widget上呈現K線圖</figcaption></figure><h4>Creation: Size &amp; Interactions, Content &amp; Personality, Patterns</h4><p>首先說明<strong>Deep Link</strong>。所謂deep link，是指當使用者點擊widget上的資訊時，直接將使用者帶到該資訊在App中所存放的位置。例如在使用者點擊新聞的widget時，Widget上正好呈現某特定新聞，App會直接將使用者帶到該則新聞。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*BIKLTmkC15eDcMeZEiCsjg.jpeg" /><figcaption>Tap Target可以直接deep link到app的該資訊上</figcaption></figure><p>Widget的尺寸上提供了Small、Medium、Large三種。而不同的尺寸也提供了不同數量的Tap Target：Small widget只提供一個Tap Target，而另外兩個較大尺寸則提供了Multiple Tap Targets。前面所說的deep link概念就會在不同的Tap Target中發揮作用。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*8-V3fDTc5GwYt0KEuE0PVw.jpeg" /><figcaption>三種Widget尺寸</figcaption></figure><p>例如在一個新聞的Medium widget中，使用者有多個新聞的Tap Target可以點擊，而每一個Tap Target都會deep link到該新聞。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ahw7b7Ck6WHQhreUoVhkPw.gif" /><figcaption>多個Tap Target也是使用同一個Deep Link概念</figcaption></figure><p>Tap Target的Layout呈現方式(Target Style)則有三種：Fill Style、Cell Style、Content Style。Fill Style是我們目前最直覺的：點擊app icon、進入App，沒有別的互動結果。每一個small widget都是使用fill style，亦即前面所說的Small Widget只提供一個Tap Target。Cell Style和Content Style則提供了多個資訊的進入點。當資訊屬性不大相同時，我們可以使用Cell Style，例如以下Files的widget。（Cell Style和Content Style使用的情形與選擇我並不太肯定，希望有人能跟我解釋或討論）</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*efnGOoC_7rML_6VqsWRLjg.jpeg" /><figcaption>3種Tap Target的Layout方式</figcaption></figure><p>決定了尺寸和Tap Target的排版後，開始思考這個app的最主要價值(Content &amp; Personality)：”What are people looking for when they launch my app?”。這邊我覺得有點怪怪的，前面都已經在思考資訊的了，為何會到這個階段突然又問了一次這個問題呢？不過設計流程常常不是那麼美好，通常極為混亂，所以我想他們可能是在提醒設計師思考視覺的時候同時要去思考資訊的意思。總而言之這個階段是從整體的app中提取出視覺元素並把它放到widget上面呈現，同時思考資訊的架構。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MDmFkn1IcpNXO2l93Dvgcg.png" /><figcaption>Small widget上建議最多呈現四組資訊</figcaption></figure><p>而同一個app、不同大小的widget layout有兩種design patterns。一種是使用相同的Layout，另外一種是使用不同的layout，講起來像屁話不過還是要思考使用不同layout的目的。另外不能直接將small widget放大就說這是較大尺寸的widget。要好好思考不同尺寸下可以放下哪些不同的資訊，而非單純的放大widget。如果真的沒有可以放的資訊，那就不要硬是提供較大的widget給使用者使用，提供所有尺寸的widget並不是必須的。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PLCc4zaXr6gkSyhxHKaLNg.jpeg" /><figcaption>思考資訊而非單純放大</figcaption></figure><p>最後Patterns的部分，Apple提供了一些layout pattern的範例給大家參考。可以作為設計的參考點。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FqPSH4JHowJplPNfm1iWvw.jpeg" /><figcaption>Widget layout example</figcaption></figure><p>接下來一系列在像素尺度上的dos&amp;don’ts我就不用圖片說明，有興趣的朋友可以點入<a href="https://developer.apple.com/videos/play/wwdc2020/10103/">影片</a>參考，Apple的視覺化解說非常清晰明瞭，不懂英文的我想應該也能大致理解。這邊我就用簡單幾句筆記帶過：Widget Layout需保持16px的margin，圖形資訊則可以使用較緊密的11px margin、margin在不同尺寸的widget中須保持一制性、使用SF Pro字體（如果真的必須使用，我也不知道怎麼辦，整個Home Screen應該會爛掉）、考量夜間模式的widget設計，設計夜間模式時保持與app內一致的色彩設計、設計無資訊時的模式、只有當app屬於content aggregator時才能使用logo於右上角、禁止將app icon和app name放在widget內、不可在widget上使用文字與使用者對話或指導使用者，如必要需使用圖像傳遞資訊、時間資訊不可以使用last updated或last checked。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I4Ed1DuEdzZnjtgpV3AdHg.png" /><figcaption>不使用對話方式傳遞資訊</figcaption></figure><p>其中我覺得最喜歡的是這個do&amp;don’t：圖形資訊的圓角需要與widget圓角共圓心。這個規定讓我感受到Apple對設計細節的要求，所以很喜歡，雖然我不知道背後的設計原則。麻煩了解背後原理的朋友告訴我⋯⋯謝謝。除了共圓心之外，不同尺寸的螢幕會需要不同radius的圓角，不過似乎Swift UI container可以在開發上達成這個設計需求，所以應該不用太擔心。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1n4Bzfpyk6tI74QoeiT7tQ.png" /><figcaption>Widget的圓角需與widget內的圖形資訊共圓心</figcaption></figure><h4>結</h4><p>究竟widget發布後，資訊會變得更混亂還是更唾手可得、這會是一場災難抑或是一個極佳體驗，在今年秋季iOS14發布後就可以揭曉。另外我也非常期待看到各種不同的App會怎麼樣去設計他們的widget，原本已經爭奇鬥豔的Home Screen現在又多了一個項目來衡量一個App的設計品質。然而一個好的widget設計對於一個App的商業影響有多大、投資的設計與開發成本又是否值得，這些都是值得思考的地方。</p><h4>資料來源</h4><p><a href="https://developer.apple.com/videos/play/wwdc2020/10103/"><em>Design great widgets by Apple</em></a><em><br></em><a href="https://www.apple.com/ios/ios-14-preview/"><em>iOS14 Preview — Apple</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58264880b464" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MS in HCI @ University of Maryland 人機互動碩士在美國留學的小小分享]]></title>
            <link>https://cj-huang.medium.com/ms-in-hci-university-of-maryland-%E4%BA%BA%E6%A9%9F%E4%BA%92%E5%8B%95%E7%A2%A9%E5%A3%AB%E5%9C%A8%E7%BE%8E%E5%9C%8B%E7%95%99%E5%AD%B8%E7%9A%84%E5%B0%8F%E5%B0%8F%E5%88%86%E4%BA%AB-676a8a089cfd?source=rss-ffea3adc8862------2</link>
            <guid isPermaLink="false">https://medium.com/p/676a8a089cfd</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[產品設計]]></category>
            <category><![CDATA[人機互動]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[美國留學]]></category>
            <dc:creator><![CDATA[CJ Huang]]></dc:creator>
            <pubDate>Wed, 20 May 2020 04:45:36 GMT</pubDate>
            <atom:updated>2022-06-16T20:33:40.312Z</atom:updated>
            <content:encoded><![CDATA[<h3>MS in HCI @ University of Maryland 人機互動碩士美國留學</h3><h4>簡單說說念了一年的想法</h4><figure><img alt="A night view of UMD campus" src="https://cdn-images-1.medium.com/max/1024/1*RdMLaQ51bQhs2Tif9xlLmg.jpeg" /><figcaption>UMD Campus by <a href="https://unsplash.com/@ryankosmides?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ryan Kosmides</a> on <a href="https://unsplash.com/@ryankosmides?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><em>Update: 這篇文在 2020 夏天發了之後有很多人聯絡我想討論這個 HCI Program 。然而因為我已經畢業一年，課程有許多變化，我建議各位可以 Reach out Linkedin 上正在就讀的同學，我想他們能給的資訊絕對比我更精確很多。Thanks and good luck!</em></p><p>正文：</p><p>網路上好像對我們學校 University of Maryland, College Park 的 <a href="https://ischool.umd.edu/hcim">MS in HCI Program</a> 的評價普通，但這一兩年其實這個 program 有蠻多改變，我自己是唸得蠻開心的。所以身為現在在校唯一的台灣人，我來簡單說明一下這個 Program 的現況。希望之後台灣人能變多一點 😂 。也順便記錄一下人生只有一次的留學體驗。我主要會寫課程和系上對學生職涯的資源，如果要比較廣泛的大學介紹、申請策略，網路上找找會有非常多資料。</p><p><strong>另外以下講的是從一個，畢業後目標在美國就業的角度出發。我在台灣時只有做過實習(Design/Programming各一)，沒有正職經驗。如果是希望念 phD，從事人機互動相關研究，請隨意看看，參考就好。</strong></p><h4>必修課程幾乎從零開始</h4><p><a href="https://ischool.umd.edu/hcim-curriculum">這是我們系上的課程規劃</a>。第一年上學期基本上是必修：User Research Methods, HCI Fundamentals, Introduction to Programming (這門有程式經驗的人可以免修)。</p><p>在 <strong>UX Research Methods</strong> 中，主要教這本 <a href="https://www.amazon.com/Contextual-Design-Life-Interactive-Technologies/dp/0128008946/ref=dp_ob_title_bk">Contextual Design</a> 。課程中，系上會和 <a href="https://www.urbandictionary.com/define.php?term=dmv">DMV Area</a> 的一些公司合作，會從脈絡訪談做到使用不同的模型去 consolidate 用戶的質化資料，最後擠出 Insights。算是蠻基本的學習，不過能練習使用非母語去對不同文化底蘊的人進行脈絡訪談，對我這個剛到美國一個月、從小在台灣土生土長的屁孩來說，算是收穫頗豐。至於設計的部分，就看自己跟組員願意把案子推到什麼程度。</p><p>至於 <strong>HCI Foundamentals</strong> 主要讀這本 <a href="https://www.amazon.com/Interaction-Design-Beyond-Human-Computer-ebook/dp/B07QGMC6WL/ref=sr_1_1?dchild=1&amp;keywords=interaction+design&amp;qid=1589408828&amp;s=books&amp;sr=1-1">Interaction Design</a> 。很基本，但也很難。從一些互動設計的經典跟歷史，講到研究方法、Design Pattern 和開發流程，甚至到 Inclusive Design 的概念，大概就是沈玉琳先生所說的從外太空講到內子宮。這課我們一樣是和公司合作，幫他們的產品進行幾次易用性測試。我的組最後有提一些設計建議、畫一些設計圖，然後去他們在 DC 的辦公室報告。(另外我自己是覺得這本教科書寫的有點雜，最近實習主管叫我讀了這本 <a href="https://www.amazon.com/About-Face-Essentials-Interaction-Design/dp/1118766571">About Face</a> ，我覺得比較有系統也比較好讀。偷偷推薦一下。)</p><p>另外以上這兩門課也都分別會帶到這本 <a href="https://www.amazon.com/Research-Methods-Human-Computer-Interaction-Jonathan/dp/0128053909/ref=dp_ob_title_bk">Research Methods in Human-Computer Interaction</a> 裡面的其他研究方法。</p><p>最後一門 <strong>Introduction to Programming</strong> 就是在教前端。老師很 Chill ⋯⋯，你想做什麼都可以，所以我太愛他了。雖然我有一些 CS 基礎，但我還是修了這門課，因為我覺得可以把握這個課實做一點特別的設計想法。</p><p>雖然這幾門課好像講了很多東西，不過這個領域真的是非常廣且深，我覺得就算念了半年也只是皮毛而已。只能說學海無涯，回頭是岸 🍵 ～</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*77Qn8W1WvNITBQvY0zz20A.jpeg" /><figcaption>天氣不太好但系館的花開了</figcaption></figure><h4>第二學期更著重設計</h4><p>第一年下學期必修就只有 Interaction Design Studio ，另外需要自己選修兩門。我自己是選了一門幾乎快變大家當成必修的 Visual Design 和一門新開的 Game Design。</p><p><strong>Interaction Design </strong>這年來了一個 OCAD 畢業、設計背景很強的教授。 閱讀的內容非常多和雜。而實做上我們設計了一套桌遊和一個設計系統。期末的時候大家把自己做的設計系統跟別人交換，並用別人的 Library 去實做自己的產品概念。我自己非常喜歡這個教授的原因是因為，他們帶了很多我以為不會帶到的議題，並且讓我覺得他們是在培養一個好的設計師，而非只是在教這門課或是單純的技術。Robert Kiyosaki 曾說過 “A question opens a mind, a statement closes a mind.” 這位教授就像這樣，在課程中提出了很多問題，去開啟我們身為未來設計師的思考空間。我自己另外還有修他們的一門 3D 列印。他們講到了設計師對製造業的社會責任、推測設計、Dark Pattern、甚至 Walter Benjamin 的 Aura 和 Latour 對創新的哲學，都對我有蠻大的啟發。</p><p><strong>Visual Design</strong> 的教授是一個在美國很多 Agency 工作過很多年的設計師。整個課程總共會做三個品牌的視覺案，都是個人作品，從介面到包裝海報。講課有基本的視覺設計原則、字體、動畫。這些要在半年內講完當然是不可能的，不過他會像進擊的鼓手裡面一樣盯學生的作品，所以基本上視覺的素養還有能力會有很大的進步。因為都是個人案，加上整個學期有非常多次發表的機會，對於上台表達自己的視覺設計思路跟呈現，是很棒的訓練。這門課也讓我重新思考設計師跟從主流 UI 風格的好處和壞處。</p><p><strong>Game Design</strong> 是一門選修新課，總共做了四個遊戲，從卡牌遊戲、桌遊、Narrative Game 到 電子遊戲。教授上課找了很多厲害的遊戲設計師來分享，他自己也說了蠻多遊戲設計的基本概念和架構。上課時也是玩了一堆遊戲⋯ 收穫蠻豐富的，最大的收穫就是了解到自己大概一輩子不會踏入遊戲產業哈哈⋯</p><p>如果對這學期讀了什麼教科書有興趣可以再問我，因為真的太多本了，我自己都讀不太完😭。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tKpZWiTeiy5T5Ye8V9dkKg.jpeg" /><figcaption>Interaction Design 做的桌遊</figcaption></figure><h4>持續改進中的課程規劃、同學組成多元</h4><p>除了上面我說的課之外，其他選修課還有 Data Science、Advanced Usability Test、Data Visualization、Inclusive Design 等等。 我應該明年念完有機會再分享。另外因為系上一直有想要調整課程，所以推出了很多一學分的課，除了我剛剛說的 3D Printing，還有 Participatory Design 和作品集建立等等。Faculty 他們很在乎學生的體驗跟回饋，提供的意見都會有行動上的調整。他們也幾乎每週都會辦講座，請業界人士來演講。另外我想提的一個優點就是，我們的 Program 人數不多，大約30到40人，上課都是小班，可以很接近教授問問題取得Feedback，同學也都認識。我這年開始錄取的人口還蠻多元的，大概一半美國人一半國際學生，會講中文的只有五個，所以算是蠻適合練習英文的環境。當然每年的錄取計畫都不一樣，所以我也不能保證是不是之後都會是這樣。</p><h4>研究有HCIL、設計有UXTerps</h4><p><a href="https://hcil.umd.edu/">HCIL</a> 在美國算是數一數二的 HCI 研究室。對 HCI 有點了解的人應該會知道的 Ben Shneiderman 先生就常常在這裡出沒。除了每週都有活動之外，也有蠻多研究助理機會給學生。如果是對 phD 有興趣的朋友可以在網頁上看看他們的研究方向。我自己是除了每個禮拜去吃免費披薩之外，對這方面了解不多就不唬爛了。如果對一些設計思考相關的活動有興趣的話，還可以參加學校的<a href="https://www.facebook.com/uxterps/">UX社團</a>。他們會定期辦活動還有黑客松等，是一個豐富作品集的機會。除此之外，學校還有另外的設計社團，不過這個我沒有很了解就不多說了。校外在 DC 的設計相關社群活動也蠻多的，例如 AIGA、UXPA 等等。Meetup上面看幾乎每週都有。我的一個同學前陣子都會去參加，請前輩們幫忙看作品集。</p><h4>斟酌背景再決定申請</h4><p>這是一個兩年的 Program，找實習、工作來說時間上比較充足一點點。但由於第一學期課程有點基本，對有業界經驗的前輩來說這個時間花的可能就不是很值得，美國其他一年的 Program 可能就更適合你。系上還是有不少具備相關經驗的人，不過我不確定他們的心得怎麼樣。相反的，如果你是作品集還不夠豐富，也沒有什麼相關工作經驗，我覺得這是個不錯的選擇。另外系上有些教授跟課程蠻偏向做教育類的互動，如果對學習服務的產品設計或研究有興趣，是一個不錯的選擇。對了，系上也有蠻多TA機會，可以省下非常多學費，不過大部分是 Coding 類(設計的還是有)，教授通常比較會錄取有相關經驗的同學。</p><h4>有時間玩的話其實可以蠻嗨的</h4><p>講了太多正經的東西有點悶，所以來講些這附近好玩的好了。雖然這邊比不上紐約那麼五光十色，不過DC還是蠻多好玩的。從 College Park 坐 DC 地鐵大概30分鐘到可以到 DC 市區，美術館博物館、夜店酒吧什麼的都應有盡有。環境比紐約乾淨大概六倍，但一樣到處都是麻味就是了，可是這邊是合法的(咦?)。 如果有車的話，在這附近也有蠻多戶外活動可以做，我朋友就蠻常去攀岩爬山打高爾夫球，所以算是個蠻折衷、有點健康又不太健康的地方。如果有空想去其他城市逛逛，巴爾的摩(0.5hr)、費城(3hrs)、紐約(4hrs)，都算是可以接受的車程。但是學期開始之後基本上就是忙到頭上長蒼蠅⋯</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qVA2GXV1ZA9roj3MgS9PoQ.jpeg" /><figcaption>MLB國民隊冠軍遊行</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ANJw_vg6Jzxd9Lb4JTqeBQ.jpeg" /><figcaption>抓到有人在DC二戰紀念碑亂丟垃圾</figcaption></figure><p>以上大概就是我這一年看到的，之後幾年肯定也會有更多改變。這兩年在很多方面都受到別人幫忙，覺得自己也要花一些時間付出，如果有任何對這個學校的問題都歡迎聯絡我 ✉️ 。之後如果有空也會多寫寫東西。謝謝＾＾</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=676a8a089cfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>