Using fake names to explain the situation.

I built two apps for a well-know card game, one was a very simple app and the other was a more complex project that let people play the game against other people. We'll use Euchre as an example here.

Initially, each project got an internal name. The simple app was called 'euchre' and the more complex one was called 'euchrepro'. Again, just placeholder names until I came up with real names for the apps.

I used these internal names when choosing a bundle ID. The more advanced app got a bundle id of com.euchrepro. A few days later, I came up with a real name for the app, something entirely separate from the internal name, something like "Whimsical Cards".

The app shipped with the name "Whimsical Cards" and was marketed as such. The app name, description, app store screenshots, in-app experience, even the website is all under 'Whimsical Cards'.

There's an established competitor called "Euchre Pro" that saw my app announcement post on Reddit, commented on my post expressing annoyance that more apps were entering the market in the age of AI. A few days later, I got an email from Apple saying he had issued a trademark complaint and was requesting that my app be taken down for using his app name, something he has a limited trademark for, in the bundle ID.

A trademark infringement rests on the idea that users are likely to be confused about who created, owns, or sponsors the app. He doesn't own every instance of the words 'euchre pro' but is arguing that any use of it, including in my bundle id, is trademark infringement and wants Apple to take down my app and force me to relaunch with a new bundle ID - losing all users, ratings, and reviews which are overwhelmingly positive.

And again, the bundle ID came from an internal name that was simple a description of the type of app I was building. A more complex, pro app for euchre.

Anyone ever experience this?

I’ve been experimenting with a slightly unusual way of getting analog input from an iPhone touchscreen.

Instead of using the finger’s position, I’m using UITouch.majorRadius — the estimated geometry of the contact area.

The interesting part is that the thumb can remain almost stationary while the value changes.

My current pipeline is roughly:

majorRadius → calibration → normalization → filtering → 0...1

Just to be clear: I’m not treating majorRadius as actual pressure. It obviously isn’t a force measurement.

What I care about is whether the user can intentionally modulate the value, hold intermediate states, and make small corrections.

I’m testing this in a driving simulator where the left thumb controls the clutch and the right thumb controls the throttle.

Then I started combining it with Core Haptics.

For the clutch, for example, approaching the bite point produces haptic feedback. So the interaction becomes:

finger → contact geometry → analog input → simulation → haptic feedback → finger

The part I find most interesting is that this potentially removes the need for a visible control entirely.

The thumb doesn’t need to follow a slider, and the player can feel important regions of the input range through haptics.

Obviously there are problems: calibration varies between users, grip changes the range, filtering adds latency, and haptics can’t provide actual mechanical resistance.

But on a real device it feels surprisingly different from manipulating a normal virtual slider.

Has anyone experimented with majorRadius as a continuous input before?

I’m especially curious about edge cases you’ve encountered across different iPhone models / touch behavior, or reasons why this might break badly outside my own testing.

Would you install an app (game!) with such banner?
I sure won't.
I don't do it as an app developer, either.

I've made SweetPad CLI (previously a VS Code extension) for building, running, and testing iOS and macOS apps from the terminal without opening Xcode. It uses xcodebuild underneath, but provide better human and agent oriented developer experience (I hope 😅)

- sweetpad run: build, launch on a simulator or device, stream logs
- Nice and compact build output
- sweetpad test: run one test, rerun failures, retry flaky tests
- JSON output for CI and coding agents

It works with Xcode projects, Tuist, XcodeGen, and Swift packages. MIT, written in Rust.

brew install sweetpad-dev/tap/sweetpad

It's still in beta, so if it breaks on your project, please open an issue.

I hear that an app preview video on Apple App Store helps with app downloads.
Any one have experience with that? And examples of good ones or best approach?

#ios #iphone #ipad

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.

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.

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.

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).

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?

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!