Davron Karimov

@t0mbfx Amazing Tom, wish I will reach the same soon

@seraleev Solo with Claude 😅

Are you a solo dev or do you have a team? 1) Solo dev 2) Have a team

@seraleev Do you localise your app itself too, or only screen shots and metadata?

Before saying ASO is dead, localize your app. Translate metadata, adapt screenshots, pick the right title and subtitle for each market. Run price localization against purchasing power parity. App Store is not just the US. Some of my apps make most of their money from India, Netherlands, Thailand. Localization is one of the most underrated levers in ASO. It works.

@vatsal_sanghvi Nice, do you use adds?

my consumer app made some money while I was sleeping

@Fun_Trades1 I shorted exactly where you buy, interesting how market is showing different scenarios for different people

L on gold | -2100 This market is wierd. I anticipated a quick reaction from my entry. But it chopped for over 1h! I lost faith in the setup and close a bit early. Good decision. But it still shows that this low volume chop market is not for me.

Nice Animations to use by @Shubham_iosdev . Great work!

Day 2 of LeetCode: Maybe (Maybe Not!) The most elegant way to find the GCD of two strings. 😂 I was recently diving into the "1071. Greatest Common Divisor of Strings" problem, and the solution in Swift is a "masterclass" in combining simple math with string logic. The goal of the task is to find the largest string X such that both str1 and str2 are formed by repeating X. The "Magic" Check: guard str1 + str2 == str2 + str1 Before doing any heavy lifting, this check confirms if a common divisor even exists. If they don't commute when concatenated, they don't share a base pattern. It’s a simple proof of a periodic property! The Euclidean Twist: Once we know they share a pattern, the problem stops being a string problem and becomes a math problem. We just need the GCD of the two lengths. By applying the Euclidean algorithm (which dates back to 300 BC!), we find the exact length of that repeating unit in O(logn) time. New Day New Knowledge. What’s your favorite "simple" solution to a seemingly not complex LeetCode problem? Let's discuss in the comments! 👇 #Swift #Coding #Algorithms #LeetCode #SoftwareEngineering

@isaacthequach Maybe yes or maybe no 😄

ONE FUNDED account can change your life forever

@DanKulkov Worst Feeling

> yay, new trial > 4 minutes later > oh

@Anas_founder Air

Developers, which one do you prefer? -Mac mini -MacBook Air

@bymarcoperez Awesome! Hopefully It will be 10000$ MRR

My app just hit $200 MRR 🥹 Cheers to the next hundred!

@Fun_Trades1 Nice try

First trade of the week | BE Unfortunately, I got stopped at BE by a tick before price hit my target. I do have to say that my fear of losing was a bit too high because of last week. I shouldn’t have moved my stop to BE.

@athcanft What if you don't have money for the adds?

how i got my app to $10k MRR in 7 steps 👇

@Fun_Trades1 I hope my account will grow too

Weekly Review X I thought it would be interesting for some of you to see the development of my X account. I believe it’s very cool to look at the stats of a smaller creator like me, so: 9 posts 421 replies 8% Engagement rate +145 followers Thank you all for the support! 🫶

Working On some Redesign of Shift Worker Calendar & Rota and What popped in my mind is that : Being an indie dev means you are the: -CEO - Lead Engineer - UI/UX Designer - Marketing Lead - Support Desk - Janitor It’s exhausting, overwhelming, and occasionally frustrating. But seeing that first "Active User" notification? Will BE Worth every line of code! Link to my app: apps.apple.com/uz/app/shift-w… #IOSDev #IndieHackers #ShipIt #VibeCoding #iOSIndieDev

@Fun_Trades1 Be careful

Little recap on the day I lost one funded today and two 25k funded accounts are roughly $250 away from loss limit. The 50k funded is $700 away from the loss limit. I bought a new 50k eval (2 total), which I will trade very agressive. I took a BE (+$40) on one of them today.

Your tech stack doesn't matter if your cold-start time is killing your App Store rankings. I spent the morning profiling my app's launch sequence in Instruments. Every 100ms added to that splash screen is a drop in day-1 retention. And the App Store algorithm is watching. My current "Indie" checklist: Lazy load all non-essential SwiftData containers. Zero heavy SDKs in the AppDelegate. SwiftUI for the UI, but keeping the logic out of the View structs. Code for the user, but optimize for the algorithm.

Most indie developers start with an idea. I start with search intent. Building apps like Onyx (Invoicing) and Zyna (Fasting) has taught me that a "perfect" app with zero ASO is just an expensive hobby. For the US market, relevance is everything. I’ve been spending as much time in the App Store Connect analytics as I have in Xcode. If you can’t convert the searcher in the first 3 seconds of looking at your screenshots, the tech stack doesn’t matter.

Being $300 away from a funded account is a mental trap. Every bone in my body wants to force a trade just to "get it over with," but that’s how you blow the lead. Treating today’s price action exactly like a SwiftUI bug: wait for the logic to align, don’t guess, and only execute when the setup is perfect. discipline > desire. I did this mistake 100 times, not this time hopefully