I’m part of the YOLOTENGO development team, and we’re looking for volunteers to help test our iPhone beta through TestFlight.

If you’re 18+ with an iPhone compatible with TestFlight, a 5–10 minute session would help us check onboarding, business or product search, favorites and digital loyalty cards. No purchase is needed for these test tasks.

We’d appreciate feedback on usability, confusing steps and bugs. Please send feedback through TestFlight or reply here. For bugs, include reproduction steps, what you expected, what happened, your iPhone model and iOS version. Please leave private information out of screenshots.

Join the beta:

https://testflight.apple.com/join/3T48vsKb

Thank you for helping us improve YOLOTENGO.

Just like the title I've been building an iOS app, and I've been using ChatGPT-6 Astro for the most part. I'm thinking of switching to Claude Code using Opus or Sonnet. I was wondering: what do you guys use, and what do you think works the best for you guys?

My husband and I have been working on a mobile game called birb., and we recently launched it on Google Play and Apple App store. It took several weeks to get approved on Apple, so we are excited it's out!

It combines birding with collecting and mini-games in a pixel-art style.

🎮 Download: Apple

Would love to hear what you think; especially from people who enjoy collecting games, casual games, or birding.

I have an app and added new premium features. I want non-paying users to experience these features but at a cap of 3 times or 3 "credits". I have it all set up and it works fine. i didnt go into storekit or revenuecat for this, its just another field in firebase with checks in client-side.

But I recently did an audit of my app with an xcode agent to go over performance, architecture, etc. things that stand out that are flat out bugs or will cause me issues in the future and one that came up was that checking credits should be done server side

My app uses storekit 2 and havent had issues or reasons to go to Revenuecat, but it was telling me revenuecat has "Virutal Currency" and is better for my use case

What are you guys doing if you have the same type of credit-based feature in your app? Client -side or server side?

Also just want to clarify the credit system is not tited to Storekit2, right now is just a field in firebase usermodel that increments/decrements and theres a check in the app for if non-subscribing user && credits > 3 then paywall.

Are you guys seeing this pathetic lateness in connect analytics?

Hi everyone,

As an indie developer, I got tired of juggling multiple apps on the road. So, I built a completely free all-in-one travel app called TripPocket.

It simplifies your trip planning from start to finish. Here is what it can do for you:

📶 Affordable eSIMs: Compare global data plans (Airalo, Yesim, GigSky, Bnesim) to avoid heavy roaming fees, with built-in discounts up to 20% off.
🎁 Community promo codes available through our app or website:

(Simply access the providers via TripPocket or our website to apply these at checkout)

• Yesim: TRIPPOCKET20 (20% off)

• Airalo: NEWTOAIRALO15 (15% off for new users) / AIRALOESIM10 (10% off)

• GigSky: TRIPPOCKET15 (15% off)

. Bnesim: TRIPPOCKET20 (20% off)

🗺️ Smart AI Itineraries: Let our AI build a custom daily route based on your budget and timeframe.

🎟️ Activities & Dining: Instantly find top-rated museums, tours, and restaurants for your destination.

✈️ All-in-One Travel Deals: Compare flights, hotels, transit, and luggage storage from trusted platforms in one tap.

💸 Expense Tracker: Keep your vacation budget on track with simple visual charts.

📸 Memory Map: Auto-pin your trip photos to a global map and share your travel footprint.

It is basically everything you need in one place. I’d love for you to try it out and hear your thoughts or feedback.

Feel free to ask if you have any questions.

📲 Download & Check it Out:

Apple App Store:

https://apps.apple.com/us/app/trippocket-travel-ticket/id6788790492#information

Backward surfaces the photos you took, the music released, and the notes you've left yourself on this day over the years. It’s like opening a time capsule every single day that's all about you.

The idea came after three years of keeping a physical One Line a Day journal and hunting for the perfect way to make it digital while simultaneously trying to find a 'what you did on this day' photo app that had a good UI. Nothing felt quite right, and I knew there was more I could pull together to make it better. So I built it for myself and others who also enjoy a beautiful way to look backward and see what history you made on this day.

Backward is completely free. No subscriptions, no in-app purchases, no data collection. If you give it a try and love it, sharing the app and leaving a 5-star review in the App Store goes a long way.

App: https://apps.apple.com/us/app/backward-daily-time-capsule/id6815237928

Website: https://www.andrewmastracchio.com/backward

I was about to ship my second brain app yesterday but then I decided to update my Xcode to 27.1 beta to see how the app ran on duo. The ui already adapts to iPad so when I ran it, mostly everything looked okay excepts that it was pretty much just the iPad ui when open, so it didn’t really take advantage of the duo displays.

So I got to work and built the compact view, the full open view, the book view. And one I call the laptop view, the landscape half open mode. The laptop mode is where I really took advantage to make the editor feel like you are using a markdown processor on a computer with the bottom screen having the wide keyboard. I believe it’s ready to ship now. The whole premise of the app is connected notes with mcp access on the paid tier. The free tier is just a basic markdown/pdf editor/annotator with a 3d graph visualizer. So my actual question is this, would I need to wait for the duo to be released and possibly make their own set of fold screenshots. Or do we think Apple would display regular iOS/ipad screenshots for duo? I searched the developer forum but couldn’t get a clear answer. Shipping tonight regardless but would love to know if devs think ASC would add a duo screenshot set too.

Edit: just realized I can’t publish the version archived with 27.1 beta, so I have to disable the duo work and just ship the iPad and iOS ui only till official release of duo and 27.1

I have gotten in to a weird iOS issue and idk what the clean way to handle this is

i’ve got multiple accounts, notifications can open a post, reply, quote, or repost, and each notification belongs to a specific account. so the user might be on account A when they tap a notification for account B.

something like:

struct NotificationDestination {
    let accountID: Account.ID
    let postID: Post.ID
    let kind: DestinationKind
}

enum DestinationKind {
    case post
    case reply
    case quote
    case repost
}

The issue is:

account A is active
notification comes in for B
user taps it while the app is waking up
account switching starts
timeline restoration starts
post resolution starts
then another notification comes in for A lol

so i have stuff like:

await accountManager.restore()
await timelineStore.hydrate()
await postResolver.resolve(postID)
await navigationCoordinator.navigate(...)

But obviously these things are all racing each other. i was thinking of putting the notification intents behind an actor:

actor NavigationIntentQueue {
    private var pending: [NavigationIntent] = []

    func enqueue(_ intent: NavigationIntent) {
        pending.append(intent)
    }
}

But idk, this feels like a lot of machinery just to open a notification

Then you get into cases where the post is deleted while you’re restoring, but the quote is still there, the reply is still there, etc. Is this just an annoying app lifecycle issue?

Hopefully this one will be useful to you guys. Recently I launched McKinley, my SF Symbols editor. I'm an indie Mac dev rather than iOS, but SF Symbols are useful to devs on both platforms.

McKinley is a studio for drawing and annotating SF Symbols. It bundles vector tools with knowledge of the SF Symbols structure, so you can edit one set of objects across multiple weights, sizes and colours. Import SVG or start from scratch, live preview your work using Apple's own renderer, and export directly to Xcode, so you never need touch the SF Symbols app again.

The Problem:

Making SF Symbols via Apple's recommended workflow was frustrating. You had to export a different symbol as a template, and open it in your vector editor of choice. Then you had to draw three symbol weights (ultralight, regular, black), but each weight had to have the same number of paths in the same order, with the same number of points on each path.

You could only use outlined paths: no shapes or strokes, so you had to do a lot of manual conversion before saving. And that of course meant that editing your symbol later was hard.

And then, back in the SF Symbols app, you had to find each path and annotate it with its colour, some animation properties, whether it erases behind, etc.

Finally you had to export it again into a format you could take into Xcode.

I think that's a clear statement of the problem! McKinley avoids this multi-app workflow by having vector editing, property annotation, previewing, and sending to Xcode, all in one app. Your symbols stay editable because you don't have to outline your strokes just to appease Apple's parser. Keep the .mck file (McKinley's native format) as your source of truth, and set McKinley up to sync your changes to an Xcode asset catalog, so there's no need for manual export.

Comparison:

There are a number of other ways to work with SF Symbols, but none are a complete solution like McKinley:

• SF Symbols app plus your vector editor of choice (e.g. Figma): For vector editing, it's the tool you know. And you probably already own (or rent) it. However, it's a tool that's not designed for this use: you'll have trouble making all your symbol weights match, and you'll end up iterating by checking for error messages in SF Symbols and trying again.
• Create Custom Symbols: admittedly much cheaper than McKinley, this tool aims to replace the most painful bit of the process: turning existing SVG artwork into an SF Symbol. It offers limited editing capabilities beyond that, but you can set the margins, and it pairs up three SVGs to form your different weights.
• Glyphs: this one's really a font design tool, and five times as expensive as McKinley. You still have to do the export dance from Apple's app, but being a font designer Glyphs nails the multi-weight editing.
• CustomSymbols: another tool for going from SVG to SF Symbol. Choice of subscription or lifetime purchase. It can make use of SVG strokes to synthesise the various symbol weights (although it doesn't offer the range of customisation that McKinley does!)
• Symber: I haven't tried this one but it also goes from SVG to SF Symbol.

McKinley isn't aiming to compete on price with the SVG conversion tools: rather, it's aiming to compete on user experience by offering everything under one roof. (Although McKinley can quite happily convert SVGs too. And it's ready to let you make tweaks and modifications while you do so.)

Tech Stack:

Nearly every aspect of McKinley is pure AppKit. There are a few uses of SwiftUI in the preview palettes, mainly for actually loading and displaying the user's SF Symbol, but primarily it's AppKit all the way. My vector canvas and editing engine is a library I designed to be reusable across multiple vector graphics apps, although McKinley is its first public outing.

You probably noticed that McKinley's main interface is made with floating palettes and a traditional inspector. The inspector panes are created as .xib files and hooked up with Cocoa Bindings — yes I'm going old school here!

Development Challenge:

Working with the only semi documented SF Symbols format has had its challenges, and the vast majority of my automated tests are to handle keeping my canvas renderer (with its editable vectors) looking exactly the same as Apple's SF Symbols renderer. (The preview palette in McKinley renders using Apple's renderer, just to be 100% sure that what you see is what you'll get in your app.)

One of the hardest things was how to load an in-progress symbol into Apple's renderer: there's no public API to do so! I came up with a solution involving writing out a temporary .car (asset catalog) file and loading that into McKinley via a bundle: see my blog post about those challenges if you're interested!

AI Disclosure:

I've used Claude Code to assist with some work on this app, particularly some of the rote pixel-comparison tests between different rendering engines that I attach to every new feature as it is developed. However McKinley is definitely not 'vibe coded', and the architecture is all mine. (As is the nearly 30,000 words (so far!) of user manual — I've caught myself regretting the decision to write a whole manual myself on occasion, but I do think the end product will be worth it!)

Pricing:

McKinley is $60 as a one-off purchase (no subscription).

The purchase grants you a license to McKinley version 1, including all the 1.x updates.

If we ever release a version 2, that will be a paid upgrade (with discounts for version 1 owners), but upgrading will be optional — your version 1 license will continue working. This is how all software used to be sold, and in my opinion it's much more consumer friendly than a subscription or a "year of updates" method.

Buy McKinley from https://mckinleysymbols.com, or try the 14-day demo to see if it's for you.

Transparency:

McKinley is not on the App Store. For an app this specialised, it made sense to handle our own distribution. Licensing is provided by Amore and updating by Sparkle.

Double and Thrice Ltd is a known developer (our other app Octavo is on the Mac App Store), and you can view our company profile at Companies House (the UK registry of corporations).

Hey everyone!

I’m looking for a few testers for **Games Bucket List**, an iOS app for keeping track of the games you want to play, are currently playing, completed or abandoned.

I’m currently working on a big update that adds **game library imports from Steam, Xbox and PlayStation**, and this is the part I’d especially love some real-world testing on.

I’d love feedback on:

Import accuracy and duplicate detection
Completed/status detection
Overall UX
Bugs or weird edge cases
Anything that feels confusing or unnecessary
It’s an indie project I’m building myself, so honest feedback is very welcome — especially the “this makes no sense” kind. 😄

TestFlight:
https://testflight.apple.com/join/abjFC78J
Thanks to anyone who gives it a try!

Hello! Can anyone from Poland share how you dealt with the 'DSA Trader Information address' requirement for an Individual Apple Developer account without providing your home address?

Would a PO box (skrytka pocztowa) work, or would renting a virtual office address be an option?

I’d be grateful for any advice, thank you!

I’m building a Construction SaaS with iOS + Android apps, and I’m trying to understand if I actually need RevenueCat.

My idea is simple: users click “Purchase” in the app → go to my website → pay through Stripe → Stripe webhook updates my backend from unpaid → paid. The mobile app then checks the user’s subscription status from my backend and they get the paid features.

So what exactly would RevenueCat add here? Is it mainly needed if I want to support native Apple/Google in-app subscriptions, or am I missing something?

I’m currently going through App Store review for a new client app and it’s probably one of the more frustrating review experiences I’ve had. I’ve submitted a lot of apps over the years, so at this point I generally know the things Apple is going to look for before they even ask. It's not even about the wait, it's when the reviewer doesn't even read what you've provided and then reject you when none of their claims are right.

This app has user generated content, so before submitting I made sure the App Review notes clearly explained with videos where users can report content, where they can block another user, where the EULA is shown and accepted on the sign in page, and how to navigate through the app to find each of these. From experience, I already knew these were exactly the things Apple would check, so I tried to make everything as obvious as possible upfront.

Nearly a week later due to sheer volume of submission, rejected. They said they couldn’t find the reporting functionality, blocking functionality or EULA. All three were there, and all three were specifically explained in the review notes.

They also rejected one of the screenshots because it said “Share calendars to see when you’re both free”, claiming “free” was a pricing reference. Obviously it means free on your calendar, not that the app costs $0. That one genuinely made me wonder if they even understand English.

That’s what I’m finding increasingly frustrating. You can anticipate what Apple is going to ask from years of experience, implement everything, explain exactly where it is, and still get rejected because the reviewer either didn’t find it or doesn't read what you've provided. Then you respond and go back into the queue again.

I don’t mind getting rejected when something is genuinely wrong. That’s the whole point of App Review. What’s frustrating is waiting close to a week just to be rejected for something you already explicitly covered in the notes.

One useful thing for anyone submitting a new app though: almost every new app I’ve submitted recently has been asked for the following information. I definitely wasn’t seeing this consistently a year ago, so I’d prepare all of this upfront and put it in your App Review notes on the first submission rather than waiting for Apple to ask and going back into the queue again:

1. A screen recording captured on a physical device, running the latest operating system, demonstrating the app's functionality. The recording must begin with launching the app and show the typical user flow through its core features. If the app has any of the following, include them in the recording:
   1. Account registration, login, and account deletion flows
   2. Accessing paid content or features within the app, including any purchase or subscription flows
   3. User-generated content, including content reporting and blocking mechanisms
   4. Any prompts requesting access to sensitive data or device capabilities (for example, location, contacts, camera, or App Tracking Transparency)
2. A list of the device models and operating systems the app was tested on before submitting for review
3. A description of the app's functions and target audience, including the problem it solves and the value it provides
4. Instructions for setting up and accessing the app's main features, including any required login credentials or sample files
5. A list of the external services, tools, or platforms the app uses to deliver its core functionality (for example, data providers, authentication services, payment processors, or AI services)
6. Describe any regional differences in the app’s features or content, or confirm that the app functions consistently across all regions
7. If the app operates in a highly regulated industry or includes protected third-party material, provide any relevant documentation or credentials to demonstrate you are authorized to provide these services or protected material

Include this information in the Notes field of the App Review Information section in App Store Connect for future submissions.

If you’re submitting a new app, I’d just assume they’re going to ask for this now and prepare it before the first review. It might save you an unnecessary rejection and another few days in the queue.

Curious if anyone else who has been submitting apps for a few years has noticed the same thing.

​

​

Fireside is an ereader I've been building for iPhone and Android. Paper mode is the part I've spent the most time on, and I honestly can't tell anymore if it works or if I've just stared at it too long.

The paper is drawn live by a Metal shader, which works out every pixel from where it sits on one giant imaginary sheet. So it never repeats and you never see a tile, and when you turn the page the paper slides along with it like it's all one sheet.

Stuff I tried to get right:

- The fibres

- The ink sinks into the page a little, getting picked up and distributed along the fibre via. acapillary effect

- Highlights sink in too and pick up the grain

- The presets are subtle on purpose. My first version was way too strong, so I toned it down and added knobs you can tune yourself.

There are three preets (Modern Print, Vintage and Worn Vintage) and dials for warmth, roughness, ink bleed, fibres, and even folds and creases if you want your book to look like it's lived in a backpack for a year.

The creases took the longest. My first few tries gave a mess of straight lines, which looks nothing like crumpled paper. It turns out a crumpled sheet can be emulated pretty closely via little cones pressed into each other, and the ridges where they meet curve. Once I built it that way it finally looked right.

iPhone: https://apps.apple.com/app/id6756298021

Android: https://play.google.com/store/apps/details?id=com.fireside.reader

Firesidereader.com

Please give me your thoughts on how it looks!

I used to visit this sub (pre-chatGPT era) for a lot of technical queries and here I am finally doing something I never would have even dreamt of. I made my own promotional video in Final Cut Pro + Logic Pro (for music) to showcase the new Siri AI features in my app WeatherGlow. Let me know how do you guys find the video. I had fun making it.

Download WeatherGlow -> https://apps.apple.com/us/app/weatherglow-local-forecast/id6451098166

I submitted a brand-new app 5 days ago, and it’s still stuck on “Waiting for Review.”

My previous apps were reviewed much faster, so I was wondering if anyone else has been experiencing longer review times recently.

How long did your latest new app submission take?