From the mid-20th to our current 21st century, our times have been referred to as the digital age, information age, and more. Information has become a commodity that is quickly and widely disseminated and easily available. Every moment of every day, people are seeking content. Whether news, podcasts, reviews, case studies, products, articles, e-books, or more, people constantly seek content and information unique to their desires and needs.
While seeking this information, we frequent multiple websites throughout the day and often find numerous tabs open in our browser window. When on the go, we use our mobile devices to search the web or utilize mobile applications to meet our needs. Being mobile or stationary does not affect the rate at which users expect to access the information they are seeking.
Users need to feel comfortable and capable while accessing the information they seek regardless of the method used to access this information. Therefore, websites have become responsive, formatted to fit the screens of our many devices. Furthermore, websites, software, and services have developed companion apps so users can accomplish their goals conveniently and effectively. These days, it is common to have a companion app for a site, software, or service, and sometimes odd when one does not exist.
However, the organization and flow of an app or site are crucial. If an app or site is ill-organized, confusing, and challenging to navigate, the user will likely become frustrated and forego utilizing that platform.
Information Architecture
In User Experience (UX) Design, Information Architecture (IA) is the science of organizing and structuring content in a logical user-friendly way. This discipline focuses on the organization of information within digital products, such as applications, software, and websites.
Information Architecture considers the user while structuring the content the user is seeking. Solid structure and flow within the apps and websites we utilize help us locate the content we want effortlessly. If users can find the content they are pursuing straightforwardly, they are more likely to continue utilizing the app or website.
IA Visualizations
UX architects understand how the end-user will interact with a platform. They unite the platform and user in a way that makes sense and is comfortable for the user. UX architects achieve information architecture by focusing on the structure and flow of digital products. They conduct research and translate and organize the information into visual representations including sitemaps, wireframes, and prototypes.
Site Maps
A UX site map is a visual representation of the architecture of a website. Site maps are like the table of contents, working as a visual index to a site, displaying where pages are located and what they contain. They are hierarchical diagrams that display how pages are prioritized, linked, and labeled. Information Architects build site maps to clarify the purpose and goals of a website, communicate the structure and flow of a site to colleagues and team members working on the site, or analyze the organization of an existing site for improvement.
My Site Map Exercise
In my last post, I analyzed the structure and flow of the City of Baltimore website. Websites for counties, cities, and town municipalities are widely known for having poorly organized websites overloaded with content. At first glance, the website of the City of Baltimore appeared to be more organized and simplified than the average Maryland city site. However, my site map exercise revealed some issues and pain points within the site structure.
First, I developed a site map for Baltimore’s current site. I found that some content in the current structure was redundant, some content was outdated, and some content felt out of place. Following my findings, I created a new site map, rearranging the content to propose an updated structure and flow for the site and improve the user experience. Below are my current and proposed site maps for reference. You can also view the PDF for a closer look.
City of Baltimore Companion App
Since mobile apps are highly sought after and utilized frequently, creating a companion app for the City of Baltimore would impact the city’s users and residents positively. When developing a companion app, UX professionals think about the users on a broad scale while also considering a niched group within those users—users accessing content mobily. Although an app and a site can both serve the City of Baltimore, they can serve the city in different ways.
Succeeding my site map exercise, I created a map for a potential companion app. Before creating the diagram, I reviewed the content on the City of Baltimore’s current site and asked my following questions:
- Should all content be included in the app?
- What information would mobile users benefit from the most? What pages/content would residents want to access on the go?
- What will make this app useful?
Here are my answers.
Should all content be included in the app?
All content on the City of Baltimore site does not need to be included in a companion app. Considering that the app would need to be useful and produce results rapidly, residents and users would want to utilize the app to access news, events, services, and the city’s directory primarily. Furthermore, it is likely that they already became familiar with the city’s content via the website. They would not need a full introduction to the mayor, cabinet, mayoral offices, etc. Additionally, there would be no need to view a photo gallery or stream of city-related tweets. These things could be linked externally. The app would limit the site’s content to information residents would need to access and reference quickly.
What information would mobile users benefit from the most? What pages/content would residents want to access on the go?
Mobile users would want to access information and services that interest them or impact them directly. This content includes news articles, upcoming events, service requests, government branch information, and the city’s online payment portal.
What will make this app useful?
Creating a companion app that makes processes smoother and more convenient would be more convenient for users and residents. Making payments and submitting service requests on the go would help users save time and accomplish their goals. Similarly, reading the latest news or viewing events concerning the City of Baltimore within an app would keep users informed favorably. Users would no longer have to search the web or visit the city’s site to access this content unless they desired to.
After reviewing Baltimore city’s site content and answering my research questions, I created a map for my proposed companion app. Here’s the final diagram.
Companion App Explained
In short, Baltimore city’s companion app would house five main screens within a bottom icon navigation. The five main screens are as follows: News, Events, Services, Directory, and More. Similar to the site, the app would also have a header on every page, containing the city’s logo, a search bar, a language selector, and a link to the online payment portal.
To refrain from overloading the app with content, the “News” and “More” screens within the app would contain external links to additional information existing on the main site if the user wanted to dive deeper into the city’s content. For a closer look and more understanding of the page organization, view the full PDF.
Final Thoughts
According to Vibryt, “An app is a way to bring your consumer closer to your products or services. It allows customers to easily interact and make transactions without physical limitations.” A companion app is a great way to further unite a user with a site, software, or service. There are companion apps for online banking portals, companion apps for Adobe’s design software, companion apps for online shopping at companies like Amazon, Target, Etsy, and more. Apps assist users with accomplishing their goals quickly, conveniently, and comfortably.
However, when creating an application, the Information Architecture of the app is significant. All the information within a website does not always need to carry over to the app. Furthermore, the structure and flow of the app affect the user’s experience. If the app helps the user access what they need seamlessly and smoothly, without roadblocks, it’s quite possible that the user will default to utilizing the app over the site. The apps IA will make or break the experience for the user.
Sola's Thoughts 