In general, there were no overwhelming challenges. Both project team members and their Powercode team leads are deeply experienced in areas of e-commerce, food-tech, retail, and delivery, are familiar with different payment gateway integrations, and loyalty program implementations. Both traditional, marketplace, and recurring transactions and any complex monetization logic are not an issue at all. So in most cases, we just had minor routine organizational and communicational problems, which were monitored and resolved during the day under the watchful supervision of our technical project manager. For instance, our mobile developer worked separately from Guillaume, who developed the back-end, and in different time slots, so it was really important to sync team daily goals, clearly report on progress and problems, and resolve or avoid any miscommunications that could cause extra effort for both developers.
Regarding functionality, both the Wine browsing screen and Chatbot had rather complex implementations. The Wine browsing screen has a lot of selecting filters, a search bar, and a slider for selecting a price range. The set of all screen filters is synchronized with the filters in the search window. Filters are divided into two types: chips, and sliders. Each type has a different logic for building a search link. Moreover, screen content flexibility also adds complexity. Since the content of the application is managed by the admin, we can have different sets of blocks for the campaign screens and the main browsing screen.
Regarding the Chatbot, indeed, it’s not just a bot. All content is initially obtained from the back end, and we simulate the communication with the user. It has a large amount of logic for simulating a set of messages and handling the user’s response. Each user’s response is converted to a search query, from which we compile a link with a list of products, individually recommended to the user.