Еkоmоbilе

B2C SaaS, MVNO mobile services platform for iOS and Android, where I worked as Project Coordinator and UI/UX Designer.

problem

The project was growing fast — tens of thousands of people were already using it. Tasks came from different analysts and managers, each one owning their own module: tariffs, pricing, billing, connection quality. Prototypes and specs were made for the web version and weren't adapted to mobile patterns.

There was no single source of truth for how the app worked as a whole, communication between managers and backend developers often broke down, and nobody had a clear vision for the design system.

solution

I always started with understanding the business task behind the request, and from that I built my solutions. I took a proactive position: I suggested improvements to prototypes and user flows, based on usability and mobile app patterns. When I made decisions, I tried to balance the business task, mobile patterns, user experience, timing for release, and how hard the feature would be to support and grow later.

I also took ownership of the design system — creating it and making sure it was used consistently across all modules.

At some point I realized I became the only source of knowledge about how the whole app worked. To fix this — so the team didn't depend only on me — I started collecting detailed scenarios for all existing functional modules. I made them so analysts, backend developers, managers, designers and mobile developers could all use one same source of knowledge, instead of asking me directly every time.

This helped me grow into a project coordinator: I gave tasks to designers and the dev team lead, worked with different departments, and followed up on feature releases.

Modules I designed and took to release

Autopayments

Analysts gave me the spec and prototype for the Autopayments feature. The prototype was not convenient, too much information on screen. I understood the real business goal — to make more users set up autopayments. Based on my experience, I made my own version.

In my version the main action stayed Top-up Balance, and creating an autopayment became very simple — just one checkbox. I moved autopayment management to a separate module, where user can create, delete an autopayment or connect it to a different bank account. Also I added a module Manage Accounts, where user can view, connect and delete bank accounts.

So, with this solution:

I solved the business goal — when user tops up balance, he can also create autopayment in same moment, it happens automatic.
Scenarios became simple and clear for user.
App support became easier. Now modules can grow independent from each other.

eSIM Connection Module

I was preparing this module for development for several months. After getting the spec from analysts, I found a lot of scenarios and states that were not thought through. Together with analysts, business representatives and the backend team, we reworked the functional requirements for the module.

I finished the scenarios and prototypes for the mobile app screens, so it would make development faster and the module's logic easier to read for the whole team.

After the design was approved, I coordinated the mobile development team, backend developers and QA department. I was responsible that the mobile team implement the functionality as fast as possible.

Document Verification

The task came in — build a document verification module, and fast. I worked together with the analytics team, business team and backend developers. Based on the spec, I made prototypes, covered all states and transitions, and put together full scenarios with comments.

During development, I coordinated the mobile team, backend team and QA. Sometimes I had to work overtime, so the company would not get fined.

Connection Quality Test

I designed the prototypes and flow for the feature where the user runs a test of connection and internet quality and sees the results. I also planned different scenarios depending on the test result. For Android users.

I coordinated the mobile development, backend and QA teams during development and rollout.

Chat

Designed the full UI with all states for the in-app chat between the user and tech support. Coordinated the development.

Stories

Designed the UI for the in-app stories feature. Planned a step-by-step rollout of the full functionality. Coordinated the mobile development, backend development and marketing teams.

Widgets

I designed the widgets. There were no problems with iOS. Android was harder — it has more screen sizes and more flexibility. I made a design with the best balance between development cost and how good it looks on screen.