There are a number of app genres that the App Store reviewers decided to be too saturated. Among those are astrology, horoscope, palm-reading, and similar tell-your-future-from-your-biometric apps. If your app is one of those, you can't publish it on the App Stores. You could try publishing it as a Developer ID macOS application – use Catalyst if it's an iOS app. However there are other causes of "Guideline 4.3 Spam" rejection: Publishing similar apps that differs only in content. Publishing white-label apps under your own Developer Account. A competitor's app looks similar to yours. Search the web for "How to Pass App Store Review: Guideline 4.3 Spam" to find out how to diagnose the problem further as well as some potential solutions.

It sounds like your app may have look-and-feel that is similar to a more established competitor. You might want to review competing apps in the same category or targeting the same audience and see whether any strikes resemblance with your app. Notably the ones that has more downloads (or simply been around much longer than yours). For further information, search the web for "Look-Alike Apps are Considered Spam by App Review" – you should find more pointers on how to tackle this issue.

Depends on how you distribute your application. If it's an App Store app, you would need to use iAP for almost all digital services (one notable exception is currency exchange or money transfers, only applicable to licensed financial institutions). If it is accessed from the web browser, no need to use iAP. However privately-distributed custom apps also do not need to go through iAP. That is regardless of the technologies used to develop the app.

The concern is that people with less bandwidth would be more hesitant to download your app. iOS devices would download the device-specific version whereas the Mac App Store would download the entire binary (all architecture slices).

By now you should just get the M1 Mac Mini.

Only public health organizations are able to deploy contact tracing apps to the App Store. You'll need to get the relevant department in your country's government to apply for an Apple Developer account which in turn would be used to upload the app.

This sounds like it’s being triggered by an advertisement library. Some ads have a “mini game” inside of it, which may look like ”3rd party game streaming”. Usually these are banner ads but when tapped shows the mini game in full screen mode. In turn the game somewhat forces the user to interact with it.

How did the legal battle went? That said, exchanging foreign currency is borderline illegal in many countries without a license. Most countries only recognizes one legal tender (its own currency) and thus using any other currency for trade is not legal – unless exempted by the foreign exchange license. Furthermore I was a bit surprised that you didn’t start with a web app for this. It doesn’t appear that the business’ concept depends on any native app functionality (which in turn risking Guideline 4.2 rejection). Moreover you’d be leaving out Android users if you didn’t start with a web app (and grow to native once you have some traction).

Also you can help App Review by providing a pre-filled user profile as their login.

It sounds like that App Review do not have a full understanding of what the app does. Remember that the average review time is five minutes. Therefore you need to provide an overview the breadth of your app that can be deduced within that time. Have you tried adding an "intro" screen which provides such overview? Notably highlighting native iOS functionalities of the app? I've written an article on this if you're interested – google for "How To Pass App Store Review: Guideline 4.2 Design – Minimum functionality" for more information.

Yes, Xcode 11 can have iOS 10 deployment target. There is also a 64-bit iOS 10 simulator available as optional download. If you have a real iPhone 5, Xcode 11 can still connect to it and debug your app as per normal.

Having the same functionality in the app as well as your website is practically asking for Guideline 4.2 rejection. An app would need to have functionalities that can't be done by a website (or web-app) alone. Moreover, not having a website is not the answer. The app would need to have functionalities that are not accessible from within a browser. Some examples include: Siri integration Push notification On-device machine-learning

If you're just want to get started, choose one of the Xcode app templates for the Mac and you're already have an app. More so, iOS and macOS now shares a lot of frameworks such that many iOS apps are just a checkbox away from being a mac app.

I'm not a big fan of adding 3rd party frameworks just to support a coding style (or software architecture). Adding dependencies creates risk – maintenance risk, security vulnerability risk, and maybe license risk. Hence "glue code" framework isn't worth those risks IMO.On the other hand, one can implement VIPER + Clean Architecture just by using iOS' built in frameworks. I've recently made a sample project illustrating this.

In VIPER, the navigation from one top-level view controller to another is done by a "router" component. Hence when using XIB, you need to have the view controllers call the router component to instantiate and show other view controllers. This router component can also be the UISplitViewController's delegate (and maybe the two root navigation controllers of the split view).Have a look at the sequence diagram in this article for an example.OTOH when you're using storyboards, the storyboard "is" kinda the "router".