Client

Loominote AI

Year

2026

Timeline

8 weeks

Services

#AI Product #iOS #Redesign #UX Audit #Mobile App

Loominote AI — a voice task and smart notes app that was losing users before they even started

Full redesign of an iOS app for voice-first tasks and notes. Paid subscription conversion grew from 18% to 57%.

Challenge

Problems & solutions

1

Problem

Each bank wants its own set of services - from operations to investments and insurance. How to create a system for quickly assembling an app for each bank's unique requirements while maintaining UX quality? Without flexibility, banks won't buy the product, but complex customization will slow down launch.

1

Solution

Built a modular design system with ready-made solution blocks and components for each service. We select needed blocks (cards, transfers, investments) and quickly customize them to the bank's brand. Each block contains tested logic and UX patterns. The bank gets a ready app without designing from scratch.

2

Problem

Each bank has its own target audience by age - some work with youth, others with older clients, some with everyone. Young users want speed and modern interface, elderly want simplicity and clarity at each step. How to create one white-label solution that adapts to different age groups without redesigning?

2

Solution

Each bank has its own target audience by age - some work with youth, others with older clients, some with everyone. Young users want speed and modern interface, elderly want simplicity and clarity at each step. How to create one white-label solution that adapts to different age groups without redesigning?

3

Problem

White-label solution is sold to banks, not directly to end users. How to test app usability without access to real bank clients? Can't just release MVP and collect feedback - banks buy a ready product. UX errors will be discovered only after implementation, when fixes are expensive and time-consuming.

3

Solution

Conducted testing at three levels. First - with bank employees who know client requests. Second - interviews with real clients of different banks, identified common problems. Third - focus group of different ages and audit by UX experts. This allowed testing the solution before implementation and avoiding expensive fixes.

Research

Research process

Started by studying previous documentation - it described user problems and the history of all iterations.

Tracked changes in each iteration to understand which solutions worked and which didn't. This helped avoid repeating mistakes and build a redesign strategy based on real experience from previous versions.

Product & Service Audit

Analyzed financial products of different banks - from basic operations to investments and insurance. Identified common patterns and unique requirements of each bank. This determined the architecture of the modular system.

Product & Service Audit

Tested the interface with users of different age groups (from 18 to 70+ years). Identified which patterns work universally and where adaptation is needed. Studied popular apps in the country to use familiar patterns.

Iterative Prototyping

Created a series of prototypes with different modularity approaches. Tested with business units of bank clients, demonstrated assembly speed for their requirements. Each iteration improved the balance between flexibility and implementation speed.

Первый баннер

Loominote AI — a voice task and smart notes app that was losing users before they even started

Loominote AI — a voice task and smart notes app that was losing users before they even started

Текст первого баннера на странице

Full redesign of an iOS app for voice-first tasks and notes. Paid subscription conversion grew from 18% to 57%.

Challenge

Problems & solutions

Problems & solutions

1

Problem

Each bank wants its own set of services - from operations to investments and insurance. How to create a system for quickly assembling an app for each bank's unique requirements while maintaining UX quality? Without flexibility, banks won't buy the product, but complex customization will slow down launch.

1

Solution

Built a modular design system with ready-made solution blocks and components for each service. We select needed blocks (cards, transfers, investments) and quickly customize them to the bank's brand. Each block contains tested logic and UX patterns. The bank gets a ready app without designing from scratch.

2

Problem

Each bank has its own target audience by age - some work with youth, others with older clients, some with everyone. Young users want speed and modern interface, elderly want simplicity and clarity at each step. How to create one white-label solution that adapts to different age groups without redesigning?

2

Solution

Each bank has its own target audience by age - some work with youth, others with older clients, some with everyone. Young users want speed and modern interface, elderly want simplicity and clarity at each step. How to create one white-label solution that adapts to different age groups without redesigning?

3

Problem

White-label solution is sold to banks, not directly to end users. How to test app usability without access to real bank clients? Can't just release MVP and collect feedback - banks buy a ready product. UX errors will be discovered only after implementation, when fixes are expensive and time-consuming.

3

Solution

Conducted testing at three levels. First - with bank employees who know client requests. Second - interviews with real clients of different banks, identified common problems. Third - focus group of different ages and audit by UX experts. This allowed testing the solution before implementation and avoiding expensive fixes.

Второй баннер

I started with an audit, not with screens.

I started with an audit, not with screens.

Текст второго баннера на странице

Three reasons why the product wasn't converting.

Research

Research process

Research process

Started by studying previous documentation - it described user problems and the history of all iterations.

Tracked changes in each iteration to understand which solutions worked and which didn't. This helped avoid repeating mistakes and build a redesign strategy based on real experience from previous versions.

Product & Service Audit

Analyzed financial products of different banks - from basic operations to investments and insurance. Identified common patterns and unique requirements of each bank. This determined the architecture of the modular system.

Product & Service Audit

Tested the interface with users of different age groups (from 18 to 70+ years). Identified which patterns work universally and where adaptation is needed. Studied popular apps in the country to use familiar patterns.

Iterative Prototyping

Created a series of prototypes with different modularity approaches. Tested with business units of bank clients, demonstrated assembly speed for their requirements. Each iteration improved the balance between flexibility and implementation speed.

Третий баннер

Третий баннер

Третий баннер

Текст третьего баннера на странице

Шоурил

Onboarding

Onboarding

Текст для шоурила

Before redesigning the app — I started with onboarding. Completion rate grew from 8% to 52%. The client saw that the niche works — users just didn't understand the product.

Создание записи

Paywall

Paywall

Показать полный флоу создания записи от начала до конца — быстро и без лишних шагов. Акцент на том что запись создаётся в минимальное количество касаний.

The problem was in the price hierarchy — the annual total was shown large, the monthly breakdown small. Users saw $200 and left. I redesigned the entire paywall: structure, value presentation, and pricing logic. Conversion grew from 2% to 17%.

Тарифы

Hide completed

Hide completed

Показать переход из профиля в раздел тарифов. Экран тарифов должен выглядеть визуально сильно — это продающий экран продукта. Анимация перехода плавная и акцентированная.

Completed tasks stayed in the list and created visual noise. Users lost focus. I added the ability to hide completed tasks — priority stays on what matters now, history is never lost.

График работы Сценарий 1

Appstore

Appstore

Показать основной экран дашборда. Выходной день — переключение в рабочий. Появляются пустые слоты — постепенно заполняются разными клиентами. Появление уведомления о подтверждении записи внутри дашборда.

Текст для Appstore

Текст для appstore

График работы Сценарий 2

Onboarding

Onboarding

Переход на вид месяца — дни заполняются на индикаторе. Нажатие на день — появление всплывашки сверху с количеством клиентов и итоговой стоимостью.

Текст для onboaring

Управление записью Сценарий 1

Homepage

Homepage

Расходники Показать список постоянных расходников. В примере использовать реальные позиции для колориста: перчатки, краска, окислитель. Показать как выбираем расходники и как меняется итоговая цена записи при выборе.

They completed onboarding, paid — and deleted the app. LTV was zero, no one came back for a second month. The home screen didn't explain how to use the product: unclear structure, broken navigation, a banner that got in the way. I redesigned the hierarchy — now more than half of paying users renew their subscription.

Управление записью Сценарий 2

Task creation

Task creation

Чаевые и скидка Показать как применяются чаевые и скидка к записи.

Текст для Task creation

Настройка календаря Сценарий 1

Note editor

Note editor

График Показать экраны настройки рабочих дней: пн вт ср чт пт. Показать взаимодействие — включение и выключение дней, изменение рабочего времени.

The client thought that more buttons meant more visible features. In reality it was visual noise. Transcript, translation, editing — each action required going back and tapping again. I merged everything into one editor. Less choice — better product.

Настройка календаря Сценарий 2

Scan

Scan

Перерывы Настройка постоянного перерыва — добавление регулярного перерыва в расписание.

The feature was hidden, and after scanning — a blank screen with no feedback. Users closed the app thinking it had frozen. I made the feature accessible from the unified creation point and added a loading state — now the product explains what's happening under the hood.

Настройка календаря Сценарий 3

Voice recording

Voice recording

Перерыв в течении дня Уже в графике — постановка разового перерыва прямо в текущем рабочем дне.

Voice was the only way to create — the client saw it as an advantage. In practice it cut off everyone who found voice input inconvenient. I moved the recorder off the front stage and placed it alongside all other creation methods. Everyone finds what works for them — voice, text, scan or photo.

Геймификация Скролл навбара

Publish content

Publish content

Геймификация Показать микроанимации и UX решения. Анимация возврата на сегодня когда ушёл на 10 дней вперёд. Кнопка назад при скролле. Дополнительные элементы геймификации на усмотрение дизайнера на основе реальных экранов проекта.

A unique feature — from a note straight to social media. But it used to be a list of buttons all leading to the same action. I unified everything into one point — choose the format, AI adapts the content. A note becomes a post, an email or an article.

Геймификация Скролл дня

Mind map

Mind map

Геймификация Показать микроанимации и UX решения. Анимация возврата на сегодня когда ушёл на 10 дней вперёд. Кнопка назад при скролле. Дополнительные элементы геймификации на усмотрение дизайнера на основе реальных экранов проекта.

Текст для Mind map

Геймификация Скролл дня

Results

Results

Геймификация Показать микроанимации и UX решения. Анимация возврата на сегодня когда ушёл на 10 дней вперёд. Кнопка назад при скролле. Дополнительные элементы геймификации на усмотрение дизайнера на основе реальных экранов проекта.

A product is built not on guesses — but on hypotheses that are validated with data. Every decision in this project went through audit, testing and measurement. You don't need to reinvent — you need to implement patterns that already work and that people already understand.

© 2015

Design by

Vadim Gaidamakin