It looks like you're offline.
Open Library logo
additional options menu

MARC Record from Library of Congress

Record ID marc_loc_2016/BooksAll.2016.part39.utf8:237732903:3513
Source Library of Congress
Download Link /show-records/marc_loc_2016/BooksAll.2016.part39.utf8:237732903:3513?format=raw

LEADER: 03513cam a22003137a 4500
001 2012277026
003 DLC
005 20141118083444.0
008 130125s2013 caua 001 0 eng d
010 $a 2012277026
016 7 $a016142759$2Uk
020 $a9780321884480 (pbk.)
020 $a0321884485 (pbk.)
035 $a(OCoLC)ocn796754695
040 $aBTCTA$beng$cBTCTA$dUKMGB$dYDXCP$dTZF$dOCLCO$dIXA$dEINCP$dVP@$dBWX$dUAA$dUPM$dDLC
042 $alccopycat
050 00 $aQA76.59$b.N54 2013
082 04 $a005.26$223
100 1 $aNielsen, Jakob,$d1957-
245 10 $aMobile usability /$cJakob Nielsen, Raluca Budiu.
260 $aBerkeley, CA :$bNew Riders,$cc2013.
300 $axi, 203 p. :$bcol. ill. ;$c24 cm.
500 $aIncludes index.
505 0 $aMachine generated contents note: 1.Our Research: How We Ran the Usability Studies -- Diary Studies -- Usability Testing -- Qualitative User Research -- 2.Mobile Strategy -- Usability Varies by Mobile Device Category -- A Separate Mobile Experience Is Best -- Mobile Site vs. Full Site -- Mobile-optimized Sites -- Why Full Sites Don't Work for Mobile Use -- Mobile Is Less Forgiving than Desktop -- Responsive Design -- Usability Guidelines Are Rarely Dichotomies -- Mobile Sites vs. Apps: The Coming Strategy Shift -- Current Mobile Strategy: Apps Best -- Future Mobile Strategy: Sites Best -- When Will the Strategy Shift Happen? -- Mobile Apps -- Mobile Apps Are Intermittent-use Apps -- Half-speed Progress, But Hope Ahead -- 3.Designing for the Small Screen -- Wasted Mobile Space -- Chrome -- Overloaded vs. Generic Commands -- Case Study: Optimizing a Screen for Mobile Use -- Typing on Mobile -- Download Times -- Early Registration Must Die -- Example: Pizza Ordering Application -- Case Study: The WSJ Mobile App -- Confusing Startup Screen -- Degrading the Brand -- A Better Design -- A New WSJ Workflow -- Better Next Year -- 4.Writing for Mobile -- Mobile Content Is Twice as Difficult -- Why Mobile Reading Is Challenging -- If in Doubt, Leave It Out -- Filler = Bad -- Old Words Are Best -- Bylines for Mobile Content? -- Defer Secondary Information to Secondary Screens -- Example 1 Mobile Coupons -- Example 2 Progressive Disclosure in Wikipedia -- Deferring Information = Initial Info Read More -- Mini-IA: Structuring the Information About a Concept -- Linear Paging? Usually Bad -- Alphabetical Sorting Must (Mostly) Die -- Example: Usage-relevant Structure -- Usage-driven Structure -- 5.Tablets and E-readers -- iPad Usability -- Tablets Are Shared Devices -- What Are iPads Used For? -- The Triple Threat of iPad Design -- Inconsistent Interaction Design -- The Print Metaphor -- Card Sharks vs. Holy Scrollers -- Swipe Ambiguity -- TMN: Too Much Navigation -- Splash Screens and Startup Noises -- Orientation -- Toward a Better iPad User Experience -- Kindle Usability -- Kindle: The E-reader -- Kindle Fire Usability -- 6.Looking Toward the Future -- Transmedia Design for the Three Screens -- PCs Will Remain Important -- The Third Screen: TV -- Transmedia User Experience -- Beyond Flatland -- In the Future, We'll All Be Harry Potter -- Next-generation Magic -- Don't Harm the Muggles -- Appendix: A Bit of History -- Field Study in 2000 -- WAP Doesn't Work -- Deja Vu: 1994 All Over Again -- Mobile Killer App: Killing Time.
650 0 $aMobile computing.
650 0 $aWeb site development.
650 0 $aApplication software$xDevelopment.
650 0 $aUser interfaces (Computer systems)
700 1 $aBudiu, Raluca.