Design & creative · US iPhone listing

ASO Audit: Halide

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

5/10Fine. A dangerous place to stop.

Halide shows beautiful photographs, awards, rating artwork and more awards. The useful camera controls arrive surrounded by another feature list. For an app selling photographic control, the opening leaves the controlling part oddly distant.

ASO Audit: Halide illustration: A camera lens separates a mountain photograph into exposure layers.
Gabriel Machuret wearing an ASO Guru T-shirt: comparing two options.

Gab’s verdict · 5/10Gabriel Machuret

Editorial illustrationThe camera has controls. The campaign has an awards dependency.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 · 28/30 characters

Halide Mark III - Pro Camera

Observed subtitle · 28/30 characters

Zero AI, Natural Photos, RAW

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

Why this gets 5/10

The photographic style and manual controls give the product a clear identity. That is useful. The awards should support the camera demonstration, not keep taking its place. Replace repeated recognition with one capture decision and its resulting image. Show the settings that matter, keep comparisons controlled and make access clear. Natural results should be demonstrated, not buried beneath leadership language.

  1. Reason to care

    1/2

    The photography context and natural-image positioning establish a relevant creative intent. A visible capture decision would make the practical benefit clearer.

  2. Product evidence

    1/2

    Finished photos and controls appear without a connected capture example.

  3. Readable at a glance

    1/2

    Angled devices, small copy and repeated marks fragment attention.

  4. A useful sequence

    1/2

    Photos and controls introduce related aspects of making an image, although repeated recognition interrupts the demonstration.

  5. A reason to choose

    1/2

    Manual control is specific; leadership claims are not demonstrated here.

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

The gallery has no capture context

Look at the original: The frame includes the app icon, a publisher rating-count claim and several finished images without visible capture settings.

Why I’m flagging it: Finished photographs cannot explain which supported control produced them.

Brief this change

Pair one authorised image with its real capture settings and a concrete benefit.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The angle is decorative friction

Look at the original: Looks and editing controls appear together under an Editors’ Choice emblem.

Why I’m flagging it: Tilted devices and recognition reduce the readability of actual controls.

Brief this change

Use a straight, enlarged crop of one Look or adjustment.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Four features compete again

Look at the original: The camera interface is visible beside four feature phrases and repeated rating artwork.

Why I’m flagging it: Manual control shares space with repeated rating artwork and other labels.

Brief this change

Give one important camera adjustment its own readable example and result.

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

Halide Mark III - Pro Camera

Zero AI, Natural Photos, RAW

Proposed alternative

Halide: Manual RAW Camera

Natural photos, creative Looks

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

Keep the brand and common camera intent while using the subtitle to connect the natural-photo proposition with the current Looks system.

The tradeoff: This removes the Mark III edition cue and the explicit zero-AI phrase. Evaluate brand recognition and processing comprehension separately; do not change metadata during the creative experiment.

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 Halide or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Choose how your photo is made

    Illustrative layout · verify the real flow

    Put this in the frame: One verified Process Zero capture with its actual mode visible and a clearly labelled same-scene reference if used.

    Why it earns the space: Connect the proposition to evidence instead of a ranking claim.

  2. 02Show useful evidence

    Proposed headline

    Find your Look

    Illustrative layout · verify the real flow

    Put this in the frame: The current Looks selection with a properly attributed photograph and accurate access.

    Why it earns the space: Show a deliberate visual choice without promising a universal improvement.

  3. 03Move the decision forward

    Proposed headline

    Take control when you want it

    Illustrative layout · verify the real flow

    Put this in the frame: A current camera view demonstrating one focus or exposure adjustment.

    Why it earns the space: Make manual control understandable without obscuring automatic capture options.

The test: Does a verified Process Zero demonstration explain Halide better than the current reputation-led opener? 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

ProCamera. Professional Camera ↗

Pro HDR, RAW+ Manual Video Cam

ProCamera names professional capture, HDR, RAW and manual video in its visible metadata.

The lesson: Halide can differentiate the processing choice instead of trying to win a longer feature list.

Observed competitor metadata

Obscura — Pro Camera ↗

Manual Controls, ProRAW, Video

Obscura names manual controls, ProRAW and video.

The lesson: Explain how Halide’s Looks and Process Zero serve a distinct still-photography decision without claiming competitors lack control.

Observed competitor metadata

ProCam - Pro Camera ↗

Manual Camera + RAW

ProCam pairs a pro-camera name with manual camera and RAW.

The lesson: Manual and RAW are shared category cues. Keep the brand recognisable and make the specific capture workflow understandable.

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.

manual camera / RAW camera

Visitor’s job: Control exposure, focus and output format while shooting.

Evidence: The name says pro camera and the third still exposes capture controls.

Decision: Retain camera intent and qualify device-specific format support before proposing exact creative copy.

natural iPhone photos / Process Zero

Visitor’s job: Choose an alternative to heavier computational processing.

Evidence: The subtitle names natural photos and the description explains Process Zero.

Decision: Demonstrate a verified same-scene result without asserting that every viewer will prefer it.

film looks / camera presets

Visitor’s job: Apply a deliberate photographic rendering during capture or editing.

Evidence: The second still shows Looks and the description distinguishes them from a simple post-capture colour filter.

Decision: Explain the supported workflow and access; do not blur capture settings and imported-photo editing.

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 2020–2025 accounts were selected for beginner comparison, capture responsiveness and saving expectations. All predate this capture. Other accounts contain business-motive speculation or a five-star rating with strongly negative text; neither is used as evidence of current reliability or developer intent.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 23 October 2020–17 September 2025. No sentiment percentage is calculated.

23 October 2020 · 5/5 stars

“see the difference side-by-side”

An October 2020 beginner valued comparing image formats during a Mark II trial and found the interface approachable.

What I’d investigate: Use comparison as a research lead, while recognising that the account predates Mark III and does not verify today’s workflow.

Listing review source · Review ID 6566553499

10 March 2023 · 3/5 stars

“bigger delay”

A March 2023 trial user praised the interface and macro mode but reported capture delays and control problems on an iPhone 14 Pro.

What I’d investigate: Retain the praise and criticism. Verify current capture performance and device support rather than presenting an old report as a current failure.

Listing review source · Review ID 9699552422

17 September 2025 · 3/5 stars

“rescued photos”

A September 2025 reviewer liked the information and processing control but reported lag and saving problems; they also said rescued photos helped.

What I’d investigate: Preserve that recovery detail. Test save reliability before making speed or dependable-capture claims, without inferring how common the issue is.

Listing review source · Review ID 13148956309

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

The gallery has no capture context

Finished photographs cannot explain which supported control produced them.

Deliverable: Pair one authorised image with its real capture settings and a concrete benefit.

Creative brief and current-product check
02

The angle is decorative friction

Tilted devices and recognition reduce the readability of actual controls.

Deliverable: Use a straight, enlarged crop of one supported Look or adjustment.

Creative brief and current-product check
03

Four features compete again

Manual control shares space with repeated rating artwork and other labels.

Deliverable: Give one important camera adjustment its own readable example and result.

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

One test worth running

Does a verified Process Zero demonstration explain Halide better than the current reputation-led opener?

Audience
US English iPhone visitors interested in photography, separated by prior Halide familiarity and supported device family.
Control
The current first-frame gallery after unsupported or stale claims are corrected consistently across variants.
Treatment
Replace only frame one with an authentic capture-mode and result demonstration. Preserve the following device composition, metadata and paid offer.
Method
Verify output provenance, device support and save behaviour first. Run randomized comprehension research and an eligible App Store product page optimization test using the same verified offer.
Primary measure
Correct explanation of the processing choice in research and platform-reported download conversion in the storefront test.
Guardrails
No belief that the full camera is free, every format is universal or one image proves better results in every scene. Track trial activation and paid conversion separately where available.
Decision rule
Predefine a useful effect, sample size and duration from baseline data. Ship only if clarity improves without materially worsening qualified trial or purchase behaviour; keep control if inconclusive.
What could muddy the result
Mark III publicity, device launches, lighting and scene preference, legacy entitlements and promotional pricing can affect results.

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/10

    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/10Halide is here

    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. Pair one authorised image with its real capture settings and a concrete benefit.
  2. Use a straight, enlarged crop of one supported Look or adjustment.
  3. Give one important camera adjustment its own readable example and result.

What would change my mind?

  • Current device and format support plus capture/save reliability.
  • Scope and dates behind the publisher’s award, rating and superiority artwork.
  • Baseline processing comprehension and trial-to-paid behaviour by acquisition source.
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 Halide. 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.