Tawaqo — Building mobile commerce for Iraq
I led a three-person design team building Tawaqo from zero for mobile shoppers in Iraq. We connected physical shopping and a newly launched Gift Zone, then kept revising the flows through surveys, customer contact and event monitoring.
Delivery scope
Monthly B2C users
B2C only; reported product scale, not a growth or conversion metric. Gift Zone is newly launched.
The problem & the evidence
Where the problem came from
Refunds, cash on delivery and unfamiliarity with common website interaction patterns were major challenges in Iraq. We could not assume that familiar e-commerce conventions would be familiar to our customers. Research and support contact continually informed changes to the product.
- Ongoing customer surveys and direct customer conversations.
- Support feedback and monitoring of product events.
- Original mobile designs and the live B2C storefront.
- Research methods
- Surveys, customer conversations, support feedback and event monitoring.
- Results documentation
- Ongoing research and iteration. Study sample sizes and experiment results are not published in this case.
- Users struggled to identify the correct region.
- Added a Help Center in Profile and contextual guidance in a bottom sheet matched to the current brand or category.
- Location selection caused difficulty.
- Made the step optional and accepted the resulting increase in support workload.
- How it was measured
- The product has 3,000 monthly B2C users, reported by the design lead. Surveys, customer contact and event monitoring support ongoing iteration. No conversion uplift or refund reduction is claimed here.
- A/B testing
No A/B test result is documented for this case. The changes described come from ongoing research and product observation.
Measurement context
The monthly user figure applies only to B2C; its reporting period and activity definition are not specified here. B2B figures are confidential. Gift Zone has recently launched, so mature outcome claims are not available. The screenshots are design artifacts, not evidence of live prices or measured results.
Decisions & leading the team
Help without leaving the purchase
Surveys showed that users could not reliably identify their device or account region. I added a Help Center in Profile and brought relevant guidance into the buying journey. A bottom sheet opens content matched to the current brand or category, so users do not have to leave and search for the right article.
Optional location, with an operational cost
Customers struggled with location selection, so we made that step optional. This increased support workload. We accepted that trade-off rather than keeping a difficult step mandatory; it remains part of our ongoing monitoring and iteration.
One system for two shopping contexts
The physical store and Gift Zone needed distinct identities without becoming unrelated products. A shared design system, component structure and familiar flows were central design challenges. The mobile layouts show a common Store / Cards entry with category-specific content and purchase requirements.
The service model: two purchase paths
The digital purchase journey
- User
Browse Store or Gift Zone
Choose a category or brand.
- User
Check product requirements
Choose the region and value, or enter the top-up destination.
- System
Offer relevant help
Open brand- or category-specific guidance in a bottom sheet when needed.
- User
Confirm and pay
Review the total and use an available local payment method.
- System
Show the order state
Distinguish confirmation in progress from delivery or a problem that needs follow-up.
Screens & design decisions
The mobile storefront
The Store / Cards switch connects physical shopping with gift cards and top-ups. Categories, offers and product browsing remain within the same product. This is a Figma design export, not a live-site capture.
Gift Zone: a different catalogue, a familiar structure
Brand, category, region and delivery labels help distinguish digital products. The purple identity separates Gift Zone while the shared entry and navigation keep it connected to Store.
Region and value before purchase
The product page exposes region, denomination, availability and redemption help before payment. Surveys revealed that users needed help identifying their device or account region.
Direct top-up has its own confirmation
A direct top-up needs a phone number rather than a redeemable code. The confirmation sheet shows the destination, amount and local payment options together.
Payment confirmation is a separate state
This design makes a pending bank confirmation visible instead of presenting the order as delivered. The time estimate and promotional values shown belong to the design and are not portfolio outcome metrics.
My direct work
- Led a team of three: myself, a senior product designer and a junior product designer.
- Led the design work for a mobile product built from zero, including consistency between Store and Gift Zone.
- Used surveys, customer conversations and event monitoring to identify friction and keep simplifying the flows.
- Proposed contextual help for region selection and made location selection optional in response to customer difficulties.
What I learned
Removing a step can move work to another team. Making location optional reduced a mandatory demand on the customer but increased support workload; both sides belong in the design decision.