Download the Map Controls for Balsamiq Mockups on mockupstogo.net.
The collection includes a wide variety of map controls like zoom bars, pan controls, scale bars, overview map, logos, pins, rings. All of them are symbols that you can add to your assets directory.
Enjoy and let me know if I missed something… and like it or re-tweet it
- Using “Preventive Medicine” Against Bad Clients (by Maria Malidaki) - Love the section about useful documents
- Accessibility and web innovation – a talk (by Christian Heilmann) - Chris makes a case for deeper involvement in the actual development of cool technology that is accessible (or cool development that makes technology accessible)
- Architecture v. Web Design (by Dmitry Fadeyev) - Dmitry on the essence of architecture to create space and how this is (or is not) applied to web design
- What’s new for web designers – Apr 2011 (by Cameron Chapman) - Once again, great collection of apps for designers, thx Cameron
- Are your users S.T.U.P.I.D? (by Stephen Turbek) - Get Smart (and download the info poster)
- Essential Facebook Etiquette: 10 Dos and Don’ts (by bellefoong) - Funny how we need to learn social etiquette again, huh?
- How To Design The Perfect Form (by Brian) - Extensive collection of examples and best practices for forms
- Integrating UX into Agile Development (by Janet M. Six) - State your requirements as user stories: As a [role], I want to [action based on a feature], so [user goal].
- Mobile Application Development: Web vs. Native (by Andre Charland, Brian LeRoux) - Excellent research on web versus native development for mobile. Sooner or later we all need to understand the ins and outs of mobile dev.
- A new micro clearfix hack (by Nicolas Gallagher) - updated hack to clear floats without resorting to using presentational markup
- Web Developers vs. Web Developers (Infographic Remix) (by Cassie McDaniel) - nice remix of the original web designers vs web developers infographic by Shane Snow
What makes a Map App successful?
It sounds so easy and obvious. It's the basic, the 101 of analysis, Input-Analysis-Output. Usually I skip over introductions of books and that's especially true when I know the subject matter like GIS, but for some reason I started reading "The Esri Guide to GIS Analysis, Volume 1" (by Andy Mitchell, Esri Press) and it struck me like lightning, this is exactly what we should be doing:
You start an analysis by figuring out what information you need. This is often in the form of a question. Where were most of the burglaries last month? How much forest in each watershed? Which parcels are within 500 feet of this liquor store? Being as specific as possible about the question you're trying to answer will help you decide how to approach the analysis, which method to use, and how to present the results.
Other factors that influence the analysis are how it will be used and who will use it. You might simply be exploring the data on your own to get a better understanding of how a place developed or how things behave; or you may need to present results to policy makers or the public for discussion, for scientific review, or in a courtroom setting. In the latter cases, your methods need to be more rigorous, and the results more focused.
Frame the Question
Framing the question correctly will tell you:
- The problem you are trying to solve
- The approach of the analysis you want to use
- Which methods to use
- How to present the results
Who & How
Other factors that influence the analysis are:
- Who will use it?
- How will they use it?
- How are the results being used?
All this will impact your design, on what you should focus and how to lay the elements out on the page. Consider:
- Get the user to the location they are interested quickly
- Create clear call to action that allows the user to get answers to his/her question
- Simplify the methods on how to do analysis
- Provide means to use or export the results
Jakob Nielsen outlines in his latest alertbox newsletter (http://www.useit.com/alertbox/search-skills.html) the inability of users to search effectively.
My colleague Neal Dinoff, Esri Usability Lab Manager, summarized the article and outlined Jakob Nielsen's core findings:
- People (even highly educated people) have remarkably poor search skills.
- Once they head down a keyword path, no matter how fruitless, they seldom change their search strategy
- Users will enter search terms into any open text field with no understanding of whether they are searching the whole site, the World Wide Web, or only a discreet section of the site.
- Users are overconfident in the reliability of results.
- Almost no one uses Advanced Search. When they do, they use it incorrectly.
Neal continues to conclude lessons for our search design:
- Don't assume that advanced search will help your website; you might build such features, but people will use them only in exceptional cases.
- Spend the vast majority of your resources on improving regular search (simple search).
- Design for the way the world is, not the way we wish it were. This means accepting search dominance, and trying to help users with poor research skills.
I believe more implications can be deducted:
- Curate (make sense of) content (!!!):
- Aggregate (most relevant in one location)
- Distill (more simplistic)
- Elevate (identify and describe trends/insights)
- Mashup (create new points of view based on multiple sources)
- Every page is a potential landing page, so help user to:
- Locate themselves (titles)
- Provide context (the bigger picture)
- Find the content/functions they were originally looking for
- Navigate further (well thought-through navigation architecture + good links + meaningful footer links)
- Create pages so that they can be found through:
- Search Engine Optimization (metatags, headings, etc.)
- Write in the language of your users, that’s how they will search
What are your Experiences?
- Observations versus Recommendations (by Harry Brignull) - use the FOG method, mark your statements Fact, Opinion or Guess
- Top 10 Free Source Code Editors – Reviewed (by hongkiat) - a listing of 11 free editors with their Pros and Cons
- How to Spot and Avoid Web Copy that Kills Websites (by Rick Sloboda) - here some downfalls of the often overlooked but actually really important subject of copy on the web
- Login / Registration Form: Ideas and Beautiful Examples (by bellefoong) - a little login inspiration, nice collection
- Progressive Disclosure in User Interfaces (by Alexander Dawson) - nice intro plus advantages and disadvantages
- The 5 Models Of Content Curation (by Rohit Bhargava) - content curation in its various situations explained
- 9 Ways To A Better Interview (by Mitch Joel) - in my opinion it boils down to caring about the other person and the subject and not getting hung up on standard questions and a script
- Tips for Creating an Excellent E-Commerce Website (by Mathew Carpenter) - some interesting tips here
"Esri Redistricting is a Web-based solution for state and local governments, legislators, and advocacy groups to create political and geographic redistricting plans." The app is hosted by Esri and delivered as software-as-a-service through annual subscriptions (30 days free trial available).
Mockups in MS PowerPoint
First of all I want to mention that the project became a success only for the dedicated and hard work of so many talented people, my part was really only the literal drop on a hot stone.
Very early on I had the feeling that this project would benefit from higher graphical fidelity (maps, charts, colors were important) so I decided to use Microsoft PowerPoint to communicate the designs. Using my wireframe stencils to draw the UI elements we iterated through multiple versions and approaches.
Main Lesson: Use slide master layout as background
My biggest lesson was the need to create a new layout to the Slide Master which would serve as the background. This layout included the banner (logo, user information), the menu (ribbon) and the map area.
- Changes propagated to all slides (e.g. modify a label)
- Easy manipulation of elements on top of static background
- Remove source of errors (forgot to update a slide)
- Cleaner in general
I find the following list really helpful when planning and conducting user testing. I collect and refine it constantly and would greatly appreciate any comments or additions I have missed (and I'm sure I did).
- setup web meeting
- tell secretary to not delete account and associated recordings
- test connection, equipment and recording capabilities
- setup schedule for participants
- send connection info to stakeholders
- remind everybody to mute their phones (or whatever else is necessary)
- prepare necessary data and files
- hide windows toolbar
- close mail program
- enable full screen for all users
- show host cursors to all attendees
- allow access to observers
- share desktop
- clear user generated content from previous user
- reset application
- remove cookies
- start blank application (if that's part of the test)
- take a break/breather for yourself
- prepare your personal notes taking material
- get acquainted with name and capabilities of next participant
- provide water for participant
- start recording
- greet participant and get going
- clarify time line for test results (findings & analysis)
- send thank you emails to participants
I think she has a valid point here... But just to make sure I ask the audience...
Which one is your answer? Why?
Pardon the off-topic, can't stop laughing.
It depends. But mostly bad
John Colby's from Birmingham City University arguments on why pop-ups are bad:
- Because people are warned about them (http://www.bbc.co.uk/webwise/guides/about-popups)
- Because of their association with scams, viruses, malware, sites using popups are 'less trustworthy'
- Users with sight or cognitive problems (http://soap.stanford.edu/show.php?contentid=47)
- (And personally) if they insist on using popups I'll go away.
Richard from Userite remembers us that:
with Charles McCathieNevile from Opera adding:
...that many users have pop-ups blocked by default now, so won't actually see it even if they are not blind.
Harry Loots of the IEEE has a point when he says:
If it will supply useful information to the user, then don't kick against it, but make sure that the feedback / information so provided is accessible. For example, if the pop-up is used to confirm the product has been added and the user's browser does not support scripting/popups, a physical line of text may be displayed to confirm the product has been added (which can be hidden in the view seen by users who get the popup)
When a client asks for a specific design element, one needs to wonder where this need came from in the first place.
In the case that the client is not satisfied with visibility of system status. Try
- Improving titles and labels
- Adding non-obstructive instructions
- Providing feedback in an alternative way (as Harry pointed out), additional confirmation page always helps
- Keeping elements and its status (e.g. shopping cart belongs to the top right corner) in its user-anticipated location
- Using visual cues to show what just happened
Jennison Mark Asuncion just posted 4 upcoming accessibility events in North America:
- Ottawa's First Accessibility Unconference, May 6 in Ottawa Ontario (free event) register now at http://www.a11yyow.ca
- John Slatin AccessU 2011, May 17-19, Austin TX http://www.knowbility.org/v/accessu-detail/John-Slatin-AccessU/39/
- Accessibility Camp Seattle, May 20-21 (free event) register now at http://www.AccessibilityCampSeattle.org
- The Guelph Accessibility Conference, May 31-June 1, Guelph ON http://www.accessconf.open.uoguelph.ca/
Missed one? Post it in the comments section.