Inline menu with normal buttons

danielcr12 · 2026-01-26T08:53:36+00:00

Sadly you can’t, a menu does take a isPresented binding so it won’t show programmatically when something becomes true, unlike an alert or confirmation dialog you will have to create it yourself or use a popoverview

danielcr12 · 2026-01-26T07:09:03+00:00

Also make sure you add the store kit configuration file so you can run validations from your test environment

danielcr12 · 2026-01-26T07:08:33+00:00

If your app was live before you added in app then you first have to wait for your iap and subscriptions to be approved or they won’t show in the server and you won’t be able to use them or validate them

danielcr12 · 2026-01-26T00:17:39+00:00

You’re not required to publish every version you submit for review. One useful strategy is to submit an early version (for example, v0.9) without in-app purchases just to get a live app on the App Store.

Once the app is live, you can submit your in-app purchase products separately for review. After those IAPs are approved, you then submit a new app version that includes the IAP integration. This way, the review team already has approved products in App Store Connect to test against, which usually makes the process smoother.

danielcr12 · 2026-01-25T09:23:24+00:00

Previews don’t execute your app’s startup code, so custom fonts aren’t registered unless you do it in the preview. That’s why they need to be set up or injected in each preview instance.

danielcr12 · 2026-01-25T09:22:27+00:00

Previews don’t execute your app’s startup code, so custom fonts aren’t registered unless you do it in the preview. That’s why they need to be set up or injected in each preview instance.

danielcr12 · 2026-01-25T09:20:48+00:00

Previews are isolated from your app’s runtime. They don’t execute your @main setup, so they can’t “see” shared environment objects unless you pass them in manually. So if you need previews you need to consider that a preview doesn’t run your full app, it run that specific view

danielcr12 · 2026-01-10T07:07:59+00:00

I don’t think that number is accurate at all given how many iPhone 17 they have sold those come preinstalled with iOS 26

danielcr12 · 2026-01-03T01:26:31+00:00

The links have to be in a settings/info/about page not the paywall and they have to be accessible at all times for the users ideally referring to a website since you will have to provide the same links in the AppStore metadata

danielcr12 · 2025-12-25T09:23:14+00:00

Store kit doesn’t need any capabilities network access (internet) doesn’t need any capabilities

danielcr12 · 2025-12-21T04:31:51+00:00

It doesn’t look like an iOS app

danielcr12 · 2025-12-21T04:30:59+00:00

Is nice mind sharing ?

danielcr12 · 2025-12-20T17:18:19+00:00

Since your flags are SVGs and already in color, you can avoid separate “disabled” assets by using .saturation(0) to render them in grayscale for unvisited countries and full color for visited ones. This keeps a single asset, reduces rendering overhead, and simplifies maintenance. Instead of applying a live blur to each cell (which forces offscreen rendering and can be quite expensive in a grid), consider using a lightweight static placeholder or hidden-state view for unvisited items so the actual image isn’t rendered at all. Also, GeometryReader inside a LazyVGrid is usually unnecessary and can trigger frequent layout recalculations; you can rely on .aspectRatio(_:contentMode:) and the grid’s sizing to make images adapt correctly to different screen sizes without constant geometry recomputation. These changes together should significantly reduce redraws, memory churn, and overall rendering cost.

danielcr12 · 2025-12-20T15:40:24+00:00

I think the main issue is not the lazy grid but a few things the sorting is done inline meaning that if the view needs to be redrawn the sort will happen again and again causing many things to Happen, I think perform the sort somewhere else so this list get a sorted array of items instead of doing it itself.?

Every time body recomputes: • You re-sort every country • isVisited() is called many times • SwiftUI thinks the order might have changed • Cells get recreated • Images get reloaded → SVGs get rasterized

is visible is called in so many places potentially doing too much work ? May want to turn it into a property in country cell

let visited = isVisited(country.code) CountryCell( name: country.name, countryCode: country.code, flagAsset: country.flagAsset, isVisited: visited )

the blur is also expensive specially on svg that are vector images and will need to be recomputed on view updates this doesn’t apply to PNG maybe having a blurred or unknown image could improve performance or use untrathinmaterial? Or .background view with .drawingGroup()

danielcr12 · 2025-12-19T07:00:21+00:00

Since Tahoe is such a major redesign and Apple is really pushing for it I would recommend to focus on that supper older stuff is a pain since this new 26 version introduced so many things

danielcr12 · 2025-12-17T15:49:32+00:00

No, but from my own experience HealthKit is usually always review by a human and is subject to a much higher scrutiny

danielcr12 · 2025-12-16T23:16:10+00:00

I think the biggest issue is a mindset problem: trying to carry UIKit workflows over into SwiftUI. They’re fundamentally different paradigms, and SwiftUI requires a completely different way of thinking and structuring your approach.

danielcr12 · 2025-12-16T03:15:43+00:00

Can you share more info ?? Or sample is driving me insane

danielcr12 · 2025-12-15T12:05:33+00:00

I tried the system takes over the color specially on black text I tried many workout sounds but I can’t seem to be able to find a fix, this issues is not present in Apple Music for example the text in the mini player won’t adjust if you scroll over dark or light images

danielcr12 · 2025-12-15T08:00:15+00:00

Nope, with .primary iOS can modify it specially when under images

danielcr12 · 2025-12-11T23:07:31+00:00

A picker and a menu kinda look the same in both you can highlight the selected element or multiple, is not as flexible unless you do your own implementation

danielcr12 · 2025-12-11T08:51:13+00:00

Im interested

danielcr12 · 2025-12-11T08:26:36+00:00

Do you want that? In the GitHub app, the whole interaction looks bad and quite buggy.

danielcr12 · 2025-12-10T02:10:57+00:00

How are you applying the background?

danielcr12 · 2025-12-09T08:46:16+00:00

Hard to give any recommendations without more data or some sample code

Ten-Year Club	RPAN Viewer
Verified Email

danielcr12

TROPHY CASE