Hi, I was reading about this case study on the legacy IoT app optimization project that Beetroot consultants did for an established healthtech leader. The legacy codebase was riddled with critical bugs and the application suffered from serious performance bottlenecks and a confusing user experience that was tanking user engagement.

They created a dedicated team to address this under a flexible team extension model: 2 iOS developers, 2 Android developers, 1 QA automation engineer and 1 manual QA engineer with UI/UX design support. They ran into the classic dilemma: instead of choosing the expensive, risky rewrite from scratch, they took the hard way. They decided to refactor the legacy codebase to get rid of technical debt and squash the core bugs.

Crucially, they embedded deep product analytics tools like Firebase, Amplitude, and Smartlook directly into the new architecture. This let them track exactly how the app interacted with IoT medical hardware. For medical applications this deliberate refactoring approach is super interesting. What are your primary indicators for deciding whether to refactor the existing code or drop everything and start a full rewrite?

If, like me, you couldn't wait for less rounded corners and installed the MacOS beta on your only Mac, you might realize that you can't push updates to the app store. In this situation I would recommend the 25 free Xcode cloud hours that you get with the program membership. All I had to do was put my code in Git and connect the repo. Then I set it to archive for app store.

This might be the easiest CI/CD system I've ever used and the builds are pretty fast! Hats off to the Xcode cloud team.

Hey everyone,
I’m currently setting up a dedicated Mac server environment designed specifically for iOS developers who need cloud access to real Mac hardware for Xcode building, testing, or automated CI pipelines.
Before opening it up officially, I need a few active iOS devs to stress-test the remote access, latency, and hardware performance.
What I'm looking for:
3 to 5 developers building or testing iOS apps (especially those who don't have a secondary Mac, need remote build machines, or want to offload heavy compilation).
Devs willing to try using a remote Mac environment and give honest feedback on build speeds, remote desktop/SSH responsiveness, and overall setup experience.
What you get:
Free, full remote access to dedicated Mac hardware to run Xcode, test builds, or set up workflows (no credit card required).
Direct support from me to help configure the environment, setup remote tools, or tune performance for your project.
If you want free access to Mac hardware for your Xcode workflow, drop a comment or send a DM with what you're working on and your current build setup!

Aggregate data from 123 real App Store / Play listings scored by an ASO grader between May and July, in case it's useful for prioritizing your own store listing work:

• Titles: 81% of apps grade A or better. Median title uses 90% of available characters. If you're reading ASO advice about title optimization, you're reading advice everyone already follows.
• Descriptions: 90% grade A or better, median 2,418 characters.
• Localization: 94% grade D. 88% of apps have zero localized metadata. Median localization score 10/100 vs 100/100 for titles.
• About half of apps keyword-stuff descriptions, which is useless on iOS since Apple doesn't index the description field at all.
• No app in the sample scored above 81/100 overall (median 74).

The practical takeaway: adding localized metadata (title/subtitle/keywords per storefront, without translating the app itself) is statistically the least-crowded optimization left. Apple also indexes keywords from some extra localizations in the same storefront (e.g. en-GB + es-MX both count in US search), which most of that 88% are leaving on the table.

Caveat: self-selected sample (devs who checked their own score), so real-world numbers are likely worse than this.

Posted the SpeechAnalyzer vs Whisper benchmark here recently and a few of you asked about Parakeet V2/V3. Ran both through the same harness, plus MOSS-Transcribe-Diarize which someone on HN suggested. Same 5,559 LibriSpeech utterances, same normalizer and scorer as round 1.

Results (WER, clean / other):

• Parakeet TDT v2 int8: 2.01 / 3.40 (wins)
• MOSS: 2.07 / 4.68
• SpeechAnalyzer: 2.12 / 4.56
• Parakeet TDT v3 int8: 2.51 / 4.28
• Whisper Small: 3.74 / 7.95

The stuff that actually matters if you're picking an engine:

Integration was easy. Parakeet ran via FluidAudio (Swift package, CoreML, runs on the ANE). We already link it for diarization so adding it to the benchmark was maybe 50 lines. If you have an AVAudioPCMBuffer pipeline already it's an afternoon.

Budget for the quantization tax though. NVIDIA's published 1.69/3.19 is bf16 on GPU. The int8 CoreML port you'd ship scores 2.01/3.40. Still the most accurate thing you can run on-device, but a decent chunk of its paper lead over Apple's free engine evaporates once it's actually shippable.

v3 gives you 25 languages for a real English accuracy cost (2.51 vs 2.01 clean). Still beats Whisper Small everywhere though.

MOSS does transcription + diarization in one pass and the speaker labels were perfect in a small controlled test. But there's no Swift or CoreML path (Python/MLX only), it's 1.7GB with ~2.7GB RAM, and it can't stream. Not output-streaming, I mean it literally cannot start transcribing until it has the complete recording, so anything with live captions needs a second engine anyway. Also fun: audio where speech starts at exactly t=0 returns an empty transcript, deterministically. Prepend a second of silence and it's fine.

This benchmark got Whisper removed from our app btw. Parakeet v3 replaced it as the downloadable engine (beats Whisper Small everywhere at a similar size, 25 languages), and for English Auto still prefers SpeechAnalyzer: 0.11 points, zero bundle bytes, improves with the OS. The cost-benefit section of the article is probably the useful part if you're making this call yourself.

Article + raw per-utterance transcripts if you want to rescore: https://get-inscribe.com/blog/parakeet-moss-apple-speech-benchmark.html

Disclosure: I build Inscribe (ships the Apple engines + Parakeet, formerly Whisper), all engines ran through identical production code paths.

Please help me,

Apple IAP submission has bug lately on submission, it doesnt accept any device screenshot of IAP

When I put a symbol on the edge, iOS neatly rearranges the content to fit around it. How do I recreate this on the other side with my own content, without the complications of using frame where anything too small will cut off, anything to large will look stupid, and the ideal threshold is changing as different sized content replaces?

Pretty big news for bug testing apps: https://code.claude.com/docs/en/desktop-ios-simulator

How does the community feel about this potentially opening the door to even more AI slop in the app store?

I've built the engine for a paint-by-number iOS app but I can't work out where the hundreds of competing apps source thousands of flat vector images. Is there an actual B2B licensing vendor for this, or is everyone doing in-house art teams / AI generation / cloning each other?

They released this new Xcode build yesterday and I just can't get anything to upload with it. I uploaded with builds 1 through 3 just fine.

Hey everyone,

I'm building a fitness app focused on handstand training, and I'm trying to figure out the best way to handle my in-app icons.

Right now I'm using SF Symbols, which works fine and keeps everything looking native on iOS. But it feels a bit generic, and there simply aren't symbols that match what I actually need.
What I'm really after are custom icons tailored to my use case: a coherent set representing different handstand poses and variations (tuck, straddle, one-arm, press to handstand, etc.).

The tricky part is consistency. I don't just need one nice icon, I need a whole family of them that share the same visual language: same line weight, same style, same proportions, so they look like they belong together in the app.

A few questions, as a solo dev working on a side project, for those who've been through this:

• How do you usually generate a consistent icon set like this? Hand-drawn, AI tools, a designer, a mix?
  • I saw people talking about Flaticon.com and noun project.
• Any tools or workflows you'd recommend for keeping a uniform style across many icons?
  • I was thinking asking Claude or ChatGPT to generate specific Symbols matching the SF Symbols, haven't tried it yet.
• Any tips specifically for figurative / pose-based icons?

Would love to hear how you've approached this. 
Thanks!

I am currently working on a HID device that needs to work with iPads.

Is there any way I can send data from the iPad to the HID device without going through the MFI program?

Pretty much any kind of data will do. All I need is something to send to my HID device so I can trigger a few LEDs on my HID device.

I would need to be able to distinguish between 3 different signals.

Is this possible on IOS?

(*Apple OS = iOS, iPadOS, watchOS, tvOS, visionOS, macOS)

Axiom is a battle-tested, batteries-included suite of agents, skills, and tools for AI coding. It helps LLMs be notably better at Apple OS development.

I've been updating Axiom in lockstep with Apple OS 27 betas. Here are some of the interesting changes with OS 27 beta 4.

✅ New

• Swift — Parenthesis-free optional any/some types. var x: any P? and some P? now compile. (Beta 3 rejected the paren-free form.)

• HealthKit — HKHealthStore.earliestAuthorizedSampleDate(for:): New async throws call returning the earliest date you're authorized to read, per HKObjectType. This is helpful for bounding a query instead of paging into data you can't see.

• UIKit + SwiftUI — systemPrefersReducedResourceUsage: The OS can now tell your app it prefers reduced resource usage. When it's true, stop discretionary work.

🗑️ Removed

• AVKit — The AVInterface* family, which shipped in an early 27 beta, is gone. Use AVPlaybackUserInterface* instead.

⚠️ Deprecated

• ARKit — unprojectPoint(_:ontoPlane:orientation:viewportSize:). Use unprojectPoint(_:ontoPlane:viewRotationAngle:viewportSize:) instead.

• AppIntents — DisplayRepresentation.Components (OptionSet). Use DisplayRepresentation(title:subtitle:image:) or displayRepresentations(for:) instead.

• BrowserEngineKit — MediaEnvironment.activate()/.suspend(). Use ProcessCapability.activate()/.suspend() instead.

Caveats: This list is mostly Swift-focused, although I've been supporting more Obj-C with every release.

I built an open-source tool called tapflow.

On our team, checking app builds kept running into the same problem. Maintaining physical devices across multiple iOS versions became a burden, and iOS simulators could only be used by people with Xcode installed. So whenever a designer, PM, or backend engineer wanted to check a build—a layout, a flow, or what a staging build did with their API change—a mobile engineer usually had to help them. This happened several times a day.

I wanted an easier way for the rest of the team to check app builds.

It streams an iOS simulator to the browser over H.264, running on a Mac you already own. Anyone with the URL can tap, type, and scroll on the simulator. There's nothing to install on their side, and touch input goes straight through the HID layer, so there's no WebDriverAgent to set up.

A few details:

• The agent only makes outbound connections to a relay, so there are no firewall or NAT rules to configure. Builds and streams stay on your own network since it's fully self-hosted.
• It also drives Android emulators, but I'll keep this post focused on iOS.
• It uses simulators rather than physical devices, so camera, biometrics, and NFC aren't supported.
• It's still v0.x, so expect a few rough edges.

Repo (MIT): https://github.com/jo-duchan/tapflow

Docs: https://tapflow.dev

How does your team let non-developers try an iOS build without the full toolchain? I'm curious whether you've built something similar or use another tool.

Small two person studio. We just added GameKit to our multiplayer word game: achievements mirrored from our own trophy system, an ELO leaderboard, and friend discovery via GKLocalPlayer.loadFriends. Its in TestFlight now, ships with our next release.

What I could not find anywhere while building it: does any of this measurably matter?

• has anyone seen GC integration move installs at all? The old "supports Game Center" App Store surface seems basically gone.

• do achievements or leaderboards show up in your retention numbers, or are they cosmetic?

• friend discovery via loadFriends: the iOS consent sheet feels intimidating. What share of your users actually grant friend list access?

• anything you shipped and later wished you had skipped?

Our hypothesis is that the friend graph part is the only piece that really matters (our own cohort data says one match against a friend roughly 5x'es D60 retention), and achievements/leaderboards are mostly polish. Happy to come back and share our before/after numbers once its live, if people are interested.

I want to install GG beta but I’m worried about the app submission sitch since this is my only Mac. Can I still build and submit iOS apps and Mac apps from Xcode 26 while running it?

Author here. The part that surprised us: we shipped the CoreML execution provider assuming Apple-silicon acceleration beats CPU, and benchmarking for this writeup showed plain CPU runs our int8-quantized graph 2.4x faster per inference and creates sessions ~20x faster, so we flipped the default. Also covers doing zero-shot CLIP classification with no text encoder on the device (prompt vectors precomputed and committed as JS) and the memory mistake that pinned 994 MB. Happy to answer questions about onnxruntime-react-native specifics.

I’ve made a small command line tool called simslim.

It disables background services inside iOS simulators that usually are not needed during development, like Siri, Spotlight indexing, photo analysis, News, and iCloud sync.

On my M1 Pro with 16 GB of RAM, one simulator went from around 4 GB of memory and 258 processes to about 0.9 GB and 70 processes. I managed to run 19 simulators at once, compared to around 5 before things started falling apart.

Some simulator features stop working depending on what gets disabled, so it is not meant for every kind of testing. You can keep specific services running when needed.

Give it a try: https://github.com/MobAI-App/simslim

When I run a dev build on a physical device, it always happens via Network (wifi), even when plugged in via USB. This sucks so hard. The whole experience is laggy and slow and completely unusable. I cannot identify any app hangs, because everything hangs all the time.

Does anyone know of a way to disable this? I just want to connect via USB when I plug the phone in and wireless when it's not plugged in.

I sometimes have the feeling Apple hates us developers and builds really bad tools just out of spite. It just makes no sense to release something like this. Sorry for the rant...

I made a tool/system for helping to get more useful feedback for users, helped me to solve some clear needs in my app. Right now it’s mainly geared towards iOS apps (iOS SDK and App Store integration). Looking for more people to test it out! If you have an iOS app with a decent number of users, and want to understand their needs better, would love to chat!

I built a Safari extension that reads the offers page on bank sites (those "add to card" cash back deals) so the app can activate them for you. I figured it'd be a weekend of querySelector. It's been months of warfare.

Highlights:

- querySelectorAll returns nothing. Chase renders the whole offers hub in web components with shadow roots. You have to walk the document, collect every open shadowRoot recursively, and run your selectors across all of them.

- The list is virtualized. 150+ offers, but only the visible tiles exist in the DOM. Scroll-scrape-merge as you go, dedupe across viewports, or you'll capture 2 of 165 and feel great about it.

- A bare .click() does nothing. SPA tiles want the full pointer ceremony — pointerdown, mousedown, pointerup, mouseup, click — dispatched in order.

- "Back" isn't back. After activating an offer you're on a detail page. history.back() is ignored half the time. You hunt for the on-page back control — and then discover a "Back to top" scroll anchor matches your finder and eats a second per offer.

- The page name lies. The all-offers page doesn't name which card it belongs to anywhere in the DOM. The fix that finally stuck: read the account id from the URL and remember the pairing the first time any named page reveals it.

None of this is documented anywhere, obviously. Every fix came from device traces of real runs.
Anyone else maintaining scrapers pointed at hostile SPAs? What's the worst DOM you've fought?

I was struggling to find a good way to create App Store screenshots for my apps.

I tried a few AI skills that generated websites for composing the screenshots, but the workflow felt inefficient and the editing options were limited. I wanted a proper native editor where I could quickly import simulator captures, make visual adjustments, and export everything in the correct App Store sizes.

So I built Screenshot Studio, a native macOS app that lets you:

- Import iPhone and iPad simulator screenshots

- Add device frames, headlines, subtitles, and backgrounds

- Move and scale elements directly on the canvas

- Preview both iPhone and iPad layouts

- Export at Apple’s required pixel sizes

- Upload directly to App Store Connect

- Reuse your designs when updating screenshots for a new release

It also includes an agent skill that can help automate the workflow, from capturing screenshots with UI tests to preparing and uploading the final gallery.

The app is completely free, with no ads, subscriptions, paywalls, or locked features.

You can get it here:

https://github.com/rafabertholdo/screenshot-studio

It requires macOS 14 or newer. I’d love to hear your feedback, especially from developers who regularly maintain screenshots for multiple apps.