Skip to content

Collapse unit converters into single page and refresh layout #594

Open

Description

Problem Statement
Today, we treat each converter type as a high-level navigation item. This means that if you want to switch between volume and weight converters, you need to navigate to an entirely different page. While we do offer shortcuts to switch between modes, they are not very discoverable (#157), and parsing a mixed list of calculators and converters is unnecessarily more complex than it needs to be. Furthermore, the converter page interface is laid out differently than other calculator modes and feedback suggests that the interface could be made more intuitive.

image

Evidence or User Insights
We currently have a flat navigation structure. According to app navigation guidance, this structure is appropriate when there are less than 8 pages in the group. We already have 13 converters, and #515 is looking at evaluating which converters and units we include, and suggests we may actually be missing some converter types (increase to 17). In this case, hierarchical or an alternative navigation would be preferred.

Some other UX issues have been identified as well. It is unclear how to quickly switch units (#172 and #266). There is some additional conversation in #382 and #379 as well.

Proposal
Collapse converters into a single "Converter" page where you can select the type of conversion in addition to the units. There may be an opportunity to streamline input even further with #589 to allow users to input any unit they like without having to explicitly select a converter type first.

Goals

  • Collapse top-level converter navigation into a single Converter (open question: does currency converter feel different enough to remain separate?)
  • Redesign page layout for greater consistency with other calculator modes
  • Redesign value input to align with other converter patterns (e.g., found in translation apps)

Non-Goals

Low-Fidelity Concept
image

Bing Translator/Converter UX (for inspiration)
bing

image

Requested Assignment
I'm just suggesting this idea. I don't want to implement it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions