Role
Platform
Live app
Timeline
purchase conversion
Side-by-side plans: +21% projected 1-year ARPU in an A/B test.
ARPU
Personalized onboarding: +35% purchase conversion in an A/B test.
MRR
Redesign release: −38% refund rate, March vs. June 2026.
The challenge
By October 2025, Chat AI Plus was losing ground. Purchase conversion and revenue per user had dropped, and refunds had risen. Support tickets, App Store reviews, and my review of competing apps showed why.
To convert more users and keep them, the app had to be:
Worth paying for
Other AI apps offered more features for the same price. Ours had to close the gap.
Easy to use
The UX had aged. Existing features needed to be simpler and more capable.
Modern
The UI looked dated. Users needed a product that felt as modern as the AI inside it.
Revenue
Giving users the confidence to subscribe
A full redesign was a bigger bet that called for deeper research, so we started where users decided whether to subscribe. Across three A/B tests, I redesigned the onboarding, the paywall, and the screen after it.
Personalizing before the paywall
Our onboarding showed a few feature screens, then the paywall. I expected setting up a personal assistant to make the app feel tailored, so more users would subscribe. The trade-off: a longer onboarding could raise drop-off.
I added questions about goals, interests, AI experience, and name, then a screen showing the assistant being built from their answers. These choices ordered the app’s prompt categories, and the chat addressed users by name.
Research insight:
Competing AI apps and web funnels often personalized the experience before asking users to pay.
A/B test · Personalized onboarding
Setting up a personal assistant made users more willing to subscribe
+35%
purchase conversion
+45%
ARPU
+43%
trial-to-paid
Drop-off rose, but the gain at the paywall outweighed it. Refunds didn’t rise.
Showing plans side by side
Our paywall initially showed only the yearly plan. A free trial toggle swapped it for weekly. After the yearly price rose, its refunds doubled, so the toggle was turned on by default to lead with the lower-risk weekly plan (variant A).
Refunds dropped as expected, but so did purchases. Many users started a trial instead of buying right away, and not enough of them paid to make up for it.
Data insight:
On variant A, the weekly plan with the trial grew from about 30% to 87% of subscriptions, so fewer buyers paid for a full year upfront and ARPU fell.
To lift conversion and ARPU, I put both plans on one screen so users could easily compare them and pick the one that fit. I also preselected the yearly plan and made the price per week the main number on both, so yearly looked affordable and clearly cheaper.
The risk was that refunds would rise again if more users chose the yearly plan. But we believed choosing yearly with the weekly plan in view would be a more deliberate decision. Those unsure about a year could pick weekly instead, with an optional 3-day free trial.
A/B test · Side-by-side plans
Making plans easy to compare brought more buyers and revenue
+52%
+21%
projected 1-year ARPU
85% of buyers chose the yearly plan, yet yearly refunds were more than a third below their earlier peak.
Making the trial clear
Our paywall had the free trial off by default. We suspected that some users who weren’t ready to pay closed the paywall because they missed the trial or didn’t fully understand how it worked.
I designed a screen that opened right after users closed the paywall. Its headline spoke to users who weren’t sure yet, and the screen offered the free trial as the only choice. A timeline showed how the trial would go, so users knew they could cancel before being charged.
Research insight:
Many subscription apps follow a closed paywall with a free trial: closing it is often a no to the offer, not the app, so a trial is a lower-commitment way in.
A/B test · Trial screen after closing the paywall
A trial offer won back users who’d closed the paywall
Research
Seeing how people really use the app
Our A/B tests raised conversion and revenue per user at the paywall, but couldn’t fix the product itself. In early 2026, overall conversion dropped by more than a third, and the App Store rating fell. Complaints kept reaching support, but they rarely said where exactly users got stuck.
Usability testing
I ran the study end to end, from planning and recruiting to moderating 6 online sessions, analysis, and the final report. Participants matched our target audience: they used AI chat apps from weekly to many times a day, for work, everyday tasks, and creative projects. None had used ours, so they saw it the way new users do.
Session structure
Overall impressions
Half of the participants called ChatGPT the ideal AI chat for its simplicity. Ours didn’t feel that simple:
Usability testing · 6 participants
Didn’t read as a chat
The main screen had too many elements and a button instead of an input. Some saw a set of separate tools and couldn’t tell what the app was mainly for.
Hard to navigate
Most mistook the New Chat icon for an edit button, and moving between the chat, History, and the main screen was confusing.
Felt cluttered
Colors and emoji crowded the interface and made it hard to focus. Some said they also made the app look less credible.
Hard to rely on daily
Simple text requests went fine, but more complex tasks took effort or weren’t possible, so the app felt too limited.
Deciding what to change
Participants finished almost every task, but often struggled. After analyzing each session in detail, I identified 17 problems recurring across participants and ranked them by frequency. The top ones shaped 8 key recommendations, which set the redesign’s priorities.
My competitor review backed up these findings, and I also suggested fixes for less frequent problems worth solving. I presented the results to the product team, and together we defined what went into the redesign.
Redesign
Rebuilding the app from what I learned
I redesigned the whole app with a clean, modern UI, simplified the navigation, and cut extra steps from common tasks. I also added web search for up-to-date answers.
Making the app read as a chat with extra features
As testing showed, the main screen hid the app’s main action, typing a request, among tools, colors, and emoji. So I made these changes:
Research insight:
4 of 6 participants named an input on the main screen as their top improvement.
Success metrics:
Chat starts, time to first request, and feature card taps, compared with the old main screen.
Showing users what they could ask
On the old main screen, Chat Prompts were emoji tiles that hid the prompts, and usage data showed they were rarely tapped. A missed chance: suggestions help unsure users start chatting, and engaged ones are more likely to subscribe. So I made these changes:
Research insight:
3 of 6 participants dismissed Chat Prompts, mostly because they didn’t see the tiles as prompts at all.
Success metrics:
Requests sent from suggestions compared with the old Chat Prompts, and web search use from Popular.
Removing workarounds from everyday tasks
Originally, technical limits meant each source needed its own path: web links went through a separate tool, and a message could hold only one link, photo, or file. Links pasted into the regular chat input weren’t read at all. Over time, AI chats moved past these limits. So I made these changes:
Research insight:
4 of 6 participants pasted links into the regular chat input, and 3 of 6 tried to add several sources in one message.
Success metrics:
The share of messages with links compared with the old version, and the share of messages with more than one source.
Letting users refine AI images
At first, our model could create images in different styles, but only from scratch, so asking to change a detail produced a completely new image. Newer models could edit images through conversation, exactly what users asked support for and tried in testing. So I made this change:
Research insight:
5 of 6 participants wanted to keep improving the same image, and 3 of 6 were frustrated at retyping the prompt to try another style.
Success metrics:
Images saved or shared and installs from shared ones, compared with the old version, as well as edits per image.
Helping users find past results
Usage data showed users often opened History, but past results were hard to find: search matched only chat names, and generated images could only be found inside chats. So I made these changes:
Research insight:
4 of 6 participants pointed to issues in the old History. One called it “a mess.”
Success metrics:
Chats opened from search compared with the old History, and images opened from the Images tab.
Also shipped
Smaller fixes based on my UX audit, usability testing and competitor review:
Guiding existing users through the changes
The redesign fixed real problems, but also changed where existing users expected to find things. People often resist even a better interface at first, a reaction known as change aversion.
I didn’t want subscribers to cancel because they felt lost, so I designed a short tour for existing users only, with an update screen and 3 tips on the chat input, Suggestions and History. Users could skip the tour, and it stayed in Settings to replay anytime.
Results after release
The redesign went out to all users, alongside other updates, including a model upgrade and pricing changes.
Before vs. after the redesign · March vs. June 2026
Users paid more, asked for fewer refunds, and rated the app higher
+18%
MRR
−38%
refund rate
4.46 → 4.77
App Store rating
Refunds went from well above the AI-app median to around it.
From the first A/B test in October 2025 to June 2026, MRR grew by over 30%.
What I’d do next
Test free tries of premium features
Free users got only 3 text requests and couldn’t get results from other features. Even a trial meant committing to a subscription. Seeing a feature in action first could show the app fits their needs and make that step easier. I’d A/B test one free try per feature to see whether the gain in ARPU outweighs the cost of free generations.
Turn cancellation reasons into next steps
The redesign fixed what we expected to matter most, but some subscribers still canceled. When someone turns off renewal, I’d ask why in the app, with options like price or a missing feature, plus a free-text option. The answers would show what to prioritize next, and could also help tailor a win-back offer to each person’s reason.
Next case study












