08 · Customer energy portal · Legacy project

My legacy energy portal

Mkaly Energy App

Mkaly is the customer-facing energy portal I worked on to bring public information, account access, billing, payments, and consumption-related tasks into one web interface.

Abstract energy flow from a utility meter through consumption stages to a household load

01

Problem

I wanted to bring common energy-account tasks into a clearer path instead of leaving people to navigate disconnected service channels.

02

Constraints

  • I treated billing and consumption information as privacy-sensitive by default
  • I kept real customer data out of the account and authentication examples
  • I made the main actions understandable for non-technical users
  • I limited this case study to public or empty interface states

03

Technical decisions

  • I built the Mkaly interface with Next.js and React
  • I worked with a Django backend in the original implementation
  • I separated public information, projects, billing, account access, and administration into distinct views
  • I used Tailwind CSS for the responsive utility styling

04

Evidence

  • I verified that the public landing page still responds
  • I captured the available interface states and confirmed that their images load without broken resources
  • I have not re-tested the source, authentication, billing data, or account workflows

05

What I learned

Mkaly showed me that a utility portal has to turn sensitive operational data into clear actions while keeping authentication and privacy boundaries obvious.