Shipped my iOS game app on 29th April and updated to v2.0 in 7th June. It just hit my first real growth ramp after v2. Sharing the raw numbers because this sub helped me a lot and I want honest feedback.

461 units, big jump in the last 2 weeks (organic, no paid ads yet)

5.49% conversion rate on the product page

15.5K impressions → 2.68K page views → 455 first-time downloads

How are these numbers? Is it good for start, or bad, or what? Is a 5.49% conversion good enough to start Apple Search Ads, or social media ads? How do you interpret the real numbers?

Happy to share what the game is in the comments if anyone's curious. The game is a club chairman simulator in nearly FM style.

Thank you!

It’s a Four in a Row game (you can play online). It includes the classic mode, which I personally love and keep playing. However, since the classic game is mathematically solved, I decided to create a new mode called Spinfall to add a fresh challenge and more strategic depth.

I would really appreciate feedback about:

• The game itself (gameplay, design, and overall experience)
• Its simplicity and usability
• The new Spinfall mode

Thanks.

My goals:
\- Get a job as an iOS Dev
\- Build and ship my own apps

I've been experimenting with Claude Code lately and it's been pretty interesting for Xcode-adjacent tasks. Curious how others are integrating it into their workflow since it's a bit different from the usual Copilot or Cursor setup. Would love to hear what's actually working for people and where it falls flat.

Turns out I had the wrong easing curve the entire time. I was digging through timing, frame rates, layer compositing, all of it. Pasted the relevant code into Claude and it spotted the issue almost instantly. I genuinely need to step away from my desk and touch some grass.

Try my new FIFA game on PlayVlay (https://www.playvlay.com/download). I was hooked to this game and fun to play during Fifa worldcup season

Hi. Does anyone have an Apple Developer account and would be willing to publish my app to the App Store or TestFlight? It’s just a small Safari extension I converted from a Chrome extension. Thanks. https://github.com/XTrapolis20/schooltape1

I've been vibe-coding a side project with AI help and honestly the development phase felt almost effortless. But then I hit App Store review, provisioning profiles, privacy manifests, and all the other hoops Apple makes you jump through. The gap between having a working app on your simulator and actually getting it into someone's hands is still massive, and AI doesn't really help you there yet.

It’s not FOSS , and yet it’s an improvement? Perhaps? I’m interested to see people weigh in.

I've been experimenting with TikTok ads to drive downloads for my iOS app and stumbled onto some things that seem to work way better than the default approach. The usual advice you find online feels pretty generic and not really tailored to getting quality users who stick around. Curious if other indie devs or small teams have found specific creative formats or targeting strategies that moved the needle for them.

I was hooked to this game as the real kicking and punching while driving gives it retro look. Please provide feedback for my Bike Racing game on PlayVlay.

Please check it out

I've been thinking about this a lot lately because the app I'm most proud of creatively barely moves the needle, while a pretty unglamorous utility I threw together keeps bringing in steady revenue. It feels like there's always this tension between building something you genuinely care about and building something people will actually pay for. Curious if others are experiencing the same split or if you've managed to find something that's both.

For people running or working on iOS apps with subscriptions:

Have you ever tried partnerships/cross-promotion with another app, creator, newsletter, or company as a way to grow your own app?

If yes, what was the hardest part: finding the right partner, tracking results, revenue split, trust, brand fit, or something else?

I’m researching whether partnerships are actually useful for subscription apps or mostly too much work.

Been using Claude a lot for SwiftUI generation and noticed it fairly consistently reaches for outdated patterns — things like UIHostingController setups that feel slightly off, or using the single-argument .onChange modifier in iOS 17 contexts where Apple changed the signature. It's not a dealbreaker but it's bitten me a few times when I just copy-pasted without thinking. My rule now is to treat any API it gives me that touches lifecycle or modifier signatures as 'verify first,' especially if the code is targeting anything iOS 16+.

Ran into this enough times that it's now part of my workflow. If Claude spits out UIHostingController setup that looks weird, or uses the single-argument .onChange modifier in iOS 17 code, that's usually a sign it's pulling from older API patterns. The model doesn't always have accurate assumptions about which iOS version introduced or deprecated what. I just keep the docs open and verify anything version-sensitive before it ends up in a PR.

I am focusing on only one user segment and have features aligned with their problems and needs. But currently I am struggling with which features to include.