Finance · US iPhone listing

ASO Audit: Lunch Money

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

3/10The app deserves better.

Lunch Money has real financial detail and presents it at a size best enjoyed with specialist optics. Dashboard, Categories, Transactions: three navigation labels where three benefits should be. The review action never actually happens.

ASO Audit: Lunch Money illustration: Expense receipts sort into budget compartments.
Gabriel Machuret in an ASO Guru T-shirt: squinting at unreadable details.

Gab’s verdict · 3/10Gabriel Machuret

Editorial illustrationA finance dashboard photographed from the cheap seats.See the actual listing screenshots ↓
Listing snapshot · what I checked

What I actually checked

One storefront, one language and a dated capture. This is an independent editorial audit, not a client case study.

Store & market
Apple App Store · United States
Language & device
en-US · iPhone
Captured
30 September 2026
Creative reviewed
First 3 still screenshots; video and other devices excluded
Observed app name · 11/30 characters

Lunch Money

Observed subtitle · 7/30 characters

Finance

Gab’s take · Five criteria. Two points each.

Why this gets 3/10

The financial detail and category controls suggest useful depth. Keep that substance. The tiny whole-screen view makes the visitor work too hard to discover why it matters. Enlarge the unreviewed transaction, show the review action and finish with its budget effect. Small screenshots of whole sections are not an adequate sales argument for a detailed finance product.

  1. Reason to care

    0/2

    Dashboard names a section rather than a user benefit.

  2. Product evidence

    1/2

    Financial detail appears, but transaction review is not demonstrated.

  3. Readable at a glance

    0/2

    Tiny captions and dark full-screen panels are difficult to scan.

  4. A useful sequence

    1/2

    Related financial sections lack a completed decision sequence.

  5. A reason to choose

    1/2

    Detailed category control is useful but insufficiently explained.

0: not earned · 1: useful but incomplete · 2: clearly demonstrated. Judged on the dated opening creative; public metadata provides context. These points assess creative execution, not private conversion or ranking performance. Read the scoring criteria · See all ten verdict levels

Three things worth your attention

The screenshot teardown

Inspect the numbered original, read the problem, then compare the proposed fix. The publisher’s creative stays unchanged.

What the visitor sees → what I’d change

Dashboard is a room name

Look at the original: The dashboard combines financial totals with an actionable review prompt.

Why I’m flagging it: The heading describes location while the useful review prompt stays small.

Brief this change

Lead with reviewing outstanding transactions and zoom into the relevant prompt.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The breakdown needs a question

Look at the original: The app shows a category hierarchy and a spending breakdown with sample values.

Why I’m flagging it: Categories and amounts lack a clearly stated decision benefit.

Brief this change

Enlarge one useful spending breakdown using labelled sample data.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The swipe is missing

Look at the original: The headline promises swipe review while the pictured state is a transaction list.

Why I’m flagging it: The caption promises a gesture while the picture remains stationary.

Brief this change

Show a genuine review gesture and its resulting state.

See how the proposed sequence fits together ↓
Figure 1. First three still screenshots from the US iPhone listing, captured 30 September 2026. Creative belongs to the app publisher and is reproduced for analysis. Publisher claims inside screenshots are not independently verified.

What I’d put on the table

Proposed copy for discussion. These are not current listing fields or tested winners.

Observed listing

Lunch Money

Finance

Proposed alternative

Lunch Money: Budget Companion

Review spending on the go

Name 29/30 · Subtitle 25/30 characters
Metadata comparison. A proposed alternative to review against the current listing.

Make the companion role explicit in the name and give the subtitle a concrete mobile task. The current description and transaction creative support this positioning.

The tradeoff: The name becomes longer and budget is broader than the demonstrated review task. Verify current mobile budgeting scope and query demand; this proposal does not imply web-feature parity or free access to the underlying service.

Gab’s proposed direction

Give each screenshot a job.

Read the sequence from top to bottom on mobile, left to right on desktop. These are message-layout sketches, not screens from Lunch Money or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Check your Lunch Money account

    Illustrative layout · verify the real flow

    Put this in the frame: A verified current summary with accurate registered-account context and clearly illustrative figures.

    Why it earns the space: Introduce the mobile companion role.

  2. 02Show useful evidence

    Proposed headline

    Review a transaction

    Illustrative layout · verify the real flow

    Put this in the frame: One genuine swipe or review control with its exact confirmation state.

    Why it earns the space: Demonstrate the action promised by the current third headline.

  3. 03Move the decision forward

    Proposed headline

    Understand its category

    Illustrative layout · verify the real flow

    Put this in the frame: The same transaction’s category or breakdown view.

    Why it earns the space: Connect the review action to useful organisation without implying that every review changes a budget.

The test: Does an action-and-result transaction frame improve understanding of the mobile review workflow? The sketch gives the designer a direction; the actual product and access conditions decide what can ship.

Want this level of detail for your app?

Bring the listing. I’ll help you decide what to keep, what to fix and what to test.

Talk to Gabriel →
Compare three alternatives

Three alternatives—and what they make clearer

Observed competitor metadata

YNAB ↗

Never worry about money again

YNAB uses an emotional money-management promise in its subtitle.

The lesson: Lunch Money can distinguish its concrete review task without promising reduced financial worry or a particular savings outcome.

Observed competitor metadata

Monarch: Budget & Track Money ↗

Spending, Net Worth, Investing

Monarch names budgeting and tracking with net-worth and investing terms.

The lesson: The broader scope is visible in metadata. Explain the Lunch Money companion’s verified mobile job rather than imply equivalent functionality.

Observed competitor metadata

Goodbudget Budget Planner ↗

Money & Expense Tracker

Goodbudget names budget planning, money and expense tracking.

The lesson: The category overlaps, so a specific transaction-review workflow and honest account requirements provide more useful differentiation than generic tracking language.

Competitor comparison. US listing names and subtitles captured 30 September 2026. These are positioning comparisons, not ranking or revenue comparisons.
Keyword ideas and their evidence

The keyword questions I’d investigate

Intent candidates grounded in the listing—not fabricated search-volume or difficulty scores.

Lunch Money app / mobile companion

Visitor’s job: Access an existing Lunch Money account from iPhone.

Evidence: The brand name and description identify the official companion for registered users.

Decision: Keep identity and account context explicit; do not confuse the official app with third-party tools using the service’s API.

expense tracking / spending categories

Visitor’s job: Understand and organise transactions by category.

Evidence: The category and transaction screenshots directly show this job.

Decision: Demonstrate current review and categorisation behaviour without implying automatic accuracy or financial advice.

budget dashboard / income and spending

Visitor’s job: Check a summary while away from the web app.

Evidence: The first still shows income, expenses and a period selector; the description names summary statistics.

Decision: Verify current mobile scope and explain example values. The visible Finance line does not establish a deliberate custom-subtitle strategy.

The unseen keyword field may already cover some of these terms. Build an evidence-backed keyword shortlist before making a metadata change.

What the selected reviews tell us

What three reviewers can teach us

Three 2025–2026 accounts were chosen for companion scope, rule expectations and mobile access to the broader service. A separate subscription complaint remains a lead for entitlement research rather than evidence that annual plans generally fail. Competitor comparisons and unsupported reliability claims in other reviews are not adopted.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 18 July 2025–29 April 2026. No sentiment percentage is calculated.

18 July 2025 · 5/5 stars

“more limited functionality”

A July 2025 reviewer explicitly described the mobile app as a more limited companion, while praising the broader product’s budget periods and rollover options.

What I’d investigate: Keep the web-first context. Do not assume every praised budgeting setting can be configured on iPhone.

Listing review source · Review ID 12904912956

29 April 2026 · 3/5 stars

“Rules doesn’t work consistently”

An April 2026 reviewer reported unexpected rule creation and extra work correcting transactions despite changing a preference.

What I’d investigate: Investigate the current relationship between categorisation, review and rules. One account does not establish the cause, prevalence or whether the behaviour remains.

Listing review source · Review ID 14007460849

30 August 2025 · 5/5 stars

“excellent companion”

An August 2025 reviewer valued the mobile companion, support, community and API ecosystem.

What I’d investigate: Preserve the broader-product context; praise for an open API does not establish that third-party tools are official or that mobile matches the web app.

Listing review source · Review ID 13080209498

A displayed review can be old, unusually positive or internally inconsistent with its star rating. These accounts suggest questions; they do not establish current defects or typical customer experience. Use the Review Research Desk to keep evidence and interpretation separate.

What I’d do first

01

Dashboard is a room name

The heading describes location while the useful review prompt stays small.

Deliverable: Lead with reviewing outstanding transactions and zoom into the relevant prompt.

Creative brief and current-product check
02

The breakdown needs a question

Categories and amounts lack a clearly stated decision benefit.

Deliverable: Enlarge one useful spending breakdown using labelled sample data.

Creative brief and current-product check
03

The swipe is missing

The caption promises a gesture while the picture remains stationary.

Deliverable: Show a genuine review gesture and its supported resulting state.

Creative brief and current-product check
Open the full test plan

One test worth running

Does an action-and-result transaction frame improve understanding of the mobile review workflow?

Audience
Eligible US English iPhone default-page visitors, with comprehension research split between registered Lunch Money users and people evaluating the broader service.
Control
The captured dashboard, category and transaction-list sequence after verifying current interface and clarifying companion access in both variants.
Treatment
Replace only frame three with an actual transaction-review action and its result. Keep the first two frames, sample account context, metadata and subscription offer fixed.
Method
Verify the current gesture and any side effects using non-sensitive test data, then run randomized comprehension research and eligible App Store product page optimization.
Primary measure
Correct explanation of what transaction review changes in comprehension research; platform-reported download conversion is a separate acquisition measure.
Guardrails
Visitors must distinguish reviewed status, category edits and rules, and understand that registration and service access are required. Do not use sample savings rates as a success promise or imply all web features are mobile features.
Decision rule
Predefine meaningful comprehension improvement, sample requirement and acceptable acquisition tradeoff from real baseline data. Retain control if inconclusive or if the new frame creates stronger mistaken automation expectations.
What could muddy the result
Bank-data timing, web and mobile releases, subscription offers and the proportion of existing customers may affect the result.

Check Apple’s current product page optimization guidance and custom product page guidance before configuring a test. Write your experiment brief.

How the ten-point scale works

So, does their ASO suck?

1–3: thumbs down · 4–6: thumbs up and down · 7–10: thumbs up

  1. 1/10

    Yeah. It really does!

    The basics need a serious rethink.

  2. 2/10

    I hope no agency is getting paid for this.

    Too many obvious things have been left unfinished.

  3. 3/10Lunch Money is here

    The app deserves better.

    There is a useful product here. The listing needs to show it.

  4. 4/10

    Recognisable. Not convincing.

    Some basics work, but the opening wastes attention and under-explains the benefit.

  5. 5/10

    Fine. A dangerous place to stop.

    There is usable creative here, but too much of the sales argument is left to the visitor.

  6. 6/10

    Useful. Still leaving too much unsaid.

    Real strengths, undermined by meaningful gaps in the opening story or execution.

  7. 7/10

    Good. The product proof earns it.

    A clear, useful demonstration with specific refinements still needed.

  8. 8/10

    Good. Now sweat the details.

    The main promise is clear and supported. Refinement matters more than reinvention.

  9. 9/10

    Whoever did this knows their stuff.

    Clear positioning, thoughtful choices and very few loose ends.

  10. 10/10

    Okay, now you’re showing off.

    An unusually clear, convincing storefront worth learning from.

An editorial verdict on the captured storefront, not a measured ASO score or an assessment of an agency’s private work.

Try this on your app · worksheet and assignment

Your ASO assignment

  1. Lead with reviewing outstanding transactions and zoom into the relevant prompt.
  2. Enlarge one useful spending breakdown using labelled sample data.
  3. Show a genuine review gesture and its supported resulting state.

What would change my mind?

  • Current review, categorisation and rule behaviour on iPhone.
  • Account entitlements, setup requirements and mobile-versus-web capability.
  • Baseline audience mix, review comprehension and attributable acquisition.
Sources and capture dates

Sources and scope

No private analytics, search-rank dataset or internal keyword field was supplied. Review quotations are short excerpts; explanations are our summaries. App names and screenshots belong to their respective owners. We are not affiliated with Lunch Money. Read our editorial methodology.

Your app. Your priorities.

Get an audit you can actually use.

Send your listing, market and the problem you want to solve. I’ll explain the scope and fee before work starts. Your budget should buy decisions, not a longer PDF.

Apply the method to your app

Build a relevant keyword shortlist, plan your screenshot sequence or get help with the creative decisions.

More app teardowns

Browse the complete app teardown library →

Enough theory. Your app next.

Let’s fix what’s holding your listing back.

Send your app link, target market and the problem. We’ll start there.