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

How To: Hide Left Side Navigation on Home Page

I was recently asked: "How can I hide the side nav bar on the main homepage layout ?? I want to be able to use the side NAV with in the team site etc etc, but I don't want it on the front page.. " There are a couple of ways to do this in SharePoint 2010. If you are using a non-publishing site you can add a Content Editor Web Part to the page and add the following to the HTML Source.
body #s4-leftpanel
display: none;
margin-left: 0px;
Basically the CSS above hides the left navigation Div, and then sets the content area to not have a left margin. Once you are done, simply modify the web part and hide it on the page. If you are using a publishing site for your homepage simply add the same styles specified above to a custom page layout. That way if you have a need for other pages that do not need the left side navigation you can re-use the page layout.

Small Calendar for SharePoint 2010 & 2013

First off I would like to apologize for the lack of posts. I have been really busy with my new role as the UX Design lead within Slalom Consulting Boston. I will share more about that in another post. In a previous post Create Really Small Calendar I showcased how to do this for SharePoint 2007. However the 2010 and 2013 calendar views have changed and therefore we cannot use the same method or CSS as 2007.SharePoint 2010 Small Calendar:
SharePoint 2013 Small Calendar:
See video below for a video walk through on how to create a small calendar for SharePoint 2010 and & SharePoint 2013 with just CSS.Per the video above here is the code that I referenced:2010 CSS link reference in Master Page:
<SharePoint:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/smallcalendar.css %>" After="corev4.css" runat="server"/>2010 CSS:
/**** Small Calendar ***/
.ms-acal-item{height: 10px !important;}

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 RowTable Row Left Site Actions Navigate Up Edit Tab List Browse Page Table Row Right Give Feedback Welcome Menu WorkspaceBody Container Title Row Title Title Logo Title Text / BreadcrumbPage DescriptionSocial Data SeparatorI like It Tags/Notes Top Header 2/Top Links li Static-Selected li Static SearchHelpStatus Bar Container Main A…