Your SlideShare is downloading. ×
0
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Interface usability-adding-schweppervescence-ver3-8
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Interface usability-adding-schweppervescence-ver3-8

172

Published on

The whole point of a good GUI (Graphical User Interface) is being able to understand what is going on without reading every single detail. That is why we prefer big red crosses to say "Don't do that …

The whole point of a good GUI (Graphical User Interface) is being able to understand what is going on without reading every single detail. That is why we prefer big red crosses to say "Don't do that you oaf!" instead of a line of text that says "I think you may want to reconsider your options."

Published in: Business, Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
172
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
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
  • TODO: Include text for first two pts
  • Don’t delete –this is the version number for SlideShare
  • TO DO Add Schweppervescenceimg
  • TODO: Include text for first two pts
  • http://www.ssw.com.au/ssw/standards/rules/RulestoBetterInterfaces-general.aspx#SelfEvident
  • I am embarrassed by this
  • Adam looks weird here...
  • Section header
  • Look I don’t know and I don’t care
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-General.aspx#EasySearch
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-General.aspx#EasySearch
  • TODO: Make pictures bigger
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-General.aspx#HomePagePortal
  • I thought of a non-web example – this is Adobe Illustrator, but all of Adobe’s Creative Suite does this. Gives you the option to hide it if you don’t like the portal.
  • So cliche...
  • http://skunk/ssw/Standards/Rules/RulestoBetterInterfaces-Forms.aspx#DataEntryForms Remembering recentsearchs
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-General.aspx#messagebox
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-General.aspx#Popup
  • So cliche...
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-Data.aspx#AllInComboBoxes
  • FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF-
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-Data.aspx#UseCheckBoxThey store dataDon’t use them to perform actions!Use a button instead
  • FAIL!
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-Data.aspx#RichTextboxNotesTO DO: Why this isn’t in controls/move to controls
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-Forms.aspx#ElipsisForDialogs
  • So cliche...
  • http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterWebsitesLayout.aspx#Breadcrumb
  • http://www.ssw.com.au/SSW/Standards/Rules/RulesToBetterWebsitesNavigation.aspx#OneLink
  • Underline - http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterWebsitesNavigation.aspx#DontUseUnderlinesRollover - http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterWebsitesNavigation.aspx#underline Show Visited Links - http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterWebsitesNavigation.aspx#visitedlink
  • TODO thing with footer
  • http://www.ssw.com.au/ssw/Standards/rules/RulesToBetterWebsitesNavigation.aspx#ManageExternalLinks
  • (non-important)TODO: Give Adam two very long pages1. one using css2. One using jquery
  • Actually, the designer consensus for _blank is to never do it because you are taking a decision away from the user. So perhaps this could actually be an issue you can ask for debate.
  • http://www.ssw.com.au/SSW/Standards/Rules/RulesToBetterWebsitesNavigation.aspx#ClickingThroughIT’S AN AD!!!
  • http://www.ssw.com.au/SSW/Standards/Rules/RulesToBetterWebsitesNavigation.aspx#ClickingThroughIT’S AN AD!!!
  • http://www.ssw.com.au/ssw/standards/rules/RulestoBetterInterfaces-Controls.aspx#CorrectValidationFocus
  • http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterWebsitesLayout.aspx#StatusIcon
  • http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterWebsitesLayout.aspx#StatusIcon
  • http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces-Data.aspx#CorrectValidationFocus
  • Filters at the topThe number of results found A statement that explains the criteria that you used for searching The number of pages found hyperlinks centred in the middlehyperlinks should be shown on the footer of the page only
  • Filters at the topThe number of results found A statement that explains the criteria that you used for searching The number of pages found hyperlinks centred in the middlehyperlinks should be shown on the footer of the page only
  • http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterWebsitesLayout.aspx#ImproveSearchWebsites are continually saying “404 – page not found” or “your search did not match anything”..... this should be avoided.
  • Shorts in winter guy
  • TODO: Include text for first two pts
  • Move this to OWN SECTION
  • Transcript

    • 1. Interface Usability Adding Schweppervescence Adam Cogan Chief Architect at SSW Microsoft Regional Director @AdamCogan Future Thinking. Immediate Results.
    • 2. Agenda  General Usability Practices  Windows Apps  Popups and Message Boxes  Controls and Forms (Windows and Web)  Reports  Web UI  Mobile interfaces  Controversy! Future Thinking. Immediate Results.
    • 3. Technology is intimidating. People are afraid to break the system or lose the data. Encourage experimentation, increase comfort Have reversible actions (Undo) Previewed actions Avoid dialogs unless there’s a system error (not user error) Track user preferences and defaults, *remember recent* Comfort of Learning
    • 4. ? What is good UI?
    • 5. Chief Architect at SSW  Developing custom solutions for businesses across a range of industries such as Government, banking, insurance Microsoft Gold Partner Microsoft Regional Director VSTS MVP @AdamCogan About Adam Future Thinking. Immediate Results.
    • 6. A good UI just works the way you expect  There are no surprises  There is no need to use help  RTFM Future Thinking. Immediate Results.
    • 7.  Intuitive  Feels fast  Eg. No white screens, threading code  Consistent  No clutter – not busy… A good UI is...
    • 8.  Minimal “modal” popups  Good error handling  Easy to customize + apps (aka a platform)  Gamification eg. Badges A good UI is...
    • 9. MSDN
    • 10. Stack Overflow
    • 11.  http://channel9.msdn.com/achievements/visualstudio Visual Studio Achievements
    • 12.  Good UI:
    • 13. Future Thinking. Immediate Results.
    • 14. 1. General Usability Practices Future Thinking. Immediate Results.
    • 15. Do you intuitively know how to use something?
    • 16. A thermostat
    • 17. VS
    • 18.  Less is more  The importance of Defaults - Aim for 'Next', 'Next', 'Next‘  Hide advanced options, but make them easy to find! Do you realize that when it comes to interface design 'less is more'?
    • 19. Future Thinking. Immediate Results.
    • 20.  You’re late for a flight and you need to check in  … Do you realise people scan, not read?
    • 21.  Google: SSW storyboarding Do you know to use storyboards?
    • 22. Is your data easy to search?
    • 23.  TOUCH What is more important than search?
    • 24.  Eg. http://www.microsoft.com/presspass/features/2011/jun11/06- 01corporatenews.aspx Windows 8 live tiles - metro
    • 25. Do you consider optical alignment?
    • 26. Bad
    • 27. Good …
    • 28. And now…
    • 29.  iSlate
    • 30.  iSlate
    • 31.  iSlate….  IsLate?
    • 32. Do you make matrix columns as simple as possible?
    • 33. Do you make matrix columns as simple as possible?
    • 34.  ? What about Columns or Text?
    • 35.  Columns are easier to scan  Use when comparing data, or need ordering  Text is aesthetically pleasing What about Columns or Text?
    • 36.  Make it more than just navigation  Put useful current information on the homepage E.g. Top billing customers for the month and a button under it for adding an invoice E.g. See the number of bugs counted by the most common Do you make the homepage a portal? Future Thinking. Immediate Results.
    • 37.  Do you think this rule is limited to web UI?
    • 38.  Can see what functions are being used more often (e.g. reports, menu items)  To work out what fields to show on search pages (standard and advanced tabs)  Know which parameters are being used Do you log usage?
    • 39.  Put all options in even if some aren’t selectable Let’s look at two examples:  Checkbox  Image… Include extra information if it gives you context
    • 40. A good app should…  Encourage experimentation to increase comfort:  Undo  Remember your last state  Live preview
    • 41. Live previews
    • 42.  Auto save records  Prompt to save the record when the user leaves a page that has been modified  When the user logs back on prompt them that they have drafts  E.g. mail.google.com Do you use the concept of drafts?
    • 43. Do you have a "last taken" option?
    • 44. I have a dream
    • 45. Help - Do you have a wiki for each page or form?
    • 46. Help - Do you help users when they get errors by directing them to a wiki or KB?
    • 47. http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfaces.aspx Lots more:
    • 48. 2. Windows Applications
    • 49.  Training Videos  Online User Guide  Knowledge Base  Make a Suggestion  Report a Bug  Check for Updates  Run Unit Tests...  About [Product Name]... Menu - Do you know the 8 items every "Help" menu needs?
    • 50. Menu - Do you have a "Help | Training Videos" item?
    • 51.  Easier to keep up-to-date and maintain  Stats on usage  Allows community commenting Menu - Do you have your "Help | User Guide" online?
    • 52. Menu - Do you include a "Tools | Validate Data"?
    • 53.  Don’t give descriptive information about the page  Give the user instructions on how to use the page Bad example - This page allows you to define a search Good example – To start a search choose an option to the left Give Instructional Help
    • 54.  http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInt erfaces-Windows-Application.aspx Lots more:
    • 55. 3. Popups and Message Boxes
    • 56. When good sites go bad…
    • 57. Not even Apple could make the popup less annoying
    • 58. Do you avoid message boxes?
    • 59.  Only use them in the following scenarios:  Confirming the deletion of a record  Kicking off a long running process Do you avoid message boxes?
    • 60. Is it ok to cancel? Do you use messages that are concise and informative?
    • 61. Microsoft uses this one Do you use messages that are concise and informative?
    • 62.  Some people like popup forms.  Some do not.  ? Vote – What about popup forms?
    • 63. You can’t read or edit content behind Long loading times – ask CRM4 users! Popup modal forms are no good
    • 64. Obvious you have an action to take Simplify a form Doesn’t get lost behind another window Can dim the background for focus Popup modal forms are good
    • 65. Should this be a popup?
    • 66. Who likes popup forms?  ? Re-vote....
    • 67.  http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterInt erfaces-Popups-and-Messages.aspx Lots more:
    • 68. 4. Controls and Forms (Windows and Web)
    • 69.  Less is more!  Select all should be “-All-”  Note: if you want to select nothing then add an entry to the dropdown for (null) Do you know how to label dropdown lists?
    • 70. Rule #9 http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterBusinessIntelligence.asp x#AllDimensionsTag
    • 71.  When you use a combo box, it's very helpful to be able to see at a glance how many results can be expected Do you include the number of results in drop down list?
    • 72. What if user wants to sort by either alphabetical or numerical?
    • 73. What’s a better way to do this???
    • 74. Radio buttons…
    • 75.  users know it is data, not a label of the application  users can copy and paste from the field Do you use Text Boxes for displaying data?
    • 76. Which is better? A: Neither, use a checkbox!
    • 77. Good
    • 78. What’s wrong with this?
    • 79.  Better Example Also applicable for the rule “Less is More - Do you always try to reduce complexity?”
    • 80.  Checkboxes  1 option – eg. yes/no, on/off  Multiple simultaneous options – e.g. Eggs and Bacon and Tomato  Radio buttons  2-3 exclusive options – e.g. Coke or Pepsi  Drop down list  3+ exclusive options e.g. Favourite SSW employee Guidelines – when to use what?
    • 81. Do you disable buttons that are unavailable?
    • 82.  What’s wrong with this?
    • 83.  A plain textbox limits the detail of the user's notes   For multi-line textboxes (e.g. Descriptions, Memos, Notes)  Allows you to use:  Links  formatting (bold, underline, etc.)  bullet points and numbering Do you know when to use rich textboxes?
    • 84.  http://demos.telerik.com/silverlight/#RichTextBox/MSWord (Telerik) Telerik rich textbox
    • 85.  Helps the user enter more data related to that field  Should call a popup form Do you use ellipses buttons?
    • 86. Do you use ellipses buttons?
    • 87.  http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInt erfaces-Controls.aspx Lots more:
    • 88. 6. Reports
    • 89.  A display containing more than four perceptual units of information cannot be understood at a glance Do you make graphs easy to digest?
    • 90. Do you make graphs easy to digest?
    • 91.  http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInt erfaces-Reports.aspx Lots more:
    • 92. 7. Web UI
    • 93. Do you follow the “Banana Rule”?  How do you get a monkey pay attention to something?  A:/ You could lure him by tempting him with a banana. The principle is.... Once we have the monkeys attention focused on the banana, he will try to get his hands on it!
    • 94. Treat your users like monkeys!
    • 95.  Bad banana!
    • 96. ? How do I know where I am?
    • 97. Do you know to use Breadcrumbs?  Note the links.... What is the exception? ....
    • 98. But don’t link to yourself!  If you’re on the homepage, there’s no point having a link to the homepage  If you have a breadcrumb, don’t link to the current page
    • 99.  SharePoint
    • 100.  Underlines are only used for links! This does NOT mean all links should be underlined  Always have a *rollover* effect  You should indicate *visited* links. Do you know the correct way to display a hyperlink?
    • 101.  Via CSS ... Do you know the correct way to display a hyperlink? Rollover effect Visited links Normal links Must be in this order!
    • 102.  If a link is to an external site, a visual indication should be provided to the user like this:  This should be done via CSS or jQuery  ... Hyperlinks - external
    • 103. Via CSS:
    • 104.  Custom for SSW  Filters image links and other parameters  ... Via jQuery
    • 105.  ‘CSS is manual’  ‘JQuery is automatic’  Content heavy websites with large archives – are you really going to go back and add a class to each link?? Via jQuery
    • 106.  Warning: Corneliu the god of performance warns against this recommendation because  CSS is fast  jQuery is slow  TODO: The next step is to verify this via a VS 2012 Ultimate Coded UI test! Via jQuery
    • 107.  Warning: Not mainstream  HTML 5 does not have the TARGET  On the purchase page add “terms and conditions (opens in a new window)”  http://www.ssw.com.au/SSW/Standards/Rules/RulesToBetter WebsitesNavigation.aspx#ManageExternalLinks Should external links open in a New Window?
    • 108.  http://www.ssw.com.au/ssw/Events/Scrum-Training-Course.aspx Do you save clicking through?
    • 109.  http://www.ssw.com.au/ssw/Events/Scrum-Training-Course.aspx Do you save clicking through?
    • 110. Do you indicate which fields are required?  Prevents a wasted trip to the server  Should get the required fields right the first time around http://www.ssw.com.au/ssw/standards/rules/Rules toBetterInterfaces- Controls.aspx#CorrectValidationFocus
    • 111. Do you use icons in web pages to indicate status directly?
    • 112. Do you use icons in web pages to indicate status directly?
    • 113. For Validation Errors, don’t assume they have to read a messagebox Automatically focus on the control Note: Balloons also direct the eye… Do you use SetFocusOnError on controls that fail validation
    • 114.  What’s important  ? Do you have a consistent search results screen?
    • 115.  A statement that explains the criteria  Pages navigation  Number of results found  Filters at the top  ... Do you have a consistent search results screen?
    • 116. Do you always give more information under “Did not match anything”?  Websites are continually saying ‘404 – page not found’ or ‘your search did not match anything  This should be avoided  …
    • 117.  ?  Use SSW Link Auditor www.ssw.com.au/ssw/LinkAuditor Broken Links are inexcusable!
    • 118.  Master pages  CSS Do you know the two things to create a consistent look and feel?
    • 119. Do you give the 6 options to share?
    • 120. Do you make the logged in state obvious?
    • 121.  www.ssw.com.au/SSW/Standards/Rules/RulesToBetterWebsit esNavigation.aspx Lots more:
    • 122. 6. Mobile Interfaces
    • 123. First impressions: You only get one shot
    • 124. First impressions  Better to have a Porsche UI and a VW engine  than a VW UI and a Porsche engine.  Of course you want a Porsche UI and a Porsche engine, but...
    • 125. ? When do you build a iPhone app vs iPhone web app?
    • 126.  Depending on  budget  usage of native API • Camera, Contacts, Photos e.t.c.  existing web app and just add CSS  Offline: An iphone (or WP8 ) web app without a network connection, will not load the web page you were on previously. Well, it can… http://damianbrady.com.au/dyrnaa/game/ iPhone app vs iPhone Web app
    • 127. ? When do you build a WP8 app vs an iPhone app?
    • 128.  A: If your app is build on Silverlight today.  Time to market  Lower $  Reuse MVVM  Reuse Silverlight controls  Reuse the Business and Data layer WP8 app vs iPhone app
    • 129. The biggest thing going for Windows Phone 8 is:  .NET dev shops  environment more productive than xcode “VS2012 kicks the sh*t out of any other IDE” - Damian Brady WP8 app vs iPhone app
    • 130.  Note: WP7 is built on Silverlight 3  Note: WP7.5 is built on Silverlight 4  Note: WP7.5 was built by a "web team" not "Rich client app team", so some issues exist:  Avoid using System.Windows.Browser.dll in your Silverlight App (as it works only OOB on desktop) and you will have to use a different control on Windows Phone 8 WP8 app vs iPhone app
    • 131.  WP8 has resolved those problems and is perfect in every way  <3 WP8 app vs iPhone app
    • 132. Others reasons are:  You can deploy your app without going through the appstore/market place. E.g. my SSW business app Appstore: No Market place: Yes (hidden) WP8 app vs iPhone app
    • 133.  Turn around through the appstore is quicker: Appstore: 1-3 weeks (unmanaged code) Market place: 2 days (managed code) Quicker since it is managed code. Unmanaged code is easy to spot  App store is more aggressive in blocking apps WP8 app vs iPhone app
    • 134.  Do you know what guidelines to follow for WP8?  User Experience Design Guidelines for Windows Phone http://msdn.microsoft.com/en- us/library/windowsphone/design/hh202915(v=vs.92).aspx WP8 app vs iPhone app
    • 135.  Tip: if you’re writing your own user controls, you’re probably doing it wrong  Silverlight.CodePlex.com (WP7.5)  Phone.CodePlex.com (WP8) WP8 app vs iPhone app
    • 136.  www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterface s-Mobile.aspx Lots more:
    • 137. 7. Controversy!
    • 138. ?
    • 139.  Well, we had a few in the presentation...  
    • 140. Technology is intimidating. People are afraid to break the system or lose the data. Encourage experimentation, increase comfort Have reversible actions (Undo) Previewed actions Avoid dialogs unless there’s a system error (not user error) Track user preferences and defaults, *remember recent* Comfort of Learning
    • 141.  Rules to Better Interfaces http://www.ssw.com.au/ssw/Standards/Rules/RulestoBetterInterfa ces.aspx  Rules to Better Website Layouts http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterWebsi tesLayout.aspx Resources
    • 142. Resources
    • 143. Summary  General Usability Practices  Windows Apps  Popups and Message Boxes  Controls and Forms (Windows and Web)  Reports  Web UI  Mobile interfaces  Controversy! Future Thinking. Immediate Results.
    • 144. Thank You! Sydney | Melbourne | Brisbane | Adelaide info@ssw.com.au www.ssw.com.au
    • 145. Find me on Slideshare! http://www.slideshare.net/SSWConsulting/

    ×