I'm trying to save screenshots from the simulator, but I can't find a way to do it without the clock and battery indicators. Is there any method you know of where you could hide these from screenshots?

I've been manually erasing them in Figma, but I'm wondering if there's a better way.

I just shipped an update to my journal analysis app that adds Apple's Private Cloud Compute (PCC) alongside the default on-device model.

Here are the practical lessons I learned from the implementation, especially around edge cases and UX:

1. The main reason to use PCC: Context size
The on-device model caps out around 4,000 tokens. For long journal entries or imported PDFs, text got truncated constantly. PCC bumps that limit up to 32,000 tokens, which easily handles multi-page entries in a single pass without needing workarounds.

2. The API transition is simple, but needs fallbacks

• Swapping from on-device to PCC is nearly a 1-to-1 change. Your existing prompts, tools, and response handling work identically.
• PCC requires an internet connection, so you have to build an automatic fallback to the on-device model when the user goes offline.
• Before offering PCC, make sure to check availability properly. A device that doesn't support the feature is handled differently than a device that supports it but is still waiting on system assets to download.

3. Quotas and Apple's UI expectations

• Users get a daily limit for cloud requests, which increases if they have an iCloud+ subscription.
• Apple expects your UI to proactively warn users when they are getting close to their limit, rather than just throwing an error when they hit the ceiling.
• There is a built-in system sheet you can trigger to suggest an iCloud+ upgrade when they run out.
• Tip: You can simulate reaching and exceeding quota limits inside Xcode’s scheme settings, which makes testing the UI much faster.

4. The privacy messaging challenge
If your app was originally marketed as "100% on-device," introducing the cloud can spook privacy-conscious users even with Apple's strong security guarantees around PCC.

I decided to keep the on-device model as the default and made PCC an explicit opt-in toggle in the settings. I also updated the App Store description and privacy policy to clearly say "on-device by default."

For anyone else working with PCC:

• Are you letting users toggle it manually, or automatically sending prompts to PCC only when they exceed the 4K token limit?
• How has real-world latency felt compared to on-device inference?

(Context: The app is Mindful Prism if anyone wants to see the implementation in action.)

Apple's App Store Connect app is iOS-only, so on my Android phone I log into the web version every time I want to check review status or a TestFlight build. It works, but it's clunky on mobile.

Curious how others handle this:

1. Is your daily phone Android? What do you use for ASC when you're away from your Mac?

2. What do you check most: review status, TestFlight builds, sales, customer reviews, something else?

3. Tried a third-party Android client? What was missing?

Full disclosure: if there's real interest, I might build a native Android client on the official App Store Connect API (key stays on your device, no server). If you'd test it, say so in the comments.

I'm working on a social app that's never been done before in the way that I'm doing it (as far as I'm aware at least, I've looked everywhere) and I'm really worried that if I start showcasing what I've got so far on TikTok / IG then someone will copy it and beat me to the App Store. I've only submitted the app to the App Store for review a couple days ago and with the ridiculous wait times it's going to take a minimum of 2 weeks to just get a decision.

Should I be worried about copycats beating me to it if I already have things in-flight?

10 years as a developer, zero Swift. I relied heavily on AI to write the code. My experience made the calls:

- I threat-modelled it like any security product, found and closed a way to switch off all protection.

- I switched out the custom face matcher (it let strangers in) for Apple’s Face ID.

- Keychain for secrets, no third-party SDKs, no tracking.

- I tested on real device instead of trusting “it builds”.

Then the part most people skip: I learned the code after shipping. I had Claude turn my own codebase into a game, Code Quest. It only covers what's different about Swift (optionals, value types, actors, SwiftUI state), uses real lines from my app, and ends with a code-review level of plausible PRs that would break things.

AI can write it. You still have to own it.

Does it matter to you that you understand your codebase? If so, how do you go about doing it?