Case study · 2021–2022

Moi Svet.

A customer portal for monitoring electricity use

I adapted work from an enterprise energy platform for customers: I designed connected web and iOS flows, refined the interface through early checks and created the product's visual identity.

Role
UX/UI Designer
Platforms
Web portal · iOS
Status
iOS implemented without a public launch; web concept and prototypes
The Moi Svet web portal and iOS app screen
01

Context

From a B2B platform to a customer portal

Readings, consumption and documents — without industry complexity

The team had already developed work for an enterprise energy platform. As the product expanded into a customer portal, the audience changed: the interface would serve the company's customers rather than industry professionals.

Users needed to see readings quickly, understand consumption trends and find documents or payment options. I helped prepare user stories with the Product Manager, created prototypes and designed interfaces for both platforms. He defined the product concept and approved the UX; I designed the visual identity and some interface solutions independently.

The design challengeKeep the underlying data logic consistent while making readings, meter states and documents understandable without knowledge of industry terminology.
02

Checking the solutions

Hypothesis → prototypes → changes

The checks led to changes in layout, colour palette and data priorities

We started with the assumption that users needed clear readings and device states. Following a preliminary survey, I prepared prototypes and checked whether people could complete the flow and find the information they needed without unnecessary questions.

Company employees who were not involved in the product worked through scenarios as stand-ins for end users. These hallway checks typically involved 2–3 people.

Based on the feedback, the team made the layout more familiar and revised the palette, font sizes in data-dense areas, icons and labels.

In iOS, we refined the priority of readings, charts and device states, making them more prominent than secondary information.

The checks helped refine layout, labels and visual emphasis, but do not validate the needs of all customers. Full testing was planned for after release.

03

Solution

One system · two contexts

A detailed web portal and quick mobile access

The web portal brought together full information on facilities, readings, statistics, finances and documents. In iOS, the first screen focused on key data and notifications.

Readings

Understand a facility's status

Customers can see current readings and device status. The flow provided for manual submission and the option to receive readings automatically from a meter.

Web: facility details; iOS: essentials on the first screen

A web meter detail view and a mobile readings screen
Readings and status: web and iOS
Consumption

See the trend

History and charts help users assess consumption over time. The web interface provides more detail; the mobile screen keeps the key chart within easy reach.

Web: tables and statistics; iOS: a concise trend view

Consumption charts in the web portal and app
Consumption history: web and iOS
Documents and payment

Find financial information

Documents and payment flows are linked to the user's facility. The web interface presents the full information, while iOS provides access to key documents on the go.

Web: finances and documents; iOS: bills at hand

Documents and bills in the web portal, and bill export in the app
Documents and bills: web and iOS
04

Outcome

Results and reflection

iOS in code, web in prototypes

I designed the UI, visual identity, logo and mascot for the customer portal. I added custom icons to the system icon set and used stock illustrations.

iOSThe screens were implemented in code with close fidelity to the designs. There was no public launch.
WebThe portal remained a concept and prototypes.

No structured testing of the finished app took place during my involvement; only the build was checked. There is no data on its impact on product metrics.

What I would change todayI would revisit the visual style, break long forms into steps and give readings and device states greater prominence.