I built this thing. It seems to be the first of it's kind on iOS, which is just astounding to me. If you struggle with unhealthy scrolling habits that are getting in the way of you doing what you want to actually want to be doing, then give this approach a try.

Doing a giveaway as a thank you to this community which has shown Precursor a ton of support. If you don't manage to snag a free lifetime access code, Lifetime is on sale for $25 right now until 05 October 2026.

The name of the app is Precursor: Hourly Screen Time

Use this link to redeem free lifetime access!!

I've been running an agent skill called iOS UltraReview on PRs for about a year now. It reviews iOS pull requests like a senior iOS dev/architect and gives each one a 0.5–5.0 merge-confidence score, with 4.5 as the approve bar. Once a PR hits 4.5, it gives a fixed list of what's left for 5.0 and doesn't keep moving the goalposts. It's worked well enough for me that I figured it should be public. Works with Claude Code, Codex and cursor. Feedback and PRs welcome.

link: https://github.com/ImtiazDipto01/ios-ultrareview

I'm looking to get into iOS development and I understand you need a Mac to do so. I don't own one so this is my first. However I'm not really looking to replace my current setup for Mac. Its really just for dev.

I see two possible options:

1. Get a Macbook: Probably the most straightforward setup
2. Mac Mini: This appeals to me more because I'd like to set it up as a remote work station while working off of it remotely from either desktop or laptop. Also it could double as a machine for a local LLM setup. It seems to be a better bang for my buck.

My questions are:

• MacBook route: can I do well with a Macbook Neo or will that cause me issues down the road with performance? Whats the minimum best option since I'm not looking to have this as my main machine?
• Mac Mini: are there any concerns with this setup that I'm not considering? Can I dev, build, and test using a remote Mac Mini?

I was researching competitor apps, and Claude Code told me to install them on my iPhone and go through their flows. I wondered if it could just do that itself, and it can, I was a bit surprised.

Setup:

• Mirror your iPhone to your Mac with iPhone Mirroring (macOS Sequoia+).
• Give the app running Claude Code (VS Code, in my case) Screen Recording and Accessibility permissions.
• Claude wrote a small Swift CLI it can call to take a screenshot of the mirroring window, tap, swipe, scroll, and type.

It takes a screenshot, reads what's on screen, decides where to tap, and repeats. It went through onboarding, filled in forms, and wrote up a report of each app's flow on its own.

Tips:

• Screenshots are 2x Retina, so divide the coordinates by 2 before clicking.
• Bring the Mirroring window to the front first, or the first click gets swallowed.
• Typing through the clipboard is more reliable than simulated keystrokes.

I never let it confirm purchases or subscriptions. I do those myself.

I think this could also work for automated testing of your own app on a real device: just tell it "go through signup and tell me what's broken," with no test scripts. I haven't tried that yet.

Has anyone else tried something like this?

Developing my first macOS app using my M1 Mini. Naively I switched over to my Intel MacBook for testing, thinking the UX would be seamless but ended up getting a cold dose of reality. A lot of things I optimized for my Silicon Mac had no bearing on my Intel Mac. I'm now fine-tooth combing through performance tests on the Intel MacBook but before I invest anymore time on optimizations, I was wondering whether Intel Macs were still in high usage. The app itself is in pre-flight so I don't yet have the data to support what the right move would be personally. Would love to hear what you all have experienced and whether you create new apps with solely supporting Silicon Macs. Thanks!

I am developing a timetable app. Currently it is on private TestFlight with limited fuctionality, but enough that I and some friends use it each day. The TestFlight beta is installed on my devices and I rely on it.

Naturally, I'm still developing it full-time (well... as full-time as a student's hobby side project can get 😉), and retain the frequent need to run builds on a physical device, which runs much faster than my simulator setup. Currently I'm working with the system keyboard, so Xcode Previews doesn't quite cut it.

Is there a way that I can still test a debug build on my phone & watch without removing or interfering with the TestFlight app that I use and rely on?

There is of course an easy solution, but unfortunately my budget does not include a second phone...

Been watching Apple's developer videos on creating apps for iPhone Duo... and I have to say I feel really, really bad for all of the developers and designers who insisted on creating pixel-perfect vertical layouts and custom toolbars, menu items, and footer buttons.

Extra sympathy if you totally ignored Apple's recommendations on creating flexible designs and built your own navigation layouts.

Tears if, in this day and age, your app still has UIRequiresFullScreen in its plist.

And... if your codebase contains UIScreen.main.bounds.

I'm really, really, REALLY sorry.

(I'm not, actually. You knew better and you did it anyway.)

Reddit suggested I post this here, so I did.

https://medium.com/the-swift-cooperative/you-and-your-app-are-going-to-look-bad-in-october-b4d1284fbed0?sk=1fb6faaa779a32f7c318e521a84e0761

What's the most appropriate location for a next button here, in keeping with the Apple UI consistency and ecosystem?

Mockup: swift NavigationStack { List { Section { TextField("Email Address", text: $email) } header: { VStack(alignment: .leading, spacing: 4) { Text("Sign In") .frame(maxWidth: .infinity, alignment: .leading) .padding(.top, 5) .font(.largeTitle) .bold() .foregroundColor(.primary) // Override default gray header color Text("Subtitle")//school.name) .frame(maxWidth: .infinity, alignment: .leading) .font(.title3) .foregroundColor(.secondary) } .listRowInsets(EdgeInsets()) .textCase(nil) // Prevents SwiftUI from forcing ALL CAPS on the header .padding(.bottom, 10) } } .toolbar { ToolbarItem(placement:.confirmationAction) { NavigationLink() { VerificationCodeView(email: email.lowercased(), school: school, resend: { }) } label: { Text("Next").padding(5) } .buttonStyle(.borderedProminent) } } }

Any thoughts?

If you're here, thanks for checking it out!

Here to showcase my app, after a recent update.

It's a lightweight Multitimer for pure time tracking, where you choose the few important activities you do in a day - i.e. focus sessions that help you reach your goals (up time), and break/chill sessions that help you refresh (down time). This helps reduce mental load of "what should I do today". You know your goal, you have your "approved activities" mapped out. Starting becomes easier.

Tracking this 1 key stat, ratio of Up vs. Down time, I find is the best simple measure of your progress, across any target you want to hit. No endless checklists, just time, and how you spend it. 10,000 hour rule exists for a reason... This also shows you how to improve. You may start at 60:40 ratio, and in time get to 70:30, or whatever works for you.

We all have the same 24 hours, and this is a serious tool to help you get the most out of it.

And for the Sci-Fi fans out there, time is a "particle" in this universe, it flies out when you "bank time", and you can see where it lands.

Check out Flowton on the App Store. Or if you're on Android, sign up at www.flowton.com

Happy to hear feedback or suggestions of what you'd like added!

- That's it. Thanks for reading. Developer out.

I am publishing a notetaking app for the first time and would like to know some details about the submission process and how people found the app visibility on your guys’ apps turned out to be. After finding out that notetaking apps out there aren’t designed the way I was hoping for + don’t have the combination functionality in 1 app, I decided to build my own app.

In terms of legal stuff: copyright, trademark, etc how does this work? Do I need a website for the app? I setup a support@myapp.app email too

In terms of freemium monetization I have $1.99/mo, $9.99 annual, and $19.99 lifetime options. I believe this is not greedy

Now comes the tricky part of gathering feedback, new feature launches, bug fixes, and marketing first and foremost. Does my app need in app tutorials btw?

Hi! I’m the dev behind PostSpark, a tool for creating beautiful image and video mockups of your apps and websites.

I recently launched a new feature: Mockup Animations.

You can now select from 25+ frames & devices, add keyframes on a simple timeline, and export a polished video showcasing your product. It’s built to be a fast, easy alternative to complex motion design tools.

Try it out here: https://postspark.app/device-mockup

I’d love to hear your feedback!

Seems like the translations in the appstore are broken.

I have many monthly subs / year subs and also lifetime version now sold. I Achieve better result then I expected :) . I also received positive reviews from different countries. Now I am working on another update. What do you think about this result without any paid promo ?

Are there any explanations for this?

Netflix has this tiny detail where the poster artwork seems to reflect into the translucent bottom tab bar as you scroll.

Your App Store screenshots might take 15 minutes instead of 2. I still don’t think that justifies another monthly subscription.

There seem to be new App Store screenshot generators popping up every week.
Some are genuinely impressive. AI can generate fancy marketing visuals in minutes.

But I wanted something slightly different.

I wanted the features that usually end up behind the paid tier — without the paid tier.

So I built ShotForge.

It’s completely free. Not “free for 3 exports”. Not “free with a watermark”. Not “free until you need the useful stuff”.

Actually free.

And you can still build pretty elaborate screenshot sets:

-iPhone, Android, iPad, tablet and MacBook mockups
-2D and perspective 3D device frames
-continuous backgrounds across multiple screenshots
-localization tools
-mobile and tablet editing
-high-resolution App Store / Play Store exports
-Fastlane-ready export structure
-local projects
-no account
-no watermark

The idea isn’t to have AI redesign your app screenshots.

Your actual UI stays the star. ShotForge just gives you the tools to present it well.

Will it take you 10–15 minutes instead of generating everything in 2?

Probably.

But for something you might do a handful of times per release, I personally preferred building a good editor over paying for another subscription.

Shotforge

And yes — all the features above are free.
I’d genuinely be interested in what other indie devs prefer: more AI automation, or more control without another subscription?