I had the opportunity to work closely with Atomized on a few occasions, most notably on a system-wide redesign of the flagship product.
end result
Objectives
The goal of this redesign was to address the pain points and bottlenecks of the previous design while visualizing the data using as much of the viewport as possible. I aimed to achieve that with an expandable interface that sat around the outer edges of the screen.
The goal of this redesign was to address the pain points and bottlenecks of the previous design while visualizing the data using as much of the viewport as possible. I aimed to achieve that with an expandable interface that sat around the outer edges of the screen.
high-level interface
Integration
Now that we've examined the interface around the edges, let's dig into the guts of the app and show data visualization, page hierarchy and layout, and how each page co-exists with the high-level interface.
Now that we've examined the interface around the edges, let's dig into the guts of the app and show data visualization, page hierarchy and layout, and how each page co-exists with the high-level interface.
page-level interface
Previously
Prior to engaging in the full-bodied redesign above, I worked with the Atomized team to make the calendar experience more intuitive. Some of these observations below ultimately found their way into the redesign above.
Prior to engaging in the full-bodied redesign above, I worked with the Atomized team to make the calendar experience more intuitive. Some of these observations below ultimately found their way into the redesign above.
earlier attempts to reimagine the calendar format
earlier attempts to improve the delivery of content
Editing Flights
The team had originally developed the app to account for a limited number of assets for each flight. The challenge was to design a screen that would encourage user behavior to change by delimiting capacity so that what used to be done with several flights can now be accomplished with one.
I recommended a compartmentalized fullscreen modal solution that allows the user to navigate between assets easily and view the flight history without feeling overwhelmed.
The team had originally developed the app to account for a limited number of assets for each flight. The challenge was to design a screen that would encourage user behavior to change by delimiting capacity so that what used to be done with several flights can now be accomplished with one.
I recommended a compartmentalized fullscreen modal solution that allows the user to navigate between assets easily and view the flight history without feeling overwhelmed.
