Skip to main content

UI Trend with Modal Windows

You may say that Modal windows are what pop up were 10 years ago. Like them or hate them they have become an essential UI design element for almost any website or application. Recently I have started to see a transition of how these screens are being used. We first started seeing modals about 8 years ago when a developer named Lokesh Dhakar created a Javascript Library called “Light Box”. It was a very simple way of putting focus on one image at a time and graying out everything else.

This became so popular that many people starting to throw anything and everything in these smaller focused screens. Some people call them Dialog boxes, others call them Modals but they really all mean the same thing. The main purpose is to present the user with additional information while putting the main parent page on hold until they are done.

Of course with any UI design element they have been misused and abused in many different ways. I have seen some applications that have more than 3 levels of modals one on top of each other. Or times where the modal includes an extremely complex workflow or wizard that does not allow the user to exit until a set of criteria is fulfilled. Most of the times when modals are used in the wrong way it is because the content owners are trying to inject way to much information in such a small space. Rule of thumb, if you have to consider either a “Next” button or a “Scrollbar” in your design just STOP. It may be better to have a new full page dedicated to that content and not a modal.

With the introduction of bootstrap and other frameworks modals have become pretty standard on how users will interact with them. Usually the grayed out area is a clickable area that allows users to navigate back to the parent screen. Other times we become overly cautious and have “X” icons and “Cancel” buttons to make sure users feel comfortable that they are not stuck on an overlay page and no way to get back. One interesting trend I am seeing lately is moving the “X” button outside of the modal box and into the gray area. Pinterest uses both on their website which to me is a little bit confusing...

If you look at Facebook the close icon is all the way to the top right. This is slightly annoying for the users since they have to move their cursor a pretty far distance on larger screens to close it down. However since the whole gray area is clickable it is not a deal breaker. I would be interested to see some metrics on how often in Facebook users actually click the “X” icon vs clicking on the gray background?

Twitter has the close icon closer to the box which makes it slightly easier for the users to close it down.

Overall the biggest thing to remember is that modals are meant as short term screens to present and capture small bits of additional information that supports the parent screen. They should not be used for presenting heavy content, complex workflows and modals on top of modals. One last thing to consider is that you will need to consider alternative ways of presenting these screens on mobile devices. In most cases they will become full screen take overs due to the limited space available.

Popular posts from this blog

SharePoint 2010 Base CSS Classes

This will be the first of many SharePoint 2010 posts. I will be focusing on a few of the main CSS classes used for SharePoint 2010 Public Beta. As the product becomes more final there might be some changes to the class names but I will be sure to create a new post if that happens. This will be quite a lengthy but it should be helpful. The default CSS given below are just highlights of the full CSS attributes for that class. I will be using a basic team site as my base for the screenshots. Here is a basic structure of the main areas that I will cover. Ribbon Row Table Row Left Site Actions Navigate Up Edit Tab List Browse Page Table Row Right Give Feedback Welcome Menu Workspace Body Container Title Row Title

SharePoint 2013 Responsive Table Columns

I have been wanting to write this one for a while now. It is really amazing how UX is really finding is way into everything that we use and interact with. From Custom applications both mobile and on a desktop to document management or large data visualizations. There is always room for better usability and new concepts. SharePoint lists and library functionality really has not changed much for the past 10 years... I remember back in 2003 when I saw the same table/grid based views of documents and list items that exists in SharePoint 2013. But now we can look at them in a whole new way! In this video blog you will see how to create a responsive CSS table so that when the browser size is reduced it will hide specific columns. However hiding data is not always the right thing to do. What if a user needed those columns to filter on or to use for comparison to another document? Well that is where the custom jQuery Column chooser comes in. It allows you to see what columns are displ

SharePoint 2010 Content Query for Blog Posts

I hope this post will help many of you feel comfortable with using the Content Query Web Part. In this post I will walk you through the process of creating a content query web part and configuring it to show custom field types. I will also give details on how to use XSLT to stylize and format the data being pulled. I will be using the following scenario as an example. Say that you had a site collection with a top level publishing site. This publishing site would display a the most recent blog posts from all blog sites within its own site collection. To solve this problem we will use a Content Query Web Part and a customized ItemStyle.xsl using XSLT. Please note that the “SharePoint Server Publishing Infrastructure” needs to be enabled at the site collection to display the content query web part. Step 1: Add a Content Query Web Part to Page Navigate to the site that you want the blog posts to show up and click on edit page. Under Editing Tools in the Ribbon, Click on