Apps & Responsive Web

We read the reason, fix it, and resubmit. That is inside the quote. Rejections are a normal part of shipping rather than an exception, and we check for likely rejection causes before submitting. What we cannot shorten is the review time itself.

It depends on the features. Sign-in, sharing data across devices, push notifications, and payments all need a server. An app that works entirely on the device needs neither a server nor accounts, which is how our own Sales Kit and Quote Kit are built. No server also means no running cost, so we check whether you actually need one first.

Apps go through store review again, so changes are not instant the way they are on the web. Anything expected to change often can be designed to load from the server instead, which lets you edit it without a review. How far to take that is something we decide together, based on what actually changes and how often.

Price follows the number of screens and features, not the number of platforms. Because it is one codebase, dropping the web version saves little, and adding it later costs nothing extra to build. Fewer screens is what actually lowers the number.

Yes. Both stores require a policy URL. Also, collecting nothing is not the same as no data reaching a third party: an app that fetches map tiles collects nothing yet still leaves a record on that server. A mismatch between your store declaration and your policy is itself grounds for rejection, so we write the policy against what actually leaves the device.