Your SlideShare is downloading. ×
  • Like
  • Save
Hyperscope UX analysis
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Hyperscope UX analysis

  • 1,501 views
Published

 

Published in Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,501
On SlideShare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1.  
  • 2. Where we were
  • 3. Goals
    • Make more accessible
    • Simplify product
    • Identify pain points/use cases
    • Future directions
      • Imagining editing …
  • 4. What we did
    • Learn!
    • Identify core capabilities
    • Use cases/scenarios
    • UI brainstorming
  • 5. Where we are
    • Where are we: agreed on core capabilities for UX attention
      • Automatic HTML transformer
      • Automatic granular addressability
      • Zooming
      • Sharing view and location
      • Simultaneous viewing of 2 locations
  • 6. (Vanishing?) Brand Status - Document / Where I am Zoom : Line + level clipping (4B1) This should be an empirical approach on a total-system basis--i.e., doing coordinated study and innovation, among all the factors admitted to the problem, in conjunction with experiments that provide realistic action and interplay among these variables. The question of limiting these factors is considered later in the section. The recommended en vironment for this empirical, total-system approach, is a laboratory providing a computer-backed display and communication system of the general sort described in Section III-B. There should be no stinting on the capabilities provided--it is very important to learn what value any given artifact feature may offer the total system, and the only way to learn the value is to experiment with the feature. At this point no time will be taken to develop elaborate improvements in the art of time sharing, to provide real-time service to many users. This kind of development should be done as separate, backup work.
    • Ideas:
    • Table of contents showing context, easy navigation
    • Index
    • Search
    Sidebar (4B) B. BASIC RESEARCH CONDITIONS (6B2) This should be an empirical approach on a total-system basis--i.e., doing coordinated study and innovation, among all the factors admitted to the problem, in conjunction with experiments that provide realistic action and interplay among these variables. The question of limiting these factors is considered later in the section. The recommended en vironment for this empirical, total-system approach, is a laboratory providing a computer-backed display and communication system of the general sort described in Section III-B. There should be no stinting on the capabilities provided--it is very important to learn what value any given artifact feature may offer the total system, and the only way to learn the value is to experiment with the feature. SHARE DEBATE AREA: EDITING ???