MyFrontier App Redesign

The MyFrontier app covered bill pay, account management, technician scheduling, and support, but the experience didn’t hold together. As Associate Design Director on a small team close to dev, I rebuilt the visual design and the layout system. The motion language I built from scratch targeted specific moments: payment confirmation, appointment scheduling, setup completion.

Interface Design

I designed every core screen: onboarding, dashboard, bill pay, and support. The layout system prioritized information hierarchy: the most important action on each screen got the most visual weight, and secondary actions were consistently grouped so users built muscle memory across flows.

The Problem

Nobody opens a telecom app to browse. They open it because they have a question about their bill, because a technician is coming and they need to confirm the window, or because their internet is down and they need answers fast. The MyFrontier app had accumulated inconsistencies across years: layouts that varied from flow to flow, controls that gave no feedback, and zero motion. Every fix had to respect those real-world stakes. People in a bad moment shouldn’t have to think about the interface.

The Work

I owned layout design across every screen and defined visual hierarchy for core UI components: navigation, appointment calendar, and selector patterns throughout bill pay and account management. The structural decisions made the app feel like a single product: information priority per screen, primary actions sized beyond what the tap target required, consistent control grouping. Alongside that, I built the motion system from scratch.

Motion Design

I built every Lottie file personally in After Effects, exported through the Lottie pipeline. Each animation answers a question the user is already asking. Did my payment go through? Is my appointment confirmed? The coin confirmed a payment was processing, the leaf signalled setup completion, and the intro sequence covered the initial data load so the app felt responsive from the first tap. I delivered motion specs alongside the files: easing values, timing, and documentation so dev could implement without guesswork.

What I Learned

In a utility app, the user’s trust is already conditional. A telecom app can’t afford animation that says “look at us.” Each animation had to solve a specific problem or it got cut. That constraint produced better work than having free rein would have. The motion specs and dev handoff documentation mattered as much as the animations themselves. Without clear easing values and timing, the implementation would have drifted from the intent.