We have published two iOS apps on the Uzbekistan App Store. Bak shows fuel, gas and EV-charging prices and was released on 16 October 2026. Joy Top — Tashkent food guide was released on 22 October 2026. Both are free. We re-checked the store records on 8 November 2026: for both, the seller is listed as Nodirkhon Nusratkhujaev.
Below is what we wish we had known before the first release. It is not a retelling of Apple's rules: each point links to Apple's document and, where we have one, our own case.
The account: Individual or Organization
By Apple's description, when you enrol as an individual, your legal name "will be displayed as the seller name of your apps on the App Store". An organization must be a legal entity that can enter into contracts with Apple; Apple does not accept "DBAs, fictitious business names, trade names, or branches". It needs a D-U-N-S Number (government entities excepted), a public, working website on a domain associated with the organization, and a work email on that domain. The page does not list the countries where you can enrol, so check that at enrolment.
What follows from it:
- If the storefront should show a company name rather than yours, plan time for the organization account and the D-U-N-S Number. We have not measured how long that takes and do not give a figure.
- For some apps an organization account is not enough: the seller must be the entity that provides the service. Guideline 5.1.1(ix) says apps that provide services in "highly regulated fields" (such as banking and financial services, healthcare, gambling, legal cannabis use, air travel and crypto exchanges), or that require sensitive user information, should be submitted "by a legal entity that provides the services, and not by an individual developer". For a bank or clinic app, that means the bank or clinic itself must be the seller, not the studio that built it. Under 3.1.5(i), virtual-currency wallets must come from developers enrolled as an organization.
- If a studio builds the app for you, ask whose account it will be published under. That decides whose name buyers see and whose account the app lives on. In the regulated fields above, the account must be that of the entity providing the service.
App Review is a loop, not a button
With Bak it was a loop. On 14 October 2026 the app was rejected under 2.1(a), where Apple says it will reject "binaries that crash or exhibit obvious technical problems". On an iPad Air 11" running iPadOS 27.0 the app crashed at launch. The cause was our build: any build on the iOS 27 SDK must adopt the UIScene life cycle (Apple's TN3187), and ours was our first such build. On iOS 26 that is only a warning, so everything worked on our own iPhone. We fixed the build (the build is the app's finished version that we upload to Apple), explained the fix in the notes for the reviewer, and resubmitted on 15 October. The app went live on 16 October.
What we took from it:
- Apple does not test on your phone. Guideline 2.1(a) asks you to test on-device before submitting, and the reviewer may have another iOS version and another device.
- Write the reviewer's notes as if someone will rely on them. Guideline 2.3.1(a) wants changes described "with specificity", and in our experience that is the place to explain a fix; we opened our notes with it.
- By Apple's documentation, submissions "may not be reviewed in the order you submit them", and a platform can have one app-version submission under review at a time. Leave slack in the schedule for a send-back.
Joy Top's first EAS build, on 6 October, showed another trap: if the build profile names no environment, the build gets the placeholders from the code instead of the real addresses. We now open the finished file and search it for the real server address before uploading to Apple.