Ali

doing ASO research for SignalFind made one thing clear: the biggest keyword isn’t always the best one. "bluetooth finder" has more volume, but also much stronger competition. I’d rather rank for a smaller relevant keyword than get buried trying to compete for the biggest one.

got my second sale for my Bluetooth finder app 🎉 I haven’t spent anything on ads or really done much marketing for the app. so far I’ve mostly been working on ASO, improving the App Store listing, and sharing the app only a few times on X/LinkedIn. 3 new users in the last 7 days, 2 purchases. small numbers for now, but seeing people find the app and actually pay for it without ads is pretty cool.

I used to think App Store localization was mostly about translating the app. turns out there’s an ASO opportunity too. Apple has separate English (US) and English (UK) localizations, which means I don’t have to use the exact same keyword set for both. and for other languages, I can localize the metadata around how people actually search in that language. working on this now for SignalFind: Bluetooth Finder. more localizations = more keyword opportunities to test.

What happened with the App Store review system? It has been almost 5 days, and it is still in review.

Check out SignalFind: Bluetooth Finder 👉🏻 apps.apple.com/in/app/signal…

if I launched SignalFind app again tomorrow, I’d change a few things before hitting "Submit for Review": - add product analytics before launch - track the full purchase flow from day one - ask users why they leave without buying - make sure I can see exactly where users drop off - stop staring at install numbers and look at what people actually do inside the app these are all things I ended up adding or learning after launch. would’ve saved me a lot of guessing if I had them from day one.

if a user is going to pay for your app, there's a 36% chance they decide on Day 0. not after using it for a week. not after a reminder email. Day 0. that's why every screen before the paywall is also a paywall. (red = freemium, blue = hard paywall)

launching an app taught me something quickly: installs tell you almost nothing. I wanted to know: - do they actually use the core feature? - do they reach the paywall? - do they tap buy? - where do they leave? so I added PostHog to SignalFind: Bluetooth Finder. that’s how I spotted users reaching the purchase flow and backing out. without those events, I’d probably still be guessing what to improve.

my last SignalFind app post on LinkedIn got 23K+ impressions. 65 people clicked through to the App Store and 7 new users installed the app. the interesting part: almost all of them opened the paywall, tapped buy, reached Apple’s purchase screen, but didn’t complete the purchase. I could start changing the price or paywall based on guesses. instead, I’m working on a purchase-abandon survey that appears after someone cancels the Apple purchase flow and asks what stopped them from buying. that should give me actual reasons to decide what I need to change next and improve the app based on user responses, not assumptions.

finished the purchase-abandon survey for SignalFind. now when someone taps buy, opens Apple’s purchase screen and decides not to continue, they get one quick question. they can tell me if: - price is the issue - they want to try it first - they’re not convinced it’ll work - something else stopped them or just tap “Not Now”. small change, but now I can make the next paywall decision based on actual user responses.

After years of Flutter, building SignalFind with SwiftUI made one thing clear: For iOS-only apps, native feels cleaner. - CoreBluetooth directly - No plugin/bridge layer - Fewer iOS workarounds - Easier debugging I’d still reach for Flutter when I need both platforms. But for my next iOS-only app, choosing SwiftUI will be a much easier decision.

46% of subscription apps are moving toward trials of 4 days or less but RevenueCat’s 2026 data shows something pretty surprising: - 17–32 day trials converted to paid at 42.5% - 3-day trials: 25.5% - longer trials converted ~70% better everyone seems obsessed with getting users to pay faster, but the data isn’t really backing that up

Google just made Search Console way more interesting for people building an audience online you can now connect platforms like X, Instagram, TikTok and YouTube and see: - which Google searches found your posts - which posts got impressions/clicks - what content is actually getting discovered through search

didn’t know Apple can help bring cancelled subscribers back without you building the whole win-back flow yourself you can create a win-back offer in App Store Connect eligible users can then see it in the App Store, their subscription settings, and inside your app pretty useful feature if you run a subscription app

Which one is best? - RevenueCat - Superwall been using RevenueCat for my last 2 apps but thinking of switching for my next one.

another small SEO thing I ignored for way too long: if Google finds multiple URLs with the same or very similar content, it chooses one as the canonical version. You can use rel="canonical" to tell Google which URL you prefer instead of letting it guess. worth checking once your site starts getting more landing pages and blog pages. duplicate URLs can get messy fast.

Android deep links are less painful than I thought now Play Console has a Grow -> Deep links section that shows broken configurations and tells you what needs fixing the interesting part: some deep-link fixes can be pushed live without publishing a new app release

you are absolutely cooked if you're still building mobile apps without AI tools in 2026. it's not cheating. it's just how you ship now.

small ASO thing I somehow missed: Apple now lets you create up to 70 custom product pages and assign keywords to them so someone searching a specific keyword can actually see a version of your App Store page built around that use case instead of your default page this opens up a lot of ideas