Mfatech · 2024
Shipping a Complex Mobile Product
30+ mobile screens and backlog clarity for an EV charging app, working with a 6-engineer team
30+ screens · 6 engineers
01 Status
UX / product scoping - shipped product context
UX scoping and backlog work completed. The product shipped and reached 10,000+ users within months of launch. I include that figure as product context, not as a personally owned growth result.
02 Summary
Mfatech was an EV charging mobile app project where my contribution focused on UX and product scoping.
I scoped and designed 30+ mobile screens and supported backlog clarity for a 6-engineer team across the charging service experience.
The product later reached 10,000+ users within months of launch.
03 Problem
The problem was to turn a multi-step EV charging service experience into a clear mobile user flow that engineering could work from.
The product needed screens that reflected real service steps: finding a charger, understanding availability, starting a session, managing payment or session state, and handling edge cases clearly enough for implementation.
04 My Role
- Competitive analysisReviewed competitor EV charging apps to inform product scope decisions.
- UX / product scopingTranslated the multi-step charging service into a structured mobile user flow.
- 30+ screen designDesigned the full mobile screen structure across the charging experience.
- Backlog supportWorked with the six-engineer team to keep the backlog clear and give development a more defined build direction.
05 User Flow

06 What This Proves
- Service flow to productI can translate complex service workflows into clear mobile product flows.
- Engineering clarityI can support engineering clarity through UX scoping and backlog organisation.
- Shipped product exposureI have worked in a real product context that reached market and real users.
- Product definition for engineeringI translated a complex mobile flow into clear screens, scope, and backlog direction that engineering could build from.
If a complex workflow needs to become screens, scope, and a backlog your engineers can work from.