LamTakam AILam Takam AI

Lam Takam took shape from the ground up during my time at DaapApp, in collaboration with the CTO and engineering team. The product aimed to make GPT and language-model services easier for Iranian users to access. Alongside general conversation, it offered specialist lifestyle, legal, and medical flows.

The problem and goal

Access difficulties, foreign-currency payments, and the complexity of international tools formed the context for the product. The design goal was a clear route from entry and service selection to receiving an output. In specialist services, users provided the needed information through relevant questions.

I carried out market research and competitor analysis, and contributed to product definition, initial requirements, and feature prioritization. I designed the information architecture, user flows, UX/UI, and design system, and prepared product documentation for implementation.

I worked closely with the CTO and engineers during development. Final approval of the roadmap and priorities remained with business leadership.

In the main experience, users could choose a model, start a conversation, and access specialist-service categories. Saving and managing history also let them return to earlier conversations.

Someone else selected the question content. My responsibility was to design how the questions were presented, their order, and how the flow was divided into steps.

In the lifestyle example, users entered a goal and related information, moved forward and backward between steps, and received an output at the end.

Profile and account

The profile was designed for managing account information, accessing messages, and following transaction and wallet records. Personal information, an account summary, and related routes were organized in a defined structure.

Checking an answer’s sources

Sources used for the individual answer were presented as a list of links for users to inspect. This concerned the answer’s sources, not disclosure of model-training data.

The project was implemented with the technical team using the documentation. QA carried out tests, and the designs were revised several times. I also contributed to the beta release and later improvements. Behavior and product-data analysis informed refinements to flows and UI and reconsideration of feature priorities.

The mobile version was implemented as a PWA. The product was released and, according to the recorded information, had active users. The selected designs were implemented. User counts and numerical business outcomes are not recorded for this narrative.