Others seeing a drastic decrease in app downloads and product page views recently? Not just for one app but all apps. I'd say almost 70% drop in the last 2-3 months.

I personally use it for airplane journeys and road trips with my kids. I found some alternatives but I thought they weren't very good. I also was inspired by some Bluey games and Tinyfingers.net, what an awesome site!

Totally free, no ads, no purchases, no tracking.

• Tech Stack - iOS, SVGs, Metal. AI coding assistants
• Development Challenge - I learned Metal so I could add a highly capable finger tap area for the sparkle touch board game. I saw my kid playing with it and it was lagging so I realized I needed to dig deeper for a real fix. What I did was make sure all of the effects are rendered once per frame at the same time instead of relying on SwiftUI/UIKit framework animation tools.
• AI Disclosure - AI Helped me improve my own SVG animals and backgrounds, but it is my art, public domain and CC0 sounds, and it's free with no ads or purchases at all.

I would love to add specific instruments, games, adjustments, etc.

A bit of context - I'm a personal trainer that is considering various "app options", I've narrowed my choices down to 2 that currently fit my criteria but one of them is a web app. I was wondering if there was a way for me to pay my own app developer account for a wrapper for said web app.

I don't own the webapp and the wrapper would be pointing to my client portal for the app.

Hey r/iOSProgramming! I'm an indie developer, and I just submitted DuoBeat 1.0 to App Review. While it waits, it's open on TestFlight and I'd love feedback from this crowd.

What it is: a beat-making app inspired by Teenage Engineering's Pocket Operators. It has 16 step pads, four knobs per sound, a pixel mascot that reacts to your beats, and a pocket-sized interface that's quick to jam on.

The fun technical part: the layout adapts to the device's form factor.
iPhone / outside screen of the iPhone Duo: compact PO-style groovebox
Folded "laptop" posture: split screen, with the editor on the top half and pads/controls on the bottom, like a hardware groovebox
Unfolded / iPad: full studio DAW layout

Stack: Swift/SwiftUI. I also leaned heavily on Claude Code during development, and I'm happy to talk about what worked and what didn't.

Things I'd love input on:
How intuitive the UI and UX are.
How layout transitions feel.
Audio latency and timing on your device.
Recording, exporting, and sharing.
Anything confusing you see!

TestFlight: https://testflight.apple.com/join/pstMWvHV

Happy to answer questions about the posture detection, the audio side, or the design. Thanks for checking it out!

I submitted a recent update for my app, got through review and hit the manual release. It’s showing as “ready for distribution” as per usual, but the App Store listing is still on the old version.

After 24hrs I went scouring ASC and saw a business agreement needed re-signing so I did that and still nothing. Is it just stuck? Anyone have this?

I did include Duo support but I believe that doesn’t result in holding back until the 23rd?

I'm enrolling in the Apple Developer Program as an organization (US Delaware corp, DUNS already issued and visible on dnb.com). Everything goes fine until the identity verification step, which fails every time with:
"Unable to Verify Your Identity. Verification could not be completed at this time. Please contact support."
I've tried my passport, my US work permit (EAD) and my state driver's license. All three refused within seconds, so it looks like an automated check, not a human one.
I opened a support case two days ago and only got the automatic acknowledgement so far. I also called.
Separately, I can't create a new Apple Account with my company email "Your account cannot be created at this time", on three devices and two networks, after the verification codes arrive.

Has anyone hit this? What actually unblocked it for you: waiting, a specific support channel, a different document, matching the account name to the ID exactly? Any timeline you saw would help.

For years I logged my body measurements in a paper notebook. Gym on and off, then running, then CrossFit, which is less a sport and more a subscription to soreness. Weight, biceps, shoulders, a page every few weeks. Every so often I'd think "I should put this in an app so I can actually look back at it," and then, being a developer, I didn't. For years. This year I finally did. It's called Physique.

The plan was the usual: a table of entries, add, edit, delete, settings. Plus one clever feature: photograph an old notebook page, have AI read it, review the parsed numbers on a bespoke import screen, save. I'd even started picturing the loading spinner.

Then it dawned on me that I was about to pour a lot of effort (and an alarming number of agent hours and tokens) into building a worse version of something I already use every day. ChatGPT, Claude and Grok read my handwriting better than I do, and I've known me for decades. What the app lacked wasn't a feature, it was a door. So I dropped the importer and built an MCP server and a CLI instead. The "import" is now: take a photo of the page, tell the assistant to put it in Physique, done. The entries just appear. Or skip the photo entirely and just say "log weight 82.4 kg" the way you'd talk to any agent. You can connect Claude, Claude Code, ChatGPT, Cursor, Codex, or any MCP client. The bespoke import screen remains the best feature I never built. And it isn't only about entering data: ask the agent to chart the last six months however you like, or export everything to CSV, a PDF, whatever you fancy. It's your data; do what you want with it.

Here's a 3-minute demo of it running from Claude, with the app open alongside: Physique + Claude demo on YouTube

That changed how I think about what an app is for.

I've noticed I barely edit anything myself anymore. In Notion I don't write documents; an agent writes them and I read. In Figma the agent moves the rectangles and I look at them and have opinions. And, slightly awkward to admit on this sub: I don't really write code in Xcode anymore either. Agents deliver the code, I review it in GitHub PRs, and I open Xcode now and then to press Build, like visiting an elderly relative. Its core purpose, for me at least, has quietly gone away.

So apps become the place you view the data, and agents become the thing you edit it with. That doesn't make apps less important; it changes which part matters. Physique's job is to show your numbers clearly: one dense table, every entry, the change since last time next to each value. You can still add and edit in the app, of course. I just don't think that's where the product lives anymore. Whether UI as we know it survives the next few years, I genuinely don't know. Curious if others are seeing the same shift in their own habits.

How it was built

Almost all of the code was written by agents, but I run it like a proper tech company where everyone except me is an agent: one-pager, PRD, design, tech plan, specs, tickets, then PRs reviewed by different agents from the ones that wrote them, with CI guardrails, and most of it merging itself. My job is the checkpoints: product calls, taste in Figma, approving the tech plan, manual testing, follow-up tweaks, and saying "no, that's not native" a lot. The iPad navigation went through three versions for exactly that reason. If anyone wants the gory details of the pipeline, say so, and I'll write it up properly.

The development in numbers, so far:

• roughly 150 hours of active agent work across ~300 agents (Claude Code, Cursor and a bit of Codex)
• around 4B tokens processed, of which only ~5M were actually written
• 813 commits, 157 merged PRs, 159 tickets
• at least 147 of 161 PRs written by agents (Claude Code 101, Cursor 44, Codex 2; Codex clearly needs to pull its weight)
• up to 6 agent PRs open at once, and 27 PRs opened on the busiest day. My review queue has not forgiven me.
• 6 releases before 1.0.0
• 4 design specs and 22 implementation plans
• 91 PRs with an agent code-review verdict before merge
• 5 GitHub Actions workflows plus Xcode Cloud for unit tests, snapshot tests for the UI
• 600+ xcodebuild runs (about 340 test runs and 270 builds across iPhone, iPad and Mac) and ~90 simulator launches by agents in just the last two weeks of logs. Xcode is busier than ever.
• about 26k lines of Swift across 245 files (86 of them tests), and roughly 60k lines of code in total with the backend, web app and CLI

The part that surprised me most was going multi-platform. Once the architecture, guardrails, CI, guidelines and agent docs were in place, adding platforms was almost boring. The iPad app, the native Mac app and a web app were planned and built as parallel work packages by agents, mostly autonomously, over a couple of nights, while I was in Poland on a long weekend, mostly devouring pierogi. Checking in on the PRs between plates turned out to be a perfectly workable engineering process. Then I spent a few evenings being insufferable about details until they felt native. iPad, Mac are out now with 1.0.0, alongside iPhone. The web app is at app.getphysique.app.

And Android? Skipped. Not because it's hard; with this setup it's probably a night's work to port. I just "love" Android so much that I'm saving it for later. Much later. It's a side project, so I'm allowed to be petty. I suspect this sub will cope.

Tech stack

The very short version: SwiftUI on iPhone, iPad and Mac, Firebase behind it, a plain JavaScript web app, and a hosted MCP server with OAuth, plus a CLI available on npm. Happy to go deeper on any part of it if people are interested.

Try it

Physique is free. No subscription, no ads, no streaks, no feed. If you track anything about your body, download it, connect your agent of choice and tell me honestly what you think, including the bits you'd have done differently. Claude has it in its connectors directory. ChatGPT's official directory is taking its time: it's been in their review for a couple of weeks now, so until then you add it as a custom MCP connection.

Physique: Body Measurements on the App Store

A question for you: when you give agents access to your own apps, do you build a separate agent API, or expose the same operations your UI uses? I went with "same operations, measurement data only" and I'm still not sure where the line should be.

Today I witnessed the real power of AI beyond just writing code. I am using it as a super marketer to drive up my app business, and the results are incredible.

This is what I have set up. I provided read access to the AI using their official APIs for:

• App Store Connect
• Apple Search Ads
• Meta Ads
• Firebase Analytics
• Local app source code

By combining the source code with real performance data, the AI ran a thorough analysis and suggested concrete, actionable items to improve my overall app business.

My main concern is whether this is allowed by Apple. Specifically, does Apple permit using AI agents to query App Store Connect and Apple Search Ads through their official APIs?

The setup is too powerful not to use, but we still need to abide by Apple rules. Has anyone else looked into this or tried a similar workflow?

spent way too long this week figuring out why I couldnt find the Duo in the simulator list. turns out 27.0 just doesnt have it, you need 27.1 which came out on the 15th. 27.1 also wants macOS 26.6 or newer fwiw
posting what worked in case it saves someone an hour before the 23rd.

get the runtime (didnt ask me to sign in with an apple id, which surprised me):

xcodebuild -downloadPlatform iOS
xcrun simctl list devices available | grep "iPhone Duo"

theres already an "iPhone Duo" device after that so you dont have to create one. then:

xcrun simctl boot "iPhone Duo"

open -a Simulator

for tests its just the destination. ran a small test package this way and it passed in about 19 sec incl booting the sim:

xcodebuild test -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone Duo,OS=27.1'

screenshot came out 1398x2034 for me with xcrun simctl io booted screenshot duo.png. havent checked yet if thats what app store connect wants so double check that. apple says duo screenshots are going to be required for every submission from april 2027 so might as well sort it now

for the poses/orientations apple points you to Device Hub, which is hiding inside Xcode.app/Contents/Applications/DeviceHub.app. took me a while to find lol

one weird thing: over ssh simctl bootstatus said "Data Migration Failed" but the sim booted fine anyway. when I ran it inside the actual logged in session it said Finished. so ignore that if you see it

full disclosure I run a small Mac mini rental thing (macrun.dev) and set this up on our machines, thats how I ran into all this. wrote it up longer here if useful https://macrun.dev/guides/iphone-duo-simulator but everything above works the same on your own mac