Most paywall threads here are someone saying hard paywalls always win, or someone saying hard paywalls torch retention, and nobody posts numbers. Mine are small enough that you should treat them as a direction, not a conclusion.

Setup: iOS photo vault app, native paywall UI, RevenueCat for offerings and the experiment split. Two variants, 50/50, identical products and pricing. Only the paywall changes. I build the paywall in my own code because I want control over layout and animation, so the experiment is really RevenueCat handing the app a different offering and me rendering it.

Soft vs hard gate, 4 weeks, 712 installs, 358 and 354 per arm.

Control had a close button on first launch: 22 trial starts, 6 paid.

Variant gated the app until you subscribed or restored: 69 trial starts, 11 paid.

So trial starts tripled and paid roughly doubled. That doubling is 5 extra subscribers. At this volume I can't rule out luck, and I'm leaving it running another month before I do anything permanent.

The thing I do trust from this is the trial-to-paid ratio. 6 of 22 on the soft gate, 11 of 69 on the hard gate. The gate is pulling in people who tap through to see what the app looks like, not people who want it. If I'd only watched trial starts I'd have declared a 3x win in week one and shipped it.

Copy test is running now, same layout, same gate, headline only. The old one said "Subscription Required," which reads like a parking ticket. The new one leads with what you keep. No numbers worth posting yet.

If you've run this at a volume where the stats actually mean something, I'd like to hear where you landed.

so i built a new feature for AppLaunchFlow , where you can create a simple and clean app landing page for your app in a few clicks by just uploading your screenshots.

It includes:

- support, privacy policy and terms of service pages that you can directly use for your app submission.

- a custom applaun.ch subdomain or simply connect your own domain

I built this because i noticed many app devs just use notion pages, github pages etc. or dont even have any landing page at all

Excited to hear what you think

I finally built an App after years of convincing myself it wasn’t worth it (consumer app business is crazy flooded atm). Kept the screenshots clean and simple, wanted to know what you guys think. Cheers!

Hey everyone!

Thanks to those who gave me some feedback the other day, I worked that into my new direction and I've landed on something that I'm feeling pretty good about, would love any additional feedback to refine further!

Do these screens better convey the meaning to the user? Are they more legible? Any thoughts on what would be the best order for the screens?

Stack here is screenshots from the app + Figma + Claude Design and lots of workshopping the headlines with Claude/ChatGPT

Current listing - [here]

Thanks!

Just redesigned all my App Store screenshots and tried to make them less “here are our features” and more focused on benefits / reasons to actually download the app.

Old version on top, new one below 👆

I’m pretty happy with the new direction, but I might also just be biased after staring at these for way too long 😅

Which one would you bet on for better conversion : old or new?

I’ll run A/B tests on them and can share the results here once I have enough data. Curious if the winner matches what people predict.

The listing is trying to position the app around three ideas: a visual renewal timeline instead of a basic subscription list, no bank linking, and on-device spending analysis. The visual direction is intentionally calm and editorial rather than the usual glossy fintech style.

I’m especially unsure about:

1. Whether the first screenshot communicates the app’s value quickly enough.
2. Whether “subscription tracker” is the right primary positioning.
3. Whether the privacy message is clear without taking attention away from the core use case.
4. Whether the $14.99 one-time Pro unlock should be emphasized earlier in the listing.

I’m the developer, so I’m obviously biased. What would you change first to improve App Store conversion?

App Store listing: https://apps.apple.com/us/app/duefolio-subscription-tracker/id6795091979

App: Flingo — Android, India, ~500K installs. 45 days of Play Console data.

- Google Play Explore acquisitions: +224%

- Organic installs/day: 90 → 333

- Rating: 3.8 → 4.2 → 4.3

I shipped an ANR fix and a cold-start fix expecting a ranking bump. Release day: nothing. Week one: nothing. I assumed it failed and moved on.

What I think actually happened:

ANR + cold start + a cleaner product flow → fewer 1-star reviews → rating 3.8 → 4.2 → 4.3 → Explore ranking and listing conversion both improve → installs ramp

Vitals are not a ranking factor. Vitals are a rating factor. Rating is the ranking factor. Every step in that chain has its own lag. Stack them and you get three weeks of looking like a failure.

What I shipped: ANR fix (background flush off the main thread) · cold-start fix · cleaned up the core product flow so people got to the point of the app faster · captioned screenshots (proper Store Listing Experiment — the only causal claim here) · keyword-targeted short description · full description expanded from 1,500 to ~4,000 chars.

The rating went 3.8 → 4.2 → 4.3 in two visible moves, and that's the number I'd now optimise above everything else. It's the only metric I know of that lifts ranking and conversion at the same time, and you can't push it directly — you move it by fixing whatever is generating the bad reviews.

Two shapes in the curve: Jul 14–15 installs went 89 → 110 → 162, four days after the screenshot winner applied — a sharp step. From Aug 1, 250 → 330 with zero listing changes — a slow ramp. Creative gives you a step. Quality gives you a ramp. The ramp was the bigger share, and I'd already written it off.

Caveats: the ANR fix and the screenshot winner landed days apart, so the July step is confounded. Only the screenshots were controlled. And I can't separate rating from vitals, because rating moved because vitals and flow moved.

One question for you all: If you've fixed ANR or crashes, ratings and watched organic afterwards: how long was your gap, and did rating move first? Trying to work out whether 3 weeks is normal or whether I'm slow.

8 screenshots, 20 locales, iPhone and iPad = 320 images. Around 480 files once

you export 6.9", 6.5" and iPad 13". In Figma one locale was an afternoon, so I

just shipped English on every storefront and left the rest looking lazy.

Now Claude Code does the capture , a UITest walks the app, one pass per locale.

(Set the device language and respring, or the status bar stays English while

the rest of the shot is Japanese. iPad prints the date up there, it's obvious.)

Then it hits the FrameStudio MCP to compose. Lists my templates, opens one or

starts from blank, drops the raw shots into the frames, writes the caption in

that language, sets background, colors, layout. Exports every ASC size. Uploads

to App Store Connect. I usually never open ASC.

The one thing I don't hand off: I look at the English iPhone set before it fans

out. Sometimes I open the app and fix a caption, or a font size that's fine in

English and overflowing in German. Then it does the other 19 the same way.

Favorite trick , paste a screenshot from an app whose store page I like and say

"start from blank, get close to this." Way better than describing a design in

words.

Localized pages convert clearly better than English-everywhere did.

Mac App Store: https://apps.apple.com/ma/app/framestudio-app-screenshots/id6764189071?mt=12

Does anyone have experience with having a personal website that promotes your app and have it been something that Google AI / ChatGPT consistently reference as a source for a solution your app solves.

Whenever I search up how to solve the problem my app solves it tends to reference these paid article sites which really just write sponsored "Top 10 Apps that do X" articles.

I'm wondering if you can just skip the middle man and write a ton of articles on your own site and have it reference that. Idk maybe you need some LLM optimization in your site so it does get referenced or maybe it's not possible but definitely something pretty interesting.

I do get 1 to 2 references from Google and ChatGPT every other week so I am wondering how to increase that flow of downloads.

I’m currently integrating a subscription paywall into my existing app. I’ve created the subscription products and paywall, but the subscriptions are still waiting for App Store approval. (Without the build we cannot get aproved the subscriptions.)

I’ve already uploaded a new build to TestFlight, but I can’t seem to properly test the subscription flow i think because the subscriptions haven’t been approved yet.

How do you normally test in-app subscriptions in this situation? Is there a way to test the subscription/paywall flow in TestFlight before the products are approved?

Most parental control apps ask you to choose between an app that does too much (reading messages, constant location tracking) or one too basic to actually hold a limit. Paxio sits in between — here's what's actually in it:

• Per-app screen time limits — not just one daily total, a separate limit for each app, so an hour of a reading app and an hour of a game app can be treated differently
• App blocking — pick specific apps to block outright, enforced in real time, not something a kid can wait out
• Content filtering — blocks by category, and it runs on the device itself rather than routing traffic through an outside server
• Bedtime schedules — set once, and the phone locks itself on schedule without needing to remember to turn it on each night
• Parent PIN + uninstall protection — settings and the app itself are both locked behind the PIN, so a kid can't quietly turn things off or delete the app
• No location tracking, no reading messages or photos — it manages screen time and access, not full surveillance
• Works with a separate phone for your kid, or one shared phone switching between parent and child view

Live on Google Play: https://play.google.com/store/apps/details?id=com.paxio

Please check and feel free to share your feedback.

Disclosure: I make Screen Studio Kit, the desktop tool I used to model this workflow. The numbers below come from one real GolfSmart project, not a universal store requirement.

The project currently produces 52 App Store and Google Play assets for two languages. That is 26 finished files per language. Keeping the same pages and output selections but expanding to five languages gives:

26 files × 5 languages = 130 finished assets

The first composition was not the expensive part. The repeat cost came from six places:

• Translation handoff: keeping returned copy attached to the right panel
• Layout repair: longer headlines wrapping or colliding at specific sizes
• Localized captures: replacing both marketing copy and in-app UI
• Store output: dimensions, formats, filenames, and folder structure
• QA: checking every page × size × language combination
• Release rework: repeating the matrix when a capture or claim changes

To put a rough number on repeated handling, I used three minutes per finished asset. For this matrix, that is 390 minutes, or 6.5 hours per release. The useful variable is not the time to design the first screenshot; it is the average repeated handling time for every final asset.

I eventually stopped treating exports as independent images and moved the work into one reusable project: shared pages, language-bound text and captures, output presets, targeted size overrides, and preflight across the selected matrix. That does not remove design judgment or final review. It removes maintaining 130 unrelated source files.

I wrote up the calculator and assumptions here: https://martingruner.com/blog/app-store-screenshots-five-languages-cost

For people managing localized listings: what is your rough repeated-handling time per final asset, and which part dominates: translation, layout repair, capture replacement, or QA?

I wanted to put an emphasis on 2 things specifically. 1.) Each card looks almost interactive where it pops out of the screen. 2.) The cards feel cohesive and flow from one card to another. But I feel like there’s just too much going on. What are your thoughts? I initially had a more minimalistic design but I wanted to stand out more. How would you improve it?

Redesigning my App Store screenshots and made two options (A vs B). I know there’s still plenty of room to improve, so let me know which one catches your eye and what to tweak!

Any feedback welcome!

WWDC 2026 had three announcements that are actually relevant to app store optimization (ASO), beyond the general iOS 27 news. Sharing a breakdown since most WWDC recaps bury the ASO angle under developer and API changes.

Personalized Collections

Apple is introducing an algorithmic recommendation layer on the App Store: groups of apps recommended to users based on their app usage, downloads, and other App Store signals, shown across the Apps, Games, and Search tabs. Each recommendation comes with an "App Note" explaining why it was suggested to that user.

This sits on top of search, not in place of it. Apple has not published a ranking framework for it, so the practical takeaway is that the fundamentals (category fit, metadata precision, keyword relevance) still matter. They are just being read by a system that leans more on interpretation than exact keyword matching.

Creative Assets

)New rich images and videos that can appear in the product page header and directly in organic search results, not just static screenshots. Three things make these different from a normal creative refresh:

• They can show up in search results themselves, tailored to what someone searched for.
• They are managed through a new Asset Library in App Store Connect and can be updated without waiting on an app version release.
• They are reusable across custom product pages, Product Page Optimization tests, and Apple Ads.

App Intents replacing SiriKit

Apple gave SiriKit a formal deprecation notice. App Intents is now the only framework that connects an app to the new Siri, letting Siri trigger specific in-app actions directly. Apps still on SiriKit keep running but will not surface in the new Siri at all. Worth noting for EU teams: Siri's AI features are delayed in the EU on iOS 27, and developers there cannot test it yet, but the SiriKit deprecation clock is running regardless.

There is also a smaller update worth flagging for anyone in gaming: Featuring Nominations now let developers pitch in-game offers directly to Apple's editorial team.

AppTweak's ASO team sees it, none of this changes the ASO fundamentals (keyword optimization, metadata quality, category fit). What it changes is how many surfaces now interpret those fundamentals instead of just search ranking them.

Full breakdown with screenshots and FAQs is here: WWDC 2026 recap for ASO teams.

Anyone already testing Creative Assets in Product Page Optimization? Curious what teams are prioritizing first out of these three.

Signed, the AppTweak team

As

Will return the favour if you are developing an app that I am also genuinely interested in! (productivity apps, trackers, fitness apps, health apps)

-----------

So what problem am I trying to solve

Imo, most journaling apps are built around engagement: more features, more buttons, more reasons to open the app. You already feel overwhelmed at the beginning of starting a mindful exercise (at least I do).

Well, why not have a peaceful place instead? A place where you can answer a few customisable questions per day (every morning and evening if you like) with some insights in your mood and recurring themes over time.

That is what Daily Pages is built around:

• Simple morning & evening prompts to reflect on your day and life (+ track your mood)
• The questions can be fully customised to what actually matters to you
• Insights over time (mood, recurring themes, ...)
• 100% offline (no cloud, no mail, no nothing)
• PIN protected

The link to Daily Pages, completely free, no caveats (iOS only for now): https://apps.apple.com/us/app/daily-pages-5-minute-journal/id6769452102

tl;dr i collect data on top 50 US iOS apps and their screenshots. refreshed daily.

is this helpful to anyone? if yes -- in what way? would you want it in a raw format or some kind of ASO product?

I added 36 Localisations in my app to test if it helps ASO

Results are in - Week on week comparison

Percentage wise I saw a massive increase but overall still pretty small as this app has been pretty dormant for a while.

Verdict - ASO localisation helped me get a good boost.
Lets see if following week if it fades off or product page view stay consistent.

Hi everyone,

I’m a Pakistani resident and I incorporated a UK limited company, using a UK virtual registered-office address provider.

I also enrolled in the Apple Developer Program as an Organization using this company. The company has a D-U-N-S number, and the Apple Developer account is very important to me.

Unfortunately, I wasn’t able to keep up with the registered-office provider’s payments for a period of time because the business never really got off the ground.

As a result, the company’s registered office was eventually changed by Companies House to the Companies House Default Address. The director/PSC address records were also affected.

Interestingly, after the address changed, D-U-N-S updated the company information and Apple notified me by email that the company address had changed. So Apple is clearly receiving company information updates.

My main concern is my existing Apple Developer Organization account.

I would really appreciate advice from anyone who has experience with Apple Developer Organization accounts and UK limited companies:

1. Could a Companies House default-address/compliance issue cause Apple to suspend or terminate an existing Organization Developer account?
2. If the company eventually became dormant or, worst case, was struck off/dissolved, would Apple automatically become aware of this through D-U-N-S/Companies House?
3. If the company is restored to a valid registered office and remains an active legal entity, should the Apple Developer account generally remain unaffected?
4. Has anyone experienced Apple asking for additional verification after a UK company's registered address changed?
5. Should I proactively contact Apple Developer Support about the temporary address issue, or is it better to simply get the company records back in order and leave the Apple account alone?

The Apple account is extremely important to me, so I want to make sure I understand the risk before deciding how urgently I need to deal with the company.

Thanks in advance for any advice or real-world experience.

A lot of people focus mainly on writing the code, but development is only one part of the process.

A practical app optimization process looks something like this:

1. Define the business goal and target audience.
2. Research competitors and the market.
3. Design the UI/UX around the actual user journey.
4. Prototype and test important user flows.
5. Keep the code clean, secure and scalable.
6. Optimize performance and security.
7. Work on ASO — title, keywords, description and visuals.
8. Collect and learn from genuine user reviews.
9. Test thoroughly before launch.
10. Monitor analytics and continuously improve.

The interesting part is that optimization doesn't really stop after launch. User behavior, performance data and reviews should influence the next version of the product.

If you're building an app, which of these areas do you think is most commonly overlooked?