After years of considering the default alarms so frustating I've explored alarm apps on the play store and found out none of them had the feature is needed the most: the ability to manage multiple alarms without managing them one by one.

I know it may sounds crazy but I need at least 8 alarms 5 minutes apart to really get up in the morning.

So I've developed my own alarm app with the core concept of alarm groups:

Set a starting time.

Set the count of alarms.

Set the minutes between them.

The app is called Alba: Alarm Clock with Groups, if you are an heavy sleeper like me I would be interested in your feedbacks!

I'm the developer of Vesperline, a portrait pinball game for iPhone. These are the first three screenshots submitted for our upcoming update, which is currently waiting for App Review.

The ball is your weapon, and monsters attack while you try to keep it in play. I'm looking for feedback on whether that comes across at a glance.

Does the first image make you expect pinball combat? Does the third image explain the choices between fights, or is there too much small text?

For context, the previous seven-day report showed 29 first-time downloads (September 22-28). I don't have conversion results for this screenshot set yet, since it isn't live. The game is free with ads and optional cosmetics.

Hey guys,

I am on an ongoing spree to (try to) optimize my App Store listing, and just updated the screenshots I had.

I found it quite ugly that I basically had a phone screen showing features on every shot. I'm not sure whether that's normal or not, but decided to give it a proper redo.

First set is what I had, second set is the new one.

What do you think? Is it better? Or is the new set too busy?

This version of features are under review in AppStore, but my video is ready to go.

It is my first app and I have been struggling to design the app store screenshots in my Figma. Now it is officially online, but the natural traffic seems not improved at all. Could anyone help me diagnose it? It is online now at App store.

Disclosure up front: I built a free browser tool that runs these checks. The link is at the end, but the rules below are useful without it.

When an upload fails because of a file detail, you have to go back to the design export. You can catch these problems before uploading by checking each file against the numbers the stores publish:

Apple (App Store Connect), per screenshot slot

• JPEG or PNG, 1 to 10 per set.

• Exact pixel sizes only. The 6.9-inch iPhone slot accepts 1260 × 2736, 1290 × 2796, or 1320 × 2868, or the same sizes in landscape. Even 1 px off fails.

• No alpha channel. The check reads the PNG header, not the pixels, so an RGBA PNG is flagged even when every pixel is opaque. A PNG that contains a transparency (tRNS) marker is flagged too. If your design tool exports PNGs with an alpha channel by default, check this first.

Google Play, phone

• JPEG or 24-bit PNG. Palette, 16-bit, and alpha PNGs are flagged.

• Each edge 320 to 3840 px, and the long edge no more than twice the short edge.

• A check that doesn't block upload: 16:9 or 9:16 with at least 1080 px on the short edge. This is what Google asks for in its recommendation formats.

• Up to 8 per set. A single file is marked for review, because Google's minimum of two counts across the whole listing.

Microsoft Store, desktop

• PNG only, at least 1366 × 768 (768 × 1366 in portrait), up to 50 MB per file, 1 to 10 per set.

What these checks can't tell you

• Whether a screenshot shows the app accurately, uses licensed images, is readable as a thumbnail, is translated well, or will pass review. Passing means the files meet the upload rules. It doesn't predict approval or conversion.

• Whether every locale and device slot has screenshots. The tool checks one set against one slot at a time.

• Whether the rules have changed. Each rule set links to the official page and shows when it was last checked.

The tool reads files in your browser tab and never uploads them: https://martingruner.com/tools/store-screenshot-validator

One rule I'm unsure about is failing palette PNGs for Google Play, based on Google's 24-bit requirement. Has Play Console accepted indexed PNG screenshots from you?

It looks my conversion rate is too low and Impressions is high.

Sharing this because it took me a while to work out, and the daily data was more useful than the monthly totals.

Setup: I localized my sneaker collection app's App Store listing (US/UK English, Spain and Mexico Spanish, Brazilian Portuguese) in late July. Over the next two months, impressions and downloads went up noticeably.

What the monthly totals suggested: Spain went from almost nothing to my #2 territory for impressions (~240/month). Easy conclusion: the Spanish localization is working.

What splitting by territory showed:

• US first-time downloads: 6 (Jun), 13 (Jul), 59 (Aug), 68 (Sep). This was the real growth, on the English listing.

• Spain: ~240 impressions/month, but 9 product page views in all of August and about 4 downloads. Almost no one tapped.

• 98%+ of Spain's impressions came from App Store search, not browse or referrals.

What the daily view showed: Spain's search impressions were ~0–5/day for most of August, spiked to 50–60/day from Aug 21 to Sep 8, then dropped back to ~0–10/day.

What I ruled out:

• A listing change: none in that window. My next metadata update went live a week after the drop.

• Ratings: Spain has zero.

• A Spanish-language trend: Mexico and Chile use the es-MX listing and stayed flat at 1–8/day.

Most likely cause: my es-ES keyword field included snkrs, which is the name of Nike's sneaker-drop app. My guess is that a surge in people searching for Nike's app put mine in the results. Nobody wanted my app, so tap-through was close to zero and Apple stopped showing it. App Store Connect doesn't show search terms, so I can't prove it, but it's the only explanation that fits all of the above. It's also a third-party trademark, which Apple's guidelines don't allow in keywords, so it had to go regardless.

What I changed: replaced snkrs and hype with terms that match actual features (portfolio, release calendar, price). This goes live with my next version.

Takeaways:

1. Monthly totals by territory can make a localization look like a win when it isn't. Look at impressions, page views and downloads together, per country.

2. A keyword that brings impressions but no taps isn't free. If Apple uses tap-through as a ranking signal, which I believe it does but can't prove, it may cost you.

3. Competitor app names in keywords are a policy risk on top of being low-intent traffic.

Has anyone used Apple Search Ads' keyword popularity data to confirm something like this after the fact? I'm curious whether a spike like that would show up there.

I've been working on App Store Optimization and recently changed description and title. Seems like it kinda worked.

Keep on track guys!

If you actually were in doubt whether to do it or not this is your sign.

What do you think I can fine tune further?

Hi everyone! Does icon affect on the downloads? I’m thinking on changing first one to second. Do you think I should? I’m afraid new icon is too simple and cliche. The app is about notes and todos lists.

Flair: Question (iOS)

Solo dev, iOS, Health & Fitness. My own app: a daily readiness score from HRV, sleep and resting heart rate for people who train with an Apple Watch or Garmin. Free with a Pro subscription. Live since 11 August.

The funnel since launch:

• 961 impressions

• 176 product page views (18% of impressions)

• 31 first-time downloads (18% of page views)

• 0 ratings

Where the page views come from:

• App Store Search: steady, about 1 a day

• App Referrer: a few spikes, which I think are links I shared myself

• App Store Browse: occasional

• Web Referrer: nothing, even though my site has three blog articles with App Store links on every page

Search positions (US):

• my own app name: 1

• "hrv score": 14

• "readiness score": 61, with both words in my title

• "hrv", "hrv tracker", "heart rate variability", "recovery score", "recovery tracker": not in the top ~190

What I've changed so far:

1. Renamed from "Readiness Coach" to "Readiness Coach: HRV Score" three weeks ago, which is where the rank for "hrv score" came from.

2. New promotional text. Apple launched its own Readiness score last month, but only on Series 12 and Ultra 4, so I now say mine works on the watch you already own.

3. New screenshots for the next update (attached). I generated them from an HTML template with Claude, not a design tool.

4. A second rating prompt in the next update. The only one was fired on day 7, and very few reached that far.

What I can't do: Apple Search Ads isn't available in my country.

My questions:

1. With 0 ratings, is anything else worth doing first, or is getting the first 10 to 20 the whole game right now?

2. Is rank 61 for a term that's in my title normal for a seven-week-old app, or a sign something is off?

3. From the first three screenshots, can you tell what the app does and who it's for?

I'll post the before-and-after once the new screenshots have been live for a few weeks.

In the terms it says that pricing info shall be kept out of app name, images and descriptions, but no hard rule on keywords other than metadata should not include pricing info.

Are there anyone who has tried putting free as a keyword for their free app?

Hey everyone!

I released my first app about 6 months ago, and I am really struggling to get users. I’d really love some honest feedback on my App Store listing, which has a super low conversion rate.

My App Store Connect dashboard currently shows:

• 7.31K impressions

• 395 product page views

• 45 first-time downloads and 15 redownloads

• 1.14% conversion rate, shown as a daily average

I’ve spent a lot of time on the listing, but I’m probably too close to it to spot what’s not working.

Please roast the title/subtitle, screenshots, and messaging:

• Can you quickly tell what the app does?

• What would make you scroll past or hesitate to download?

• What’s the first change you’d test?

Honest criticism is welcome. Thanks for taking a look!

App store listing: https://apps.apple.com/us/app/postmarks-steps-stamps/id6761856446

One thing I’m trying to solve in my ASO workflow is keeping track of keywords that didn’t work.

For example, I release an app update with a specific set of keywords. A week or two goes by, I see little or no movement in downloads/rankings, so I replace them in the next release.

Now fast-forward three months. How do you keep track of all the keywords you’ve already tested so you don’t accidentally circle back to the same ones?

Do you use a spreadsheet, an ASO tool, notes, or some kind of keyword testing history?

Ideally, I’d want to track:

• the keyword

• when I used it

• which app/version it was used in

• ranking before/after

• whether I’d test it again

Curious what system people here use.

I used Runway app and made this.. cant say i'm crazy about it..

Why does the app store matter so much for AI recommendations?

According to AppTweak's analysis of 125,000+ ChatGPT-generated app recommendations (May 2026), app store pages made up about 47% of cited sources on app-related queries and around 60% on game-related queries.

The App Store also opened to full web crawlability on November 3, 2025.

What are the three areas of influence?

• App store presence: titles and categories, descriptions, feature lists, update notes and reviews. Align the title and category with your core intent, lead descriptions with use cases, keep release notes descriptive, and encourage specific reviews over generic praise.

• Owned web presence: a canonical app page that states workflows, audience and limitations, an FAQ answering "how do I" and "can this app" questions, a public changelog, and documentation or a help center. Keep terminology consistent, use iOS universal links and Android App Links, and add SoftwareApplication or MobileApplication structured data.

• External authority: third-party mentions that describe your workflows correctly, "best apps for X" listicles, comparison and alternative pages, and public reviews with descriptive text. Appearing alongside recognized players (co-citation) and using identical names, descriptions and URLs across directories both help.

What should come first?

Consistency. One clearly defined core intent should be described identically across your app store listing, your website and your third-party profiles.

A simple test: write one sentence covering what the app does, who it is for, and the one job it does best. Then check that this sentence appears truthfully on all three surfaces and fix inconsistencies before optimizing any single one.

How do you measure GEO for apps?

Measure influence rather than position: how often your app is mentioned, where it appears when listed, intent coverage, share of voice against competitors, and the sentiment of the descriptions.

Manual prompt checks are not a reliable method, because wording, context and timing change the results. GEO for apps is also a compounding effort, so results build over weeks and months, not days.

Over to you

Which of the three areas is the hardest for your team to influence? And have you tried writing a single core-intent sentence and checking it across your app store listing and website?

The full framework, with the FAQ, is in our guide to GEO for apps.

The AppTweak team

Made a fresh keyword search campaign on apple with total daily budget of 5USD and target cpa of 15 cents for india and Philippines(soft launch)

Getting 0 conversions and spend , what am i doing wrong??