<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Blog-O! (Posts about heatmap)</title><link>https://bwinton.github.io/weblog.latte.ca/</link><description></description><atom:link rel="self" href="https://bwinton.github.io/weblog.latte.ca/tags/heatmap.xml" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sat, 13 Apr 2019 21:03:20 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Figuring out where things are in an image.</title><link>https://bwinton.github.io/weblog.latte.ca/blake/tech/firefox/heatmap1/</link><dc:creator>Blake Winton</dc:creator><description>&lt;div&gt;&lt;p&gt;People love &lt;a href="https://blog.mozilla.org/ux/2012/06/firefox-heatmap-study-2012-results-are-in/"&gt;heatmaps&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;They’re a great way to show how much various UI elements are used in relation
to each other, and are much easier to read at a glance than a table of click-
counts would be.  They can also reveal hidden patterns of usage based on the
locations of elements, let us know if we’re focusing our efforts on the
correct elements, and tell us how effective our communication about new
features is.  Because they’re so useful, one of the things I am doing in my
new role is setting up the framework to provide our UX team with automatically
updating heatmaps for both Desktop and Android Firefox.
&lt;/p&gt;&lt;p&gt;&lt;a href="https://bwinton.github.io/weblog.latte.ca/blake/tech/firefox/heatmap1/"&gt;Read more…&lt;/a&gt; (4 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>heatmap</category><category>mozilla</category><category>tributary</category><guid>https://bwinton.github.io/weblog.latte.ca/blake/tech/firefox/heatmap1/</guid><pubDate>Mon, 07 Jul 2014 15:53:31 GMT</pubDate></item></channel></rss>