Skip to main content

Studio archive · Case study

TimePassages

Redesigning a complex astrology app without stripping away its depth

TimePassages redesigned current astrology chart screen

The brief

TimePassages had grown across dense charts, profiles, forecasts, comparison tools, purchases, learning, and settings. Waverly Lab was brought in to redesign those connected experiences as one coherent mobile product without flattening the depth its users relied on.

What we did

  • Product strategy
  • Information architecture
  • Product design
  • Prototyping
  • Design systems

Shipped product

Confirmed project outcome

The redesigned TimePassages experience shipped.

Core flows moved from information architecture and wireframes through high-fidelity design, an interactive prototype, a reusable component system, and developer handoff.

01

Give dense information a clear hierarchy

Astrology charts compress a large amount of technical information into a small screen. The redesign established a consistent hierarchy across charts, profiles, transits, progressions, comparisons, settings, and forecasts so people could move through the product without relearning the interface on every screen.

A coordinated light-and-dark visual system preserved the atmosphere of the product while making navigation, controls, errors, and paid features easier to recognize.

02

Put explanation next to the moment of need

The product serves people with very different levels of astrology knowledge. We designed learning details, hints, contextual explanations, and a complete symbol and icon language so advanced ideas could stay in the product without becoming a wall for newer users.

Onboarding and profile creation were rebuilt around clearer choices, including location, birth time, chart settings, and the option to continue when information was unknown.

03

Leave behind a product system, not a stack of screens

The engagement produced low- and high-fidelity flows, an interactive prototype, reusable components, typography and color styles, icon families, and a final user-flow document for implementation.

That system gave the shipped redesign a common language across onboarding, subscriptions, purchases, profile management, charts, learning, and the long tail of application states.

Two audit slots at a time.

Start is usually within the week.