DEV Community: Ahtisham Hasan Khan

Stop Using NavigationView - Mastering NavigationStack in 2026

Ahtisham Hasan Khan — Sat, 03 Oct 2026 16:05:49 +0000

If you are still wrapping your SwiftUI views in NavigationView in 2026, we need to talk.

Apple soft-deprecated NavigationView years ago. While it might still "work" for simple prototypes, it is a nightmare for scalable, real-world applications. If you want to handle push notifications, deep links, or complex onboarding flows, you must use NavigationStack.

In this guide, I’ll show you how to move from "Push-and-Pray" navigation to a robust, state-driven routing system.

The Problem with the Old Way

In the early days of SwiftUI, we used NavigationLink directly inside our lists. It looked innocent enough:

// The Old Way (Don't do this anymore)
NavigationView {
    List(0..<5) { i in
        // ❌ Problem: DetailView is initialized immediately for EVERY row!
        NavigationLink("Go to Detail \(i)", destination: DetailView(i: i))
    }
}

Two things go wrong here. First, NavigationLink(destination:) builds every DetailView up front, even for rows nobody taps. Second, navigation lives inside the views. There is no single value that says "the user is on screen X", so you can't push a screen from a notification, restore it from a deep link, or pop back to the root from code.

The New Way: navigation as data

NavigationStack (iOS 16+) flips this around. You describe where a link goes with a value, and you describe how to show that value once, with navigationDestination(for:):

struct ContentView: View {
    var body: some View {
        NavigationStack {
            List(0..<5) { i in
                // ✅ Only a value is created here. DetailView is built on tap.
                NavigationLink("Go to Detail \(i)", value: i)
            }
            .navigationDestination(for: Int.self) { i in
                DetailView(i: i)
            }
        }
    }
}

The destination view is now built lazily, and the link only carries an Int.

Step 1: Model your routes

Real apps have more than one kind of screen. Put them in one Hashable enum so every place in the app can name a destination the same way:

enum Route: Hashable {
    case profile(userID: String)
    case settings
    case order(id: Int)
}

Step 2: Own the path in a router

Bind the stack to an array of routes. Whoever owns that array controls navigation:

import Observation

@Observable
final class Router {
    var path: [Route] = []

    func push(_ route: Route) { path.append(route) }
    func pop() { _ = path.popLast() }
    func popToRoot() { path.removeAll() }
}

@Observable needs iOS 17. On iOS 16, make it an ObservableObject with @Published var path.

Step 3: Wire the stack to the router

struct RootView: View {
    @State private var router = Router()

    var body: some View {
        NavigationStack(path: $router.path) {
            HomeView()
                .navigationDestination(for: Route.self) { route in
                    switch route {
                    case .profile(let userID): ProfileView(userID: userID)
                    case .settings: SettingsView()
                    case .order(let id): OrderView(id: id)
                    }
                }
        }
        .environment(router)
    }
}

Any child view can now navigate without knowing about its parents:

struct HomeView: View {
    @Environment(Router.self) private var router

    var body: some View {
        Button("Open settings") { router.push(.settings) }
    }
}

Step 4: Deep links and notifications for free

Because the whole stack is just [Route], opening a screen from outside the UI means setting an array. For a URL like myapp://order/42:

.onOpenURL { url in
    guard url.host == "order",
          let id = Int(url.lastPathComponent) else { return }
    router.path = [.order(id: id)]
}

The same works when a push notification arrives: parse the payload into a Route and assign the path. To jump several screens deep, assign several routes, for example [.profile(userID: "me"), .settings].

Mixed value types: NavigationPath

If different features push unrelated types and you don't want one big enum, use NavigationPath, a type-erased path that accepts any Hashable value:

@State private var path = NavigationPath()

NavigationStack(path: $path) {
    FeedView()
        .navigationDestination(for: Post.self) { PostView(post: $0) }
        .navigationDestination(for: User.self) { UserView(user: $0) }
}

An enum is easier to read and test, so I start there and only reach for NavigationPath when features need to stay independent.

Quick migration checklist

Replace NavigationView with NavigationStack. For sidebar layouts on iPad and Mac, use NavigationSplitView.
Change NavigationLink(destination:) to NavigationLink(value:).
Add one navigationDestination(for:) per value type, high in the hierarchy rather than inside lists.
Move the path into a router you can reach from anywhere.
Route deep links and notifications by assigning the path.

If you're building an iOS app and want routing like this from day one, that's the kind of work I do.

Originally published at iahtisham.com.

I'm Ahtisham, an independent iOS developer building native Swift apps. More from me:

🌐 Portfolio and client work: iahtisham.com
💸 AppPriceKit: free App Store subscription prices by country
🧾 JustInvoice: invoice maker for iPhone
📄 ScanIt: document scanner and PDF for iPhone
🌙 NUR: prayer times, offline Qur'an and adhkar, free with no ads
🏢 PrismCode Labs

Find me on X @iAhtishamDev · GitHub · LinkedIn · Upwork

Native iOS vs React Native vs Flutter: Which Should Your App Use?

Ahtisham Hasan Khan — Sat, 03 Oct 2026 16:05:42 +0000

I build native iOS apps, so take my bias into account. But I have also worked in web teams and across a product organization that shipped on several platforms, and the right answer is not always "native". Here is how I would decide if it were my money.

The short version

	Native (Swift / SwiftUI)	React Native	Flutter
Best when	iPhone is your main audience	Your team already knows React	You need iOS and Android with one custom UI
Feel on iPhone	Most native	Close, with care	Custom-drawn, consistent across platforms
New Apple features	Available immediately	After libraries catch up	After plugins catch up
Android	Separate build	Shared code	Shared code

Choose native iOS if…

Your users are mostly on iPhone. This is true for many consumer apps in the US, UK, and the Gulf, and for creator and productivity tools.
The app depends on Apple hardware or system features: camera, widgets, Live Activities, HealthKit, Apple Pay, background audio. CueCam, a teleprompter that follows the speaker's voice while recording, is the kind of product where native matters.
You care about polish at launch. App Store users notice when an app feels slightly off.

Choose React Native if…

You already have a React web team that will maintain the app.
The app is mostly forms, lists and content, without heavy device features.
You truly need Android on day one and the budget only covers one codebase.

Choose Flutter if…

You want an identical, heavily branded UI on iOS and Android.
You are building for markets where Android dominates and iOS is secondary.

The hidden cost nobody mentions

Cross-platform does not mean "build once". You still test on two platforms, go through two store reviews, and handle two sets of platform quirks. If you only needed iOS in the first place, you paid for flexibility you did not use.

My recommendation for most founders

Launch on the platform where your first users are. For many consumer and creator products that is iPhone. Prove the idea, learn what people actually use, then expand. The backend, the product decisions, and the brand all carry over to Android.

Not sure which fits your app? Send me a short description and I will give you a straight answer, even if it is "not native".

FAQ

Is native iOS development more expensive than Flutter or React Native?

If you only need iPhone, native is usually not more expensive and is often faster to get right. Cross-platform saves money mainly when you genuinely need iOS and Android at launch.

Can I start native on iOS and add Android later?

Yes. Many products launch on iOS, validate the idea, then build Android once they know what users want. The backend and product decisions carry over.

Which is better for performance and App Store quality?

Native Swift and SwiftUI give direct access to every Apple API on day one and the most iPhone-like feel. Cross-platform apps can be very good, but platform-specific features often need extra native work anyway.

What do you build with?

I build native iOS apps with Swift and SwiftUI. Every app in my portfolio is native.

Originally published at iahtisham.com.

I'm Ahtisham, an independent iOS developer building native Swift apps. More from me:

🌐 Portfolio and client work: iahtisham.com
💸 AppPriceKit: free App Store subscription prices by country
🧾 JustInvoice: invoice maker for iPhone
📄 ScanIt: document scanner and PDF for iPhone
🌙 NUR: prayer times, offline Qur'an and adhkar, free with no ads
🏢 PrismCode Labs

Find me on X @iAhtishamDev · GitHub · LinkedIn · Upwork

What is PPP pricing? Purchasing power parity for app subscriptions

Ahtisham Hasan Khan — Sat, 03 Oct 2026 16:05:36 +0000

PPP pricing (purchasing power parity pricing) means charging each country a price scaled to what things cost there, instead of converting one price at the exchange rate. A $4.99 subscription might become about $1.19 in India and $2.29 in Brazil.

Why exchange rates aren’t enough

Exchange rates reflect trade and capital flows, not what a coffee or a phone plan costs. When Apple converts $4.99 into rupees, the result is roughly $4.99 at market rates. But the World Bank estimates that goods and services in India cost about 23% of US prices, so that subscription feels about 4.3× as expensive to someone living there.

This isn’t limited to a few countries. Of the 174 App Store territories the World Bank covers, 109 have a price level below half of the US level. Only 6 are more expensive than the US. See the full ranking.

How PPP pricing is calculated

Pick a base price in a base country, usually the US.
Find each country’s price level relative to the base. The World Bank’s PA.NUS.GDP.PLI indicator gives this directly: it is the ratio of the PPP conversion factor to the market exchange rate, with the US at 100.
Multiply the base price by that ratio.
Round the result to a price the store accepts. On the App Store that means one of Apple’s price points.

Our step-by-step guide walks through the App Store version with a worked example.

Price-level index vs. other signals

World Bank price level. Broad, official, updated yearly, covers almost every App Store territory. Measures prices, not incomes.
Big Mac Index. Easy to explain, but one product in about 50 countries.
GDP per capita. Tracks income rather than prices and swings further, so it produces much deeper discounts.
Competitor prices. The most relevant signal for your niche, and the hardest to collect.

Where PPP pricing goes wrong

Treating it as the answer. A price-level ratio says what things cost, not what your audience will pay. Use it as a first draft and measure conversion afterwards.
Going too low. Very low prices can attract refund abuse or VPN shoppers. A floor price limits this.
Ignoring existing subscribers. Decreases reach them automatically; increases follow Apple’s consent rules.

Key terms

Price level, price point, equalization and storefront are defined in the App Store pricing glossary.

Originally published at AppPriceKit.

I'm Ahtisham, an independent iOS developer building native Swift apps. More from me:

🌐 Portfolio and client work: iahtisham.com
💸 AppPriceKit: free App Store subscription prices by country
🧾 JustInvoice: invoice maker for iPhone
📄 ScanIt: document scanner and PDF for iPhone
🌙 NUR: prayer times, offline Qur'an and adhkar, free with no ads
🏢 PrismCode Labs

Find me on X @iAhtishamDev · GitHub · LinkedIn · Upwork

Checklist: before you change App Store prices by country

Ahtisham Hasan Khan — Sat, 03 Oct 2026 16:05:30 +0000

Regional pricing is easy to get wrong in ways that are hard to undo. Run through this list before you schedule anything.

Before you calculate

Know where your users are. Pull downloads and trial starts by country from App Store Connect analytics. Price changes only matter where you have traffic.
Record today’s prices and conversion. Export current prices per country and a few weeks of conversion rates so you have a baseline.
Pick your base and floor. Choose a base country and price, and a minimum you won’t go below. A floor protects against very low prices in the cheapest markets.

Before you schedule

Start with a handful of countries. Three to five large lower-priced markets give a readable result.
Remember decreases can’t be reversed. Once a decrease takes effect, going back means a new increase, with notice and possibly consent.
Decide on existing subscribers. Decreases reach them automatically. For increases, choose whether to preserve their price.
Check for scheduled changes. Only one future change is allowed per country and plan; a new one overwrites the old.
Choose a start date. Leave at least a couple of days, and avoid dates when you can’t watch the results.

After the change

Keep a record. Save exactly what Apple accepted per country. AppPriceKit exports a CSV receipt for this.
Measure for at least a few weeks. Compare conversion, revenue per visitor and refunds in the changed countries against the baseline and against unchanged countries.

New to the idea? Start with what PPP pricing is, then see the suggested prices by country.

Originally published at AppPriceKit.

I'm Ahtisham, an independent iOS developer building native Swift apps. More from me:

🌐 Portfolio and client work: iahtisham.com
💸 AppPriceKit: free App Store subscription prices by country
🧾 JustInvoice: invoice maker for iPhone
📄 ScanIt: document scanner and PDF for iPhone
🌙 NUR: prayer times, offline Qur'an and adhkar, free with no ads
🏢 PrismCode Labs

Find me on X @iAhtishamDev · GitHub · LinkedIn · Upwork

Where a $4.99 subscription costs the most: App Store countries ranked by price level

Ahtisham Hasan Khan — Sat, 03 Oct 2026 16:05:25 +0000

Apple converts your subscription price at market exchange rates. We ranked 174 App Store territories by the World Bank price-level index to show where that makes a $4.99 subscription most expensive in local terms.

The short version

109 of 174 territories have a price level below half of the US level.
37 are below a third, where an exchange-rate-converted price feels more than three times as expensive as it does in the US.
Only 6 are more expensive than the US: Israel, Barbados, Switzerland, Cayman Islands, Iceland, Bermuda.
The lowest price levels are in Nigeria, Egypt, Laos.
4 territories have no World Bank estimate (Anguilla, British Virgin Islands, Montserrat, Taiwan).

How to read the table

“Price level” is the World Bank’s PA.NUS.GDP.PLI for the latest available year, divided by the US value. “$4.99 becomes” scales $4.99 by that ratio and rounds to Apple’s nearest US price point. Apple then converts that point to local currency. The price level measures what goods and services cost, not incomes, so treat it as a starting point (why).

#	Territory	Price level vs. US	$4.99 becomes	Data year
1	Nigeria	13%	$0.69	2025
2	Egypt	15%	$0.79	2025
3	Laos	22%	$1.09	2025
4	Sierra Leone	23%	$1.09	2025
5	Bhutan	23%	$1.19	2025
6	India	23%	$1.19	2025
7	Pakistan	24%	$1.19	2025
8	Myanmar	25%	$1.19	2025
9	Gambia	25%	$1.19	2025
10	Nepal	25%	$1.29	2025
11	Bangladesh	26%	$1.29	2025
12	Ethiopia	26%	$1.29	2025
13	Rwanda	27%	$1.39	2025
14	Tajikistan	28%	$1.39	2025
15	Vietnam	28%	$1.39	2025
16	Azerbaijan	28%	$1.39	2025
17	Mauritania	29%	$1.39	2025
18	Indonesia	29%	$1.39	2025
19	Turkmenistan	29%	$1.49	2025
20	Uzbekistan	29%	$1.49	2025
21	Sri Lanka	29%	$1.49	2025
22	Tanzania	29%	$1.49	2025
23	Belarus	30%	$1.49	2025
24	Zambia	30%	$1.49	2025
25	Angola	31%	$1.49	2025
26	Tunisia	31%	$1.49	2025
27	Thailand	31%	$1.49	2025
28	Madagascar	31%	$1.49	2025
29	Ukraine	31%	$1.59	2025
30	Suriname	31%	$1.59	2025
31	Malaysia	32%	$1.59	2025
32	Algeria	33%	$1.59	2025
33	Eswatini	33%	$1.59	2025
34	Georgia	33%	$1.69	2025
35	Guyana	33%	$1.69	2025
36	Philippines	33%	$1.69	2025
37	Kazakhstan	33%	$1.69	2025
38	Kyrgyzstan	33%	$1.69	2025
39	Cambodia	34%	$1.69	2025
40	Kenya	34%	$1.69	2025
41	Togo	34%	$1.69	2025
42	Mali	34%	$1.69	2025
43	Cameroon	34%	$1.69	2025
44	Guinea-Bissau	34%	$1.69	2025
45	Mongolia	34%	$1.69	2025
46	Nicaragua	34%	$1.69	2025
47	Lesotho	34%	$1.69	2025
48	Benin	34%	$1.69	2025
49	Uganda	35%	$1.69	2025
50	Republic of the Congo	35%	$1.69	2025
51	Paraguay	35%	$1.69	2025
52	Brunei	35%	$1.79	2025
53	Chad	35%	$1.79	2025
54	Malawi	35%	$1.79	2025
55	Russia	35%	$1.79	2025
56	Niger	36%	$1.79	2025
57	Senegal	36%	$1.79	2025
58	Mozambique	37%	$1.89	2025
59	Côte d'Ivoire	37%	$1.89	2025
60	Gabon	37%	$1.89	2025
61	Burkina Faso	37%	$1.89	2025
62	North Macedonia	37%	$1.89	2025
63	Lebanon	38%	$1.89	2024
64	Botswana	38%	$1.89	2025
65	Colombia	38%	$1.89	2025
66	Ghana	38%	$1.89	2025
67	Iraq	38%	$1.89	2025
68	Guinea	38%	$1.89	2025
69	Armenia	38%	$1.89	2025
70	Dominican Republic	39%	$1.89	2025
71	Mauritius	39%	$1.89	2025
72	Libya	39%	$1.99	2025
73	Bolivia	40%	$1.99	2025
74	Bosnia and Herzegovina	40%	$1.99	2025
75	Fiji	41%	$1.99	2025
76	Namibia	41%	$1.99	2025
77	El Salvador	41%	$2.09	2025
78	Equatorial Guinea	41%	$2.09	2025
79	Kosovo	41%	$2.09	2025
80	Turkey	41%	$2.09	2025
81	South Africa	41%	$2.09	2025
82	Montenegro	42%	$2.09	2025
83	Democratic Republic of the Congo	42%	$2.09	2025
84	Morocco	42%	$2.09	2025
85	Central African Republic	42%	$2.09	2025
86	Jordan	42%	$2.09	2025
87	Ecuador	43%	$2.09	2025
88	Bahrain	43%	$2.19	2025
89	Moldova	43%	$2.19	2025
90	Guatemala	43%	$2.19	2025
91	Yemen	44%	$2.19	2013
92	Romania	44%	$2.19	2025
93	Serbia	45%	$2.29	2025
94	Panama	45%	$2.29	2025
95	Honduras	46%	$2.29	2025
96	Brazil	46%	$2.29	2025
97	Argentina	46%	$2.29	2025
98	Bulgaria	46%	$2.29	2025
99	Albania	46%	$2.29	2025
100	Liberia	46%	$2.29	2025
101	Djibouti	46%	$2.29	2025
102	Zimbabwe	47%	$2.29	2025
103	Saudi Arabia	47%	$2.29	2025
104	Oman	47%	$2.39	2025
105	China	47%	$2.39	2025
106	Chile	48%	$2.39	2025
107	Cape Verde	48%	$2.39	2025
108	Dominica	48%	$2.39	2025
109	Comoros	49%	$2.39	2025
110	Trinidad and Tobago	51%	$2.59	2025
111	Maldives	51%	$2.59	2025
112	St. Lucia	51%	$2.59	2025
113	Peru	51%	$2.59	2025
114	Hungary	52%	$2.59	2025
115	Poland	52%	$2.59	2025
116	Belize	53%	$2.59	2025
117	Croatia	53%	$2.69	2025
118	Mexico	54%	$2.69	2025
119	Seychelles	54%	$2.69	2025
120	St. Vincent and the Grenadines	55%	$2.79	2025
121	Macau	55%	$2.79	2025
122	Qatar	56%	$2.79	2025
123	Grenada	57%	$2.79	2025
124	Latvia	57%	$2.89	2025
125	Kuwait	57%	$2.89	2025
126	South Korea	57%	$2.89	2025
127	Slovakia	58%	$2.89	2025
128	Papua New Guinea	58%	$2.89	2025
129	Lithuania	58%	$2.89	2025
130	Costa Rica	59%	$2.99	2025
131	Czech Republic	59%	$2.99	2025
132	Greece	60%	$2.99	2025
133	Jamaica	60%	$2.99	2025
134	Portugal	60%	$2.99	2025
135	Singapore	60%	$2.99	2025
136	Venezuela	63%	$3.09	2011
137	Slovenia	63%	$3.19	2025
138	United Arab Emirates	63%	$3.19	2024
139	São Tomé and Príncipe	64%	$3.19	2025
140	Spain	65%	$3.19	2025
141	Cyprus	65%	$3.19	2025
142	Japan	65%	$3.19	2025
143	Uruguay	66%	$3.29	2025
144	Estonia	66%	$3.29	2025
145	Malta	66%	$3.29	2025
146	St. Kitts and Nevis	69%	$3.39	2025
147	Italy	69%	$3.49	2025
148	Antigua and Barbuda	69%	$3.49	2025
149	Hong Kong	71%	$3.49	2025
150	Solomon Islands	75%	$3.69	2025
151	France	77%	$3.79	2025
152	Germany	80%	$3.99	2025
153	Belgium	81%	$4.09	2025
154	Austria	82%	$4.09	2025
155	Canada	83%	$4.19	2025
156	Netherlands	84%	$4.19	2025
157	Ireland	85%	$4.19	2025
158	Finland	85%	$4.29	2025
159	New Zealand	86%	$4.29	2025
160	Sweden	87%	$4.39	2025
161	United Kingdom	89%	$4.49	2025
162	Australia	91%	$4.49	2025
163	Norway	91%	$4.49	2025
164	Denmark	92%	$4.59	2025
165	Luxembourg	94%	$4.69	2025
166	Bahamas	96%	$4.79	2024
167	Turks and Caicos Islands	99%	$4.89	2024
168	United States	100%	$4.99	2025
169	Israel	101%	$5.09	2025
170	Barbados	110%	$5.49	2025
171	Switzerland	112%	$5.59	2025
172	Cayman Islands	113%	$5.69	2024
173	Iceland	118%	$5.89	2025
174	Bermuda	120%	$5.99	2024

What to do with this

Look at where your downloads come from. If a large share comes from countries near the top of this table, your default prices are probably costing you conversions there. Start with your three biggest lower-priced markets, set a floor price, and compare conversion before and after. The checklist covers the rest, and RevenueCat’s quick fixes for default global pricing is a good companion read.

Originally published at AppPriceKit.

I'm Ahtisham, an independent iOS developer building native Swift apps. More from me:

🌐 Portfolio and client work: iahtisham.com
💸 AppPriceKit: free App Store subscription prices by country
🧾 JustInvoice: invoice maker for iPhone
📄 ScanIt: document scanner and PDF for iPhone
🌙 NUR: prayer times, offline Qur'an and adhkar, free with no ads
🏢 PrismCode Labs

Find me on X @iAhtishamDev · GitHub · LinkedIn · Upwork

App Store subscription price increases: when subscribers must consent

Ahtisham Hasan Khan — Sat, 03 Oct 2026 16:05:19 +0000

When you raise a subscription price, you choose whether existing subscribers keep their current price. If you move them to the new price, Apple either notifies them or asks them to agree, depending on the size of the increase, their country and their history.

Option 1: keep existing subscribers on their price

Anyone who subscribed before the start date keeps paying what they pay today. Apple also lets subscribers whose subscription expires resubscribe at the preserved price within 60 days. This is the safest option and the default in AppPriceKit.

Option 2: apply the increase to existing subscribers

According to Apple’s pricing documentation, subscribers must consent before renewing at the higher price if any of these is true:

They are in a region that requires consent for any price change.
The increase is more than 50% of the current price and more than about US$5 per period (US$50 per year for annual plans).
They already had a price increase on that subscription in the past 12 months.

Otherwise they are only notified, and renew at the new price unless they cancel.

Notice periods

Annual, 6-, 3- and 2-month plans: 60 days before renewal.
Monthly plans: 27 days before renewal.
Weekly plans: 7 days before renewal.

Subscribers who need to consent and don’t respond get reminders about weekly by email, push and in-app message. If they never agree, the subscription expires at the end of the current period. That makes consent-triggering increases risky for retention.

Decreases are different

A decrease reaches every existing subscriber at their next renewal, and you can’t keep them on the higher price. Apple also notes that once a decrease takes effect it can’t be reversed; you would need to schedule a new increase, which then follows the rules above.

Practical rules of thumb

Keep increases under 50% or under about $5 per period to avoid consent prompts.
Don’t raise the same subscription twice within 12 months.
Only one future price change can be scheduled per country and plan; scheduling another overwrites the first.
When lowering prices in cheaper countries, existing subscribers there benefit too. Budget for that revenue change.

More in the checklist before changing prices by country and the App Store Connect walkthrough.

Originally published at AppPriceKit.

I'm Ahtisham, an independent iOS developer building native Swift apps. More from me:

🌐 Portfolio and client work: iahtisham.com
💸 AppPriceKit: free App Store subscription prices by country
🧾 JustInvoice: invoice maker for iPhone
📄 ScanIt: document scanner and PDF for iPhone
🌙 NUR: prayer times, offline Qur'an and adhkar, free with no ads
🏢 PrismCode Labs

Find me on X @iAhtishamDev · GitHub · LinkedIn · Upwork

How Apple sets your subscription price in 175 countries

Ahtisham Hasan Khan — Sat, 03 Oct 2026 16:05:13 +0000

When you price an auto-renewable subscription, you pick one base price and App Store Connect fills in the other 174 storefronts. Those prices come from exchange rates and local taxes, and once set they stay put until you change them.

Price points

You can’t charge any amount you like. Each storefront has a fixed ladder of price points, about 800 per currency according to Apple’s documentation. In the US the ladder goes up in $0.10 steps to $9.99, then in $0.50 steps to $49.99, then in larger steps above that. Every price you schedule must be one of these points.

Equalization

Every price point in your base country has an equivalent point in each other storefront. Apple calls these equalizations and chooses them using exchange rates and taxes. When you choose $4.99 as your US price, App Store Connect proposes the equalized point for every other country. You can accept them or edit any country before confirming.

The App Store Connect API exposes the same mapping: each subscription price point has an equalizations relationship listing its counterparts in other territories. How to use it.

Subscription prices don’t follow exchange rates

This surprises many developers. For paid apps and one-time purchases, Apple adjusts prices when taxes or exchange rates move significantly. For auto-renewable subscriptions, it doesn’t. Apple’s help page says those retail price changes “will exclude auto-renewable subscriptions”.

So a subscription priced two years ago in a country whose currency has since lost half its value is now half as expensive in dollar terms, and your proceeds have dropped with it. When VAT changes, your proceeds change too, because Apple’s commission and your share are calculated after tax. Reviewing prices once or twice a year catches both.

What equalization doesn’t do

Equalization keeps prices roughly equal at market exchange rates. It doesn’t account for what things cost locally. That is why a $4.99 subscription can be several times more expensive, in local terms, in India or Egypt than in the US. Adjusting for that is called PPP pricing. AppPriceKit uses Apple’s equalization as its last step: it picks a US price point from each country’s price level, then takes Apple’s equalized local price for that point. Equalization vs. AppPriceKit.

Originally published at AppPriceKit.

I'm Ahtisham, an independent iOS developer building native Swift apps. More from me:

🌐 Portfolio and client work: iahtisham.com
💸 AppPriceKit: free App Store subscription prices by country
🧾 JustInvoice: invoice maker for iPhone
📄 ScanIt: document scanner and PDF for iPhone
🌙 NUR: prayer times, offline Qur'an and adhkar, free with no ads
🏢 PrismCode Labs

Find me on X @iAhtishamDev · GitHub · LinkedIn · Upwork

How to update subscription prices with the App Store Connect API

Ahtisham Hasan Khan — Sat, 03 Oct 2026 16:04:54 +0000

Changing a subscription price for dozens of countries in the App Store Connect UI is slow. The App Store Connect API can do it in a few calls. These are the requests AppPriceKit makes, taken from its open-source code.

1. Authenticate with a team API key

Create a team key in App Store Connect under Users and Access → Integrations, with App Manager access. Sign a JWT with the .p8 private key using ES256, the key ID as kid, your issuer ID as iss and appstoreconnect-v1 as aud. Tokens can last up to 20 minutes; AppPriceKit uses 15.

jwt.sign({ iss: issuerId, aud: "appstoreconnect-v1" }, privateKey, {
  algorithm: "ES256",
  expiresIn: "15m",
  header: { kid: keyId },
});

2. Find the subscription

GET /v1/apps
GET /v1/apps/{appId}/subscriptionGroups
GET /v1/subscriptionGroups/{groupId}/subscriptions

3. Read current prices

GET /v1/subscriptions/{subId}/prices?include=subscriptionPricePoint,territory&limit=200

Each price has a startDate. A price with a future start date is scheduled; the latest past one is current. Paginate with the links.next URL until it is absent.

4. Find the right price point

GET /v1/subscriptions/{subId}/pricePoints?filter[territory]=USA&include=territory&limit=200

Price points are specific to a subscription and a territory. To get the local equivalent of a US point in every other territory, follow its equalizations:

GET /v1/subscriptionPricePoints/{pricePointId}/equalizations?include=territory&limit=200

Use this mapping rather than matching price points by their position in each territory’s list; the ladders differ by currency. Background in how Apple sets prices in 175 countries.

5. Schedule the new price

POST /v1/subscriptionPrices
{
  "data": {
    "type": "subscriptionPrices",
    "attributes": { "startDate": "2026-10-10", "preserveCurrentPrice": true },
    "relationships": {
      "subscription": { "data": { "type": "subscriptions", "id": "{subId}" } },
      "subscriptionPricePoint": {
        "data": { "type": "subscriptionPricePoints", "id": "{pricePointId}" }
      }
    }
  }
}

The price point ID already identifies the territory, so one request schedules one country. preserveCurrentPrice keeps existing subscribers on their current price for increases; it has no effect on decreases. See Apple’s API reference.

Gotchas we hit

Start dates. Apple needs the start date a day or two ahead, depending on time zones. A same-day date is rejected.
409 conflicts. Only one future change can exist per territory. If one is already scheduled, the request can fail with 409. Re-read prices to see what Apple actually holds before retrying.
Confirm after errors. A timeout doesn’t mean the write failed. Re-read the prices and check for your start date and price point before sending the request again.
Rate limits. Equalization lookups for 175 territories add up. Limit concurrency and retry 429s with backoff.

If you’d rather not write this yourself, AppPriceKit does all of it in the browser, and you can try it on sample data.

Originally published at AppPriceKit.

I'm Ahtisham, an independent iOS developer building native Swift apps. More from me:

🌐 Portfolio and client work: iahtisham.com
💸 AppPriceKit: free App Store subscription prices by country
🧾 JustInvoice: invoice maker for iPhone
📄 ScanIt: document scanner and PDF for iPhone
🌙 NUR: prayer times, offline Qur'an and adhkar, free with no ads
🏢 PrismCode Labs

Find me on X @iAhtishamDev · GitHub · LinkedIn · Upwork

Mastering Git Checkout: Decoding the Impact of One Simple Command

Ahtisham Hasan Khan — Tue, 21 Nov 2023 06:27:22 +0000

It all started with a meme. My team lead sent me this, and before this happened, I was one of those who used this powerful command just for creating a new branch or switching between branches.
But kudos to this meme, I've gained a better understanding of this impactful command.

In this article we will do in-depth exploration of this powerful git checkout command. an essential tool in the Git arsenal. Whether you're a coding enthusiast, a seasoned developer, or somewhere in between, This complete guide will help you understand git checkout step by step. It uses simple code examples and clear explanations to make things easy to grasp.

Understanding the Basics

The fundamental purpose of git checkout is to switch between branches in Git repository, Here's a basic example:

# Switch to an existing branch named 'feature-branch'

git checkout feature-branch

Another cool thing I like about this branch is that you can easily switch back to your previous branch with just this simple command

# Switch to previous branch

git checkout -

Undoing Changes Like a Pro

git checkout is a handy tool for reverting changes, whether to a specific file or even the last commit. Let's look at a couple of examples:

File Undo

# Discard changes made to a specific file (filename.txt)

git checkout -- filename.txt

Use this command when you want to revert changes made to a particular file back to its state in the last commit.

Commit Undo

# Undo the last commit, keeping changes in the working directory

git checkout HEAD~1

This command gracefully undoes the last commit while preserving the changes in your working directory, giving you the flexibility to make further adjustments.

Navigating Detached HEAD State

Understanding detached HEAD state is crucial. Consider the following scenario:

# Move to a specific commit without creating a branch

git checkout <commit-hash>

This command puts your repository in a "detached HEAD" state, allowing you to explore specific commits without creating a new branch.

Tailoring Your Checkout with Paths and Commits

Sometimes, you may want to inspect or revert changes made to a specific file at a particular commit. git checkout enables this with ease:

# Checkout a specific file from a particular commit

git checkout <commit-hash> -- filename.txt

This command allows you to navigate through your repository's history and work with specific files at specific points in time.

Discarding Changes Across the Board

To discard all uncommitted changes in your working directory, use the following command:

# Discard all changes in the working directory

git checkout -- .

This is particularly useful when you want to start fresh or abandon changes that haven't been committed.

Conclusion

Armed with these insights and practical examples, you're well on your way to mastering the art of git checkout. Stay tuned as we explore advanced features and best practices in upcoming articles.

Ready to elevate your Git skills? Let's dive in!

If you found this guide helpful, consider buying me Coffee ☕. Connect with me on Twitter for more updates and discussions: (https://twitter.com/iAhtishamHK).

How to enable HTTPS for WAMP Server.

Ahtisham Hasan Khan — Thu, 19 Oct 2023 07:22:10 +0000

Securing your web applications with HTTPS is a fundamental aspect of web development. In a previous article, we discussed how to enable HTTPS on XAMPP. Now, we'll focus on achieving the same security on WAMP, a widely used web development environment. Let's dive into the process of enabling HTTPS on WAMP for a more secure web experience.

Following are some easy steps to setup enviroment to use HTTPS on WAMP.

It is Important that you have already got WAMP installed, If not you can download WAMP from here.

After you've downloade and installed WAMP; the steps are as follows,

STEP 1: Download and Install OpenSSL.

Both 32 and 64-bit versions of OpenSSL are available. Make sure you're using the right installation for your Windows version.
The most recent version of OpenSSL may be found here. When Installing OpenSSL leave all settings default.

STEP 2: Generate Private Key and SSL certficate.

Load Command Prompt as an Administrator from your start menu and run the commands below. To begin, navigate to the directory where OpenSSL was installed.

cd c:/program files/openssl-win64/bin/

Generate your Private key by using follwing command.You will be asked for a passphrase. Make it anything you want just make sure you remember it for the next step.

openssl genrsa -aes256 -out private.key 2048

openssl rsa -in private.key -out private.key

Now, create your Certificate thorough following commad,You will be asked several questions on this step. You can put whatever you like or just hit enter to leave it at default.
- The only one that really matters is Common Name (e.g. server FQDN) you will need to type “localhost” for this.

openssl req -new -x509 -nodes -sha1 -key private.key -out certificate.crt -days 36500

STEP 3: Move your KEY and Certificate.

Create a folder named "KEY" in the directory C:\wamp64\bin\apache\apache2.4.51\conf
Copy the generated private.key and certificate.crt files from C:\Program Files\OpenSSL-Win64\bin
to the C:\wamp64\bin\apache\apache2.4.27\conf\key folder.

Step 4: Edit Your httpd.conf File

Open c:/wamp64/bin/apache/apache2.4.41/conf/httpd.conf and un-comment (remove the #) the following 3 lines:

LoadModule ssl_module modules/mod_ssl.so

Include conf/extra/httpd-ssl.conf

LoadModule socache_shmcb_module modules/mod_socache_shmcb.so

Step 5: Edit Your httpd-ssl.conf File

Open c:/wamp64/bin/apache/apache2.4.41/conf/extra/httpd-ssl.conf and change all the parameters to the ones shown below.

 DocumentRoot "c:/wamp64/www"
 ServerName localhost:443
 ServerAdmin admin@example.com
 ErrorLog "${SRVROOT}/logs/error.log"
 TransferLog "${SRVROOT}/logs/access.log"
 SSLSessionCache "shmcb:${SRVROOT}/logs/ssl_scache(512000)"
 SSLCertificateFile "${SRVROOT}/conf/key/certificate.crt"
 SSLCertificateKeyFile "${SRVROOT}/conf/key/private.key"
 CustomLog "${SRVROOT}/logs/ssl_request.log"

The DocumentRoot folder is the location where the website files are located. The ServerName can be set as localhost" or the name set to access the website like "example.com"

Step 6: Restart WampServer

Everything should be set up now. Make sure you restart WampServer for the changes to take effect.
If there will be any syntax error, you can check it by navigating to c:/wamp64/bin/apache/apache2.4.41/bin in Command Prompt and run following command;

httpd -t

You should now be able to access your website with HTTPS / SSL enabled.

Public Gist URL: https://gist.github.com/iahtisham/5268b2391c674d758d0c2030dfbdb882

If you found this post helpful, consider buying me Coffee ☕. Your support keeps me fueled to create more content!

"Vue 3 : Smooth migration from the Options API to the Composition API in Vue 3"

Ahtisham Hasan Khan — Sun, 20 Aug 2023 10:25:06 +0000

Introduction

With the introduction of Vue 3, a new component option and a new advised pattern were added to the framework for creating apps. You may get top-level bindings using this magical script setup> method of implementing the logics without having to go through the extra trouble of declaring an export default and a setup().

Why <script setup> ?

Leaner codebase, faster development, readable and easier coding experience by reducing component choices into a single block. With each of these features, Reactivity makes things more simpler.

Using Props with `<script setup>`

Using the <script setup> , a function called defineProps() is utilized. This function is a compiler macro, so there is no need to import it.

<template>
  <div>
    <p>Received Prop: {{ propValue }}</p>
  </div>
</template>

Options API :

<script>
export default {
  props: {
    propValue: String
  }
};
</script>

Composition API :

<script setup>
const props = defineProps({
  propValue: String
});
</script>

Using Methods with `<script setup>`

Methods will be specified as consts and available in your template just like they were in the Options API, since methods are no longer considered objects.

Options API :

<template>
  <div>
    <button @click="incrementCounter">Increment</button>
    <p>Counter: {{ counter }}</p>
  </div>
</template>

<script>
export default {
  data() {
    return {
      counter: 0
    };
  },
  methods: {
    incrementCounter() {
      this.counter++;
    }
  }
};
</script>

Composition API :


<template>
<div>
<button @click="incrementCounter()">Increment</button>
<p>Counter: {{ counter }}</p>
</div>
</template>

<script setup>
import { ref } from 'vue';

const counter = ref(0);

const incrementCounter = () => {
counter.value++;
};
</script>

Using Computed with <script setup>

Computed in Composition API operate as reactive data variables. They perform the role of a function, returning calculated values depending on reactive dependencies.

Options API :


<template>
  <div>
    <button @click="incrementCounter">Increment</button>
    <p>Counter: {{ counter }}</p>
    <p>Double Counter: {{ doubleCounter }}</p>
  </div>
</template>

<script>
export default {
  data() {
    return {
      counter: 0
    };
  },
  computed: {
    doubleCounter() {
      return this.counter * 2;
    }
  },
  methods: {
    incrementCounter() {
      this.counter++;
    }
  }
};
</script>

Composition API :


<template>
  <div>
    <button @click="incrementCounter">Increment</button>
    <p>Counter: {{ counter }}</p>
    <p>Double Counter: {{ doubleCounter }}</p>
  </div>
</template>

<script setup>
import { ref, computed } from 'vue';

const counter = ref(0);

const doubleCounter = computed(() => {
  return counter.value * 2;
});
</script>

How to enable HTTPS on XAMPP server.

Ahtisham Hasan Khan — Fri, 11 Aug 2023 12:12:56 +0000

You can checkout this article along with more programming related tips and articles on my personal website:

https://www.iahtisham.com/blog/how-to-enable-https-on-xampp-server

Following are Steps to setup HTTPS for XAMP;

STEP 1 Installing XAMMP

Download and install XAMPP Here

STEP 2 Adding VirtualHost

Navigate to
C:\xampp\apache\conf\extra

Open httpd-vhosts-conf file in Notepad

add a VIRTUALHOST in the end by copying following code

  # Virtual Hosts
<VirtualHost *:443>
    DocumentRoot "C:/xampp/htdocs/"
    ServerName localhost
    SSLEngine on
    SSLCertificateFile "conf/ssl.crt/server.crt" 
    SSLCertificateKeyFile "conf/ssl.key/server.key"
    <Directory "C:/xampp/htdocs/">
        Options All
        AllowOverride All
        Require all granted
    </Directory>
</VirtualHost>

ServerName will be the URL you want to setup HTTPS on; In this case We are using localhost

STEP 3 Creating Private Key

Now We will create Private KEY. Navigate to the directory C:\xampp\apache.

Open makecert.bat. It will ask Pass Phrase and some questions. You can give answers of your choices but the comman name should be the URL for which you are setting up SSL for; in this case its "localhost".

Once done with it you can find the certificates and Key folder in the following directory

C:\xampp\apache\conf

STEP 4 Configure httpd.config

Now, Navigate to C:\xampp\apache\conf. We will be configuring our httpd.config file,

All we need to do is to include following lines in the very bottm of httpd.config file.

 # Virtual hosts
Include conf/extra/httpd-vhosts.conf

STEP 4 Installing Certificate

Now, Open ssl.crt folder and Install the certificate on the local machine by follwing steps;]

open server.crt
click **install certificate""
click local machine, then proceed next
click on **Place all certificates in the following store"
- Browse and Choose Trusted Root Certification Authorities, click OK and NEXT
Click Finish

A message will pop up saying ""the import was successfull""

STEP 5 Configure Chrome

We will enable Allow invalid certificates for resources loaded from localhost. in Chrome.

for this paste the following on URL, it will lead you directly to it.

chrome://flags/#allow-insecure-localhost

Restart your XAMPP services and restart chrome as well.

You should now be able to access your website with HTTPS / SSL enabled.

Support Me!!

If you found this post helpful, consider buying me Coffee ☕. Your support keeps me fueled to create more content!

Public Gist URL: https://gist.github.com/iahtisham/09650933ea013fdc14906f56b191e180

Honorable Mentions:

Transform your daily grind with this dynamic calculator website – your ultimate solution for real-world problems! Explore now for a seamless and efficient experience!. Here are some of my favorites

DEV Community: Ahtisham Hasan Khan

Stop Using NavigationView - Mastering NavigationStack in 2026

The Problem with the Old Way

The New Way: navigation as data

Step 1: Model your routes

Step 2: Own the path in a router

Step 3: Wire the stack to the router

Step 4: Deep links and notifications for free

Mixed value types: NavigationPath

Quick migration checklist

Native iOS vs React Native vs Flutter: Which Should Your App Use?

The short version

Choose native iOS if…

Choose React Native if…

Choose Flutter if…

The hidden cost nobody mentions

My recommendation for most founders

FAQ

What is PPP pricing? Purchasing power parity for app subscriptions

Why exchange rates aren’t enough

How PPP pricing is calculated

Price-level index vs. other signals

Where PPP pricing goes wrong

Key terms

Checklist: before you change App Store prices by country

Before you calculate

Before you schedule

After the change

Where a $4.99 subscription costs the most: App Store countries ranked by price level

The short version

How to read the table

What to do with this

App Store subscription price increases: when subscribers must consent

Option 1: keep existing subscribers on their price

Option 2: apply the increase to existing subscribers

Notice periods

Decreases are different

Practical rules of thumb

How Apple sets your subscription price in 175 countries

Price points

Equalization

Subscription prices don’t follow exchange rates

What equalization doesn’t do

How to update subscription prices with the App Store Connect API

1. Authenticate with a team API key

2. Find the subscription

3. Read current prices

4. Find the right price point

5. Schedule the new price

Gotchas we hit

Mastering Git Checkout: Decoding the Impact of One Simple Command

Understanding the Basics

Undoing Changes Like a Pro

File Undo

Commit Undo

Navigating Detached HEAD State

Tailoring Your Checkout with Paths and Commits

Discarding Changes Across the Board

Conclusion

How to enable HTTPS for WAMP Server.

STEP 1: Download and Install OpenSSL.

STEP 2: Generate Private Key and SSL certficate.

STEP 3: Move your KEY and Certificate.

Step 4: Edit Your httpd.conf File

Step 5: Edit Your httpd-ssl.conf File

Step 6: Restart WampServer

"Vue 3 : Smooth migration from the Options API to the Composition API in Vue 3"

Introduction

Why <script setup> ?

Using Props with <script setup>

Options API :

Composition API :

Using Methods with <script setup>

Options API :

Composition API :

Using Computed with <script setup>

Options API :

Composition API :

How to enable HTTPS on XAMPP server.

You can checkout this article along with more programming related tips and articles on my personal website:

Using Props with `<script setup>`

Using Methods with `<script setup>`