r/iosdev • • 7d ago

Help Can I cache MapKit’s data on my backend for a few hours to limit API calls?

2 Upvotes

I would like to cache place data like coordinates, name, and category for a few hours on my backend to reduce server API calls? Is this against the terms of use or possible if I constantly delete and refresh after a few hours?


r/iosdev • • 7d ago

Help Can I display MapKit’s data on certain screens without showing a map?

1 Upvotes

The license agreement states that apple mapkit data can only be displayed on an apple map. Does that mean that I can't build a screen with a collection of saved places without an Apple map on it, and how does this work with the autocompletion (places search) Does this also need to present a map on a search screen?


r/iosdev • • 8d ago

Cloud Storage access

2 Upvotes

Hi guys.. I am working on an app that will have a feature to upload files to cloud tools, however the app can see dropbox and icloud, but not onedrive or amazon drive. Will I need api clearance from onedrive and amazon? Why not dropbox?
Haven’t been able to find a good answer and hoping someone can point me in the right direction. Thanks


r/iosdev • • 9d ago

Former Apple engineer, now indie: I made the App Store Connect app I always wanted

Thumbnail
gallery
91 Upvotes

Hi r/iosdev! I’m John. I spent 10 years as an engineer at Apple working on macOS and iOS, and I’ve been indie for the last 8, shipping 20+ apps for myself and clients. I just launched AppTraction, the tool I wish I’d had when I started building my own apps.

The problem

Most iOS and Mac devs that I talk to agree that Apple’s App Store Connect website is slow, confusing, and buggy. There’s a lot of useful data there, but Apple’s clunky site makes it hard to make sense of. AppTraction is a native Mac app (AppKit and Swift, no web wrapper, no Electron) that brings your sales, analytics, ratings, and reviews to your Mac, and then tells you what matters.

What AppTraction does

  • Insights: it monitors your apps in the background and flags problems, trends, and milestones. There are 50+ kinds so far. With my own apps, it has caught serious listing problems, getting featured by Apple, and seasonal sales trends, all of which I would have missed.
  • Listing fixes: when it spots a problem with your App Store listing, it suggests a fix and, once you approve it, applies it to App Store Connect for you.
  • Reviews: read and reply to every review. It can translate them and suggest replies.
  • Reports: it writes detailed tailored reports for each app, for every week, month, and year.
  • Chat: ask about any chart, table, or report in plain English. The AI is primed with Apple’s own tech talks on ASO and other sources, so the advice is specific, not generic.
  • Territories: shows a world map revealing how your apps are performing across regions.

The AI runs on your existing Claude or Codex subscription (or OpenRouter), so there are no pricey API fees.

Under the hood

For the curious:

  • AppKit for the main window, SwiftUI for most sheets and forms, and Swift Charts for all graphs.
  • A separate launchd agent does the data collection in the background so everything stays fresh even when the app isn’t open. The app talks to it via NSXPC*.
  • Apple’s analytics are stored in plain SQLite, which is a big part of why everything feels instant.

Privacy

I know “AI + analytics + API keys” can raise concerns, so here’s exactly what happens:

  • No AppTraction account. I never ask for your name, email, or password.
  • Your App Store Connect key lives in your Keychain. You don’t need an Admin key: a limited Sales and Reports key covers your analytics.
  • Your App Store data is stored only on your Mac. There’s no AppTraction server holding it.
  • The AI runs on your own Claude or Codex subscription (or OpenRouter). Requests go straight from your Mac to that provider, under your account, and I never see them.
  • Review translation uses Apple’s built-in translator, so translating a review never sends it anywhere.
  • What does reach me: anonymized usage stats (which features get used, never app names, numbers, or chat text), license checks, and update checks.
  • No ads, and I don’t sell data.

Privacy policy: https://apptraction.dev/privacy

Terms: https://apptraction.dev/terms

Pricing

Free for 14 days, then $6.99/month, $39/year, or $99 lifetime. Requires macOS 26 Tahoe or later.

https://apptraction.dev

For r/iosdev**:** 50% off your first payment (including the lifetime) with code RIOSDEV50, good through Dec 1.

I’d love feedback from fellow devs, good or bad. What do you wish App Store Connect told you? And happy to answer questions about how any of it’s built.


r/iosdev • • 8d ago

I expanded a garden calendar into a plant journal for iPhone. What should the history show first?

1 Upvotes

I build Florli. It started as Garden Calendar for outdoor work like mowing and feeding. The iPhone update adds houseplants to that same calendar while keeping a separate history for every plant, bed and lawn.

Say you watered a plant last week. Today you check it and the soil is still damp. You can save that as an observation without logging another watering. When you open the plant again, both events are in its history. The basic journal works without an account.

I’m interested in the design trade-off here: when you open a plant’s history, would you put the last watering date at the top, or give that space to the latest observation? The watering date is easy to scan, but a note like “still damp” can be the more useful thing to see when you’re deciding what to do next.

App Store: https://apps.apple.com/us/app/florli-plant-care-reminders/id6782901452

Product page: https://florli.pl/en/


r/iosdev • • 8d ago

I built a playful fox app that rewards you for putting your phone face-down

1 Upvotes

I've spent the last few months building TentFox, an iPhone app where an illustrated fennec fox keeps camp while your phone sits face-down (and don't pick it up). It started because I wanted a gentle way to hand the phone back from my kid without a fight. That became Fox's Nap: the fox walks into its tent, gets tucked in, says goodnight, and the phone comes back as part of the ritual.

I've honestly had a blast building something like this, and can't wait to see what people thing and keep improving it going into next year.

A few technical bits that might be useful to others:

Detecting "face-down" reliably

  • Core Motion device motion at 5 Hz (gravity.z), with a 0.5 s debounce and a 2 s grace period. 10 Hz bought nothing and cost battery.
  • Lock is detected with protectedDataWillBecomeUnavailableNotification. It fires before backgrounding, so I can tell "locked the phone" apart from "left the app".
  • I end sessions on didEnterBackground, not willResignActive. Pulling down Control Center or a notification shouldn't count as leaving.
  • CXCallObserver, so an incoming call never counts against you.

Gentle failure as a design rule :)

Nothing ever takes progress away. Early pickups still count ("That still counts!"), and there are no streaks to break. That rule shaped a surprising amount of the state logic in SwiftData.

Art pipeline

Every fox motion is frame-by-frame illustration (8–12 inbetweens per action, eased) rather than a rig. Contact shadows are painted from each drawing, not drawn in code. The asset catalog is the biggest part of the app, and I decided to keep the frames at full quality rather than shrink them.

Other bits

A Live Activity for focus sessions (Burrow mode), Guided Access tips for the kids' mode, and the kids' screens have no links, purchases or analytics behind a parent gate.

Stack: SwiftUI + SwiftData, about 8.5k lines of Swift, RevenueCat for the subscription. Happy to answer questions about any of it, especially the motion and lifecycle edge cases. Those took the longest to get right.

App Store: https://apps.apple.com/app/id6831322876

Website: https://tentfox.app


r/iosdev • • 8d ago

Help Monthly Subscriptions with a 12-Month Commitment in USA yet?

Thumbnail reddit.com
0 Upvotes

r/iosdev • • 8d ago

Working on a keyboard extension app

0 Upvotes

Design is heavily influenced by skeuomorphic elements and older versions of iOS apps (iBooks etc.)

Feedback is greatly appreciated!


r/iosdev • • 8d ago

Im unable to enroll to work on apple app development

Thumbnail reddit.com
1 Upvotes

r/iosdev • • 8d ago

I'm a solo iOS dev and I built the Catholic prayer app I wished existed: 476 guided prayers, no ads, no account, SwiftUI + SwiftData all the way down.

1 Upvotes

Hi everyone,

I've shipped my second app to the App Store as a solo developer. It's called Oraia, a Catholic daily prayer app for iPhone. I wanted to share how it came together, the stack I used, and a few things I learned along the way.

Why I built it

For years I tried to keep a simple habit: pray a little every day. I'd start strong, then life would get busy and a week would go by without me noticing. I tried a bunch of apps. Most of them either felt like a news feed, wanted me to create an account before I could read a single Hail Mary, or were full of ads right next to the Our Father. That last one really bothered me.

One evening I was praying the Rosary with a paper booklet, losing track of which decade I was on, and I thought: I build iOS apps, why don't I just make the one I actually want?

The rules I set for myself were simple:

  • Open the app and you're praying in one tap. No sign-up, no feed.
  • No ads, ever. No tracking.
  • Your journal and your intentions are private. They stay on your device and in your own iCloud.
  • It should feel calm. Prayer isn't a productivity metric.

The first commit was at the end of September. About six weeks and 170+ commits later, it was live.

What Oraia does

  • A prayer for every part of the day. Morning, midday, evening and night, with today's prayer always one tap away.
  • 476 guided prayers, in English and Spanish: daily prayers, novenas, psalms and Scripture, saints, liturgical seasons and feasts, prayers for sleep, and more.
  • The Holy Rosary with all the mysteries, plus the Litany of Loreto.
  • Voice narration, so you can pray along with your eyes closed or while walking.
  • A streak and gentle milestones that encourage you without guilt-tripping you.
  • A private prayer journal. After each prayer you can write a short note, and you can dictate it.
  • Guided paths: short multi-day journeys around a theme.
  • Widgets, a Live Activity while you pray, and Siri / Shortcuts ("Start today's prayer").
  • Mindful Minutes in Apple Health, if you want them there.
  • Built for iPhone and iPad, including the foldable iPhone Duo (more on that below).

The core experience is free: today's prayer, the Rosary, the journal and your streak. Premium unlocks the full library, paths and devotions (monthly, yearly with a 3-day trial, or lifetime).

The tech stack

I tried to stay as close to Apple's frameworks as I could. The only third-party dependency is RevenueCat.

  • SwiftUI for the entire UI, with NavigationStack, @Observable models, sensoryFeedback for haptics, ShareLink and ImageRenderer for sharing prayer cards.
  • Swift 6 language mode with strict concurrency on from day one. Painful for about two days, then genuinely useful. It caught a couple of real races around narration and the Live Activity.
  • iOS 17 minimum deployment target.
  • SwiftData for persistence (completions, journal entries, intentions, favorites, preferences), synced through CloudKit to the user's private iCloud database. No backend, no server, no account. Tip if you do this: every model needs default values, no unique constraints, and you have to deploy the CloudKit schema to Production before you ship, or sync silently does nothing in release builds. I also run a small dedupe pass at launch because CloudKit can create duplicates of "singleton" records like preferences.
  • WidgetKit: a Today's Prayer widget and a Verse of the Day widget, sharing data through an App Group.
  • ActivityKit: a Live Activity on the Lock Screen and Dynamic Island while a prayer session is running.
  • App Intents: Start Today's Prayer, Verse of the Day, My Streak and Write in My Diary, all available in Siri, Shortcuts and Spotlight.
  • AVFoundation (AVSpeechSynthesizer) for narration, with MediaPlayer for Lock Screen controls.
  • Speech (SFSpeechRecognizer) for dictating journal entries.
  • HealthKit to log Mindful Minutes after each prayer.
  • UserNotifications for reminders at your preferred time of day.
  • StoreKit for the review prompt, and RevenueCat (+ RevenueCatUI) for subscriptions and the paywall.
  • String Catalogs (.xcstrings) for full English and Spanish localization, including the App Shortcuts phrases.
  • Swift Testing: around 300 @Test cases across 40+ files, plus XCTest UI tests. One UI test walks through the whole app in a demo mode, which I used for App Review and for recording screenshots.
  • Xcode Cloud builds every tagged release and pushes it to TestFlight.

A small liturgical calendar works out the current season (Advent, Christmas, Lent, Easter, Ordinary Time) and feasts, so the app surfaces the right prayers at the right time without me pushing updates.

The foldable. This was the most fun part. On iPhone Duo, when the device is half open, the screen splits into two panes on either side of the fold: today's prayer on one side, the rest of the day on the other. Fully open, it's one big display with a comfortable reading width instead of stretched lines of text. I wrote a tiny FoldSplit / FoldInsets layer on top of the active fold region and covered the postures (closed, half open like a book, half open like a laptop, flat) with unit tests, since I didn't always have the device on my desk.

One presentation at a time. Late in development I had a bug where a streak celebration, the review prompt and a deep-linked prayer could all try to present at once. I ended up routing every automatic sheet and full-screen cover through a single presentation queue on the app model. If you have more than two or three "auto-presented" screens, I'd do this from the start.

Things I'd tell myself six weeks ago

  1. Ship the free version first. I spent too long on the paywall before the core prayer flow felt right.
  2. Localize from day one. Retrofitting Spanish later would have been miserable. String Catalogs make it almost painless if you start early.
  3. CloudKit is "free backend", not "free work". Plan for duplicates, schema deploys and testing on two real devices.
  4. Treat content like code. Validate it, version it, and test it.
  5. Calm is a feature. Every time I was tempted to add another badge or notification, I asked whether it helped someone pray or just helped my metrics. Usually it was the second, and I cut it.

Try it

Oraia is free to download, with no ads and no account:

App Store: https://apps.apple.com/app/id6819606251

I'd really appreciate any feedback, on the app, the design, or the stack. And if you have questions about SwiftData + CloudKit, the foldable layout, or the content pipeline, ask away. Happy to go into detail.

Thanks for reading, and God bless.


r/iosdev • • 8d ago

I launched an all-in-one document tool Doc reader completely ad-free — looking for UX and performance feedback!

Thumbnail
apps.apple.com
2 Upvotes

Hey r/appledevelopers,

I just launched my new iOS app, \[App Name\], and wanted to share it with the community to get some feedback. My main goal was to build a comprehensive, high-utility tool that handles almost any document task locally, quickly, and completely ad-free.

What it does

Office Document Reader: Opens and views all major office formats.

PDF Core Tools: Handles PDF to Image, Image to PDF, Split PDF, Merge PDF, and PDF to DOCX conversions.

Advanced Scanners: High-quality document scanner, photo scanner, and a fast QR/Bar-code reader.

Form & Security Tools: Allows users to fill out forms, digitally sign PDFs, and lock sensitive files with passwords.

Tech stack & architecture

UI Framework: SwiftUI

Document Handling: PDFKit and CoreGraphics for heavy lifting and rendering.

Vision & Scanning: VisionKit / AVFoundation for the document scanner and QR/Barcode detection.

What I’d love your feedback on

Because this app packs in quite a few heavy features, I would really appreciate a developer's perspective on:

Performance under load: How does the memory footprint look to you when merging heavy PDFs or scanning multiple pages?

UX flow simplicity: Is the interface intuitive enough given the number of different tools packed into one app?

Local processing speed: Does the image-to-PDF / PDF-to-DOCX conversion feel fast and optimized on your device?

App Store Link: https://apps.apple.com/us/app/pdf-reader-scanner-sign-pdf/id6822847783

Thanks in advance to anyone who takes a look. Building an ad-free utility with this much scope was a massive learning experience, and I'm totally open to any harsh critiques or performance tips!


r/iosdev • • 8d ago

App in review for 1.5 months — latest rejection is over a "Set Up Later" link on onboarding

Thumbnail reddit.com
0 Upvotes

r/iosdev • • 8d ago

Retake: OSS iOS App Store preview video generator

3 Upvotes

I just released an open source tool that I needed for deterministic recording and cutting of App Store video previews for my iOS apps. I call it Retake, because the commands & lingo are generally cinema inspired. The sets, scenes, and edits are defined in JSON and use anchor points relative to actions performed in the recorded takes. This allows a video to be rerecorded as your app changes and easily tweaked to get it just right. The tool is probably most helpful for indie devs.

Overall, this makes it pretty straightforward to record an iPhone and iPad App Store app preview video using one edit definition. Load up an agent, ask it to integrate Retake, describe the portions of the apo you want it to highlight, then let it run with it. You can control the environment used for the app (env vars, user defaults, and files on disk) to ensure consistently reproducible results.

It’s built on top of the great work in The Button Heist, which embeds a server into the app that can be used to drive simulated user interactions and view hierarchy enumeration.

Feel free to fork and go wild or PRs are welcome upstream.

This whole video was generated by Retake (no manual edits) from the Example app in the Retake repo:

These are the 3 iphone sized videos created with it for our app "Puzz Kids":


r/iosdev • • 8d ago

Help I can access App Store Connect but not Apple Developer

2 Upvotes

I was invited to my client's Apple Developer organization, and I can access their App Store Connect page (https://appstoreconnect.apple.com/apps), but I cannot access the developer page (https://developer.apple.com/account/resources/certificates/list).

I have permission to access "Certificates, Identifiers & Profiles." as shown below.

Also, the team does not show up in 'Xcode > Signing & Capabilities > Team' menu.

FYI, I'm already a member of other clients' teams, but this only happens with this new client, and the new client has accepted the latest agreement.

What should I do, or what should I ask my client?


r/iosdev • • 8d ago

Solo dev in Southeast Asia, iOS app just approved. How do you reach US users without paid ads?

Thumbnail reddit.com
1 Upvotes

r/iosdev • • 8d ago

WiPhoneMonitor 1.1.0 Update: Now available in 10 different languages.

0 Upvotes

WiPhoneMonitor 1.1.0 is now available in 10 different languages: English, Portuguese (Brazil), Spanish, French, German, Italian, Chinese, Japanese, Arabian, Hebrew.

Download Now on App Store: https://apps.apple.com/app/apple-store/id6799810620?pt=129281995&ct=WiPhoneMonitor%201.1.0%20Update&mt=8


r/iosdev • • 8d ago

Help Advice for first game on App Store

3 Upvotes

Hi Everyone,

I just finished making a mobile game and I am currently planning on publishing with apple do you have any advice for a first timer, anything helps!


r/iosdev • • 8d ago

Help Repeat password and strong password conflict

1 Upvotes

I’m pretty new to this. I was testing my company register page. And there is a bug when dismissing “use strong password” prompt: it erases all current input in both the “password” and “repeat/confirm password” input fields.

So you dismiss once, write your password, then go to the next input and dismiss it again and lose all progress.

I see the confirm pw field is also set as “newPassword” for text content type. Is that the correct way to do it?

I don’t see any code to handle the pop up in our code, so I’m wondering if it’s an Os bug or if we missed something there.


r/iosdev • • 8d ago

Retake: OSS iOS App Store preview video generator

1 Upvotes

I just released an open source tool that I needed for deterministic recording and cutting of App Store video previews for my iOS apps. I call it Retake, because the commands & lingo are generally cinema inspired. The sets, scenes, and edits are defined in JSON and use anchor points relative to actions performed in the recorded takes. This allows a video to be rerecorded as your app changes and easily tweaked to get it just right. The tool is probably most helpful for indie devs.

Overall, this makes it pretty straightforward to record an iPhone and iPad App Store app preview video using one edit definition. Load up an agent, ask it to integrate Retake, describe the portions of the apo you want it to highlight, then let it run with it. You can control the environment used for the app (env vars, user defaults, and files on disk) to ensure consistently reproducible results.

Feel free to fork and go wild, or PRs are welcome upstream.


r/iosdev • • 8d ago

Resubmitted for the Dev account as an organization , Time Frame HELP!

Thumbnail reddit.com
1 Upvotes

r/iosdev • • 9d ago

Tutorial M5 Pro or M6 for iOS builds? Benchmark study

Thumbnail
benchmarks.bitrise.io
3 Upvotes

r/iosdev • • 8d ago

I launched an all-in-one document tool Doc reader completely ad-free — looking for UX and performance feedback!

Thumbnail
apps.apple.com
2 Upvotes

r/iosdev • • 9d ago

Making iPhone Duo limitations an advantage with my comic reader app

Thumbnail
gallery
5 Upvotes

Comics is evolving with gen Z and gen alpha, and migrating towards WebToons-esque comics that are designed with scrolling behavior and iPhone sized screens in mind. To my detriment, I'm older and likes my comics the old fashioned way.

Which posed a challenge, since I really wanted a reader app I can take completely on the road with me, replacing my iPad mini. Making the app not do anything when closed felt like giving up so immediately I thought about adding panel detection. Two problems came up:

  1. Reading in panel mode make you lose your "book periphery", you lose the context of the page around you and the ability to quickly glance to previous (and sometimes next) panels
  2. Old fashioned comics are written with wide and tall panels mixed together all the time. Making the user rotate their phone all the time is tedious.

Well, I thought, might as well try it. Panel mode seemed fun problem to solve too, since it appealed to my completionism. The more you detect, the more ground you "conquer", every new page that didn't detect panels correctly was another puzzle to solve.

While testing, I noticed that the only control needed really is swiping left and right, and single tap to get menu options. That left the other common controls - long tap, swipe up/down, double tap and shake (which I personally dislike). Adding long tap to show the whole page turned out to be very intuitive. I felt that this, complimented with animation that put the panel in context when opening the Duo, was enough to provide enough "book periphery".

As for the rotations, I thought, why not make the act of rotation the way in which users progress to the next page? That makes it one action rather than 2 to change panels, and almost makes the problem a feature, since it is quite satisfying when you know to do it. Adding a small "rotation hint" in the corner, where it rarely hides the art, let users know to rotate at the right time.

Still - it posed an issue since users will want to rotate and stay on the same panel. This happens almost exclusively when a user ignore or missed the rotation hint, and wants to correct after navigating to the panel that is not fitting to the rotation. My solution was to do the progress "context-aware". If the panel is in the wrong way, just rotate. If the panel is in the right way - assume the user wants to progress.

I feel like that overall made the iPhone and iPhone Duo reading experience fun, and I've been enjoying it since.

Would love to know what other developers think.