A Whirlwind Launch Story: Kurly's Beauty Kurly App Service

Kurly carried out two major tasks simultaneously in 2022: a product overhaul and the launch of Beauty Kurly. The Beauty Kurly deployment was targeted based on business factors set before August, and developers had to handle product overhaul QA and Beauty Kurly development in parallel.

Introducing the 'site' Concept and Architecture Changes

During Beauty Kurly development, the app-level concept of 'site' was introduced. The existing legacy code had a structure where a single class created all app-wide dependencies, but to solve the problem of API paths changing when the site changed, the dependency injection method was modified. Initially, the site property was injected directly, but this caused the RootViewController to be re-created when switching sites, resulting in unnecessary API calls.

To solve this, the approach was changed to injecting a site service class and subscribing only when needed, using an event-based method. This improvement prevented RootViewController re-creation and reduced API calls, shortening loading time.

Templating Sections and Improving Inflow

While Market and Beauty Kurly display different products, their UI forms are similar, so sections (Guza) were templated and modeled to be handled dynamically through the back office. This improved code reusability and made maintenance easier.

After launch, feedback indicated that the conversion rate of the top switch button was low, so a floating button called 'Dungdungi' was introduced in the Kurly recommendation tab. Designed with the concept of an 'eye-catcher,' this button contributed to increasing inflow to Beauty Kurly by encouraging clicks. The developer worked on design and development in parallel to implement an experimental UI, and learned the importance of reflecting the perspectives of collaborating roles.