Build a wireframe of the lowest-friction KYC flow in the dataset.
FOLIO UX Advisor
The FOLIO UX Advisor is a competitive product intelligence assistant for fintech PMs, designers, and founders. Ask it how real users move through African fintech apps — where they hit friction, how long each step takes, what's worth copying, and what to avoid — and it answers from recorded sessions across 10 apps, the FOLIO Performance Index rankings, and cross-app behavioral data. Use the Chatbot to ask anything, or the Prompt Studio for ready-made questions and UI mockups. Preview chatbot here.
Enter your access code to use the UX Advisor
158 ready-to-run prompts for FOLIO's UX advisor chatbot. Swap any app with the inline dropdowns, set a default for every single-app prompt, then copy. Built for PMs, PMMs, and product designers mining real session data.
Mockups & Wireframes
15Recreate 's send flow screen by screen with notes on wait times.
Mock up an ideal transfer-confirmation screen using the best elements across apps.
Show me 's onboarding as an annotated mockup highlighting friction.
Build a side-by-side wireframe of vs 's home dashboard.
Recreate the fastest PIN / checkout flow as a clickable wireframe.
Build a wireframe of the lowest-friction signup flow as a clickable prototype I can copy.
Recreate 's failed-transaction retry flow as an annotated wireframe.
Wireframe an ideal KYC document-upload screen using the best elements across apps.
Build a side-by-side wireframe of vs 's confirmation screen.
Mock up a pre-KYC checklist screen as a wireframe I can hand to design.
Recreate 's loan application flow screen by screen with notes on wait times.
Mock up an ideal loan-offer acceptance screen using the best elements across apps.
Recreate the fastest repayment / authorization flow as a clickable wireframe.
Recreate 's failed-repayment retry flow as an annotated wireframe.
Cross-App Comparison
8Compare and 's transfer flows side by side with timing and friction.
Compare how and handle KYC and which is less painful.
How does 's tap count compare to the dataset median?
Which app needs the fewest screens to complete a transfer?
Compare auth methods across all apps — PIN vs biometric vs OTP.
Compare and on every Performance Index dimension.
Compare and 's loan application flows side by side with timing and friction.
Which app needs the fewest screens to complete a loan application?
What to Copy
7Show me the best-in-class sign-up flow as an annotated mockup I can copy.
What does do better than every other app in the dataset?
If I'm building a new wallet, which 3 flows should I copy and from which apps?
Which app has the cleanest auth experience, and how do they do it?
Which app's amount-entry screen has the lowest input friction, and why?
If I'm building a new lending app, which 3 flows should I copy and from which apps?
Which app's loan-amount selection screen has the lowest input friction, and why?
What to Avoid
4What are the top 5 UX mistakes to avoid based on this data?
What does get wrong that I should make sure not to repeat?
Which loading states and transitions cause the most dead time, and on which apps?
What causes users to abandon mid-flow, and where does it happen most?
Timing & Speed
7Which app has the fastest transfer flow, and what exactly makes it fast?
What's the median time to complete a transfer on , broken down by stage?
How does sign-up time on compare to the dataset median?
Which app has the slowest KYC, and where does the time go?
Rank all apps by total active flow duration, fastest to slowest.
Which app has the fastest loan application flow, and what exactly makes it fast?
What's the median time to complete a loan application on , broken down by stage?
Friction
7What are the most common friction points across all apps, and which should I avoid?
Where do users hesitate or pause the most on ?
What's the biggest friction blocker in 's transfer flow?
Which step — signup, KYC, funding, transfer — generates the most friction overall?
Show me every blocker- and terminal-severity friction event in the dataset.
What's the biggest friction blocker in 's loan application flow?
Which step — signup, KYC, loan application, disbursement, repayment — generates the most friction overall?
Rankings & Positioning
6Which apps rank highest for Clarity, and what do they do differently?
Show me an app that's better than its reputation (big PC-to-PP shift) and why.
Where does rank across all five dimensions, and what's its weakest?
Which app is most overrated by reputation versus actual preference?
What's the gap between the Trust leader and , and how do I close it?
Rank the apps by Likelihood-to-recommend and explain the top 3.
Flow Deep-Dives
12What's the ideal number of steps and fields for fintech sign-up, based on the data?
How do the fastest apps reduce sign-up abandonment?
Break KYC into its fragments (selfie, BVN, NIN) and show where time is spent.
What's the least painful way to collect KYC, based on observed sessions?
How do apps surface funding instructions, and which is clearest?
Walk me through 's full transfer flow with every screen and duration.
When do apps ask for auth — app open vs transaction — and what's least disruptive?
How is recipient / beneficiary selection handled across apps?
How do apps surface repayment instructions, and which is clearest?
Walk me through 's full loan application flow with every screen and duration.
When do apps ask for auth — app open vs repayment — and what's least disruptive?
How is bank-account linking and repayment-source selection handled across apps?
Input & Micro-Interactions
2Which apps use auto-advance, autocomplete, and auto-resolve well?
Where do users make the most input corrections, and on which fields?
Commercial, Trust & PMM
4What trust signals and regulatory badges do top apps surface, and where?
How do apps message fees and FX rates, and who's most transparent?
Based on rankings and flow data, what's 's sharpest weakness I can position against?
How do apps message interest rates, APR, and fees, and who's most transparent?
Build-Ready Specs & Handoff
7Turn the lowest-friction onboarding flow into a written spec with screens, fields, and CTAs I can hand to my designer.
Write acceptance criteria for a KYC flow based on the lowest-drop-off pattern in your data.
Draft user stories for a send-money flow modeled on .
Give me an engineering handoff note for 's auth gate, including states and edge cases.
Turn 's funding flow into a screen-by-screen build list with annotations.
Draft user stories for a loan application flow modeled on .
Turn 's disbursement flow into a screen-by-screen build list with annotations.
Diagnose My Flow
7Here's my onboarding [paste]. Compare it to the best in your data and tell me exactly what to cut or reorder.
Here's my KYC flow [paste]. Where will users drop off, based on what you've seen?
Here's my transfer confirmation screen [paste]. What's missing versus the strongest apps?
Review my failed-transaction handling [paste] against how top apps recover.
Score my signup flow against your dataset on friction, clarity, and trust, and name my weakest dimension.
Here's my loan-offer screen [paste]. What's missing versus the strongest apps?
Review my failed-repayment handling [paste] against how top apps recover.
Microcopy & States
7Write the microcopy for a KYC document-upload screen based on the clearest apps in your data.
Give me error-state copy for a failed transfer, modeled on how the best apps recover.
Draft empty-state and loading-state copy for a wallet dashboard using observed patterns.
What does 's confirmation screen say word-for-word, and how would you tighten it?
Write a pre-KYC checklist screen that tells users exactly which documents to prepare.
Give me error-state copy for a failed repayment, modeled on how the best apps recover.
Draft empty-state and loading-state copy for a loan dashboard using observed patterns.
Localization & Market Fit
9Adapt 's onboarding for a Nigerian mass-market wallet — what changes for BVN/NIN and CBN/NDIC?
The cleanest signup in your data is a USD/multicurrency app. Translate that flow for a naira wallet.
What compliance and trust copy should a Nigerian payments app show that a USD-account app wouldn't?
Which observed flows assume Google sign-in, and what's the fallback for users without it?
Adapt the best fee-disclosure pattern for a cross-border NGN→KES remittance corridor.
Adapt 's onboarding for a Nigerian mass-market lending app — what changes for BVN/NIN and CBN/NDIC?
The cleanest onboarding in your data — translate that flow for a mass-market naira lending app.
What compliance and trust copy should a Nigerian lending app show — around licensing, interest rates, and data use?
Adapt the best fee-disclosure pattern for clear loan interest, APR, and late-fee disclosure.
Usability Testing & QA
7Based on where users hesitate most, write me a usability-test script for an onboarding flow.
List the top edge cases to QA in a transfer flow, drawn from observed friction and errors.
Which onboarding step should I A/B test first to cut drop-off, and what's the hypothesis?
Give me a checklist of failure states to test in a funding flow, based on real sessions.
What 5 moments should I watch for in my own user recordings, based on common friction points?
List the top edge cases to QA in a loan application flow, drawn from observed friction and errors.
Give me a checklist of failure states to test in a repayment flow, based on real sessions.
Teardowns
4I'm doing my first UX teardown of 's . Coach me, don't do it for me. Give me only raw session evidence, recordings, timings, friction events, observed behavior, no scores or votes. Go one stage at a time, and after each ask what I notice and what it implies before you react, then sharpen my read. At the end I write the case study and you review my draft.
Show me 's raw evidence for one piece at a time, no scores or votes. For each, make me say what's happening and why it matters before you respond, then tell me where my read is sharp or off. I write the teardown, you critique it.
I'm structuring a teardown of for my portfolio. Don't hand me a structure or name the findings. Ask how I'd order it and what I think the headline issue is from the evidence, then pressure-test my choices.
Here's my draft teardown of . Don't rewrite it. Show me raw evidence I may have missed, ask how I'd reconcile it with my claims, and only after I answer, reveal what the panel found so I can see if my read held. [paste]
Comparative analysis
3I'm comparing and on . Give me each one's raw evidence, no scores or votes, and ask which differences actually matter and why before you weigh in. Push me past the surface. I write the comparison, you critique it, and reveal the scores only after I've committed.
Show me raw evidence from a few apps in without telling me which is best. Ask me to spot the most meaningful contrast myself, then tell me whether I found a real one or a cosmetic one, and coach me to build the case around it.
Help me argue which of and handles better, working only from raw evidence, not scores. Make me take a position and defend it, then challenge my evidence the way an interviewer would before I write it up.
Product improvement
3Coach me to write an improvement proposal for . Give me only raw session evidence, not scores or votes, and don't tell me which step is worst. Make me find the biggest problem from the evidence, propose a fix, and critique my diagnosis. Only after I commit, reveal what the panel found so I can check my read. Then I write the proposal.
I want to write a redesign rationale for 's . Show me the raw evidence, ask why I think it underperforms and where, and correct me only against the evidence, not by naming the answer. Have me propose the before-and-after. Review my logic, don't supply it.
Help me scope one high-impact fix for . Give me the raw friction evidence without scores, ask which fix I'd prioritize and why, and challenge my prioritization before I write it up. Reveal the panel's view afterward so I can compare.
Design track
3I'm a designer critiquing 's . Give me raw evidence, not scores, and coach me to ground the critique in it: ask what I'd change and why, and push back whenever my reasoning is taste rather than evidence. I write the case study.
Help me build a before-and-after redesign story for 's from raw evidence only. For each change I propose, make me justify it with a specific observed behavior before you react. Don't design it or name the problem for me.
Give me 's raw friction evidence one item at a time, no scores. Ask me to turn each into a specific design recommendation, then tell me which of mine are defensible and which are vague, and why.
Engineering & builder track
3I'm an engineer analyzing 's . Give me raw evidence, not scores, and ask what makes it work or fail from a build perspective before you react. Sharpen my answer. I write the technical-product breakdown, you check my reasoning.
Coach me to spec a feature that fixes 's biggest friction point. Show me the raw evidence without naming the problem, make me identify it and propose the fix, then critique my spec once I draft it. Don't write the spec.
I want to rebuild 's as a project. Give me the raw evidence of how it behaves now, no scores, ask which decisions I'd make and why, and challenge them before I write up the build. Reveal what the panel data says good looks like only after I've committed.
Interview prep
4Quiz me on 's using the raw evidence, not the scores. Show me what users did, ask me to infer where the experience breaks and why, push me when I'm vague, and only reveal the panel's verdict after I've reasoned it out.
Run a mock product interview using as the case. Ask me to analyze a flow, let me struggle, then give hiring-manager feedback on my reasoning.
Help me defend my teardown. Ask me the hardest questions about my analysis and make me answer before you suggest stronger responses.
I'll tell you my strongest finding from . Ask me to pitch it as a two-minute project story, then critique my version. Don't model it for me first.
Personal brand & job hunt
3I want to write a LinkedIn post about an insight I found on . Ask me what the insight and the takeaway are, let me draft it, then coach me on making it read as signal, not self-promotion. Don't draft it for me.
Help me write a portfolio intro from my teardown. Ask how I'd summarize my own work first, then tighten what I write. Keep it in my voice.
Coach me to write my portfolio's about section. Ask how I'd describe my analytical approach, then push me to make it specific and evidence-based. I write, you critique.
Master the FOLIO framework
2Explain FOLIO's five dimensions, then quiz me until I can describe the methodology in my own words without prompting. Correct me when I drift.
Ask me to explain, in my own words, why analysis grounded in real user data is more credible than opinion. Critique my answer and push me until I can say it convincingly to a recruiter.
Visual exercises
12Build a wireframe of 's money-transfer flow from the screenshots and session notes, and give me the raw friction evidence per step (timings, errors, retries, observed behavior) but not the scores. Have me name the worst step and propose a fix before you react, then critique my read.
Wireframe 's KYC and identity-verification flow and show me the raw evidence, including any captured error and processing screens. Ask me to diagnose where users get stuck and why, make me weigh it against at least one other step, then critique before revealing what the panel found.
Reconstruct 's loan-application flow as a wireframe with the raw step-by-step evidence. Have me pick the highest-friction step and write a fix as product requirements, then review it like a PM, checking whether the fix matches the observed behavior.
Wireframe the add-a-funding-source flow for and give me the raw evidence for how users fund the account. Have me decide whether the friction is about clarity or about steps, defend it, then critique me before showing the data.
Create stripped, unbranded wireframes of the KYC flow for three apps, , , , with no labels. Give me the friction evidence for each app separately. Have me predict which wireframe maps to which app and rank them by friction, commit to my reasoning, then reveal the answer and tell me where reading the layout misled me.
Show me unbranded wireframes of three apps' transfer flows plus the raw timing and error evidence for each, unlinked. Have me match flow to evidence and explain my logic, then reveal it and point out where the static layout did not predict the real friction.
Rebuild 's main dashboard as a wireframe with three critical actions removed. Give me a menu of candidate placements, have me place each one and justify it against information hierarchy, then show me where the real app put them and critique the gap.
Wireframe 's home screen with the primary actions blanked out. Have me decide which actions belong above the fold and where, defend the order, then reveal the real layout and the reasoning behind it.
Show me the single worst friction screen in 's as a wireframe with its raw evidence. Have me redraw that one screen to fix the problem, in words or a rough wireframe, then critique my redesign for buildability and whether it actually targets the observed failure.
Put two apps' wireframes side by side, and , with the raw evidence for each but no scores. Have me identify which design choices reduce friction and why, commit, then reveal both apps' panel results and check my read against them.
Give me only the raw session notes and timings for 's , no wireframe. Have me sketch or describe the flow screen by screen from the evidence alone, then show me the real screenshots and wireframe so I can see what I got right and what I assumed.
Show me the captured failure screens from 's with the raw evidence of what triggered each. Have me diagnose the cause of each failure and design the recovery path, then critique whether my recovery matches what actually went wrong and what compliance would allow.
Principle-grounded exercises
12Explain the Doherty Threshold, then show me the processing and wait evidence from 's . Have me judge whether the app respects or violates it and point to the specific evidence, then critique my reasoning. If the data does not clearly show it, say so.
Teach me Hick's Law, then show me a decision point in 's flow where users choose between options (document type, funding method, menu). Have me assess whether the number of choices helps or hurts and why, then critique. Tell me if the evidence is too thin to judge.
Explain Jakob's Law, then show me 's against the conventions users know from other apps. Have me identify where it follows or breaks convention and whether that caused friction in the evidence, then critique my read.
Teach me Fitts's Law, then show me the primary call-to-action screens in 's . Have me evaluate target size, placement, and reachability and judge whether the design helps or fights the user, then critique. Flag it if the screenshots do not let us assess this fairly.
Explain Miller's Law and chunking, then show me a form or verification step in where the app asks for information. Have me judge whether the load is chunked well or dumped all at once, citing the evidence, then critique my analysis.
Teach me Tesler's Law, the conservation of complexity, then show me 's KYC flow. Have me decide who absorbs the complexity, the app or the user, and back it with evidence, then critique whether I assigned it correctly.
Explain the Peak-End Rule, then show me how 's ends, the success or failure screen plus the highest-intensity moment. Have me judge what impression the peak and the end leave and why, using the captured terminal screens as evidence, then critique.
Teach me the goal-gradient effect and progress indication, then show me 's onboarding steps. Have me assess whether the app shows users their progress and whether that would affect completion, citing evidence, then critique my reasoning.
Explain Postel's Law, be liberal in what you accept. Show me where handles user input, phone numbers, documents, formats, and any input errors in the evidence. Have me judge how tolerant the app is and where rigidity caused friction, then critique.
Teach me the Law of Proximity and common region, then show me a form or dashboard screen from . Have me evaluate whether related elements are grouped clearly and where grouping breaks down, then critique my read against the layout.
Explain the serial position effect, then show me 's main navigation or action menu. Have me judge whether the most important actions sit where users notice them first and last, and whether placement matches importance, then critique.
Teach me the aesthetic-usability effect and its trap, that a polished look can hide real friction. Show me an app that looks clean but has friction in the evidence, and one that looks plain but flows well. Have me separate how it looks from how it works, then critique where my eye might be biasing my judgment. This one is hard to prove from the data, so flag the limits.