Ekomobile
Telecom app with 100K+ installs: eSIM, KYC and SIM pool
I was the product designer for the iOS and Android app and later also coordinated design and development across teams.
results
+10% eSIM connections in the first month after I redesigned the purchase and activation flow.
Identity verification (KYC) shipped before the legal deadline, so the company avoided regulatory fines.
One source of truth for the whole team: flow diagrams with system states, edge cases and errors became the main reference for product, backend, mobile and QA.
Design system in Figma with accessibility rules (contrast, touch targets); ready tokens and variants made handoff faster.
Features shipped, not shelved: autopayments, eSIM, SIM pool and identity verification are in production.
problem
The app was growing fast and already had tens of thousands of users. Requests came from different analysts and managers, each owning a separate module: tariffs, pricing, billing, connection quality. Specs and prototypes were written for the web and ignored mobile patterns.
Nobody had the full picture of how the app worked, communication between managers and backend developers often broke down, and there was no shared vision for the design system.
solution
I started every task by understanding the business goal behind it. I didn’t just draw the specs I received: I proposed better flows based on usability and mobile patterns, and balanced business goals, user experience, release dates and long-term support costs.
I took ownership of the design system and made sure every module used it consistently.
At some point I became the only person who knew how the whole app worked. To remove that bottleneck, I documented detailed scenarios for every module, so analysts, backend and mobile developers, managers and designers could find answers in one place instead of asking me. This grew into a product owner role on the agency side: I ran the backlog, proposed priorities by business value, deadlines and development cost, and agreed them with Ekomobile’s owners. All day-to-day communication with the client on development went through me.
Modules I designed and shipped
Autopayments
The analysts’ prototype put too much information on one screen. The real business goal was simple: get more users to set up autopayments.
In my version, Top up balance stayed the main action, and setting up an autopayment became a single checkbox in the same flow. Managing autopayments moved to a separate module where users can create, delete or switch the bank account. I also added an Accounts module to view, add and remove bank accounts.
So, with this solution:
The business goal is built into the main flow: users set up an autopayment while topping up.
Each scenario is short and clear.
Modules can grow independently, which makes the app easier to support.
eSIM purchase and activation
I worked on this module for several months. The original spec missed many scenarios and states, so together with analysts, business and backend we reworked the requirements.
I designed the full flow — payment, QR activation, retries and error states — and coordinated mobile, backend and QA through development. The module went through several launch versions, and I led all of them. I also designed the purchase flow for physical SIM cards.
Result: +10% eSIM connections in the first month.
Identity verification (KYC)
A regulatory requirement with a hard deadline. I designed the flow with every state and transition, wrote annotated scenarios for the team and coordinated mobile, backend and QA during development.
Result: shipped before the legal deadline, no fines.
SIM pool and connection quality test
I designed the SIM pool end to end and took it to launch: a connection quality test with different scenarios depending on the result, and switching between SIM cards from several operators. I coordinated the mobile, backend and QA teams through development and release.
Support chat
Designed the full UI with all states for the in-app chat with tech support and coordinated development.
Stories
Designed the in-app stories UI and planned a phased rollout with mobile, backend and marketing.
Widgets
iOS was straightforward. Android was harder because of the variety of screen sizes, so I found the balance between development cost and visual quality.
Design System
I audited the Figma file against what was actually in production, cleaned and restructured it, removed outdated components and added accessibility rules. Then I gave developers a step-by-step plan to roll out the changes.
