<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">

 <title>Dave Dash</title>
 <link href="http://davedash.com/tag/usabilitiy/atom.xml" rel="self"/>
 <link href="http://davedash.com/tag/usabilitiy"/>
 <updated>2012-01-17T21:54:19-08:00</updated>
 <id>http://davedash.com/</id>
 <author>
   <name>Dave Dash</name>
   <email>dd+atom1@davedash.com</email>
 </author>

 
 <entry>
   <title>Palm Pre: Always hot</title>
   <link href="http://davedash.com/2009/11/19/palm-pre-always-hot/"/>
   <updated>2009-11-19T00:00:00-08:00</updated>
   <id>http://davedash.com/2009/11/19/palm-pre-always-hot</id>
   <content type="html">&lt;p&gt;So I borrowed a Palm Pré that we had at Mozilla to see what it was like.  I was at first very excited, I remember before the Pre was released there was a lot of talk about how awesome-fantastic it was going to be.  The stories of awesomeness sort of died, and I had thought nothing of it.&lt;/p&gt;

&lt;p&gt;Immediately upon using the Pre I figured out why.  In short, it's a crappy phone.  It makes a very good attempt to do a lot, but it does them with such piss-poor performance, that nothing good is noticed.&lt;/p&gt;

&lt;p&gt;I am disappointed.  It's not even in the same class as an iPhone - maybe a future generation of Palm devices will be, but not this one.  I was hoping WebOS would be a good alternative to the iPhone.  It looks like Google will be doing that, though their phones haven't impressed me much either.  I am hoping that maybe this phone is just a dud.&lt;/p&gt;

&lt;p&gt;Here's what I didn't like:
* The Palm was always hot.
* The first run experience is painfully slow.
* The first run was an indicator of things to come, startup and shutdown are ridiculously slow.
* Every application is slow to render.
* Not all elements of an app render.
* The keys are too small.  Some people aren't migrating from a Treo and aren't used to mini keys.
* No soft keyboard.
* The palm website doesn't let you use plus-style addressing
* Media Mode was not self explanatory - and forced the phone to not work.
* Network would constantly drop out.  Couldn't use a lot of the data features.
* Phone calls didn't work so great.
* Did I mention it was ass slow, even the dialing program was slow.
* The battery dies quickly
* I could only cut/paste when composing, but I couldn't cut a string of text from an email.
* Felt too much like an old palm&lt;/p&gt;

&lt;p&gt;Despite the sadness there were a few good things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;When it did fetch email, and other notices, it displayed them nicely&lt;/li&gt;
&lt;li&gt;The unification of Facebook and Gmail was pretty cool - it also made me want to trim some of those friends from highschool off my facebook - I ain't ever gonna call em.&lt;/li&gt;
&lt;li&gt;The Icons were pretty.&lt;/li&gt;
&lt;li&gt;The card interface was interesting.&lt;/li&gt;
&lt;li&gt;The travel charger could be modified to work in non US chargers fairly easily.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;All in all, I'm glad that I had a chance to try out this device.  It showed me, that user interfaces above all need to be very fast and responsive.  Furthermore, everything you try to do should be done exceptionally well.  I'm hopeful that software updates can alleviate some of the problem, but I think the root of the problem is slow hardware.&lt;/p&gt;
</content>
 </entry>
 
 <entry>
   <title>Have unique descriptive page titles</title>
   <link href="http://davedash.com/2009/07/31/have-unique-descriptive-page-titles/"/>
   <updated>2009-07-31T00:00:00-07:00</updated>
   <id>http://davedash.com/2009/07/31/have-unique-descriptive-page-titles</id>
   <content type="html">&lt;div style=&quot;float:right&quot;&gt;&lt;a href=&quot;http://www.flickr.com/photos/44124375866@N01/3764074726&quot; title=&quot;View 'Sphinx - Free open-source SQL full-text search engine - (Build 20090715083437)' on Flickr.com&quot;&gt;&lt;div style=&quot;text-align:center;&quot;&gt;&lt;img src=&quot;http://farm4.static.flickr.com/3588/3764074726_0c02ffd18c.jpg&quot; alt=&quot;Sphinx - Free open-source SQL full-text search engine - (Build 20090715083437)&quot; border=&quot;0&quot; width=&quot;483&quot; height=&quot;338&quot; /&gt;&lt;/div&gt;&lt;/a&gt;
&lt;/div&gt;


&lt;p&gt;One of my internet pet-peeves is people using the same page title for every page on their web site.  Take a look at &lt;a href=&quot;http://www.google.com/search?hl=en&amp;amp;q=+site:www.sphinxsearch.com+sphinx+api+php&quot;&gt;this search for Sphinx&lt;/a&gt;.  As you can see virtually all the links for Sphinx are titled &quot;Sphinx - Free open-source SQL full-text search engine&quot; which blows for usability when it comes to searching, or even managing the various pages you might have open in your web browser.&lt;/p&gt;

&lt;p&gt;To get an idea of the page I want I need to look at the abstract which may or may not give me a clue.  Even the forum posts which usually have subjects, have their &lt;code&gt;&amp;lt;title&amp;gt;&lt;/code&gt; set to the site-wide default.&lt;/p&gt;

&lt;!--more--&gt;


&lt;p&gt;The first step in solving this, is identifying you have a problem in the first place.  So I wrote &lt;a href=&quot;http://github.com/davedash/Title-Variance/tree&quot;&gt;a tool&lt;/a&gt; in python to determine how unique the page titles you have are:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;% python measure.py sphinxsearch.com
1050 titles found for sphinxsearch.com
483 unique titles found for sphinxsearch.com
46% of the pages on sphinxsearch.com have unique titles
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This is fairly telling.  It means over half the pages on sphinxsearch.com have a generic title.&lt;/p&gt;

&lt;p&gt;This site faired a bit better:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;% python measure.py spindrop.us
988 titles found for spindrop.us
822 unique titles found for spindrop.us
83% of the pages on spindrop.us have unique titles
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;So please, think about people trying to use the information on your site.  Design your templates in such a way that you can come up with unique titles.&lt;/p&gt;

&lt;p&gt;Feel free to expand on this tool, it could easily output the offending pages or titles.&lt;/p&gt;
</content>
 </entry>
 

</feed>

