Case Study: MyRogers App

Sep 5, 2026

I reviewed five parts of the app: Login, Dashboard, Navigation Menu, Support Chatbot and the “More” section. I scored each one against a set of usability criteria, and for each one I mocked up a side-by-side “current vs. proposed” redesign in Figma. The proposals cut extra steps, reduce how much users have to think about, and make each part of the app easier to use.

Case Study: MyRogers App

Sep 5, 2026

I reviewed five parts of the app: Login, Dashboard, Navigation Menu, Support Chatbot and the “More” section. I scored each one against a set of usability criteria, and for each one I mocked up a side-by-side “current vs. proposed” redesign in Figma. The proposals cut extra steps, reduce how much users have to think about, and make each part of the app easier to use.

CLIENT

SAIT / Interaction Design Class

CLIENT

SAIT / Interaction Design Class

Role

UI/UX Designer

Role

UI/UX Designer

Parallax image
Parallax image

Problem

Problem


Login (Usage 1/5):

Signing in took several steps and opened a pop-up form. The “Register” button didn’t open a sign-up form. It sent users to call Rogers support instead, which was misleading. The extra steps are especially confusing for older adults.



Dashboard (Usage 1/5):

The home screen mixed promotions with the Usage, Phone and Plan tabs. Some information didn’t match the feature it was listed under, and the layout felt scattered and hard to read.

Navigation Menu (Usage 2/5):

Six tightly packed icons looked busy and made it easy to tap the wrong one, especially for older users.


Support Chatbox (Feedback 2/5, Usage 2/5):

The chatbot, “Anna,” only let users pick from preset options and wouldn’t accept typed questions. It kept looping back to the same answers, with no progress and no way to reach a person.


Solutions

Solutions

Proposed Improvement and Solutions
  • Login: One screen where users sign in as soon as they open the app, with username, password, “Remember username,” “Forgot password,” guest sign-in and a working Register link. It follows the login patterns people already know from other apps.

  • Dashboard: I removed the Phone and Plan tabs and moved that content elsewhere in the app. The new home screen is organized as an account summary and balance, followed by quick “View Bill” and “Make a Payment” buttons, then data usage, then the current bill cycle, with promotions moved to the bottom.

  • Navigation Menu: I cut it down to four clearly spaced tabs:

    • Home: account, usage and last bill

    • Billing: balance, bill and payment

    • Shop: categories and offers

    • Support: help topics and the chatbot

Fewer, better-spaced tabs mean fewer accidental taps.

  • Support Chatbot: Users can type their own questions, and a “Talk to an Agent” option appears after 2–3 failed bot attempts, so they’re never stuck in a loop.

  • “More” Section: I removed “More” from the navigation bar. Its contents now live under a “Settings” screen with clear Account and Support groups, reached from the profile and settings icons at the top of the app.

    Output: Figma Link (View Only)


    Preview: